[Zope3-dev] Advice on CVS corrections

[Steve Alexander]

Dave Harris wrote:
> I recently posted information about necessary corrections to Zope3 files. I 
> received two acknowledgements on the first post (fixing zodb/zeo in 
> zeo/schema.xml) that the change was warranted.
> 
> I looked at Zope3 CVS today and I see that neither change has been applied.
> 
> At the risk of appearing foolish, was I supposed to checkin the changes? I 
> don't currently have permission to do so - should I seek permission?

Yes.

http://dev.zope.org/CVS/FrontPage

http://dev.zope.org/CVS/ContributorIntroduction

Basically, get an account on the zope.org website, print out the 
contributors' agreement, sign it, send it to Zope Corporation. Then, 
upload your ssh key.

The most significant part of the contributors' agreement is that 
contributors agree to check in only their own work, and they agree that 
Zope Corporation jointly holds copyright with the contributor for the 
work they check in.


> I'm relatively new to Python so I doubt I can contribute much to the heavy 
> lifting (I do have over 20 years of UNIX/C experience though). I figured I 
> would work around the edges and solve the bugs that I find (rather than just 
> post bug reports.) Is that presumptuous? As a newcomer, should I simply 
> stick a pin in the map and let the professionals handle the details?

Please do contribute as much as you want to. Feel free to ask for help 
or advice or guidance on this mailing list.

The main requirement for checking in code is that python code needs to 
have unit tests, and all unit and functional tests must pass before 
changes are checked in.

There's a system of writing proposals before making larger changes.

http://dev.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/FrontPage/Zope3Proposals

Anyone can make a proposal.

--
Steve Alexander