I second this. Offering the right questions depending on the different stages of the evolution of a project could be a major contribution that this group can bring into successful planning of governance readiness.
I would be interested in working this a bit more out. Some initial ideas:
We could differentiate different “starts”: For example a project that begins with less than 5 persons and without monetary compensation in mind (at least in the beginning) might have different governance concepts to think about than a well-funded start-up with more then 20 employees or similar.
From these different starts we could define different levels that can be reached during the evolution. Some metrics that come to mind to define these levels are a growing importance (usage / number of installations / critical applications etc.), the growth of “community” (users, contributions, third-party usages etc.), growth of business, growing dependencies etc.
Without having too many details already, a matrix that offers different levels for different starts and the most important questions regarding governance readiness for each level/status would be something abstract but also pretty useful I can imagine.
I think it is time to have a second meeting and discuss the working group’s current status. I’ll share a Doodle among the working group members to set the final date/hour. Feel free to contact me if you want to join the meeting.
It covers a variety of topics including "what is governance, and what are the roles and responsibilities in projects that are typically gated in some way), why explicitly defining governance policies is useful, how projects typically evolve over time to add more policies, and then a number of project governance archetypes.
I would love to hear feedback on it, and as with all TOSW content, it is very liberally licensed, and I would love to hear if any of it could be useful for the SustainOSS governance readiness guide.
This is what I am most interested in. An idea I wanted to pitch was to create a site similar to choosealicense.com. Except instead of choosing licenses, it would be “choose a governance model” or something else clever. This allows us to leverage the categorization work in the spreadsheet and focus on easier interfaces for people to think about how to organize and govern their software communities.
Thanks for the homework. This is useful for me since I haven’t been able to keep up on the doc work closely.
@jlcanovas presented a quick review of the Poll result for the three main dimensions surveyed.
@jwf asked about the actual meaning of the issue “Accessibility of governance model” in the Barriers and Needs dimension. @georgiamoon clarified that such an issue might be related to the Principles of Authentic Participation, as it refers to the ability of newcomers to enable their participation in the project.
@jlcanovas first presented the following four possible working lines and opened the room for discussion.
Create a template with most-voted elements to help to define explicit governance models
Enrich CommunityRule to consider these questions
Illustrate most liked elements with real-life examples.
Frame questions according to the starting point and development status of the project
During the discussion time, these are some ideas that appeared:
Leverage on CommunityRule templates to provide guidelines for governance models in open source projects. They can also be used to recommend specific models
It would be nice to enable the collaborative definition of the guidelines.
Although CommunityRule provides a general approach for governance, it could be easily reused/adapted for software projects.
Choosealicense is an excellent example of what we could provide in the working group, but for governance models.
As an outcome for the working group, a website (or web-based resource) is much more suitable than a report.
There was agreement on working on a prototype website, including the main recommendations/questions/elements explored in this working group.
@jlcanovas: Create a first version of a webpage, which will include a set of recommendations (based on the questions/elements identified) to create governance models. Nathan commented that he can also help with this.
@jwf: Technical help to create the repository for the website at SustainOSS
Rest of the group: Review the website
Where do we go from here?
I think that deploying and creating the website would be a nice final contribution from this working group. I visualize the site as a two-step workflow where users can (1) check that they have considered most of the questions they need to face to create governance models and (2) draft a first versión of their governance model. This is just an idea for now, but it will be refined in the coming days.
I’ll keep you informed about the advances. Feel free to chip in whenever you want.
I think in this case, it might make more sense for us to team up with CommunityRule instead of building our own platform. I think anything we create or do will have better visibility there, provided upstream is willing to accept our patches. (Guess it helps to have upstream involved in our W.G.! )
Maybe we don’t need to create a new git repo after all?
I visualize the website as the “idea/proposal/motivation site” and the CommunityRule as the “solution” (one of). While the website can illustrate the steps we made in the working group, summarizing the ideas, questions, and survey; I don’t think the CommunityRule should be so descriptive.
Also, I think it would be better to have a landing page living on the SustainOSS side to collect the resources created in the working group (as they are currently scattered in several docs and spreadsheets).
I’m thinking about the website - Besides the existing Governance Readiness page, we can add more pages for you. Does that current page work, or do you want to have more of a stand-alone resource on the Sustain site?
I was thinking about a stand-alone resource to have more freedom with HTML/CSS/JS. However, if the final version is “just” a HTML webpage, it could replace the current website in SustainOSS portal. Let me advance a bit more in the website and we’ll see what’s the best solution.