-
Notifications
You must be signed in to change notification settings - Fork 19
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #35 from openmobilityfoundation/feature-release-wo…
…rk-1 Work for CDS Release Candidate, ready for dev
- Loading branch information
Showing
16 changed files
with
1,294 additions
and
322 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
--- | ||
name: Add Provider ID | ||
about: Create Provider ID for use in CDS | ||
title: 'Add Provider ID: [Provider Name]' | ||
labels: admin,identifier change | ||
assignees: '' | ||
|
||
--- | ||
|
||
**Note:** See the [Adding a CDS Provider ID](https://github.com/openmobilityfoundation/curb-data-specification/wiki/Adding-a-CDS-Provider-ID) page for more help. | ||
|
||
Opening this issue will allow you as a mobility service provider get an official provider ID for use across CDS globally. | ||
|
||
**Fields needed from you for the [providers.csv file](https://github.com/openmobilityfoundation/curb -data-specification/blob/main/providers.csv).** | ||
|
||
_All fields are required._ | ||
|
||
1. **provider_name** - Short name of your company. | ||
- ... | ||
1. **provider_id** - A random UUID version 4. There are lots of way to generate a unique UUID, like using this [website](https://www.uuidgenerator.net/version4). | ||
- ... | ||
1. **url** - URL to the home page of your company. | ||
|
||
Additionally, please provide your name and role within your agency to help with verification. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,40 @@ | ||
--- | ||
name: Feature request / proposal | ||
about: Suggest an idea for this project | ||
title: '' | ||
labels: '' | ||
assignees: '' | ||
|
||
--- | ||
|
||
### Is your feature request related to a problem? Please describe. | ||
|
||
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] | ||
|
||
### Describe the solution you'd like | ||
|
||
A clear and concise description of what you want to happen. | ||
|
||
### Is this a breaking change | ||
|
||
A breaking change would require consumers or implementors of an 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 | ||
|
||
For which spec is this feature being requested? | ||
|
||
* `Curbs` | ||
* `Events` | ||
* `Metrics` | ||
|
||
### Describe alternatives you've considered | ||
|
||
A clear and concise description of any alternative solutions or features you've considered. | ||
|
||
### Additional context | ||
|
||
Add any other context or screenshots about the feature request here. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,41 @@ | ||
--- | ||
name: Default | ||
about: Suggest changes to CDS | ||
title: <Insert Title> | ||
|
||
--- | ||
|
||
# CDS 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/curb-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 API(s) will this pull request impact? | ||
|
||
* `Curbs` | ||
* `Events` | ||
* `Metrics` | ||
|
||
## Additional context | ||
|
||
Add any other context or screenshots about the feature request here. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
--- | ||
name: Release Candidate | ||
about: Initiate discussion to obtain OMF approval for new release | ||
title: Release Candidate [X.Y.Z] | ||
labels: admin | ||
|
||
--- | ||
|
||
### Summary | ||
|
||
The Release Candidate for CDS `X.Y.Z` has been submitted: <https://github.com/openmobilityfoundation/curb-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/governance/blob/main/technical/ReleaseGuidelines.md#making-a-release). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,41 @@ | ||
--- | ||
name: Default | ||
about: Suggest changes to CDS | ||
title: <Insert Title> | ||
|
||
--- | ||
|
||
# CDS 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/curb-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 API(s) will this pull request impact? | ||
|
||
* `Curbs` | ||
* `Events` | ||
* `Metrics` | ||
|
||
## Additional context | ||
|
||
Add any other context or screenshots about the feature request here. |
Validating CODEOWNERS rules …
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,7 @@ | ||
## Below is the MDS CODEOWNERS file, which dictates who is required for review on any given file. | ||
## Below is the CDS CODEOWNERS file, which dictates who is required for review on any given file. | ||
|
||
## All MDS approvals | ||
## All CDS approvals | ||
* @openmobilityfoundation/omf-admin | ||
|
||
## CDS Working Group | ||
* @openmobilityfoundation/cds-maintainers @openmobilityfoundation/omf-admin |
Oops, something went wrong.