On 3/4/08, Jesus Cea <jcea@argo.es> wrote:

That said, it is my aim to keep bsddb in stdlib, providing a stable and
featureful module. I think keeping bsddb development inside python svn
is not appropiate. Currently (I could change idea), my approach will be
keeping pybssdb as a separate project and sync with python SVN from time
to time. Mainly to take advantage of buildbot architecture and, of
course, to be able to release python with current bindings.

Since I have no python commit access, this seems a sensible approach.
And I could do frequent pybssdb releases (let say, every couple of
months) without waiting for a full python release (current approach).

That makes sense. I also agree with Neal's comments, merging back into python in reasonable sized chunks is good. Don't worry about commit access for now, I'll do the initial pybsddb back into python trunk merges until we get that setup. I've merged the python trunk changes that others have made back into the pybsddb tree.

PS: I have tried to sign the Python Contributor Agreement, but I am not
sure about current pybsddb license terms. Help welcomed.

The current bsddb license first and foremost is the Python license. If I read the comments in the _bsddb file correctly I believe you could also call it a MIT style license. Keep things simple, just write "Python License" on your contributor form and submit it.

-gps