I think this is the right move. I have been using it myself for a while now.
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.
Stéphane Adjemian
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,
--
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