In past discussions (and both Summits) we discussed about potential membership models to eventually organize decision-making if needed better. While some were fans of the idea and some not, I do think that it’s useful to have a very lightweight membership model, mostly for administrative privileges on various platforms.
I also do think that the Core Team has kind of transformed into this membership model, originally meant as a group of people to handle paperwork and represent OSD in cases where it’s needed (Like Open Source Initative affiliation), I feel like it kind of transcended into a group which steers the direction of where OSD should be going. Hence I think that a membership model with a very low entry level barrier should be introduced and a smaller core group with very few additional privileges (which don’t affect stewardship of the project).
I’d even actually suggest following process:
- Convert current core group into membership group
- Introduce a membership application process
- Vote and set number of people to be part of Core (maybe 5,7 or 9? Currently it’s 11)
What do you think? I realize that one doesn’t want to create too much hierarchy too quick, but if it’s very easy to become a members, I think that we can move forward quicker.