github versus sympy.org repo confusion
Brian Granger
I am getting back to sympy now that finals are done and I noticed that
the repo situation with sympy is a bit confusing:
* There is now a sympy/sympy github repo, that looks very attractive
to fork and use...
* But it is not in sync with git.sympy.org.
What is the plan for the github repo? Should we get rid of
git.sympy.org entirely? Should be get rid of the github repo? Is
there was to keep them in sync? Which do we recommend to new devs to
clone?
Cheers,
Brian
Christian Muise
--
You received this message because you are subscribed to the Google Groups "sympy" group.
To post to this group, send email to sy...@googlegroups.com.
To unsubscribe from this group, send email to sympy+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/sympy?hl=en.
Aaron S. Meurer
You should clone from git.sympy.org and fork from github, as Christian said. We should probably setup the build bot to push changes up to github. For now, Ondrej gave write access to all the sympy developers who had a github account, so you should be able to just add sympy as a remote repository and do "git push sympy" to update it.
I think the idea behind the github sympy was to give people a repository to fork that would put them in the network, but wouldn't give them the junk branches that would come from forking, say, my repository instead.
Aaron Meurer
Brian Granger
> github's forking feature), and pull changes from the git.sympy.org repo
> (with a remote repository set up). Forking the sympy/sympy puts you in a
> github network that lets everyone track what's going on (to some extent).
I agree that the github is very nice and I use it for most of my
projects. But the extra step
of having to pull from git.sympy.org is simply confusing. why not
simply use github for everything?
Or, what is the advantage of having two main repos like this?
Cheers,
Brian
--
Brian E. Granger, Ph.D.
Assistant Professor of Physics
Cal Poly State University, San Luis Obispo
bgra...@calpoly.edu
elli...@gmail.com
Aaron S. Meurer
Aaron Meurer
Brian Granger
>
> On Jun 14, 2010, at 3:24 PM, Brian Granger wrote:
>
>> Hi,
>>
>> I am getting back to sympy now that finals are done and I noticed that
>> the repo situation with sympy is a bit confusing:
>>
>> * There is now a sympy/sympy github repo, that looks very attractive
>> to fork and use...
>> * But it is not in sync with git.sympy.org.
>>
>> What is the plan for the github repo? Should we get rid of
>> git.sympy.org entirely? Should be get rid of the github repo? Is
>> there was to keep them in sync? Which do we recommend to new devs to
>> clone?
> You should clone from git.sympy.org and fork from github, as Christian said. We should probably setup the build bot to push changes up to github. For now, Ondrej gave write access to all the sympy developers who had a github account, so you should be able to just add sympy as a remote repository and do "git push sympy" to update it.
While I am not a git master yet, I have been using it for a while now
on most of my projects. While it is my favorite DVCS, it is fairly
complex and anything we can do to simplify using git for new devs is
important. Having 2 main repos like this is simply confusing -
especially when they fall out of sync.
> I think the idea behind the github sympy was to give people a repository to fork that would put them in the network, but wouldn't give them the junk branches that would come from forking, say, my repository instead.
But don't we get all of these things even if we delete git.sympy.org?
I guess I don't see what the advantage of keeping git.sympy.org is...
Cheers,
Brian
> Aaron Meurer
>>
>> Cheers,
>>
>> Brian
>>
>> --
>> You received this message because you are subscribed to the Google Groups "sympy" group.
>> To post to this group, send email to sy...@googlegroups.com.
>> To unsubscribe from this group, send email to sympy+un...@googlegroups.com.
>> For more options, visit this group at http://groups.google.com/group/sympy?hl=en.
>>
>
> --
> You received this message because you are subscribed to the Google Groups "sympy" group.
> To post to this group, send email to sy...@googlegroups.com.
> To unsubscribe from this group, send email to sympy+un...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/sympy?hl=en.
>
>
--
Brian Granger
> git.sympy.org is on Ondrej's server, so he has it setup so that a buildbot runs the tests whenever someone pushes. Are such hooks possible for github?
Ok, that makes sense. We should see if github has such hooks...or
minimally we should have the gibhub repo automatically synched when
someone pushes.
Cheers,
Brian
Ondrej Certik
> On Mon, Jun 14, 2010 at 7:15 PM, Aaron S. Meurer <asme...@gmail.com> wrote:
>> git.sympy.org is on Ondrej's server, so he has it setup so that a buildbot runs the tests whenever someone pushes. Are such hooks possible for github?
>
> Ok, that makes sense. We should see if github has such hooks...or
> minimally we should have the gibhub repo automatically synched when
> someone pushes.
I can give root access to anyone on my server, if someone would like
to fix/improve it.
For example one can automatically push changes to the github repo somehow.
Ondrej
Vinzent Steinberg
> On Mon, Jun 14, 2010 at 7:18 PM, Brian Granger <elliso...@gmail.com> wrote:
> >> git.sympy.org is on Ondrej's server, so he has it setup so that a buildbot runs the tests whenever someone pushes. Are such hooks possible for github?
>
> > Ok, that makes sense. We should see if github has such hooks...or
> > minimally we should have the gibhub repo automatically synched when
> > someone pushes.
>
> I can give root access to anyone on my server, if someone would like
> to fix/improve it.
>
> For example one can automatically push changes to the github repo somehow.
And we should update our developing information (clone git.sympy.org,
use github sympy to fork for your github account).
Voilà an issue for this: http://code.google.com/p/sympy/issues/detail?id=1959
I like that our main repo is independent of github.
Vinzent