[Zope3-dev] Advice on CVS corrections

Dave HARRIS dpharris76 at msn.com
Thu Jan 8 12:28:11 EST 2004


Thanks for the information and the invitation to post.

I'm currently slogging through 3 'serious' UI issues and it's tough 
sledding. I'm intentionally working at the boundary condition of an empty 
Data.fs, so I'm probably seeing things long-time users have never observed.

Thanks again,
Dave Harris

>From: Steve Alexander <steve at z3u.com>
>To: Dave Harris <dpharris76 at msn.com>
>CC: zope3-dev at zope.org
>Subject: Re: [Zope3-dev] Advice on CVS corrections
>Date: Thu, 08 Jan 2004 18:58:33 +0200
>
>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
>

_________________________________________________________________
Worried about inbox overload? Get MSN Extra Storage now!  
http://join.msn.com/?PAGE=features/es




More information about the Zope3-dev mailing list