honestly, i like redmine
and i have the same doubts of stephdl about putting all on cloud.
but at the same time i like the idea to have all in one place, and a lot of interesting project are there (like elk and docker) with issues and wiki…
some doubts:
quoting stephdl: “Indeed I follow now one channel, Redmine, but if each rpm tracks its own issues in github, how you can follow all issues of the project. I must admit that I don’t know if you can register to all bugs coming from the nethserver Git.”
sometimes the issues section on github is used like a forum getting as results that after some time you’ll have a lot of open issues…
From what i’ve seen (but i’m not a github expert) the wiki is per repository… maybe it’s too much fragmented to be a useful wiki?
but after all i think it could be a good move, specially if it make devs life easier (so they will have more time to add features to nethserver )
I’m not very much into nethserver and its redmine but i can add my 2c as a developer:
moving to github is probably the best move to maximize contributions and visibility
the main concern i heard in similar cases is the portability of github issues: we need to import old issues? can we export all the data in the future? it’s easy?
Ehi @Alessandro_Lepore thanks for your 2c, really happy to have you here, could I ask you to reply to this topic? I’m really curious about your developer opinion.
Please, enlighten me: how it can maximize contributions? which kind of github features make the difference?
You will automatically watch any repositories you create or that are created by your team in an organization. If you are part of the NethServer team don’t need to subscribe repository one by one
yes, it seems fair, also if i am still a little bit skeptical, but probably becouse i’ve never used it and it seems a little different from “normal” wiki like moinmon/doku/mediawiki
ok, but there aren’t many levels of permission… are they enough?
“Available for QA,” “QA Pass,” and “QA Fail.” As soon as code is moved to the dev environment, the “Available for QA” label is applied and that process kicks off.
The team documents the steps taken to QA the update and then applies the appropriate tag. When reviewing a Milestone for a push to production, it’s now very easy to see the QA status of each issue, for the whole team to review (and potentially improve upon) the steps taken in QA, as well as review any issues. All of our code, status, and feedback is even more consolidated than before.
I’m experimenting a migration path from Redmine to GitHub. This is a brief list:
Any ON_DEV, MODIFIED, VERIFIED issue on dev.nethserver.org should complete the natural development process, towards the CLOSED state.
Any NEW and TRIAGED issue is migrated to GitHub and closed as DUPLICATE on dev.nethserver.org. A link is added to the issue description, to preserve the original reference. Around ~100 issues are currently on these states.
Search filters are very powerful. We could save some searches on the wiki, or on the main web site. For instance: all open bugs. I’d like to migrate also other pages from the Redmine wiki, such as Releases.
as always , thank you for your work , but … can i create the QA label ?
does this means that from now a new issue has to be created directly on github or always on redmine ?
yes and ofcourse i’ve joined…what I meant was that it lacked the label QA , so i’ve added it , also on waffle …
i hope to have some time to play with issues/waffle in next days