Pinax Video and Move to GitHub
The audio isn't great (they didn't seem to be directly recording the mic I was holding) and it got cut short, but for what it's worth, here's the video of my talk on Pinax at PyCon 2009:
Following the conference proper, we had a great sprint that got us within a stone's throw of a 0.7 beta release. One of the first things we did was move from svn at Google Code Project Hosting to git at GitHub. The new home of the Pinax source code is now:
http://github.com/pinax/pinax/
We also moved our wiki and task tracking off Google Code Project Hosting to our own, Pinax-based system:
Enjoy!
Comments (4)
James Tauber on April 8, 2009:
Nicola, you should probably disclose your conflict of interest before commenting on competitors :-)
Although I didn't have strong opinions about DVCSs (being a newbie), the other core developers were all overwhelmingly in favour of Git. We made the decision long before Python made their decision to go with Mercurial.
Note there is nothing to stop individual app developers using other DVCSs. In fact, we use apps that are hosted on Launchpad.
Finally, using a third-party issue tracker was never an option. We planned from day one to write our own in Pinax.
Nicola Larosa on April 8, 2009:
> Nicola, you should probably disclose your conflict of
> interest before commenting on competitors :-)
You're right, I actually was about to add a disclaimer that I work for Canonical. In the end I decided not to, because I'm not on the Bazaar nor Launchpad teams, and because I actually still prefer Mercurial to Bazaar (sorry, dear colleagues :-) ).
> Although I didn't have strong opinions about DVCSs (being a newbie),
> the other core developers were all overwhelmingly in favour of Git.
> We made the decision long before Python made their decision
> to go with Mercurial.
Well, there's not much I can say about it. Obviously, those who put in the work call the shots.
> Note there is nothing to stop individual
> app developers using other DVCSs.
I don't really know what's the integration story between git and Mercurial or Bazaar. I'll have to discover it soon.
> In fact, we use apps that are hosted on Launchpad.
I also don't yet know how you integrate them in Pinax.
> Finally, using a third-party issue tracker was never an option.
> We planned from day one to write our own in Pinax.
I'm not sure how that is relevant to this discussion, but ok.
Anonymous on April 9, 2009:
Is DVCS an acronym for Distributed Viagra Control System?
Last Modified: April 7, 2009
Author: James Tauber
Nicola Larosa on April 8, 2009:
The move to GitHub is so unfortunate, James.
While Python moves to Mercurial, and there's such great infrastructure available as Bazaar-based Launchpad, you force the git mess on developers. Bah.