sharpetronics/QGIS
1
0
Fork 0
mirror of https://github.com/qgis/QGIS.git synced 2025-08-11 00:03:56 -04:00
Code Issues Packages Projects Releases Wiki Activity

Updated QGISbugtracker (markdown)

Tim Sutton 2018-02-21 19:08:51 +02:00
parent 7ca557d2ed
commit 89e191daea
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
QGISbugtracker.md

@ -85,7 +85,9 @@ PRO:
AGAINST: AGAINST:
- less known than Github ? - less known than Github ?
- Some features are Enterprise-version only ( OpenCore model) - Some features are Enterprise-version only ( OpenCore model)
- This is not simply moving our issue tracker - it involves moving our code too
- GitHub is already working well for us for many years with no issues, switching to a new infrastructure creates a lot of flux with no obvious benefit. Our time, money and resources are better spent on our code not on our infrastructure
- Philosopy: Do we really required that everything we use is FOSS? Many (thousands) of OpenSource projects happily use GitHub to host their code without them percieving that their 'open sourceness' is 'diluted'.
- **IMPORTANT AND IGNORED IN THE DISCUSSION SO FAR**: Splintering of resources - we have many repos on GitHub - are we going to move them all? it makes the scope of the task huge. - **IMPORTANT AND IGNORED IN THE DISCUSSION SO FAR**: Splintering of resources - we have many repos on GitHub - are we going to move them all? it makes the scope of the task huge.
- **IMPORTANT AND IGNORED IN THE DISCUSSION SO FAR**: Breaking existing workflows - if we migrate fully to GitLab we need to migrate many other things - commit hooks, CI, all sorts of things people have set up based on the current locations of the source. - **IMPORTANT AND IGNORED IN THE DISCUSSION SO FAR**: Breaking existing workflows - if we migrate fully to GitLab we need to migrate many other things - commit hooks, CI, all sorts of things people have set up based on the current locations of the source.
- have to come up with a plan to handle 'tagging'/tagging system of issues to be able to search tickets? I started with some idea in 2015: https://github.com/rduivenvoorde/temp/issues - have to come up with a plan to handle 'tagging'/tagging system of issues to be able to search tickets? I started with some idea in 2015: https://github.com/rduivenvoorde/temp/issues