[TOS] Ian Weller is working on TOS infrastructure this summer

Karsten Wade kwade at redhat.com
Tue May 24 01:20:26 UTC 2011


On Mon, May 23, 2011 at 10:43:48AM -0500, Ian Weller wrote:
> On Mon, May 23, 2011 at 10:21:42AM +0100, MJ Ray wrote:
> 
> > So I can't file a report for what I feel is the underlying issue:
> > too few people have access to the infrastructure and how that access
> > is determined is unclear.
> 
> I don't necessarily want a formal procedure for this, because I would
> like people who want to help out to do so easily.

I read somewhere that 2011 is the year of governance in FOSS. I dunno
if that is true or not.

But it does help to spell it out for folks - it doesn't have to be a
formal procedure, just explicitly have clear statements in an obvious
location:

1. Here are the people who work on the infrastructure, you can contact
   them directly or (best) via the tos at ... mailing list.

2. If you want to help with the infrastructure, let us know on
   tos at ... or use the ticket system at $URL to help or take ownership
   of a task.

3. We follow a lightweight mentoring model, which means you can have a
   mentor if you want one, for as long as you need. Ask $here for more
   information.

> One possibility is to grant access when a user has accepted a ticket
> that requires them to have access to a server (or what have you).
> Thoughts, all?

Yeah, this is item 2. above - help people find the ticketing system,
make the "open ticket report" easy to find, and get the work happening
directly around problems nodes.

- Karsten
-- 
name:  Karsten 'quaid' Wade, Sr. Community Gardener
team:   Red Hat Community Architecture & Leadership
uri:               http://TheOpenSourceWay.org/wiki
gpg:                                       AD0E0C41
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://teachingopensource.org/pipermail/tos/attachments/20110523/4f897ee8/attachment.asc>


More information about the tos mailing list