Hi,
I have create a Dynare repository on GitHub:
https://github.com/DynareTeam/dynare
As you may know, GitHub has become the most popular platform for collaborative development of free software. It is user friendly and makes contributions very easy via a “Pull request” mechanism. It is also possible to add comments to specific commits (before or after they are merged), so reviewing is made easy.
Do you think it would be a good decision to decide that the main Dynare repository is the GitHub one?
On the upside, I think this could attract new contributors by lowering the barrier to entry. On the downside, it means that we lose control of our hosting architecture (though we would maintain a mirror on Kirikou at the address where the main repository currently is).
We could also move the Trac tickets to the GitHub “issues” system. There is also a Wiki on GitHub, but I think we should rather keep our existing wiki.
Stéphane and Michel: I have already granted you push/pull access to the repository, using your respective GitHub accounts (stepan-a, MichelJuillard).
Waiting for your feedback,
Hi all,
I think that this move definitely worth a try. If possible we should also use GitHub issues instead of trac. I imagine that the migration of the wiki would be much more pain. I think they use rst as a markup language and that it is possible to have a local copy of the wiki (with git)... This would be very useful.
Best, Stéphane.
Sébastien Villemot sebastien@dynare.org writes:
Hi,
I have create a Dynare repository on GitHub:
https://github.com/DynareTeam/dynare
As you may know, GitHub has become the most popular platform for collaborative development of free software. It is user friendly and makes contributions very easy via a “Pull request” mechanism. It is also possible to add comments to specific commits (before or after they are merged), so reviewing is made easy.
Do you think it would be a good decision to decide that the main Dynare repository is the GitHub one?
On the upside, I think this could attract new contributors by lowering the barrier to entry. On the downside, it means that we lose control of our hosting architecture (though we would maintain a mirror on Kirikou at the address where the main repository currently is).
We could also move the Trac tickets to the GitHub “issues” system. There is also a Wiki on GitHub, but I think we should rather keep our existing wiki.
Stéphane and Michel: I have already granted you push/pull access to the repository, using your respective GitHub accounts (stepan-a, MichelJuillard).
Waiting for your feedback,
I think this is the right move. I have been using it myself for a while now.
Best, Junior
On Thu, Feb 14, 2013 at 4:52 PM, Stéphane Adjemian < stephane.adjemian@univ-lemans.fr> wrote:
Hi all,
I think that this move definitely worth a try. If possible we should also use GitHub issues instead of trac. I imagine that the migration of the wiki would be much more pain. I think they use rst as a markup language and that it is possible to have a local copy of the wiki (with git)... This would be very useful.
Best, Stéphane.
Sébastien Villemot sebastien@dynare.org writes:
Hi,
I have create a Dynare repository on GitHub:
https://github.com/DynareTeam/dynare
As you may know, GitHub has become the most popular platform for collaborative development of free software. It is user friendly and makes contributions very easy via a “Pull request” mechanism. It is also possible to add comments to specific commits (before or after they are merged), so reviewing is made easy.
Do you think it would be a good decision to decide that the main Dynare repository is the GitHub one?
On the upside, I think this could attract new contributors by lowering the barrier to entry. On the downside, it means that we lose control of our hosting architecture (though we would maintain a mirror on Kirikou at the address where the main repository currently is).
We could also move the Trac tickets to the GitHub “issues” system. There is also a Wiki on GitHub, but I think we should rather keep our existing wiki.
Stéphane and Michel: I have already granted you push/pull access to the repository, using your respective GitHub accounts (stepan-a, MichelJuillard).
Waiting for your feedback,
-- Stéphane Adjemian Université du Maine, Gains Tel(Gains): +33(0)2 43 83 31 35 Tel(Cepremap): +33(0)1 40 77 84 16
Dev mailing list Dev@dynare.org https://www.dynare.org/cgi-bin/mailman/listinfo/dev
Hi,
Given the consensus around this decision, I have now switched our main repository to the one on GitHub. Pushes should now be made there. Email and IRC commit notifications will now be sent by GitHub.
Once you have created your account on GitHub, don't forget to "Star" the repository, so that it appears on your favourite list and so that the repository appears to be popular.
Concerning tickets/issues, I think we should open new ones on GitHub. You will probably want to click the "Watch" button on GitHub, in order to receive notifications about issues. I will gradually migrate older tickets from Trac to GitHub.
The repository on Kirikou will continue to live (in read-only mode), and will be automatically synchronized once a day.
For the time being, only Michel, Stéphane, Houtan and myself have push access to the GitHub repository (as it used to be on Kirikou). For the other people, the preferred mechanism to contribute commits to Dynare is now to use "Pull requests" on GitHub, after having created your own "Fork"; there is documentation on github.com on how to do that, but don't hesitate to email me if you have problems. Also, the old mechanism (with a personal space on Kirikou) will continue to work for now, so that you have the necessary time to adapt for the change.
Once the dust settles, I will send a message on our larger mailing list and forums to announce the change, and to encourage people to submit pull requests if they have something to contribute.
I have now migrated the trac tickets to github issues.
I have been able to move all tickets (including closed ones), except the first ten (because I had already created 10 tickets in github, and I wanted to keep the numbering unchanged).
Unfortunately, the identities of submitters and commentators has not been kept during the migration, so that all tickets and all comments appear to have been created by me… This is annoying, because some conversations will be less clear, but I don't think it's a too big issue.
I have disconnected the old trac site, so please now use github for tickets. Don't forget to subscribe to notifications if you want to be kept informed.
Sorry for the belated response: this move looks fine to me. best Marco
On 2/13/2013 4:08 PM, Sébastien Villemot wrote:
Hi,
I have create a Dynare repository on GitHub:
https://github.com/DynareTeam/dynare
As you may know, GitHub has become the most popular platform for collaborative development of free software. It is user friendly and makes contributions very easy via a "Pull request" mechanism. It is also possible to add comments to specific commits (before or after they are merged), so reviewing is made easy.
Do you think it would be a good decision to decide that the main Dynare repository is the GitHub one?
On the upside, I think this could attract new contributors by lowering the barrier to entry. On the downside, it means that we lose control of our hosting architecture (though we would maintain a mirror on Kirikou at the address where the main repository currently is).
We could also move the Trac tickets to the GitHub "issues" system. There is also a Wiki on GitHub, but I think we should rather keep our existing wiki.
Stéphane and Michel: I have already granted you push/pull access to the repository, using your respective GitHub accounts (stepan-a, MichelJuillard).
Waiting for your feedback,
Dev mailing list Dev@dynare.org https://www.dynare.org/cgi-bin/mailman/listinfo/dev
-
Junior Maih -
Marco Ratto -
stephane.adjemian＠univ-lemans.fr -
Sébastien Villemot