On Tue, Feb 13, 2001 at 11:36:21AM -0500, David H. Adler wrote:
> > - A list of projects and their development status and needs.
> > - Making sure things move forward
> > - A "this week on perl-qa" style summary
> > - The code repository
> > - Mailing list organization (creating new lists when necessary, etc..)
>
> I might be convinced to do some of this. Maybe the first two. I hate
> writing summaries, though.
Summaries should be fairly easy, since this is historically a
low-traffic list (a little too low lately). It does involve reading
just about every message though... but that's just another drop in the
bucket for you. :)
The project list collects all these neat ideas we've been kicking
around (maybe from the summaries, maybe straight from the archives)
posts a list periodically along with their stage/progress so we
remember what we're supposed to be doing.
Those two are basically book-keeping. Making sure things move forward
involves looking at the list and summaries, getting people involved in
the projects, getting some sort of commitment and estimate out of the
people involved and making sure things moved forward. It also
involves some Schwern Wrangling, which you're quite good at.
I think that's what I need. A project manager. If anyone out there
actually has experience in any of this, feel free to shout loudly.
> What's actually involved and what are you bribing me with? :-)
Graft?! Shocked, yes, I am shocked to find the implication of bribery
here! As punishment I will force you to watch lots of obscure british
cinema brought back from Blackstar. I hope you've learned your lesson.
