Merge pull request #544 from openmobilityfoundation/release-1.0.0

Release Candidate 1.0.0

Author: schnuerle

.github/PULL_REQUEST_TEMPLATE/default.md

@@ -0,0 +1,41 @@
+---
+name: Default
+about: Suggest changes to MDS
+title: <Insert Title>
+
+---
+
+# MDS Pull Request
+
+Thank you for your contribution!  Please review our OMF [contributing page](https://github.com/openmobilityfoundation/governance/blob/main/CONTRIBUTING.md) to understand guidelines and policies for participation, and our [Code of Conduct page](https://github.com/openmobilityfoundation/governance/blob/main/CODE_OF_CONDUCT.md).
+
+To avoid complications and help make the Review process as smooth as possible, make sure to:
+
+1. Target [**`dev`**](https://github.com/openmobilityfoundation/mobility-data-specification/tree/dev) branch. Please ensure you are targeting **`dev`**, not **`main`**. 
+1. Keep the *"Allow edits from maintainers"* button checked to help us resolve some issues for you.
+1. Be ready to resolve any merge conflicts before we approve your Pull Request.
+1. Have an up to date profile, per our Github [community profile](https://github.com/openmobilityfoundation/governance/blob/main/CONTRIBUTING.md#community-profile) guildance.
+
+## 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/pull_request_template.md

@@ -15,4 +15,4 @@ Please use this pull request to track Technology Council and OMF Board feedback
 
 ### 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).
+This pull request will be merged by an OMF maintainer after OMF Board Approval following the [Release Guidelines](https://github.com/openmobilityfoundation/governance/blob/main/technical/ReleaseGuidelines.md#making-a-release).

.github/PULL_REQUEST_TEMPLATE/release-candidate.md

@@ -0,0 +1,41 @@
+---
+name: Default
+about: Suggest changes to MDS
+title: <Insert Title>
+
+---
+
+# MDS Pull Request
+
+Thank you for your contribution!  Please review our OMF [contributing page](https://github.com/openmobilityfoundation/governance/blob/main/CONTRIBUTING.md) to understand guidelines and policies for participation, and our [Code of Conduct page](https://github.com/openmobilityfoundation/governance/blob/main/CODE_OF_CONDUCT.md).
+
+To avoid complications and help make the Review process as smooth as possible, make sure to:
+
+1. Target [**`dev`**](https://github.com/openmobilityfoundation/mobility-data-specification/tree/dev) branch. Please ensure you are targeting **`dev`**, not **`main`**. 
+1. Keep the *"Allow edits from maintainers"* button checked to help us resolve some issues for you.
+1. Be ready to resolve any merge conflicts before we approve your Pull Request.
+1. Have an up to date profile, per our Github [community profile](https://github.com/openmobilityfoundation/governance/blob/main/CONTRIBUTING.md#community-profile) guildance.
+
+## 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-final.md

@@ -1 +1,4 @@
-.venv/
+.venv/
+.vscode
+.DS_Store
+__pycache__

.github/pull_request_template.md

@@ -1,13 +1,3 @@
 # Code of Conduct
 
-To encourage participation by any and all interested people, we aim to create an open and welcoming environment for contributors. We pledge to make participation in this project a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
-
-**Examples of behavior that contributes to creating a positive environment include:**
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
-
-Please review the [OMF's Participation Policies](https://members.openmobilityfoundation.org/wp-content/uploads/2019/06/OMFParticipationPolicies.pdf) for more details.
+Particpation with the OMF is governed by the OMF's [Code of Conduct](https://github.com/openmobilityfoundation/governance/blob/main/CODE_OF_CONDUCT.md) and [Participation Policies](https://github.com/openmobilityfoundation/governance/raw/main/documents/OMFParticipationPolicies.pdf).

.gitignore

@@ -1,31 +1,3 @@
 # 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.
-
-* **Mobility Service Providers:** Providers are often required to implement MDS in order to comply with permitting requirements for their services. Providers can inform the development of MDS with real-world operating experience and to offer input on specification design that maximizes data quality, reliability, and utility.
-
-* **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).
+**See the new [MDS Contributor Guidelines](https://github.com/openmobilityfoundation/governance/blob/main/CONTRIBUTING.md) document for details.**