[drupal-docs] creating drupal-doc teams
Charlie Lowe
cel4145 at cyberdash.com
Thu May 19 23:34:34 UTC 2005
Definitely!
The press team, too, could probably also work in conjunction with the
marketing team on many projects. Nice thing about forming teams is that
it creates obvious groups of people to work togther on certain projects.
Robin Monks wrote:
> Hmm, shouldn't we have a press team? Something to find, correct,
> create, manage, distribute and edit drupal articles, stories and
> external sources. Kind of like Mozilla's "For the Record", "Press",
> "SFX Fire-wall", and Mozilla Links.
>
> I'd love to volenteer for this :-) Of couse it would require some
> people willing to work on these articles. I've CC'd some Mozilla
> contributers who may be interested. MozGuys, read PS: below to get
> familar with the situation here.
>
> Robin Monks
> Drupal Drops
> Mozilla Links
> MozNetwork
>
> PS: Drupal Docs 1on1
>
> OK, the major thing going on here is create an "outreach" project for
> Drupal such as Mozilla has. Drupal-docs will also provides
> documentation for Drupal itself. Michael, Percy, if you don't quite
> understand Drupal, please look at http://drupal.org
>
> On 5/19/05, *Andrew Hoppin* <andrew at civicspacelabs.org
> <mailto:andrew at civicspacelabs.org> > wrote:
>
> Gotcha. My time is limited enough in the near-term that if there are
> 2 other qualified and interested folks out there then probably best if
> I just support them for now.
>
> On May 19, 2005, at 3:27 PM, Charlie Lowe wrote:
>
> > You are definitely right. I should clarify. Of course we can have
> more
> > than two people working on each of these projects. But I'd like
> to have
> > two people in charge of the project group. Perhaps they should be
> > called
> > "team leaders" :)
> >
> > Andrew Hoppin wrote:
> >> Charlie, I'd love to help on marketing materials, though the next
> >> couple of weeks are bad for me, and I'd love the team to be larger
> >> than
> >> 2 if I were 1! :)
> >>
> >> Andrew
> >>
> >> ****************************************
> >> Andrew Hoppin
> >> 1.212.464.7665 (m)
> >> andrew at civicspacelabs.org <mailto:andrew at civicspacelabs.org>
> >> ****************************************
> >>
> >>
> >> On May 19, 2005, at 3:02 PM, Charlie Lowe wrote:
> >>
> >>
> >>> Currently, it seems we have lots of interest in taking Drupal
> >>> documentation in new and interesting directions. To facilitate
> this,
> >>> I'd
> >>> like to see if we can't form some documentation teams. Much like I
> >>> asked
> >>> if Djun and Bryan would be in charge of reorganizing the About
> >>> section
> >>> of the handbook, I'd like us to form other two person teams for any
> >>> major area that we have expressed interest in developing.
> >>>
> >>> Here are just a few examples of some areas I could imagine
> >>>
> >>> Documentation teams for
> >>>
> >>> * Restructuring/reorganizing each of the new handbook sections as
> >>> defined on the V2 page:
> >>>
> >>> http://drupal.org/handbook/v2
> >>>
> >>> For example, the About the handbook section. We need a couple of
> >>> people
> >>> to be in charge of our authoring guidelines and best practices for
> >>> creating Drupal handbook documentation.
> >>>
> >>> (Anisa spearheaded the style guide revision; perhaps we could coax
> >>> her
> >>> and one other person to handle the About the handbook section?)
> >>>
> >>> * Best practices for configuring and building Druapl sites
> >>>
> >>> (Roland has already volunteered for this one :) Is there another?)
> >>>
> >>> * Initiatives for improving the collaborative book and other
> >>> technological solutions to improve Drupal documentation usability,
> >>> integration, and creation.
> >>>
> >>> (Djun has already been working on this. Perhaps he'd like to be
> one
> >>> of
> >>> the team members. We'd only need one other volunteer then.)
> >>>
> >>> * Marketing materials
> >>>
> >>> (Andre? You seem to have lots of marketing ideas :)
> >>>
> >>> * Etc.
> >>>
> >>> The documentation team would be responsible for most decisions
> >>> regarding
> >>> their project (in some cases there might be some overlap between
> >>> other
> >>> documentation teams, so they'd have to coordinate). Initially, I
> >>> would
> >>> hope that each documentation team would run a proposal by the
> >>> drupal-docs list so that all of us could offer feedback in the
> >>> construction of their individual project so that a good
> compromise of
> >>> the important opposing interests (if any) can be reached.
> >>>
> >>> Otherwise, let us know when new documentation is posted (maybe
> this
> >>> will
> >>> be automated) so that we can offer feedback and suggestions. Or
> when
> >>> the
> >>> documentation team members are having trouble solving an issue
> >>> between
> >>> themselves, contact the list for assistance in resolution.
> >>>
> >>> In the case of any who volunteer for restructuring/revising the
> >>> handbook
> >>> sections, if they would like, they could also continue on as the
> >>> offical
> >>> book maintainers for those new books.
> >>>
> >>> If anyone has ideas for other documentation team areas, please
> >>> respond
> >>> to this post via the drupal-docs list. I've mentioned a few people
> >>> here,
> >>> but I'm sure there are a lot more. If anyone would like to
> volunteer
> >>> to
> >>> be a documentation team member for a specific project, feel free to
> >>> post
> >>> to the drupal-docs list or contact me privately.
> >>>
> >>> Once the documentation teams have been created, I'll create a
> page in
> >>> the About handbook section so that people know who's in charge of
> >>> individual projects.
> >>>
> >>> I hope this works well for everyone. Putting people in charge of
> >>> specific areas seems to me the best way for us to get the things we
> >>> want
> >>> accomplished.
> >>>
> >>> Charlie
> >>> --
> >>> [ drupal-docs | http://lists.drupal.org/listinfo/drupal-docs
> <http://lists.drupal.org/listinfo/drupal-docs> ]
> >>
> >>
> > --
> > [ drupal-docs | http://lists.drupal.org/listinfo/drupal-docs ]
>
> --
> [ drupal-docs | http://lists.drupal.org/listinfo/drupal-docs ]
>
>
More information about the drupal-docs
mailing list