Add Accessibility team in the Working Group structure.

[tim-schilling]

This draft PR seeks to make Django's governance a little more consistent around Teams and Working Groups. The board and steering council are looking into converting teams into the working group definition. The working group definition has more structure. It can be a consistent pattern that we can use to create future groups of contributors for a single purpose, like accessibility.

There are a few sections in this PR that still need more definition.

• Membership roles
• Expanding on which parts of the CoC WG the membership is similar to
• Budget
• Do you want to mention your annual report?
• Do you want to try to identify what a "positive contributions" is? It'd be helpful to prospective members in my opinion.

cc @jefftriplett @django/accessibility

[jefftriplett]

@tim-schilling good work.

[tim-schilling]

Sorry @django/accessibility, I need to ping you again with a follow-up. The checkboxes above are effectively TODOs. The resolution can be do remove the section or do nothing, but they aren't things Jeff and I should answer. I think the next steps are:

1. Have any discussion on questions or concerns on this PR
2. If we're in agreement this structure is good, we can merge into the draft folder
3. Accessibility team handles creating follow-up PRs
4. A PR is created to merge it into active
5. Submit the proposal to the board for approval

[thibaudcolas]

woot! I’ve added this to the team’s next meeting agenda. Note I think most of us already have big commitments currently (annual team report, Djangonaut Space, DjangoCon Europe accessibility support) so not sure when and who will get to this.

[thibaudcolas]

We discussed this in today’s accessibility team meeting. Notes:

Membership roles

• Chair & Co-chair: Tom & Thibaud (run meetings, logistics of membership mgmt)
• Board liaison: Sarah A
• Steering Council liaison: Tim (time zones)

Expanding on which parts of the CoC WG the membership is similar to

• Thibaud will do a new draft

Budget

No budget for now. We have some ideas but need time. Mention spending opportunities in annual report.

Do you want to mention your annual report?

Yes

Do you want to try to identify what a "positive contributions" is? It'd be helpful to prospective members in my opinion.

• Thibaud will do a new draft

[thibaudcolas]

I think this is ready for Board review, with the caveat I’d like to merge with the edits that I’ve just made rather than as-is. Which are very minor so I assume this is ok.

• I decided it wasn’t super worthwhile to detail what type of contributions are considered for new members. I think we’re pretty open to any contribution in this space.
• I also dropped the mention of the CoC membership as it felt superfluous. There’s room to be clearer about membership management but just as-is it’s clearer than the DEP 11 version, I think.

[tim-schilling]

I suppose this should go into active rather than draft.

[thibaudcolas]

Feedback from the board is this is good to go once / when @django/accessibility team is happy with the proposed changes, without further board vote. With one noted concern that it’d be nice if we were able to assess the suitability of this "teams to WG structure" with other teams so the teams don’t keep diverging in structure unnecessarily.

See also feedback from Jacob in #36. This team charter has no proposed budget, I assume we’re good but am not certain.

[tim-schilling]

@thibaudcolas can you explain the following a little bit more please?

With one noted concern that it’d be nice if we were able to assess the suitability of this "teams to WG structure" with other teams so the teams don’t keep diverging in structure unnecessarily.

[knyghty]

@tim-schilling

@thibaudcolas can you explain the following a little bit more please?

This was my concern. I am worried a bit that by adopting this without buy-in from other teams (ops, security, ...) that we will end up in a weird state with some teams in this new structure and some "legacy teams" that remain structureless / without SC supervision, or however this structure differs from the ad-hoc structure we had before.

I don't think it's a big deal.

[tim-schilling]

That's fair. I think the next step is to start this process with all teams. So we'll know pretty quick here where we have friction. Well quick in Django Governance time 😅

[thibaudcolas]

@django/accessibility – in particular @MHLut @erosselli @knyghty, @mihrab34 please review ❤️

[knyghty]

Thanks for the work here. I noticed some issues and I would like to do a few more specific run throughs, I know I wrote most of this and this is a bit why I cringe reading it.

[knyghty]

@tim-schilling I hope you don't mind me taking this over but I was quite unhappy with the DEPlike or RFClike language used in the original DEP so I've really tried to make the language more accessible. I thought this would be quicker than endless review comments and I found time at the DCEU sprints. I made a number of other changes agreed to by the accessibility team:

• Eli replaces Thibaud as co-chair (Thibaud continues as a regular member)
• We have two new members (not currently confirmed, but up for discussion. I will let you know which we confirm, if any)
• I think we agreed to remove the board liaison but if you think it's important we can keep it
• Renamed technical board to steering council
• Expanded the scope to include events and other community projects
• Switch the membership renewal from 9 months to an annual basis so the chair can just send these emails out once per year rather than tracking when people joined.

@tim-schilling can you let me know if you're happy or not with these changes?

@django/accessibility could I please get a review also?

Once we're all happy we can get this merged.

[tim-schilling]

Thank you @knyghty for making those changes. That was much easier with you doing it 😁 I'll bring it up for the steering council to review.

I think we agreed to remove the board liaison but if you think it's important we can keep it

I'm not on either group, so I don't think my opinion should matter here.

Congrats @erosselli on being a co-chair! 🥳 🎉

---

@jefftriplett can you give this a look over and a thumbs up? I believe you were leading this initiative from the board side?

[jefftriplett]

LGTM