osdf-devteam team mailing list archive

[zeto28 <amf5bp@xxxxxxxxxxxxxx>]

On Tue, Dec 21, 2010 at 09:55:36AM -0800, Andrew Ettinger wrote:

> we should probably remove the In Progress and Task Archive from our
> part of the forum

I agree.  I also think we should clarify whether "dev team" and "tech
team" refer to the same team or whether they refer to two different
teams.

> Second, we have a lot of other teams that are working on a lot of
> other things. You can see that by the sheer number of boards we have
> on the forum. The other teams need a way to communicate who is working
> on what, and the forum provides an easy way for them to get organized
> and provides visibility for who is working on what (the 'in progress'
> area; completed tasks go into the archive; etc). They will need to
> figure out their own best practices for how they work -- legal, the
> art department, and the bloggers are going to work differently than we
> do and probably differently from each other. I'm just trying to
> provide them with some initial guidelines to get their organizational
> juices flowing.
> 
> A listserver for those teams is just another tool for them to organize
> around. They will need to figure out if that fits into their process,
> if at all.
> 
> Since teams are 'self organized', we need a way to rapidly see their
> processes. My expectation is that each team will maintain a wiki page
> that gives the current ways in which they are organized, so that as
> they evolve we have a standard document that we can reference (and new
> volunteers can reference) to get involved. Eddie has been working on
> giving an initial shape to these pages to help them get started.

I agree with that - I didn't want to tell people how they have to
communicate.  I just wanted to make sure that how they do it is written
down somewhere easy to find so a potential newcomer can just look up how
to get in touch with a certain team.  Urging the team leaders to add
this info to the article "Volunteer Resources" (and keep it up to date
there) would clear this up.

zeto
--