Per Einar Ellefsen wrote:At 20:12 28.05.2002, Per Einar Ellefsen wrote:
Hi,
So, I tried to follow approximately the layout from the Apache contributor list. I didn't include the top part though, as it would mean reproducing some content and we have too many people having contributed anyway, so the list would be too long.
See http://users.skynet.be/pereinar/mod-perl/about/people.html
Great work Per Einar!
Some comments:
* need to add Bill Moseley (search, docs)
* need to add yourself (docs)
* need to add Allan (design) and Thomas (design, docs)
Hmm, I was hoping they'd send me some info :) But ok, I'll add.
* add a note that contributors are listed in the alphabetical order.
ok.
* 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).
* "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.
* Geoff's section: s/I/Geoff/, etc to be consistent with the rest of the comments.
* 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.
* Stas: s/conding/coding/
* Is this page autogenerated from some datastructure?
Yes. I used the same basic principle as the success stories, ie. there are text files, one for each author, with headers and a body. And then I have a template called people.tmpl constructing that page.
* I don't think we should use mailto: links on mangled email addresses. e.g. if I click on it in mozilla on my email address I get: at <"stas stason.org">
Ok.
Questions:
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!
2) How should we handle people we don't have enough info for? Make a separate list or add a list with names to this page? (just comma-separated).
First we already have the docs/credits.pod file. I suppose the two should be merged.
Ok, then, I'll handle 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.
3) I want your info people!
you have mine :) don't worry about that. Those who will want their info added will eventually send it to us. I think you've done a great research so far, mostly without any help from the contributors themselves.
Sure.
4) Where should it belong in the site structure? Right now it's just about/people.html, but I'm not sure about that being the correct place.. What do you think?
I think it's a fine location.
5) Should we include module authors? There were listed some in in Credits, but I guess we shouldn't include those... There were some with more info about them in Credits (which are on the page I sent to you), but I won't add any more module authors than that I think.
here lays the problem: there are many module authors and it's hard to maintain such a list. The Apache:: module list serves this purpose quite well (though it is neglected for a long period). I think the current list you've presented already includes a few authors who didn't contribute directly to the mod_perl core, so it's unfair not to include others. To avoid unfairness I suggest to have only the following:
** Major contributors (detailed) ** Other contributors (just names)
And leave the module authors out (which are already listed in the Apache:: module list), unless you really think that this list is not going to be neglected, which is going to be unfair to all the new authors.
I'll link to the Apache/Perl module list for module authors then, removing any that are currently appearing in this list.
-- Per Einar Ellefsen [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
