Hello devs and list lurkers
As a result of many requests and previous discussion we're about to migrate your privately hosted Subversion repository to github. The trac platform will remain for tickets, planning and documentation but with the move to github we hope to make it easier to contribute.
I meanwhile have put together a script to handle the migration and the switch will take place on next Friday, May 4th 2012. Those having write permissions to our SVN are kindly requested to commit their stuff until 12:00h CET on that day. Afterwards we'll start the migration. The SVN repository will remain active for a while but you won't see any updates on it.
You'll be informed once the github repository is ready and we'll also document it on our website and the trac wiki.
Have a good one, Thomas
On 2012-05-02 9:20, Thomas Bruederli wrote:
Hello devs and list lurkers
As a result of many requests and previous discussion we're about to migrate your privately hosted Subversion repository to github. The trac platform will remain for tickets, planning and documentation but with the move to github we hope to make it easier to contribute.
I meanwhile have put together a script to handle the migration and the switch will take place on next Friday, May 4th 2012. Those having write permissions to our SVN are kindly requested to commit their stuff until 12:00h CET on that day. Afterwards we'll start the migration. The SVN repository will remain active for a while but you won't see any updates on it.
You'll be informed once the github repository is ready and we'll also document it on our website and the trac wiki.
Have a good one,
With the move to github;
allow commit ids in tickets and their comments to be resolved to the source code, and allow browsing?
is a new list name needed?
Kind regards,
Jeroen van Meeuwen
On Wed, May 2, 2012 at 10:43 AM, Jeroen van Meeuwen (Kolab Systems) vanmeeuwen@kolabsys.com wrote:
On 2012-05-02 9:20, Thomas Bruederli wrote:
Hello devs and list lurkers
As a result of many requests and previous discussion we're about to migrate your privately hosted Subversion repository to github. The trac platform will remain for tickets, planning and documentation but with the move to github we hope to make it easier to contribute.
[...]
With the move to github;
- will the Trac system be set up as a mirror for said github, as to allow
commit ids in tickets and their comments to be resolved to the source code, and allow browsing?
Yes, that will still be possible. There are trac plugins available enabling that. We'll also map the github repository in the source section of trac.
- will commit messages still be making it onto svn@lists.roundcube.net, is a
new list name needed?
Once I figured out how to send push notifications from github we'll send them to the svn list, I guess. After doing some research, github doesn't provide such a feature and we'd either have to set up a clone repository somewhere which will then send the messages or use the post-receive hooks github triggers. Unfortunately the latter option doesn't contain diffs...
~Thomas
Awesome! Does this mean you'll accept patches and stuff through pull requests? If so, maybe you should put up a small FAQ about the use of github for roundcube developers. I use github on another project, and some stuff just keeps being asked, like "how do i remove all my local patches and sync with the remote repository'. Im sure there are some knowledgable github ninjas here that could help out.
Github takes a whole new way of thinking with regards to development, it's totally unlike subversion. It can confuse people quite a bit at the beginning :)
Cor
On Thu, May 3, 2012 at 10:43 AM, Cor Bosman cor@xs4all.nl wrote:
Awesome! Does this mean you'll accept patches and stuff through pull requests?
That was actually one of the reasons why we'd choose github over a privately hosted git repository.
If so, maybe you should put up a small FAQ about the use of github for roundcube developers. I use github on another project, and some stuff just keeps being asked, like "how do i remove all my local patches and sync with the remote repository'. Im sure there are some knowledgable github ninjas here that could help out.
After the switch we definitely have to update/add some documentation. Any help on this is much appreciated since I'm actually a github newbie myself.
~Thomas
On 2012-05-03 10:41, Thomas Bruederli wrote:
On Wed, May 2, 2012 at 10:43 AM, Jeroen van Meeuwen (Kolab Systems) vanmeeuwen@kolabsys.com wrote:
On 2012-05-02 9:20, Thomas Bruederli wrote:
Hello devs and list lurkers
As a result of many requests and previous discussion we're about to migrate your privately hosted Subversion repository to github. The trac platform will remain for tickets, planning and documentation but with the move to github we hope to make it easier to contribute.
[...]
With the move to github;
- will the Trac system be set up as a mirror for said github, as to
allow commit ids in tickets and their comments to be resolved to the source code, and allow browsing?
Yes, that will still be possible. There are trac plugins available enabling that. We'll also map the github repository in the source section of trac.
- will commit messages still be making it onto
svn@lists.roundcube.net, is a new list name needed?
Once I figured out how to send push notifications from github we'll send them to the svn list, I guess. After doing some research, github doesn't provide such a feature and we'd either have to set up a clone repository somewhere which will then send the messages or use the post-receive hooks github triggers. Unfortunately the latter option doesn't contain diffs...
~Thomas _______________________________________________ Roundcube Development discussion mailing list dev@lists.roundcube.net http://lists.roundcube.net/mailman/listinfo/dev
Actually there is an option to send notifications.
If you are in the admin menu go to "service hooks" and then select the "email" option.
Cheers.
Richard Pijnenburg
On Thu, May 3, 2012 at 11:30 AM, Richard Pijnenburg richard@softwaredev.nl wrote:
- will commit messages still be making it onto svn@lists.roundcube.net,
is a new list name needed?
Once I figured out how to send push notifications from github we'll send them to the svn list, I guess. After doing some research, github doesn't provide such a feature and we'd either have to set up a clone repository somewhere which will then send the messages or use the post-receive hooks github triggers. Unfortunately the latter option doesn't contain diffs...
Actually there is an option to send notifications.
If you are in the admin menu go to "service hooks" and then select the "email" option.
Oops, I kind of missed that. Thanks to Google's relevance ranking I just found dozens of hacks to do the obvious...
Thanks a lot for the hint!
~Thomas