Merge pull request #8 from openmobilityfoundation/dev

catch up the lacuna-tech MDS repo to match latest-latest OMF

Author: Mark Maxham

.github/PULL_REQUEST_TEMPLATE/default.md

@@ -0,0 +1,36 @@
+---
+name: Default
+about: Suggest changes to MDS
+title: <Insert Title>
+
+---
+
+# MDS Pull Request
+
+Thank you for your contribution!
+
+*For most Pull Requests, the target branch should be [**`dev`**](https://github.com/openmobilityfoundation/mobility-data-specification/tree/dev). Please ensure you are targeting **`dev`** to avoid complications and help make the Review process as smooth as possible.*
+
+## Explain pull request
+
+Please provide a clear and concise reason for this pull request and the impact of the change
+
+## Is this a breaking change
+
+A breaking change would require consumers or implementors of the API to modify their code for it to continue to function (ex: renaming of a required field or the change in data type of an existing field). A non-breaking change would allow existing code to continue to function (ex: addition of an optional field or the creation of a new optional endpoint).
+
+* Yes, breaking
+* No, not breaking
+* I'm not sure
+
+## Impacted Spec
+
+Which spec(s) will this pull request impact?
+
+* `agency`
+* `policy`
+* `provider`
+
+## Additional context
+
+Add any other context or screenshots about the feature request here.

.github/PULL_REQUEST_TEMPLATE/release-candidate.md

@@ -0,0 +1,18 @@
+---
+name: Release Candidate
+about: Initiate discussion to obtain OMF approval for new release
+title: Release Candidate [X.Y.Z]
+labels: admin
+assignees: jfh01
+
+---
+
+### Summary
+
+The Release Candidate for MDS `X.Y.Z` has been submitted: <https://github.com/openmobilityfoundation/mobility-data-specification/releases/tag/X.Y.Z-rc>
+
+Please use this pull request to track Technology Council and OMF Board feedback and/or requested changes.
+
+### Action Item
+
+This pull request will be merged by an OMF maintainer after OMF Board Approval following the [Release Guidelines](https://github.com/openmobilityfoundation/mobility-data-specification/blob/master/ReleaseGuidelines.md#making-a-release).

.github/PULL_REQUEST_TEMPLATE/release-final.md

@@ -0,0 +1,18 @@
+---
+name: Release Final
+about: Finalize and publish an OMF approved release
+title: Release [X.Y.Z]
+labels: admin
+assignees: jfh01
+
+---
+
+### Summary
+
+The Release Candidate for MDS `X.Y.Z` has been approved: <https://github.com/openmobilityfoundation/mobility-data-specification/releases/tag/X.Y.Z-rc>
+
+This pull request will make the release official in `master`.
+
+### Action Item
+
+Merge this pull request following the [Release Guidelines](https://github.com/openmobilityfoundation/mobility-data-specification/blob/master/ReleaseGuidelines.md#making-a-release).

.github/pull_request_template.md

@@ -4,10 +4,11 @@
 * @openmobilityfoundation/omf-admin
 
 ## Provider Services Working Group
-/provider/* @openmobilityfoundation/provider-services-wg-maintainers @openmobilityfoundation/omf-admin
+/provider/* @openmobilityfoundation/provider-maintainers @openmobilityfoundation/omf-admin
 
 ## City Services Working Group Specific, also JSON Schema
-/agency/*  @openmobilityfoundation/city-services-wg-maintainers @openmobilityfoundation/omf-admin
+/agency/* @openmobilityfoundation/city-services-maintainers @openmobilityfoundation/omf-admin
+/policy/* @openmobilityfoundation/city-services-maintainers @openmobilityfoundation/omf-admin
 
 ## schema is changed by provider and city services working group
-/schema/*  @openmobilityfoundation/provider-services-wg-maintainers @openmobilityfoundation/city-services-wg-maintainers @openmobilityfoundation/omf-admin
+/schema/* @openmobilityfoundation/provider-maintainers @openmobilityfoundation/city-services-maintainers @openmobilityfoundation/omf-admin

CODEOWNERS

@@ -1,7 +1,9 @@
 # MDS Contributor Guidelines
+
 MDS is an evolving specification with a regular release cycle. Please review the [MDS Release Guidelines](ReleaseGuidelines.md) to understand the release process.
 
 ## Who can contribute
+
 MDS is an open specification and anyone can contribute to its development. Because MDS supports a growing ecosystem of mobility services, policies, and tools, there are some key stakeholders whose participation is particularly encouraged:
 
 * **Public agencies:** As licensing authority and regulator, public agencies are the ultimate customers for MDS and the data flowing through it. The public agency role is to ensure that MDS effectively supports program management and offers a flexible foundation for policy implementation. Public agencies of all levels of technical capacity are encourage to participate in the evolution of MDS, whether by submitting pull requests and issues, or simply by providing feedback during release cycles.
@@ -11,16 +13,19 @@ MDS is an open specification and anyone can contribute to its development. Becau
 * **Public agency software partners:** Serve as a key bridge between public agencies and mobility service providers by offering tools that turn MDS data into useful insights. The public agency software partners help ensure that MDS will enable real-world product development, reflects the needs of their public agency customers, and encourages private investment in the MDS ecosystem.
 
 ## How to contribute
+
 Contributions should be offered through GitHub issues and pull requests. Please review the [MDS Release Guidelines](ReleaseGuidelines.md) for details on the release process, schedule, and communications channels.
 
 In general, you may open an issue or make a pull request at any time. Once the issue or pull request is associated with a particular Milestone, it will be included for review within the process for that release.
 
 All contributors must agree to the Open Mobility Foundation's [Individual Contributor License Agreement](http://members.openmobilityfoundation.org/wp-content/uploads/2019/06/Individual-CLA.pdf) (ICLA) and [Participation Policies](https://members.openmobilityfoundation.org/wp-content/uploads/2019/06/OMFParticipationPolicies.pdf). Pull requests will not be merged without a signed ICLA. If a contributor is working on behalf of a company or other organization, that organization must also agree to the [Entity Contributor License Agreement](https://members.openmobilityfoundation.org/wp-content/uploads/2019/06/Entity-CLA.pdf) (ECLA). These agreements clarify the intellectual property status of work that is contributed to OMF projects. They apply to all contributions, including source code, documentation, and comments.
 
 ## What belongs in MDS
+
 MDS is a tool to facilitate data exchange between mobility service providers, public agencies, and public agency software partners. Although providers are often required to support MDS as part of mobility permits or policies, MDS is intended as a neutral mechanism for information exchange. It is not intended to force or foreclose any specific policy options that a public agency may choose to pursue.
 
 MDS is built as an interface between local governments and mobility service providers. Access to MDS APIs should be restricted, and is not intended to directly support public consumption or consumer-facing applications.
 
 ## Participation Policies and Code of Conduct
+
 See our [CODE OF CONDUCT page](CODE_OF_CONDUCT.md).

CONTRIBUTING.md

@@ -1,8 +1,8 @@
 # Mobility Data Specification
 
-The Mobility Data Specification (**MDS**), a project of the [Open Mobility Foundation](http://www.openmobilityfoundation.org) (OMF), is a set of Application Programming Interfaces (APIs) focused on dockless e-scooters, bicycles and carshare. Inspired by projects like [GTFS](https://developers.google.com/transit/gtfs/reference/) and [GBFS](https://github.com/NABSA/gbfs), the goals of MDS are to provide a standardized way for municipalities or other regulatory agencies to ingest, compare and analyze data from mobility service providers, and to give municipalities the ability to express regulation in machine-readable formats.
+The Mobility Data Specification (**MDS**), a project of the [Open Mobility Foundation](http://www.openmobilityfoundation.org) (OMF), is a set of Application Programming Interfaces (APIs) focused on dockless e-scooters, bicycles, mopeds and carshare. Inspired by projects like [GTFS](https://developers.google.com/transit/gtfs/reference/) and [GBFS](https://github.com/NABSA/gbfs), the goals of MDS are to provide a standardized way for municipalities or other regulatory agencies to ingest, compare and analyze data from mobility service providers, and to give municipalities the ability to express regulation in machine-readable formats.
 
-**MDS** helps cities interact with companies who operate dockless scooters, bicycles and carshare in the public right-of-way. MDS is a key piece of digital infrastructure that supports the effective implementation of mobility policies in cities around the world.
+**MDS** helps cities interact with companies who operate dockless scooters, bicycles, mopeds and carshare in the public right-of-way. MDS is a key piece of digital infrastructure that supports the effective implementation of mobility policies in cities around the world.
 
 **MDS** is an open-source project. It was originally created by the [Los Angeles Department of Transportation](http://ladot.io) (LADOT). In November 2019, stewardship of MDS and the ownership of this repository was transferred to the Open Mobility Foundation. GitHub automatically redirects any links to this repository in the `CityOfLosAngeles` organization to the `openmobilityfoundation` instead. MDS continues to be used by LADOT and many other municipalities.
 
@@ -16,6 +16,8 @@ The Mobility Data Specification (**MDS**), a project of the [Open Mobility Found
 
 MDS is designed to be a modular kit-of-parts. Regulatory agencies can use the components of the API that are appropriate for their needs. An agency may choose to use only `agency`, `provider`, or `policy`. Or they may select specific elements (endpoints) from each to help them implement their goals.
 
+You can read more about the different APIs here: **[Understanding the different MDS APIs](https://github.com/openmobilityfoundation/mobility-data-specification/wiki/Understanding-MDS-APIs)**
+
 ## Learn More / Get Involved / Contributing
 To stay up to date on MDS releases, meetings, and events, please **subscribe to the [mds-announce](https://groups.google.com/a/groups.openmobilityfoundation.org/forum/#!forum/mds-announce) mailing list.**
 
@@ -51,6 +53,7 @@ More than 80 cities and public agencies around the world use MDS, and it has bee
 * Santa Monica: The rules and guidelines for the Santa Monica Shared Mobility Pilot Program can be found at https://www.smgov.net/sharedmobility.
 * Austin: The rules and guidelines for Austin's Micromobility Program can be found at https://austintexas.gov/micromobility.
 * Ulm: A draft of the guidelines can be found at [the city's GitHub presence](https://github.com/stadtulm/mds-zonen).
+
 * _[add your City here by opening a pull request](https://github.com/openmobilityfoundation/mobility-data-specification/compare)_
 
 ## Use Cases