Hello, I've reviewed the introduction to the fishbowl process and its description of creating a project proposal wiki document and such, and the full process a project should take. However, I have 2 very small but useful additions to Zope I wish to make. Both additions are already available for download on zope.org - and have been tested extensively. However, the larger of the two changes is perhaps 80 lines of code. It seems cumbersome, to me at least, to go through this whole process of "Inception, Elaboration, Construction, and Transition" for small code snippets which are already created and tested... So, my question is, could a side-line process be created for the integration of already existent, tested, and somewhat small, code changes? My fear, which I have already seen come to life through use of the collector, is that without such a lightwieght process for occasional small changes - many already existent (and many future) small changes to Zope will be bypassed rather then integrated due to the time needed to go through all stages of the process. I don't have all the answers, and I know this isn't a common problem, but it is something I know I'm experiencing right now at this second... Please keep in mind that I am not trying to be critical, nor am I attempting to change the fishbowl process for normal projects - I only wish a parallel process to exist for very small changes, so that the changes are not forgotten or passed up. ~ Jonathan M. Franz ~ Senior Developer/Technical Leader ~ ~ SW-Dev Division, Springdale, Ohio Office ~ 513.618.2248 ~ ~ OneNet Communications (A USNet/MDM Company) www.one.net ~

...

...

Message: 1 From: Brian Lloyd <Brian@digicool.com> To: "'zope-announce@zope.org'" <zope-announce@zope.org>, "'zope@zope.org'" <zope@zope.org>, "'zope-dev@zope.org'" <zope-dev@zope.org> Subject: [Zope-dev] Announcing dev.zope.org Date: Fri, 14 Jul 2000 16:36:28 -0400

Hello all, For some time now, it has been a goal of ours to open up the Zope development process. Some of you may have heard me promise this at the Zope track back in January. Well, it took a little longer than I had hoped it would, but I'm happy to announce an important step in making that a reality: http://dev.zope.org. dev.zope.org is the place for discovering, initiating, and contributing to work on the core Zope platform and related Zope technologies. You can think of it as the rough equivalent of what Mozilla.org is to Mozilla. Why has it taken so long? Because there is much more to "opening the development process" than simply doling out CVS access. Evolving a relatively large and complex piece of software like Zope is a non-trivial task, and doing it in a highly distributed environment is harder still. The dev.zope.org site will provide the background materials and tools to ensure that work on Zope is consistent in organization and execution. It will also help those new to Zope development to come up to speed and get involved quickly. There is still plenty to do be done on the site, but it is done enough to start using it so I want to start learning by doing. If you have questions or comments on the dev site, please send them to me at brian@digicool.com and CC the zope-dev list (which is where I expect traffic related to dev.zope.org should go in the near term). Brian Lloyd brian@digicool.com Software Engineer 540.371.6909 Digital Creations http://www.digicool.com <<<