sharpetronics/QGIS
1
0
Fork 0
mirror of https://github.com/qgis/QGIS.git synced 2025-06-22 00:02:40 -04:00
Code Issues Packages Projects Releases Wiki Activity

fix form and some more details

Vincent Picavet 2018-02-21 17:48:22 +01:00
parent a555ada6d2
commit 7a1a914d1c
1 changed files with 25 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

46
QGISbugtracker.md

@ -1,4 +1,5 @@
Questions to be tackled : ## Questions to be tackled
- Keeping history or not ? - Keeping history or not ?
- Plan for actions with detailed migration work and associated person in charge - Plan for actions with detailed migration work and associated person in charge
- Agenda : are we really in a hurry ? - Agenda : are we really in a hurry ?
@ -27,22 +28,22 @@ Questions to be tackled :
- roadmap items ( = milestones) - roadmap items ( = milestones)
- notifications parameters for each issue/user - notifications parameters for each issue/user
Options: ## Options
- Status QUO: we stay with RedMine and just live on as we do now - A/ Status QUO: we stay with RedMine and just live on as we do now
- Move to hosted Github and try to export/copy current issues from Redmine to Github - B/ Move to hosted GitHub and try to export/copy current issues from Redmine to Github
- Move to hosted Github BUT only for QGIS 3.0 issues (actually start with a clean sheet), making Redmine readonly OR only accept 2.x issues from now on (and tell 3.0 issues to move to Github - C/ Move to hosted GitHub BUT only for QGIS 3.0 issues (actually start with a clean sheet), making Redmine readonly
- D/ Move to hosted GitHub BUT only for QGIS 3.0 issues (actually start with a clean sheet), making Redmine only accept 2.x issues from now on (and tell 3.0 issues to move to Github)
- E/ Move to hosted Gitlab.com and try to export/copy current issues from Redmine to Gitlab
- F/ Host Gitlab ourselves and try to export/copy current issues from Redmine to Gitlab
- G/ Move to hosted Gitlab and try to export/copy BUT only for QGIS 3.0 issues (actually start with a clean sheet), making Redmine readonly
- H/ Move to hosted Gitlab and try to export/copy BUT only for QGIS 3.0 issues (actually start with a clean sheet), making only accept 2.x issues from now on (and tell 3.0 issues to move to Github)
- I/ Host Gitlab ourselves and try to export/copy BUT only for QGIS 3.0 issues (actually start with a clean sheet), making Redmine readonly
- J/ Host Gitlab ourselves and try to export/copy BUT only for QGIS 3.0 issues (actually start with a clean sheet), making only accept 2.x issues from now on (and tell 3.0 issues to move to Github)
??? (not sure if these are options).... ## Analysis of options
- Move to hosted Gitlab and try to export/copy current issues from Redmine to Gitlab ### Stay with Redmine
- Host Gitlab ourselves and try to export/copy current issues from Redmine to Gitlab
- Move to hosted Gitlab and try to export/copy BUT only for QGIS 3.0 issues (actually start with a clean sheet), making Redmine readonly OR only accept 2.x issues from now on (and tell 3.0 issues to move to Github
- Host Gitlab ourselves and try to export/copy BUT only for QGIS 3.0 issues (actually start with a clean sheet), making Redmine readonly OR only accept 2.x issues from now on (and tell 3.0 issues to move to Github
Stay with Redmine
=================
PRO: PRO:
- ready and working now - ready and working now
@ -53,13 +54,12 @@ AGAINST:
- not user friendly enough? - not user friendly enough?
Move to Github ### Move to Github
==============
PRO: PRO:
- we will have one system for both code and issues - we will have one system for both code and issues
- free (as in beer) system, without need of hosting it - free (as in beer) system, without need of hosting it
- Github promisses easy path to GitLAB in case of move - Github promises easy path to GitLAB in case of move
AGAINST: AGAINST:
- closed system - closed system
@ -70,14 +70,18 @@ AGAINST:
??? (or keep this option out for this discussion) ??? ??? (or keep this option out for this discussion) ???
Move to Gitlab ### Move to Gitlab
==============
PRO: PRO:
- we could host it ourselves, OR start with hosted version - we could host it ourselves, OR start with hosted version
- more open the Github - OpenSource version ( community edition )
- Easy install ( Docker )
- Dynamic development
- Very good and powerful CI infrastructure
- Gitlab.com allows connecting with GitHub account ( and others )
- Migration tools available
AGAINST: AGAINST:
- less known/advanced then Github? - less known/advanced then Github?
- - Some features are Enterprise-version only ( OpenCore model)