On 7/22/11 4:01 PM, Robert Bradshaw wrote:
On Fri, Jul 22, 2011 at 8:05 AM, Jason Grout
<jason-s...@creativetrax.com> wrote:
On 7/22/11 3:39 AM, Minh Nguyen wrote:
Hi Andrei,
On Tue, Jul 19, 2011 at 8:35 PM, Andrei<andrei.fo...@gmail.com> wrote:
You probably know that GitHub is extremely popular hosting for
open-source
projects (https://github.com/about). I think it would be very beneficial
for
SAGE to be mirrored to GitHub as well.
You are more than welcome to mirror Sage at GitHub. Also, as Sage uses
Mercurial, it's more logical to use bitbucket.org to mirror Sage as
this involves no hassle regarding conversion from one revision control
system to another.
There's no reason not to have both, other than the work, of course...
I think one big reason to mirror to github has to do with github possibly
having far more users (see
https://github.com/blog/865-github-dominates-the-forges, though they don't
compare to bitbucket there, so of course the conclusion about bitbucket is
unwarranted)
It's a bit unclear what the advantages of having a (read-only) mirror
there are. What's your goal?
Now if pull requests could be automatically turned into tickets,
that'd be cool :).
That would be very cool, and probably very doable given the github API.
If we had something like that, I'd experiment with doing my
development on github (I decided a few months ago that I like git better
than mercurial at this stage of their development...)
I could imagine a trac plugin which checks for new pull requests or new
comments/commits on old pull requests. When it detects a change, it
updates trac. On the other hand, when a comment is posted to trac, it
is posted to the github issue.
This seems like one direction (trac->github): https://gist.github.com/497554
Thanks,
Jason
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
