Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explicit leadership roles & appointments #31

Closed
drnikki opened this issue Mar 27, 2017 · 7 comments
Closed

Explicit leadership roles & appointments #31

drnikki opened this issue Mar 27, 2017 · 7 comments
Assignees

Comments

@drnikki
Copy link
Contributor

drnikki commented Mar 27, 2017

The amorphous structure of the DD&I group - if you show up, you're part of us - is wonderful. So many people have commented lately that leaders should be held to a different (higher?) standards than community members. If this is the case, for the DD&I group, we'd need to first define who the leaders are and what their responsibilities are.

This issue is for that!

@rubyji
Copy link
Member

rubyji commented Mar 28, 2017

I missed the conversation in Slack around this, but this might be a good goal for our second year as a group. I can see having a chair/lead organizer, vice chair(s)/organizers, and project leaders - something along those lines. Maybe a steering committee.

@cleverington
Copy link
Contributor

Based on recent events, I'll bump a prop on this issue to review it during our Weekly Meeting to create a Steering Committee for Moderation purposes.

@lyndsey
Copy link

lyndsey commented Apr 16, 2017

In the first instance perhaps identifying a few "Ask [name] about..." people and pinning it in Slack would really help? It can help to flesh out some roles and conversation topics too. For example:

Ask [name] about the group aims and what we want to achieve
Ask [name] about how to get involved and help
Ask [name] about finding resources for your organisation
Ask [name] about increasing diversity at your next conference or event

@drnikki
Copy link
Contributor Author

drnikki commented Apr 28, 2017

We discussed this explicitly in the strategy meeting (full notes in #28), and the relevant parts here are:

DDI has the same problem as the community. Should we lead by example? Consensus: yes

  • Roles should allow people outside to understand who to talk with.
  • Be clear about roles and responsibilities.
  • If you want a 501, you have to have them, although that’s not a rush.
  • Helps new arrivals understand who gets listened to more than others.
  • How to handle people who don’t have/need formal role, but have a strong voice?
  • There appears to be a clear need for teams like the moderation team.
  • there should be individuals for accountability and teams for support of those individuals.
  • Use the status emojis for roles to help support roles, or put the role in name.
  • Teams are Taxonomy based
  • Put something into the issue queue so we can attract people who are not here.

Initial Teams:

  • Moderators
  • Communications
    -- Web site
    -- Twitter
    -- PR
  • Leadership
    -- Chair
    -- Vice Chair

Initial Members:

Communications
Scott
Ruby
Alanna
Leadership
Nikki
Ruby
Moderation Team
Alanna
Kara

Solidification By: Ruby and Alanna

@sugaroverflow
Copy link
Member

Linking the collaborative doc of teams and volunteers: https://docs.google.com/document/d/1E24reX_62IgRAYlq97v9McDDc1fT-Jc4hqMlb7FxciM/edit#

@YesCT
Copy link

YesCT commented May 5, 2017

Administrative roles and organizing (around moderation) sound different than taking moderation shifts... the doc here I think is more of the admin org.

Use #69 to volunteer for being a moderator.

@drnikki
Copy link
Contributor Author

drnikki commented May 12, 2017

We did create teams! Like mentioned above, use #69 to become a moderator. Team leadership was announced in the May 11 meeting - agenda and notes in #65

@drnikki drnikki closed this as completed May 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants