You are viewing a plain text version of this content. The canonical link for it is here.
Posted to docs-dev@perl.apache.org by Per Einar Ellefsen <pe...@skynet.be> on 2002/05/28 20:12:52 UTC
mod_perl Contributors
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
Questions:
1) Layout: ok? Tell me what you want, I fix.
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).
3) I want your info people!
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?
--
Per Einar Ellefsen
per.einar@skynet.be
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org
Re: mod_perl Contributors
Posted by Stas Bekman <st...@stason.org>.
ay be you can use some photos from Ask's photos:
http://photo.tomat.dk/tpc4/index1.html
here, though need to be processed to cut off the noise. Also you can use
apachecon.com and conference.oreilly.com to get various info and photos
of those who were speakers at the conferences.
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org
RE: mod_perl Contributors
Posted by "Jonathan M. Hollin" <ne...@digital-word.com>.
Let's not forget Jonathan either...
Oooo... :-) I am honoured. Thank you.
Jonathan
WYPUG (http://wypug.pm.org)
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org
Re: mod_perl Contributors
Posted by Per Einar Ellefsen <pe...@skynet.be>.
At 11:40 29.05.2002, Stas Bekman wrote:
>* need to add Allan (design) and Thomas (design, docs)
Let's not forget Jonathan either...
I realize just now that I don't know Allan's last name... Allan?
>--
Per Einar Ellefsen
per.einar@skynet.be
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org
Re: mod_perl Contributors
Posted by Per Einar Ellefsen <pe...@skynet.be>.
At 06:30 01.06.2002, Stas Bekman wrote:
>Per Einar Ellefsen wrote:
>>
>>Hi,
>>So, after having managed to delete all my files regarding this list, I
>>managed to get back on track, and have now reached what I think hits the spot.
>>http://users.skynet.be/pereinar/mod-perl/about/
>>Two pages: (major) contributors and other.
>
>Fantastic!
>
>------
>
>On http://users.skynet.be/pereinar/mod-perl/about/other.html you say:
>
>"If there was no Perl, there would be no mod_perl."
>
>Perl acknowledges its contributors in the file AUTHORS in the source
>distribution.
Ok, thanks, I was wondering about that..
>>On the major one, there is a "TOC" table. I just need some input on how
>>it should look. I was thinking something like the colors of the menu... ?
>
>I think this is just fine as is.
I'll still make it width="100%" and see if Allan comes up with any great ideas.
>Another question is where are we going to link to this docset from? From
>the Contribute docset? Then probably put it there?
Well, right now I had begun the "About" DocSet.. As I had said a lloooong
time ago, I was hoping to put this into it:
- Link to us
- Contributors
- and now I came up with... maybe "History of mod_perl". Would be
interesting I think.
--
Per Einar Ellefsen
per.einar@skynet.be
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org
Re: mod_perl Contributors
Posted by Per Einar Ellefsen <pe...@skynet.be>.
At 12:39 02.06.2002, Stas Bekman wrote:
>Per Einar Ellefsen wrote:
>>Ok, here's my last one: http://users.skynet.be/pereinar/mod-perl/about/
>>If no major comments are made, I'll add it now.
>
>looks good, go ahead and commit it. we can do tweaks afterwards.
>
>I guess you could add some bg color to the heading of the TOC? so
>'Activities' won't hang in the air.
Yes, that's what I wanted to do.. and it looks pretty good actually! I used
the styles from the menu, so it fits in with the rest of the design. It's
still at the same URL: http://users.skynet.be/pereinar/mod-perl/about/ .
I'll commit it now.
--
Per Einar Ellefsen
per.einar@skynet.be
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org
Re: mod_perl Contributors
Posted by Stas Bekman <st...@stason.org>.
Per Einar Ellefsen wrote:
> Ok, here's my last one: http://users.skynet.be/pereinar/mod-perl/about/
> If no major comments are made, I'll add it now.
looks good, go ahead and commit it. we can do tweaks afterwards.
I guess you could add some bg color to the heading of the TOC? so
'Activities' won't hang in the air.
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org
Re: mod_perl Contributors
Posted by Per Einar Ellefsen <pe...@skynet.be>.
Ok, here's my last one: http://users.skynet.be/pereinar/mod-perl/about/
If no major comments are made, I'll add it now.
At 06:30 01.06.2002, Stas Bekman wrote:
>Per Einar Ellefsen wrote:
>>
>>Hi,
>>So, after having managed to delete all my files regarding this list, I
>>managed to get back on track, and have now reached what I think hits the spot.
>>http://users.skynet.be/pereinar/mod-perl/about/
>>Two pages: (major) contributors and other.
>
>Fantastic!
>
>------
>
>On http://users.skynet.be/pereinar/mod-perl/about/other.html you say:
>
>"If there was no Perl, there would be no mod_perl."
>
>Perl acknowledges its contributors in the file AUTHORS in the source
>distribution.
>
>>On the major one, there is a "TOC" table. I just need some input on how
>>it should look. I was thinking something like the colors of the menu... ?
>
>I think this is just fine as is.
>
>Another question is where are we going to link to this docset from? From
>the Contribute docset? Then probably put it there?
--
Per Einar Ellefsen
per.einar@skynet.be
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org
Re: mod_perl Contributors
Posted by Stas Bekman <st...@stason.org>.
Per Einar Ellefsen wrote:
>
>
>
> Hi,
>
> So, after having managed to delete all my files regarding this list, I
> managed to get back on track, and have now reached what I think hits the
> spot.
>
> http://users.skynet.be/pereinar/mod-perl/about/
>
> Two pages: (major) contributors and other.
Fantastic!
------
On http://users.skynet.be/pereinar/mod-perl/about/other.html you say:
"If there was no Perl, there would be no mod_perl."
Perl acknowledges its contributors in the file AUTHORS in the source
distribution.
> On the major one, there is a "TOC" table. I just need some input on how
> it should look. I was thinking something like the colors of the menu... ?
I think this is just fine as is.
Another question is where are we going to link to this docset from? From
the Contribute docset? Then probably put it there?
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org
Re: mod_perl Contributors
Posted by Per Einar Ellefsen <pe...@skynet.be>.
Hi,
So, after having managed to delete all my files regarding this list, I
managed to get back on track, and have now reached what I think hits the spot.
http://users.skynet.be/pereinar/mod-perl/about/
Two pages: (major) contributors and other.
On the major one, there is a "TOC" table. I just need some input on how it
should look. I was thinking something like the colors of the menu... ?
--
Per Einar Ellefsen
per.einar@skynet.be
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org
Re: mod_perl Contributors
Posted by Stas Bekman <st...@stason.org>.
Per Einar Ellefsen wrote:
>
> I have implemented most of these changes now.
> http://users.skynet.be/pereinar/mod-perl/about/people.html
cool
>>>>>> 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.
>
>
> Hmm, so core and docs? I think that'd be the best.
> Although I still think that separating people into 2 categories is bad.
that's not good. There are contributors who do neither core nor docs,
but help to answer users questions. I believe this can be flexible,
since we don't use some db and need to query by enumerated category. So
just adding whatever we feel like is fine.
> Maybe I'll try a TOC by name with some short description as on the HTTPD
> list.
That's what I meant.
>>>> 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
>
>
> Again, I don't want to separate people into 2 categories. Everyone has
> done as much, and if we separate them:
> 1) Discussion might come up with "what is most profitable for the
> community, code or docs?" (code will win :)
we aren't talking about profitability. But rather saying who does what.
But sure it's fine with me to put everybody in one place.
> 2) Some people (like you) belong in both.
Than we can simply duplicate names.
> However, separating major and rest into 2 files is good. (However I
> think it should be detailed info/no info instead of major/rest).
Why? The two are orthogonal.
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org
Re: mod_perl Contributors
Posted by Per Einar Ellefsen <pe...@skynet.be>.
I have implemented most of these changes now.
http://users.skynet.be/pereinar/mod-perl/about/people.html
Haven't removed module authors yet.
At 13:50 29.05.2002, Stas Bekman wrote:
>BTW, if anybody complains about wrong details we can always fix those. We
>just try our best and errors are possible.
Yes, I'll add a note about that...
>>>* 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.
I changed it to "abstracting".
>>>>>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.
Hmm, so core and docs? I think that'd be the best.
Although I still think that separating people into 2 categories is bad.
Maybe I'll try a TOC by name with some short description as on the HTTPD list.
>>>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
Again, I don't want to separate people into 2 categories. Everyone has done
as much, and if we separate them:
1) Discussion might come up with "what is most profitable for the
community, code or docs?" (code will win :)
2) Some people (like you) belong in both.
However, separating major and rest into 2 files is good. (However I think
it should be detailed info/no info instead of major/rest).
--
Per Einar Ellefsen
per.einar@skynet.be
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org
Re: mod_perl Contributors
Posted by Stas Bekman <st...@stason.org>.
> 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:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org
Re: mod_perl Contributors
Posted by Per Einar Ellefsen <pe...@skynet.be>.
At 11:40 29.05.2002, Stas Bekman wrote:
>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
per.einar@skynet.be
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org
Re: mod_perl Contributors
Posted by Stas Bekman <st...@stason.org>.
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)
* add a note that contributors are listed in the alphabetical order.
* Don't link mod_perl_method_handlers.pod, but to the section in the
guide that now includes it.
* "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
* 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.
* Stas: s/conding/coding/
* Is this page autogenerated from some datastructure?
* 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">
>> 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
>> 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.
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.
>> 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.
>> 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.
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org
Re: mod_perl Contributors
Posted by Per Einar Ellefsen <pe...@skynet.be>.
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
>
>Questions:
>
>1) Layout: ok? Tell me what you want, I fix.
>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).
>3) I want your info people!
>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?
Another question:
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.
--
Per Einar Ellefsen
per.einar@skynet.be
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org