As issues (i.e., post-its at the session) can be part of one or more categories (decision-making mechanisms, community, methodology and legal) it may be better to consider such categories as viewpoints. For instance, the code of conduct in a project may mainly be seen as a legal asset but also as part of the other categories, with different implications.
It is important to consider how the identified categories would work depending on the role of the stakeholder (i.e., contributor, manager, external user, etc.)
The category called Decision-making mechanisms is maybe the most important one and may play a foundation role for the rest.
Goal of the Working Group
There is a general agreement that Governance Readiness matters.
To assess the readiness of a project the idea is to provide a set of questions that can help you to realize the status of your project.
To build a language to speak about governance (e.g., helping to identify what a good governance practice is).
To pay special attention to how governance may evolve in software projects.
Identify questions that motivate people to create/identify a governance model.
Describe the scenario (e.g., new vs. old projects).
Specify the expected role of the respondent.
Describe good / acceptable / poor answers.
Be careful with assumptions.
Collect good/bad governance practices.
Identify the main challenges related to governance issues.
Explore the advances on communityRule initiative to study possible alternatives for building a governance language. I can also help us to identify the type of questions we can make.
@jwf: Create a document crossing the items obtained from the Sustain OSS event against the communityRule website questions. I can also help with this.
@jlcanovas: Have a closer look at metagov.org initiative (parent project of communityRule). Attend to its weekly meeting to better understand its plan and objectives.
Where do we go from here?
Although this first meeting was a bit loose, I believe it helped to focus the work of the Working Group. Before planning the next meeting, I would like to advance on the action items to identify concrete elements that we can discuss.
I’ll keep you informed about our advances. I plan to create a new poll in some days to choose the date/time of the next meeting.
Thanks everyone who joined the call and made it happen in these crazy days.
PS: If I forget something, please tell me and I’ll update the thread
Awesome! Thanks for your contribution. I think it would be interesting to include as well the orthogonal dimensions identified in our report, to later see how they map with the first/second/optional choices. I can give you a hand with this.
We have been working on the Question Mapping Exercise proposed by @jwf. All elements identified at the SustainOSS event are now classified according to the sections proposed by CommunityRule. It is still a draft version and it would need more “eyes” to check (and maybe, discuss) that the classification makes sense. You can find the document here.
I have also explored the metagov.org initiative and attended one of their meetings. Among other things, the initiative is developing CommunityRule, which is directly related to our process of identifying governance models. As you can see, we are currently joining efforts to collaborate in this line. Also, the weekly meetings are an exciting place to discuss governance-related issues.
Can I help?
Yes! It would be great! The document is still a draft version and it would need more “eyes” to check (and maybe, discuss) that the classification makes sense.
For those of you that could give us a hand with the Question Mapping Exercise, please open the document and have a look at questions (column B) and the CommunityRule section (column H). Do you agree on that classification? It may be useful to have a quick look at the CommunityRule sections here.
If you have any remarks, feel free to create a comment in the cell directly.
Is there a deadline?
I plan to collect the feedback by Monday May 4th. Thanks in advance!
In the coming days, I will circulate a poll to rank the questions. The point is to identify some prioritization. Step by step. Keep tuned
here I am, reporting the next step in the plan for reaching the Governance Readiness status
As commented in the previous post, elements in the Question Mapping Exercise were classified according to the sections proposed by CommunityRule. We shared the classification to gather possible mismatches or concerns. No additional feedback has been collected. As a living document, any future comment can also be considered.
We now want to rate the elements of the Question Mapping Exercise. The objective is to prioritize the elements and analyze if we can focus on a subset of them.
Can I help?
Yes! Please give us a hand! We have prepared a poll to collect your input.
Hi @jlcanovas and everyone else. Thank you for the interesting discussion and the major steps forward you already took. I have a question regarding the poll and I hope I didn’t miss something that makes the question redundant.
When I ask myself “How important is each question in the development of OSS projects?” I think it depends on what stage of development process the OSS project already is. For example in the beginning it might not be so important to think about “Which organization structure is the most appropriate?” or “How to deal with membership?” because you might not yet know if your project will attract enough people in the end to have to think about it.
On the other hand questions like “Which license should be applied?” is of major importance in the beginning and might not be relevant in later stages of development - as you have already decided on this.
So, in sum, I think rating “How important is each question in the development of OSS projects?” depends a bit on the stage of development that has been reached already?
Don’t know, however, how to get such an evolutionary dimension into the poll : )
(ps and btw: missed to introduce myself: I am Erik from the Free Software Foundation Europe. I was also participating in the session at sustain summit but missed the last meeting (mainly because I could not write down my email on the wall for further notice before it was removed : D )
I understand your concerns, I’ve received similar feedback from other channels. Another issue is the high number of elements per question.
I admit I identified some of these problems and tried to minimize them as much as possible, but it was pretty hard. I could reduce the number of elements for the questions, but I did not find an effective way to address the lack of context (e.g., the “evolutionary dimension,” as you phrase it).
In the end, I decided not to “pollute” the poll with additional classifications and use the same context we had during the meeting at Brussels. I see now that such decision was not optimal
Maybe we could (partly) overcome this situation by specifying that the question rating would refer at the early stages of the development. With this, we are aiming at a subset of projects but maybe the most important ones when deploying a first governance model. ¿What do you think?
Lately I think about governance Rate of Change in open source. I agree the value of a governance model is better evaluated on situational context. Governance that what works at the beginning might not work ten years later. (Or, work without a lot of friction.) While license decisions are usually one-and-done, governance models or strategies vary in effectiveness over time.
I think this will be a unique challenge for this Working Group to map. How we contextualize these questions in an ongoing evolution instead of a one-and-done approach is important moving forward, I think.
I suggest finishing the current survey distribution. We should acknowledge the biases and caveats of the data; it is not neutral. But right now, it is early feedback for the Working Group to narrow down and focus on specific governance aspects.
Over time, we might discover interesting topics worthy of their own dedicated exploration. This could lead to new working groups, or new explorations in existing Working Groups.
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.