Governance: For OSD Community + Repos

[Erioldoesdesign (Eriol Fox)]

Starting a thread re. governance of everything to do with OSD - inclusive of whatever we consider to be ‘maintainers’ as well as ‘core team’ etc.

With a hope to continue and progress conversations about a written and robust governance framework from 2023 onwards

---

Reference docs

https://cloud.opensourcedesign.net/apps/files/files/11851?dir=/Core%20team&openfile=true

---

Reference forum threads

Open Source Design core/board

mmm i agree, after some reflection I think having a low member number board e.g no less than 3 and an odd number to allow for voting clarity. But I would see a board function as a place to ‘escalate’ decisions and issue to as well as gather yearly advice (or another time period) I think the ‘departments’ are a good idea generally to segment the goals and mission of OSD - and would really help to spread the labour of different aspects of OSD’s maintenance tasks.

---

For now I suggest that we do two things:

1. Review previous notes, form our opinions/thoughts and make statements about those thoughts (i would strongly encourage no ‘direct responses’ and ‘probing questions’ towards people’s statements just yet - clarifying questions absolutely encouraged though.
2. Edit/add reference docs and forum threads from years past to help us remember what has come before.
3. Link and share other governance structures, docs etc. here as examples that you think could work for OSD.