I think the current suggested form is to fork the sympy/sympy (with 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).
Cheers On Mon, Jun 14, 2010 at 5:24 PM, Brian Granger <elliso...@gmail.com> 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? > > 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+unsubscr...@googlegroups.com <sympy%2bunsubscr...@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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sympy?hl=en.
