News for hackers. Stuff that matters.
Re:Guido van Rossum: Thoughts about Python Future by jerome_etienne on Tuesday July 27, 2010 @08:38AM (#1550989)
About Commit privileges, using distributed version control system would help reduce the fear of commit.
Re:Guido van Rossum: Thoughts about Python Future by jcsalterego on Tuesday July 27, 2010 @08:52AM (#1551014)
Speaking of DVCS, Mercurial was chosen at PyCon 2009, although the implementation timeline appears TBD.

http://www.python.org/dev/peps/pep-0374/#decision

http://www.python.org/dev/peps/pep-0385/

http://mail.python.org/pipermail/python-dev/2009-March/08793...

Re:Guido van Rossum: Thoughts about Python Future by JoachimSchipper on Tuesday July 27, 2010 @08:45AM (#1551000)
Why? The "main" git repository is as important as the "main" Subversion repository. git is easier to work with for distributed development, but whatever is branded Python still shouldn't suck.
Re:Guido van Rossum: Thoughts about Python Future by cdavid on Tuesday July 27, 2010 @08:49AM (#1551009)
With a DVCS, you don't need commit privileges to benefit from all the advantages of using a VCS in the first place. So even if you keep the exact same list of comiters, "second-class" contributors can develop things much more easily.

It also means that you can "screw-up" until you push (and as such can put things for review, etc... more easily).

Re:Guido van Rossum: Thoughts about Python Future by JoachimSchipper on Tuesday July 27, 2010 @09:19AM (#1551075)
It's a bit more convenient, but svn plus private repositories, or SVK, or git-svn work equally well.

Again, I'm not saying git isn't more convenient - it is; the point is that even git-using projects end up with a "main repository" to which only a small number of people can commit. Increasing the number of people with commit rights can be useful even when using git.

Re:Guido van Rossum: Thoughts about Python Future by mgrouchy on Tuesday July 27, 2010 @08:59AM (#1551032)
Also with a model similar to Github where you fork the repository and submit pull requests, Python developers could cherrypick the best commits from anyone who is interested in contributing.

This probably doesn't scale, but you could certainly do it for just the predetermined contributors.

Re:Guido van Rossum: Thoughts about Python Future by tkahn6 on Tuesday July 27, 2010 @11:10AM (#1551449)
You should check out Linus' tech talk at Google about Git. Not only is Linus a really good speaker, he explains how a DVCS like git changes the workflow when it comes to managing the 'main' repository.

Spoiler: He has a 'circle of trust'. He pulls and merges commits from people he thinks are really smart and those people in turn pull and merge from people they think are smart.

http://www.youtube.com/watch?v=4XpnKHJAok8

Re:Guido van Rossum: Thoughts about Python Future by callahad on Tuesday July 27, 2010 @08:49AM (#1551010)
s/commit privileges/push privileges/g

From what I understand, a lot of the uncertainty isn't about committing, per se, but rather about changing the canonical repository.