Actually, when I said developers I ment people with commit access. But, thinking about it, if you don't care about the code or the documentation, I don't believe you should be using the -dev list; just the -user one.
Personally, I'll monitor the documentation emails whether they come through -dev or -xxx. Again, for the record +0. But since I believe there's some negatives that doesn't matter. As for how long the thread is - this is nothing compared to [EMAIL PROTECTED] the other week ;) let it take as long as it takes. J. > From: Carlos [mailto:[EMAIL PROTECTED]] > > David, John, et al: > > I would very strongly recommend against increasing traffic on one list by > piping another lists output to it. I believe that the nature > documentation > discussion is parallel to the development process. > > I would also caution against mass subscribing people to > cocoon-docs. I would > much rather let people self select into the docs list. That way > we have only > the people who are interested in participating in the documentation effort > to be on the list. > > As for crossposting, I have an idea. Find a way to automate > reports back to > cocoon-dev using something similar to what Nikola Ken uses for reporting > patches. It would imply creating a documentation catergory in > Bugzilla but > it would be a better answer than crossposting or posting to Cocoon-dev IMO > > Thought, comments? > Carlos > > > On 05/07/02 2:05, "David Crossley" <[EMAIL PROTECTED]> wrote: > > > Gerhard Froehlich wrote: > >> +0 here. > >> > >> I'm not 100% convinced, that we can seperate the document > >> process from the development process this clear. > >> > >> I'm afraid that will cause lots of cross postings in both > >> lists. > > > > I too am concerned on this front. However, i think that there > > is a solution. > > > > If the docs list knew that every dev was subscribed and so > > was getting the postings anyway, then there is no need to > > cross-post. This could be written in to some guidelines, > > which could be occasionally posted to the list as a reminder. > > > > We have the excellent idea that John declared, that new > > people joining the dev list would automatically get -docs > > and -cvs lists. So what do with the existing developers? > > Perhaps it is possible to subscribe the whole existing dev > > list to cocoon-docs at commencement. Is that too radical? > > > > --David > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, email: [EMAIL PROTECTED] > > > > -- > Carlos E. Araya > ---+ WebCT Administrator/Trainer > P | California Virtual Campus > - | C/O De Anza College > G | 21250 Stevens Creek Blvd > ---+ Cupertino, CA 95014 > > email [EMAIL PROTECTED] > web http://www.cvc1.org/ (work) > http://www.silverwolf-net.net (personal) > phone 408 257 0420 (work) > PGP Fingerprint: E629 5DFD 7EAE 4995 E9D7 3D2F 5A9F 0CE7 DFE7 1756 > > > "Do not meddle in the affairs of dragons....for you are crunchy and taste > good with ketchup and mayonnaise.." > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
