Re: Request for Guidance
Berin Lautenbach wrote: > > In particular, I'm going to > > - put the IncubatorMussings document onto incubator as the overall > process description. um, would you mind taking one more poll first before it becomes 'official' policy (since that's what being on the web site means)? i know i didn't examine it too closely because a) it seemed to be in heavy flux, and b) i was concerned i might have a lot of objections to some aspects and dealing with opposing views can get dicey in a wiki. i'd like to take the time to actually 'take it in' first, if you don't mind.. (but go ahead if you *do* mind, since i certainly should have done this before now. :-) -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Request for Guidance
Rodent of Unusual Size wrote: Berin Lautenbach wrote: In particular, I'm going to - put the IncubatorMussings document onto incubator as the overall process description. um, would you mind taking one more poll first before it becomes 'official' policy (since that's what being on the web site means) Not necessarily. Put it in the website CVS linking it from the drafts section and add a part on top so that it's clear that it's a WIP. ? i know i didn't examine it too closely because a) it seemed to be in heavy flux, and b) i was concerned i might have a lot of objections to some aspects and dealing with opposing views can get dicey in a wiki. i'd like to take the time to actually 'take it in' first, if you don't mind.. If we see the diffs from CVS it will be easier to discuss for us too. I'm definately +1 for moving it to the site CVS given the above points. In any case, Berin, you can use the *.cwiki format for that file, so it's easier to understand the diffs (actually all normative docs should be like that IMHO because of this). Example: http://xml.apache.org/forrest/wiki-sample.html Also we can use the faq DTD for faqs and the howto DTD for howtos. (but go ahead if you *do* mind, since i certainly should have done this before now. :-) -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Status of Pluto?
Carsten Ziegeler wrote: Thanks for the info, Sam. I asked this mainly because of the wiki entry (http://nagoya.apache.org/wiki/apachewiki.cgi?PlutoProposal) where some people showed there interest in Pluto (or in the proposal) and most of them are not aware of the current state. And I was just wondering why this is the case. Apparently, you are interested in pluto, but are not a current subscriber to jetspeed-dev. That is not something that I anticipated. Can somebody talk me through the process of updating incubator-site? Carsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Request for Guidance
> From: Rodent of Unusual Size > > In particular, I'm going to > > > > - put the IncubatorMussings document onto incubator as the overall > > process description. > > um, would you mind taking one more poll first before it becomes > 'official' policy (since that's what being on the web site means)? > i know i didn't examine it too closely because a) it seemed to be > in heavy flux, and b) i was concerned i might have a lot of objections > to some aspects and dealing with opposing views can get dicey in > a wiki. i'd like to take the time to actually 'take it in' first, > if you don't mind.. (but go ahead if you *do* mind, since i certainly > should have done this before now. :-) . Not only do I not mind - I'd be extremely grateful. I'm trying to get as much review and agreement as possible before doing anything too rash. I just finished yesterday "Forrestising" the first part of it, but I'll hold off until you (and anyone else who is interested) have had a chance to review the wiki content. Will continue on the actual "policy" document (as opposed to the Musings document which is more of a description document). Cheers, Berin This message was sent through MyMail http://www.mymail.com.au - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Request for Guidance
> From: Nicola Ken Barozzi <[EMAIL PROTECTED]> > Not necessarily. Put it in the website CVS linking it from the drafts > section and add a part on top so that it's clear that it's a WIP. Sounds like a good compromise. I will do this. However - fair warning - I am going to be a pest and keep niggling to move it from Draft to formal :>. > In any case, Berin, you can use the *.cwiki format for that file, so > it's easier to understand the diffs (actually all normative docs should > be like that IMHO because of this). Have already translated to standard Forrest, so if it's OK might just add as that? NOTE: I do not personally see this as normative, and have marked the page as such. I am separately creating a cut down "Policy" document that should (I believe) be the normative reference. By stating there is only one Normative reference, and making sure it is as lean and clean as possible, I believe we can save arguments down the track. See : http://nagoya.apache.org/wiki/apachewiki.cgi?IncubatorPolicyDraft for an *embryonic* version of the normative document. This is the one I was suggesting should actually have a formal vote, as this is the one that people will point to and say "here is what you have to do". Cheers, Berin This message was sent through MyMail http://www.mymail.com.au - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Request for Guidance
See : http://nagoya.apache.org/wiki/apachewiki.cgi?IncubatorPolicyDraft for an *embryonic* version of the normative document. This is the one I was suggesting should actually have a formal vote, as this is the one that people will point to and say "here is what you have to do". Er, I have way too much experience with wikis to trust them as the source for normative documents -- that's why we use cvs. Roy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Request for Guidance
> From: "Roy T. Fielding" <[EMAIL PROTECTED]> > Er, I have way too much experience with wikis to trust them as > the source for normative documents -- that's why we use cvs. I'm explaining myself *very* badly today, my apologies. There are two documents I (and others) are currently working on. The first is the "IncubatorMussings" document. Currently in Wiki, I am about to transfer to CVS as a draft document. It is a process description document. The second is the "IncubatorPolicyDraft". This is embryonic only, and is in Wiki until it's a bit more advanced. This is (or is envisionned to be) the "real" policy document. When it is a bit further on, and those who want to have had some input, I will move it to CVS. When they are both complete (i.e. not yet), I would see the second document - the Policy - as being the normative reference for Incubation. The former is far more descriptive and is purely to help incubees along the path. As such, it is *not* normative. If there is an argument between these two documents (or in fact with any other document/reference), then the Policy document is normative. Of course this does not occur until the Policy document is moved from Wiki to CVS and is agreed by all parties as being correct. Thus the comment in the previous e-mail that I see the Policy document as being a document that should possibly be subject to a formal vote, but (what I should have clarified) is that this would only happen once it is out of Wiki and in CVS as a controlled document. Hope that makes a bit more sense. Cheers, Berin This message was sent through MyMail http://www.mymail.com.au - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
