-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
e9db206
commit 984ca20
Showing
1 changed file
with
16 additions
and
0 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,16 @@ | ||
--- | ||
name: Issue Template | ||
about: This template provides guidelines on how to structure an issue for the controlled-vocabularies | ||
repository | ||
title: "[CONTROLLED_VOCABULARY_NAME] My Issue Title" | ||
labels: '' | ||
assignees: marioscrock | ||
|
||
--- | ||
|
||
When adding a new issue, please specify the name of the controlled vocabulary you refer to by replacing the right value in the issue title between square brackets. | ||
Replace `CONTROLLED_VOCABULARY_NAME` with one of the following values: `application-layer-protocol`, `communication-method`, `conditions-for-access-and-usage`, `mobility-theme`, `mobility-data-standard`, `georeferencing-method`, `grammar`, `network-coverage`, ` intended-information-service`, `transport-mode`, `update-frequency`. If more than one values are applicable insert them in the title using an additional `[CONTROLLED_VOCABULARY_NAME]`. | ||
|
||
If the issue is generic and valid for all the controlled vocabularies, you can remove the part between square brackets. | ||
|
||
Provide a short title summarising the issue, and a full description of the use case and/or the proposal to be implemented. |