cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Torsten Curdt <>
Subject Re: [vote] Diana Shannon as Documentation Coordinator
Date Tue, 16 Apr 2002 14:11:00 GMT
On Tue, 16 Apr 2002, Stefano Mazzocchi wrote:


> I've challenged her offering a 'documentation coordinator' job overhere.
> Just like we have a 'release coordinator', I think it makes sense to
> have a 'documentation coordinator'.


> The job includes:
>  1) planning and proposing a better (as defined above) documentation
> outline
>  2) coordinating the authoring effort (means: kicking some asses if
> people commit code without committing docs that go along with them: we
> might go as far as prohibiting code submissions, even in the scratchpad,
> without appropriate documentation along)

ups... we are approaching strict times... ;-)

>  3) providing editing of existing docs (and future docs)
>  4) managing relationships between users and developers
> I personally think Diana is great for this job becuase:
>  1) she volunteered (in my book, this would be enough since nobody ever
> did in one of my projects after 5 years of more of OSS... but there is
> more)
>  2) her native language is English, but she has worked in many foreign
> countries and she speaks several languages.
>  3) she has a medium understanding of Cocoon as a user. No developer can
> have this job since he/she would loose the user's point of view. I think
> Diana can be a mix between the two points of view and coordinate them so
> that they converge.
> All right, at this point I stop and I ask Diana to chime in and present
> herself.

looking forward on that...

> Ah, one more thing: she asked me if the community needed samples of her
> skills to provide a vote and I admit it's a little strange to ask to
> give commit access to somebody without having to do anything.
> Well, IMO, volunteering for such a critical yet hard job is enough of a
> statement for my vote, so I vote +1 to have Diana 'documentation
> coordinator' and grant commit access to her so that she can update the
> docs directly.

Well, IMO an introduction would be fine. ...but then - no problem.

> Of course, we, as a dev community, must make all possible efforts to
> help her in those situations where she requires help.

of course...

> At the end, I'm overly pleased by proposing (finally!) a women in the
> Cocoon Development community.


> So, Diana, please, introduce yourself and introduce your plan of action
> (as you did with me privately) so that the rest of the community can
> vote.

..please do so..


To unsubscribe, e-mail:
For additional commands, email:

View raw message