-
Notifications
You must be signed in to change notification settings - Fork 2
Issue Tracker
The GeoStack Project edited this page Oct 8, 2020
·
9 revisions
GeoStack - Issue Tracker
This is the 'How-To' page for the project's Issue Tracker in case you want to post an issue ticket!
IMPORTANT NOTES
- There is only one Issue Tracker for all the GeoStack repositories.
- Use the correct label to classify your issue ticket!
- Allow 5 - 10 work days to respond: the project team members do not monitor the issue tracker every day!
Overview Issue Labels --> To post new tickets!
- Help - For support with problems when studying the GeoStack Workshop or Course.
- BUG - To report an actual or suspected software problem to fix or investigate.
- FIX - To report something small in the Software or Documentation to fix. E.g. a typo, web link, comment etc.
- Software - For questions and improvements to existing software.
- Documentation - For questions and improvements to existing documentation.
- Datasets - For questions and improvements on the project's datasets.
- Websites - For questions and improvements to the project's web pages on GitHub and the YouTube channel.
- Multimedia - For questions and improvements to the project's videos, photos, images, audio etc.
- Release - For questions or information about a release of the project.
- Request - To submit a feature requests to improve or add new things in future releases. Check the wiki page PEP first!
- Legal - For questions about the legal information, licenses, re-use etc.
- Question - For all other questions! Check the FAQ first!
- Contact - To request contact with one of the team members if submitting an issue ticket is not a suitable way for your issue.
Overview of Issue Labels --> For re-labeling by the project team only!
- Duplicate - Your ticket can be re-labeled as a 'Duplicate' if there is already an existing ticket for your subject.
- The web link to the existing ticket will be added to your ticket and then your ticket will be closed.
- NoFix - Your ticket can be re-labeled as a 'NoFix' because the issue you reported can not be fixed or realized for some reason.
- The reason why will be added to your ticket and then your ticket will be closed.
- PEP - Your 'Request' or any other ticket can be re-labeled to 'PEP' as a Project Enhancement Proposal to implement in a future release.
- If there are additional notes to the PEP that are not in the ticket then a web link is added to the ticket to the corresponding PEP content item on the wiki page PEP!
- The ticket will be closed when it is completed for the future release.