At 20:18 18.04.2002, Bill Moseley wrote:
At 06:19 PM 04/18/02 +0200, Per Einar Ellefsen wrote:
>>I think this is too dangerous. How are you going to decide who has
>>contributed enough to be included in the venerable list of those "behind
>>mod_perl". Somebody will feel left out and it's a pity.
>>
>>I suggest we simply say developed by Doug MacEachern with help from
>>numerous other developers too many to list here.
>
>Well, I think it would still be very interesting to have in-depth
>information about the most active contributors, including an image etc...
>Gives a more personal look.

I keep thinking the same thing.  It would be nice to have more personal
touches -- it's nice to see the community.  But I can't imagine picking
people, either.

I'll do as best I can: try to list everyone (ok, maybe a little hard), alphabetically ordered (so no discrimination), and with a little more info for: (1) those who come with their info, (2) those we really need info for (Doug is clearly that guy).


Here I go again throwing an idea out without the time to back it up, but...

I keep thinking what would be nice is to have a place for
mini-articles/howtos.  So, for example, someone could write "Sessions in
Ten Minutes, by Perrin" and show a bit of mod_perl code.  Which would
really be focused on how to accomplish some common task with mod_perl, so
helpful, but also a way to showcase the mod_perl community.

That way it's easy to decide who get's to be "named" on the site, by those
that contribute.  And get some cool content, too.  One article limit, perhaps.

I know that duplicates a lot of the current docs, but I'm thinking more
article like (more narratives, I suppose).

This was exactly my idea and also why I wanted to apply for Take23 editor-ship. But no reply yet, I'll think I'll send a direct mail to Matt and see what's up.



-- Per Einar Ellefsen [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to