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

Reorganize Governance and README #521

Merged
merged 4 commits into from
Aug 2, 2023
Merged

Conversation

josee-sabourin
Copy link
Contributor

We have heard from community members that it is difficult to understand how to participate in GBFS development. MobilityData is re-evaluating the governance and trying to make it as easy as possible for someone to participate and to understand their role as a contributor as well as MobilityData's role as a maintainer.

This first modification does not change any governance process (and therefore does not require a vote), it simply moves the governance to it's own page (governance.md) on the repository and shows a more simple version of the governance on the README.md.

In the coming weeks we will work to improve the layout of governance.md and propose any changes to the governance if need be.

josee-sabourin and others added 2 commits July 12, 2023 10:46
@mplsmitch
Copy link
Collaborator

I'm totally in favor of moving the governance to a separate document. The README needs frequent updates to things like current versions etc. that don't need to be voted on whereas any change to the governance should require a vote. Having the governance in a separate document will help with that.

I think the proposed README text could be more concise. There's some redundancy between the bullet points and the paragraph above. Here's what I would suggest:

Comments or questions can be addressed to the community by opening an issue. Proposals for changes or additions to the specification can be made through pull requests. Questions can also be addressed to the community via the public GBFS Slack channel or to the shared mobility staff at MobilityData: sharedmobility@mobilitydata.org.

Proposing a Change

  • Anyone can propose a change to the specification by opening a pull request.
  • Proposed changes should align with the Guiding Principles.
  • All changes are subject to a vote.
  • A proposal passes if there are at least 3 votes in favor and none opposed, with at least one vote from a GBFS producer, and one from a GBFS consumer.
  • Anyone can vote.

If you would like to propose a change but aren’t comfortable opening a pull request, MobilityData is happy to help. Get in touch at sharedmobility@mobilitydata.org.

For more information on the specification governance, including instructions on how and when to call a vote, see governance.md

Find a real-world example of the governance in action here.

README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
governance.md Outdated Show resolved Hide resolved
Co-authored-by: Fabien Richard-Allouard <fabien@mobilitydata.org>
README.md Outdated Show resolved Hide resolved
Copy link
Contributor

@richfab richfab left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Added one small formatting suggestion.

Co-authored-by: Fabien Richard-Allouard <fabien@mobilitydata.org>
Copy link
Contributor

@richfab richfab left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 🚀

@josee-sabourin josee-sabourin merged commit 35908bd into master Aug 2, 2023
1 check passed
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.

3 participants