As several people have pointed out, the traffic on the Zope mailing list is too heavy for comfort. We propose dealing with this by splitting off a separate list, zope-dev@zope.org, for handling developer-specific issues, leaving the current Zope@zope.org list for user oriented issues. To clarify, here are some examples of the way i see the division of topics: zope@zope.org zope-dev@zope.org ------------- ----------------- installation and operation dtml coding questions and hints content management using the programmer APIs desired user-level features new and existing architecture design business decisions contributed widgets w.r.t. open source public relations in general These are off the top of my head - and i'm relatively new to the community, so i'm quite open to suggestions about what belongs where. Overall question is, does the split make sense in principle? Please speak up particularly if you have objections. Barring substantial objections, i hope to institute the new list by the end of the week. Ken Manheimer klm@digicool.com
Ken Manheimer wrote: [snip]
zope@zope.org zope-dev@zope.org ------------- ----------------- installation and operation dtml coding questions and hints content management using the programmer APIs desired user-level features new and existing architecture design business decisions contributed widgets w.r.t. open source public relations in general
These are off the top of my head - and i'm relatively new to the community, so i'm quite open to suggestions about what belongs where. Overall question is, does the split make sense in principle?
I'm not against this split. However, I'll end up subscribing to both anyway, as both areas interest me. I suspect the same would happen with most of us, as I think most of us are interested in desired user level features and business decisions on how to proceed with Zope as well as the coding side of things. I'm also a bit vague about the two 'categories' we're looking at. That is, 'zope-dev' is fairly clear, but 'zope' is everything left over (and it could be argued desired user-level features also belongs on zope-dev). Perhaps this is the intent, anyway? It is however unlikely you can do a mailing list split that will allow many people to unsubscribe from one or the other right now, and a split is useful to me anyway in that there'll be more structure in my mailbox (with the appropriate mail filters). Regards, Martijn
Ken Manheimer wrote:
To clarify, here are some examples of the way i see the division of topics:
zope@zope.org zope-dev@zope.org ------------- ----------------- installation and operation dtml coding questions and hints content management using the programmer APIs desired user-level features new and existing architecture design business decisions contributed widgets w.r.t. open source public relations in general
I would spilt it a bit differently, to at least 3 lists: zope@zope.org zope-dtml@zope.org zope-dev@zope.org ------------ -------------- --------------- installation and operation dtml coding hints product coding content management dtml documentation architectural issues business decisions contributed widgets external method coding PR in general product integration contributed products zope.org site issues developer documentation announcements Note that I do not have feature requests on this list. Although I would recommend discussing a feature on the appropriate list before submitting a request, the request should be made at the collector on zope.org. I've split the list in this way because I beleive that we are going to be getting many more HTML/DTML coders than Python coders in the future. Like me. This also follows the general Zen of separating content from presentation, and presentation from logic. Michael Bernstein.
Ok, after a bit more thought, I came up with a fourth list: zope-bugs@zope.org Michael Bernstein.
participants (3)
-
Ken Manheimer -
Martijn Faassen -
Michael Bernstein