openmobilityfoundation / governance Goto Github PK

The index pages for both repos still point to the Google Doc version of privacy guide, instead of to the final PDF.

We currently have three requirements for items that live in the repo:

• Are 100% public facing.
• Are not managed directly by WG or Committee leaders
• Are relevant to more than one OMF repo/committee/group

Would suggest replacing the 2nd and 3rd bullet with

• Are not better suited for a WG or Committee-specific repo

Reasons being that some Committees (like Strategy) may want to publish into this repo rather than have their own, and there may be some topics (ex: guidance on using the Policy API) that are specific to a particular repo/WG, but which don't belong as part of the spec.

I suggest we rename our 'master' branches to 'main' (or 'default').

The term master, with its association to slavery, is offensive to many people. As a name, it is no more descriptive or useful than the more neutral alternatives. I don't believe that renaming will create any significant issues for MDS users or contributors.

For more on the topic:
https://www.zdnet.com/article/github-to-replace-master-with-alternative-term-to-avoid-slavery-references/

It may be useful for this document to be extended to explicitly map GBFS fields to /vehicles, and to provide guidance that suggests the use of /vehicles as an alternative to GBFS in regulatory contexts. Had initial discussion with @heidiguenin and @schnuerle. Will continue to discuss as we speak with the GBFS and MDS communities and learn more about what would be most valuable.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I wish this had a [...]

Hard to find OMF documents.

Describe the solution you'd like
A clear and concise description of what you want to happen.

Move PDFs from website to here in Github in a 'documents' folder. Point website links here.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Leave as is.

Additional context
Add any other context or screenshots about the feature request here. Links are helpful too.

Link to current location in Wordpress. https://www.openmobilityfoundation.org/resources/

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I wish this had a [...]

Redundant locations for organization documents.

Describe the solution you'd like
A clear and concise description of what you want to happen.

Would like to redirect/point instances of the code of conduct, license, contributing guide in other areas (website, mds repo, etc) to the new locations here (once this repo is public).

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

We could leaving multiple copies of each, but that's not good for maintaining. We could put official copies on website, but we'd like version control.

Additional context
Add any other context or screenshots about the feature request here. Links are helpful too.

N/A