[Zope-Coders] How to get going :-)

[Chris Withers]

>   1. Write a proposal for the change in the "approved" location
>       (the dogbowl for CMF, dev.zope.org for Zope).

Where's the appropriate place on the dogbowl?

>       Solicit feedback
>       on the change from the appropriate mailing list.

In the FS ZSQL case, that's been done already and it went down well.
Combined with the fact that we've heavily road tested the code on a big
consulting gig here, I'm pretty sure it's a well defined, good, small lump
that can be easily integrated :-)

>       Small changes
>       (trivial bugfixes) don't require proposals, but should have
>       corresponding tracker / collector issues.

Man, now I can submit, handle and commit the changes nessesary for CMF
bugs... cooool :-))

>       $ cvs tag chrisw-FSSQLMethods-base  # remember our start point
>       $ cvs tag -b chrisw-FSSQLMethods-branch \
>         -r chrisw-FSSQLMethods-base       # make the branch from it

Why the two step process? I guess 'cos once you commit to a branch, you
can't get back to where the branch started?

>       $ cp /home/chrisw/test_FSSQLMethod.py tests

What sort of tests should be aimed for with community checkins?

>       $ gvim tests/test_all.py            # add the test

gvim?

>   4. Ensure that all unit tests run against the sandbox::
>       $ cd ../Instance
>       $ ./zctl.py test Products/CMFCore/test_all.py
>       $ ./zctl.py test Products/CMFDefault/test_all.py
>       ...etc

where's zctl.py nowdays? does it come with documentation?
Is the process for running the Zope tests the same or should I use
testrunner.py?

>   6. Lobby for inclusion in the head (bugfixes and new features)

Ah, okay, so community contributors should never merge to the head? Who
should do that?

>(malcontents@zope.com in the case of the CMF)

Like it ;-)

>       o URLs to the checked-in versions, using http://cvs.zope.org.

As in the ViewCVS urls? Do you want them to the content-type=plain/text
version or ?

>       o URLs of the rationale for the changes.

...can they be in mailing list archives?

>       o Rationale policy was followed.

What's the rationale policy for the CMF? Is it different for Zope or any of
the other modules?

>       o The patch is minimal for the purpose (no gratuitous diffs!)

One .py and a couple lines in __init__.py okay? ;-)

cheers,

Chris