On Thu, Apr 29, 2010 at 1:32 PM, Ondrej Certik <ond...@certik.cz> wrote:

> Hi,
>
> I just found out this:
>
> http://github.com/certik/sympy/network
>
> it nicely shows patches from other people, one can nicely see which
> branches are not yet merged in, as well as to see some patch
> description by pointing the mouse to some dot.
>

There is also the fork queue, which you can only view if you are the owner
or a collaborator on a project.  It shows you unmerged changes from your
forks, and allows you to easily cherry-pick or ignore changesets into a
branch of your choice.  And, of course, pull requests, although this project
is close-knit enough that you probably have no need of it.

If you were not aware, you can also leave comments on commits (on specific
lines, even), which assists the code review process.

Might I recommend an account for sympy (named sympy, naturally enough) that
has one repository that is a direct mirror of the canonical repo on
sympy.org?  That way, we have a nice place to go to create forks (that
doesn't have developer's personal branches and whatnot), and if you feel
like using the networky features of github, you can pull into that repo and
push straight back into the canonical one.

GitHub was built for collaboration, and the tools there really help if you
take advantage of them.

BTW, the Patches Tutorial[0] is quite thorough (good job!), although there
are still quite a few hg-isms floating around in there (hey - I can fix
that!).  I'd suggest providing a link to it in the README, perhaps?  I've
been noticing more and more projects asking contributors to make topic
branches[1] when they fork, and I think it really helps keep things cleaner
and simpler for whoever has to look over the code and approve it.

Whew - sorry if any of this goes against what you've already got working (or
you're doing it already); I haven't really been paying much attention to the
sympy development process.

[0]: http://docs.sympy.org/sympy-patches-tutorial.html
[1]: http://progit.org/book/ch3-4.html

-- 
James Pearson
--
The best way to predict the future is to invent it.
 - Alan Kay

-- 
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.

Reply via email to