Skip to content

Commit 1cab312

Browse files
schnuerleschnuerle
authored
Merge pull request #35 from openmobilityfoundation/feature-release-work-1
Work for CDS Release Candidate, ready for dev
2 parents c1723ad + 63597d1 commit 1cab312

File tree

16 files changed

+1294
-322
lines changed

16 files changed

+1294
-322
lines changed

‎.github/ISSUE_TEMPLATE/add-provider-id.md‎

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
---
2+
name: Add Provider ID
3+
about: Create Provider ID for use in CDS
4+
title: 'Add Provider ID: [Provider Name]'
5+
labels: admin,identifier change
6+
assignees: ''
7+
8+
---
9+
10+
**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.
11+
12+
Opening this issue will allow you as a mobility service provider get an official provider ID for use across CDS globally.
13+
14+
**Fields needed from you for the [providers.csv file](https://github.com/openmobilityfoundation/curb -data-specification/blob/main/providers.csv).**
15+
16+
_All fields are required._
17+
18+
1. **provider_name** - Short name of your company.
19+
- ...
20+
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).
21+
- ...
22+
1. **url** - URL to the home page of your company.
23+
24+
Additionally, please provide your name and role within your agency to help with verification.

‎.github/ISSUE_TEMPLATE/feature-request.md‎

Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
---
2+
name: Feature request / proposal
3+
about: Suggest an idea for this project
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
### Is your feature request related to a problem? Please describe.
11+
12+
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
13+
14+
### Describe the solution you'd like
15+
16+
A clear and concise description of what you want to happen.
17+
18+
### Is this a breaking change
19+
20+
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).
21+
22+
* Yes, breaking
23+
* No, not breaking
24+
* I'm not sure
25+
26+
### Impacted Spec
27+
28+
For which spec is this feature being requested?
29+
30+
* `Curbs`
31+
* `Events`
32+
* `Metrics`
33+
34+
### Describe alternatives you've considered
35+
36+
A clear and concise description of any alternative solutions or features you've considered.
37+
38+
### Additional context
39+
40+
Add any other context or screenshots about the feature request here.

‎.github/PULL_REQUEST_TEMPLATE/pull_request_template.md‎

Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
---
2+
name: Default
3+
about: Suggest changes to CDS
4+
title: <Insert Title>
5+
6+
---
7+
8+
# CDS Pull Request
9+
10+
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).
11+
12+
To avoid complications and help make the Review process as smooth as possible, make sure to:
13+
14+
1. Target [**`dev`**](https://github.com/openmobilityfoundation/curb-data-specification/tree/dev) branch. Please ensure you are targeting **`dev`**, not **`main`**.
15+
1. Keep the *"Allow edits from maintainers"* button checked to help us resolve some issues for you.
16+
1. Be ready to resolve any merge conflicts before we approve your Pull Request.
17+
1. Have an up to date profile, per our Github [community profile](https://github.com/openmobilityfoundation/governance/blob/main/CONTRIBUTING.md#community-profile) guildance.
18+
19+
## Explain pull request
20+
21+
Please provide a clear and concise reason for this pull request and the impact of the change
22+
23+
## Is this a breaking change
24+
25+
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).
26+
27+
* Yes, breaking
28+
* No, not breaking
29+
* I'm not sure
30+
31+
## Impacted Spec
32+
33+
Which API(s) will this pull request impact?
34+
35+
* `Curbs`
36+
* `Events`
37+
* `Metrics`
38+
39+
## Additional context
40+
41+
Add any other context or screenshots about the feature request here.

‎.github/PULL_REQUEST_TEMPLATE/release-candidate.md‎

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
---
2+
name: Release Candidate
3+
about: Initiate discussion to obtain OMF approval for new release
4+
title: Release Candidate [X.Y.Z]
5+
labels: admin
6+
7+
---
8+
9+
### Summary
10+
11+
The Release Candidate for CDS `X.Y.Z` has been submitted: <https://github.com/openmobilityfoundation/curb-data-specification/releases/tag/X.Y.Z-rc>
12+
13+
Please use this pull request to track Technology Council and OMF Board feedback and/or requested changes.
14+
15+
### Action Item
16+
17+
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.md‎

Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
---
2+
name: Default
3+
about: Suggest changes to CDS
4+
title: <Insert Title>
5+
6+
---
7+
8+
# CDS Pull Request
9+
10+
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).
11+
12+
To avoid complications and help make the Review process as smooth as possible, make sure to:
13+
14+
1. Target [**`dev`**](https://github.com/openmobilityfoundation/curb-data-specification/tree/dev) branch. Please ensure you are targeting **`dev`**, not **`main`**.
15+
1. Keep the *"Allow edits from maintainers"* button checked to help us resolve some issues for you.
16+
1. Be ready to resolve any merge conflicts before we approve your Pull Request.
17+
1. Have an up to date profile, per our Github [community profile](https://github.com/openmobilityfoundation/governance/blob/main/CONTRIBUTING.md#community-profile) guildance.
18+
19+
## Explain pull request
20+
21+
Please provide a clear and concise reason for this pull request and the impact of the change
22+
23+
## Is this a breaking change
24+
25+
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).
26+
27+
* Yes, breaking
28+
* No, not breaking
29+
* I'm not sure
30+
31+
## Impacted Spec
32+
33+
Which API(s) will this pull request impact?
34+
35+
* `Curbs`
36+
* `Events`
37+
* `Metrics`
38+
39+
## Additional context
40+
41+
Add any other context or screenshots about the feature request here.

‎CODEOWNERS‎

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,7 @@
1-
## Below is the MDS CODEOWNERS file, which dictates who is required for review on any given file.
1+
## Below is the CDS CODEOWNERS file, which dictates who is required for review on any given file.
22

3-
## All MDS approvals
3+
## All CDS approvals
44
* @openmobilityfoundation/omf-admin
5+
6+
## CDS Working Group
7+
* @openmobilityfoundation/cds-maintainers @openmobilityfoundation/omf-admin

0 commit comments

Comments
 (0)