Per Einar Ellefsen wrote: > At 15:36 05.06.2002, Valerio_Valdez Paolini wrote: > >> On Tue, 4 Jun 2002, Slava Bizyayev wrote: >> >> > I don't know should it be a kitchen of every system administrator, or >> > somebody could volunteer to serve the public web site about the current >> > conditions of different web clients and recommended masks?.. I can't >> host it >> > on my devl4, because it is a development machine. That would be >> better to >> > find some stable place, like mod_perl, or apache project ;-). >> >> Can you provide a compatibility list? I think that the new mod_perl site >> is looking for new articles, may be the first part of Apache::Dynagzip >> man page is a good candidate... You could add also known bugs and >> features. But I cannot decide what goes on mod_perl site :) > > > Just like I would have said it myself :-) We're clearly looking for > information, and I was especially watching this thread for possible > inclusion. We have a nice place to do this, it's in our "Browser bugs" > section. Depending on the size of the document, it might go there or in > its own doc. Anyway, we welcome any submissions. Format is standard Pod. > See > >http://cvs.apache.org/viewcvs.cgi/modperl-docs/admin/style.pod?rev=1.8&content-type=text/vnd.viewcvs-markup > > for style information, but don't worry too much about that, we'll fix > that as we go.
I just want to add some clarifications to Per Einar comment. Are we looking for not strictly mod_perl but closely related material, which matters to the majority of mod_perl programmers? The short answer: Tutorials -> yes manpages -> no articles -> take23.org The long answer: Tutorials cover some interesting topics using several implementations. Tutorials are pretty much static and don't require much maintenance. We heartly welcome these. The ongoing discission of MVC is a good example of a tutorial candidate, templating comparison and *generic* tips and tricks are other ones. Manpages, which aren't the core module are not very welcome at this moment, as they usually require high level of maintenance, and we have hardly resources to cope with perl.apache.org. So at least for now, manpages aren't welcome. If you have feature tutorials, either submit those to take23.org or any other online zine. perl.com is looking for such articles. so does apacheweek.com. probable there are others. The new perl.apache.org is not a dump place for docs. The more irrelevant stuff we throw there the less added value the site will have, the harder it'll be to find something and the whole idea of expanding docs will do more bad than good. So new tutorials are definitely welcome, but re-read the first para to see the definition of a good candidate and so the existing tutorials at: http://perl.apache.org/release/docs/tutorials/index.html before submitting your tutorial. If your idea of tutorial doesn't fit into perl.apache.org's tutorial's idea, we will gladly link to it. --- Now back to the topic. If you can submit to us known problems with browsers and solutions that would be great. But please don't submit the Apache::Dynagzip manpage. __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
