Posted on June 30th, 2008 by Kevin Dangoor
The Michigan Python Users Group (MichiPUG) monthly meeting is coming up this Thursday, July 3rd at 7PM. This month, I’ll be speaking about the Zope Object Database (ZODB). Unlike last month’s meeting, where I led us in a random experiment with Google App Engine, I actually have some experience with the ZODB.
I’ll be demonstrating use of the ZODB and will talk about concurrency, replication, packing, etc. If you’re not familiar with the ZODB (and you’re somewhere near Ann Arbor!), this is a useful topic to get to know, because the ZODB is great for a variety of situations.
Update (May 13, 2009): You can see my examples from this talk.
Posted on June 26th, 2008 by
Posted on June 24th, 2008 by delicious
Posted on June 23rd, 2008 by
Posted on June 23rd, 2008 by Kevin Dangoor
Posted on June 23rd, 2008 by delicious
Posted on June 14th, 2008 by delicious
Posted on June 12th, 2008 by
Posted on June 11th, 2008 by Kevin Dangoor
Anyone who runs a significant open source project should read this, especially if you don’t currently require your contributors to send in any kind of agreement:
So why have it? Why create the barrier to entry for newcomers who just want to pitch in? I have great sympathy for the impatient potential contributor huffing “why do I need to sign this, anyway?”, so this blog post is an effort to boil it down.
[From “Why Do I need To Sign This?”]
I’ve spoken with Alex a couple of times about open source intellectual property, and he’s definitely given this a lot of thought. For a project the size of Dojo, involving many very large contributors, having something like Dojo’s CLA seems critical for keeping the IP clean.
With TurboGears, from the beginning, I’ve required people to send in a simple contributor agreement and this sums up why: “One of the best aspects of the CLA process is that it gets people who are contributing to think about what it means to contribute.”. Significant open source projects that people depend on need to have contributors that are serious about maintaining the project’s quality and the project’s IP. Making people aware of this responsibility from the get-go is a big positive.
I’m posting this in hopes that more of my friends in open source software will keep these things in mind as their projects grow and the outside code contributions increase.
Posted on June 11th, 2008 by delicious