Clarify what being on the org team means

[gsaslis]

In an open community that is entirely volunteer-driven, it makes perfect sense (to me) to have an org team that is also open, so that anyone can step up and help out.

From my point of view, this has worked reasonably well during the past 4 years. There is always room for improvement though, and one of the things I would like to see improved is a more explicit / transparent process (or a better definition) of "who is on the DevStaff org team".

This is a good incentive for volunteers, as it is a form of recognition for their work. Also, attribution is one of the cornerstones of open source software.

At the moment, it is not very clear:

• how someone can "join" the org team
• when/if someone should "leave" the org team
• what responsibilities an org team member has
• what privileges / access rights each org team member should have

Please feel free to share your thoughts!

Thanks in advance,
Yorgos

[gsaslis]

any thoughts anyone !?

[ealefrag]

Speaking for myself, I would love to understand better what currently means to be a member of the org team. If you/anyone could brief me, I suspect that it would be easier to come up with a suggestion.

[kabitakis]

Current status

1. how someone can "join" the org team
   By joining the org team at a couple of org meetings.

2. when/if someone should "leave" the org team
   There is no such thing as leaving the org team. People become inactive and the rest of the team knows they will not be involved but they don't lose their "privileges" (account access).

3. what responsibilities an org team member has
   Nothing clear. People who show up in org meeting are assigned some tasks for the upcoming meetup(s) or the community in general. Especially for a meetup there are some tasks that are assigned to specific members usually: order pizzas, get beers and soft drinks, create event on meetup.com, post on facebook, post on linkedin, post on slack, make the intro presentation, create/update github repo, count the attendees, communicate with venue owners/hosts and more. Usually, during an org meeting, a member says he/she can do task A for the next X meetups and in case he/she can't do it sometime he/she informs the org team on slack.

4. what privileges / access rights each org team member should have
   An org team member has admin access to some community's accounts: meetup.com, github, facebook, linkedin, slack.

[gsaslis]

thanks for putting this down in writing @kabitakis ! we now have a reference point.

Regarding (4) I would add that they get some positive awareness by being mentioned as Org Team members in meetup.com.

Regarding (2), I would propose that we reconsider. Both from an information security point of view, but also from a "privilege" point of view, we should perhaps make a separation with active vs. past org team members.

wdyt?