[Zope3-dev] Re: [DraftProposals]
Neat! I saw those possibilities in the last days already and think it's a nice idea to manage them there. How did you make the existing specs appear there so quickly? Guess I'll play around a bit with the management of the series. One thing that we should consider: Do we want to handle Zope 3/Zope 2 as two distinct products in Launchpad? I noticed that having a 'trunk' series would get confusing when handling both within one Product. Can we rename the existing 'Zope' Product to 'Zope 3'? Christian SteveAlexander wrote: Actually, I suggested a while back to use Launchpad to track the status of proposals. This kind of thing has been very successful for the Ubuntu project. Here's the Zope3 proposals imported into a demonstration version of Launchpad. https://features.demo.launchpad.net/products/zope/+specs -- gocept gmbh co. kg - forsterstraße 29 - 06112 halle/saale - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development signature.asc Description: OpenPGP digital signature ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: [DraftProposals] (edit)
On Mon, Dec 18, 2006 at 11:11:21PM -0800, Christian Theune wrote: I don't think so. The Zope 3 wiki was built up as, and still is, a resource for the development *of* Zope 3. We shouldn't So according to you ZOPE3 is still an engineering project as the main Wiki/Documentation site is basically a resource for the development of ZOPE. Indeed, this is the way ZOPE3 is presented to the outside world now. It is my impression and I am acting on that. People starting with ZOPE, or implementing with ZOPE, get lost in documentation about *proposals* on ZOPE. Place yourself in the shoes of someone new to ZOPE3 and trying to find his/her way. That should matter to you. Let me phrase it as a technical challenge (so the engineer can understand it): How do you create a web resource for ZOPE3 that allows people to find and resolve implementation issues easily? Without them having to wade through (alive or dead) proposals? And how do you trick search engines not to expose these proposals? Pj. ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: [DraftProposals] (edit)
Hi, Pjotr Prins wrote: On Mon, Dec 18, 2006 at 11:11:21PM -0800, Christian Theune wrote: I don't think so. The Zope 3 wiki was built up as, and still is, a resource for the development *of* Zope 3. We shouldn't So according to you ZOPE3 is still an engineering project as the main Wiki/Documentation site is basically a resource for the development of ZOPE. Indeed, this is the way ZOPE3 is presented to the outside world now. It is my impression and I am acting on that. People starting with ZOPE, or implementing with ZOPE, get lost in documentation about *proposals* on ZOPE. Place yourself in the shoes of someone new to ZOPE3 and trying to find his/her way. That should matter to you. I'm sorry if it looked like I don't care. It does matter to me that people coming to Zope 3 need information. However, that doesn't remove the justification for the existing project management resources. Steve pointed out some functions of launchpad and maybe those can take over those responsibilities in the future. Let me phrase it as a technical challenge (so the engineer can understand it): How do you create a web resource for ZOPE3 that allows people to find and resolve implementation issues easily? Without them having to wade through (alive or dead) proposals? And how do you trick search engines not to expose these proposals? I don't have a clear answer for this. I personally appreciate that you are investing effort and contribute. About your challenge: Maybe we do not have to use the Zope 3 development wiki to provide users/developers with information how to use Zope 3. Maybe the Zope 3 wiki in the future can become the place if we start using launchpad. I agree that we want to separate the concerns and don't have people looking for documentation about using Zope 3 end up in the depth of the development proposals. (However, implemented proposals should be a reasonable source of documentation for their scope!) Christian -- gocept gmbh co. kg - forsterstraße 29 - 06112 halle/saale - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development signature.asc Description: OpenPGP digital signature ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
