Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Itowns Governance evolution proposal by Oslandia - take 1 #1

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

vpicavet
Copy link

@vpicavet vpicavet commented Sep 3, 2024

This is a proposal for a more open governance, which would better correspond to a community project, and the criteria for an open project of OpenSource foundations like OSGeo.

I kept as much as possible of the previous organization, but inverted the decision process to be bottom-up instead of top-down, while keeping a sponsor committee with an indirect but effective operational power, processing decisions on funding and resource allocations ( and an extra right to veto, as discussed earlier ).

Consider this a proposal that feeds the discussion, not necessarily a final text, as there are most probably items to be explained with more details.

@alavenant
Copy link

Thank you for this valuable initiative. We greatly appreciate the time you've invested in improving the project's governance structure. Your expertise in Open Source is highly valued, and your insights are always welcome.
We apologize for the delayed response. Now that we're actively engaged with this matter, we're committed to maintaining more timely and fluid communication moving forward.

We are largely in agreement with your suggestions, though we believe a few adjustments would enhance both governance efficiency and daily collaboration, particularly regarding the current team size. Once we are able to finalize these details together, we plan to update our governance structure accordingly.

Fusion of PSC / PC

Past experiences in the itowns project have shown that limiting communication to developers can be detrimental. The current Project Committee (PC) and Project Steering Committee (PSC) structure provides an effective framework to address these concerns and support project growth. However, the project is currently in a critical growth phase where we believe a focused, compact leadership team is essential. We think this team should integrate both technical leadership (core developers) and strategic oversight (sponsors' representatives). Therefore, we suggest merging the Project Steering Committee (PSC) and PC committees, combining selected core contributors with PC members. A separation in two committes can still be re-evaluated once the team grows.

Furthermore, we think we should grant this merged committee a veto power, as currently outlined in the Steering Committee roles. While this power should be exercised judiciously, we believe it's crucial for maintaining clear direction and strong leadership during this critical phase of development.

Contribute with funds

o Your proposal : “Contribute an amount equivalent of a full-time annual commitment for one year to the project ( funding or resources ) ”
o We support the proposal to enable financial contributions from sponsors, which aligns with our objectives for the coming years. However, before we can incorporate this into our governance structure, we need to establish the appropriate legal framework, specifically by creating a dedicated legal entity for the project. If you are willing to take the initiative in establishing a foundation or other suitable organizational structure to facilitate funding contributions, we would welcome your leadership in this matter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants