Stas Bekman wrote:
Frank Wiles wrote:
On Wed, 4 Aug 2004 23:52:46 -0600 Doran Barton <[EMAIL PROTECTED]> wrote:
What can I do to help? Jayce^ said a lot of help is needed in the
documentation department. I can certainly help there. What else?
General advocacy? Someone should write a feature for SysAdmin or other
publications showing off the beauty and power of MP2.
I've sent in an article proposal to SysAdmin to do an article on MP2. I've written a couple of articles for them in the past and some
of their offices are in my home town so I know some of the folks
there. It would be for the January issue on Open Source.
I'll let the list know if it is accepted. If it is accepted I may
be asking a few of you to give it a once over before I submit it to
make sure everything is peachy.
As I've suggested at the BOF, an ad-hoc work won't be as successful as something that's more co-ordinated.
Yup, we need strong coordination on this one.
Ideally, I'd love to see quick docs, with itemized lists of what do we want to achieve, who owns those items, etc.
Yes, good idea.
e.g. for articles, it'd be nice to have something like this:
Magazines:
- No contact at the moment:
o SysAdmin - Frank Wiles <[EMAIL PROTECTED]> sent a proposal o DrDobbs - currently unwilling to have mp articles o Linux Jrnl - need to ask
- Active contacts:
o The Perl Review - perrin writes a monthly column o The Perl Magazine - geoff is working on the Oct article o perl.com - stas is going to write the article for Sep 12.
- People willing to write articles/stories
o Perrin ... o Philippe ...
The data is fake of course at the moment.
I hope so, 'caus I don't know what article I am supposed to be writing.
We create another file for PR efforts, etc.
What do you think? We put these files under cvs modperl-docs and we sync the discussions here with these files.
Would we want those files to be publicly visible on the perl.apache.org site as well (I wouldn't mind).
It's hard to understand what's happening from emails, it's easier to track that via files.
Yup, wether we decide to simply use a few text files or POD files that end up on the site as well,
I'd like to volounter as maintainer of that stuff once we agree what/where we put the 'stuff'.
So, unless anybody strongly objects, I'll prepare an overview of what has been said this week and
split it up in some sort of documents.
signature.asc
Description: OpenPGP digital signature
