As I read it, Jonathan is proposing to move (centralize) some pieces of the Koha development ecosystem that are already handled in such ways, but disseminated in personal github/gitlab accounts. I agree with his proposal, and I like the fact that we can move all the issues along with the repo :-D (one of my issues with moving kohadevbox, that has more than 200 issues on its own). I also think Mark has a fair point regarding the QA process (even tough we are already working like that for those projects), and I'm sure this is a good chance to explore new additions to our workflow, and how our rigorous QA process can be adapted without loosing the abilities we already have. Awesome, Jonathan. Good one. +1 from me :-D El mar., 23 ene. 2018 a las 20:38, Mark Tompsett (<mtompset@hotmail.com>) escribió:
Greetings,
The idea is to centralize our things in one place, ease the PRs and the ability to clone/fork keeping the visibility on what is the reference (account 'koha-community').
+1 centralize.
(No troll please)
Hopefully this isn’t a troll. I’m a tad confused on the mechanics of the PRs though. At this point in time, with bugzilla, the notion of pull requests is irrelevant to the person looking for something to sign off, or perhaps even QA. How do we see the git bz / git push / git pull’s working as part of the larger approval flow?
GPML, Mark Tompsett _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
-- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F