Hmm, I was hoping they'd send me some info :) But ok, I'll add.
just add the name and the rest will come if they send you the info, if not just leave the name and what you know already :)
* Don't link mod_perl_method_handlers.pod, but to the section in the guide that now includes it.
I did :) It's still called method_handlers.pod (we merged it into the guide from the FAQs).
my bad :)
* "Brian provides the bandwidth for perl.apache.org along with the mailing list and cvs repository."
It's Covalent that provides those things. I guess better say:
Brian provides sysadmin support for perl.apache.org
Ok.
actually it could be collab.net, or both, but I think the above is just fine.
BTW, if anybody complains about wrong details we can always fix those. We just try our best and errors are possible.
* Gerald Richter is not working on the 2.0 build system. He work on abstracting the existing system. the 2.0 build system is a courtesy of Doug.
Hmm, he told me he worked on the build system :) But sure.
I know, but that sounds like he wrote the build system. that's unfair to Doug. When Gerald will have some working thing we will update his info.
1) Layout: ok? Tell me what you want, I fix.
looks fine, though I like the way http://httpd.apache.org/contributors/ gives a short TOC of all contributors. Also they include a short description which I suggest to be on our site more generic: core, modules, docs, support, advocacy, etc. Plus things like
Hmm, as I said (I think), the problem with this is that the list would be very long without necessarily giving much added benefit. I like the fact of dealing people up into categories, but we are faced with the problem that many of the contributors have contributed to the core, modules, docs, support *and* advocacy!
So what? let it be long. But at least we need a simple TOC. We can start with a simple TOC and later add more info if we feel like doing that.
Second yes, just follow the concept in docs/credits.pod, the last item lists just the names of contributors. Though don't comma separate it, but use the items just as in the above file. So names will be easier to read and spot.
Ok. It'll be a pretty long list (there is a pretty long list there, and one more in CREDITS.pod from modperl CVS). That's why I wanted to make it a separate page.
I didn't say separate page is a bad idea. I was just saying not to collapse all the names into one sentence.
Hmm, may be we shouldn't merge the two credits files but have 4 files:
credits/docs-major credits/docs-rest credits/code-major credits/code-rest
just an idea. I'm not sure what's the best approach.
__________________________________________________________________ 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
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
