In order to be able to report bugs against Mana and Bugzilla, it would be nice if this components could be added.
About Bugzilla: "Project infrastructure > Bugzilla" ? About Mana: "Koha > Mana" (i.e. Mana code integreated to Koha) or you are talking about the server code?
Hi Jonathan, yes, Project infrastructure > Bugzilla For Mana I was thinking of the code outside of Koha. Not sure how to handle that best. I wanted to report 'improve the email sent by Mana' (bug 22488)
(In reply to Katrin Fischer from comment #2) > yes, Project infrastructure > Bugzilla Done!
(In reply to Katrin Fischer from comment #2) > For Mana I was thinking of the code outside of Koha. Not sure how to handle > that best. I wanted to report 'improve the email sent by Mana' (bug 22488) The code is at https://git.biblibre.com/biblibre/koha-mana and, I think, should be moved to gitlab. And so we would use the bug tracker of the project.
(In reply to Jonathan Druart from comment #4) > (In reply to Katrin Fischer from comment #2) > > For Mana I was thinking of the code outside of Koha. Not sure how to handle > > that best. I wanted to report 'improve the email sent by Mana' (bug 22488) > > The code is at https://git.biblibre.com/biblibre/koha-mana and, I think, > should be moved to gitlab. And so we would use the bug tracker of the > project. Agreed, we should move it to the central repository as a community project. I'd be ok with using the issue tracker too, but in the past we have made a point about not forcing users to have many accounts. Keeping an option to report here too might be in line with that.
We have various side projects popping up these days.. and like that they're getting centralised onto gitlab but I do wonder how the community should be involved in their maintenance. I agree it's a good idea to have a project here for them so we're able to keep track of them in one place.. but whose role is it to SO, QA, and Release such fixes into the wild..? Should it fall to the same team or should there be some roles with a subteam.. Mana feels especially important to get right as it could end up tracking the Koha release cycle as we add features to it and add support for them in Koha.
(In reply to Martin Renvoize from comment #6) > We have various side projects popping up these days.. and like that they're > getting centralised onto gitlab but I do wonder how the community should be > involved in their maintenance. I agree it's a good idea to have a project > here for them so we're able to keep track of them in one place.. but whose > role is it to SO, QA, and Release such fixes into the wild..? > > Should it fall to the same team or should there be some roles with a > subteam.. Mana feels especially important to get right as it could end up > tracking the Koha release cycle as we add features to it and add support for > them in Koha. In my understanding if the community decides to integrate a project (Mana, Hea, etc.), they have to maintain/keep an eye on it (server-side as well). Could be good to discuss that in dev meeting?
I'm semi-fine with having Mana being integrated into Koha general infrastructure: * pro => the infrastructure already exist. I don't want this project to appear as a "BibLibre project" * cons => I see mana as a central point for sharing things that could be used by other software. For example: - use mana-kb in Coral to share licenses (onix-pl) and resources (kbart) - use mana-kb in Urungi to share layers and dashboards/reports moving mana to gitlab means "linking" mana-kb & Koha in many ppl's mind. So harder to expand it to other software. Both pro & cons are interesting and legit. My final opinion is not made.
(In reply to Paul Poulain from comment #8) > I'm semi-fine with having Mana being integrated into Koha general > infrastructure: > * pro => the infrastructure already exist. I don't want this project to > appear as a "BibLibre project" > * cons => I see mana as a central point for sharing things that could be > used by other software. For example: > - use mana-kb in Coral to share licenses (onix-pl) and resources (kbart) > - use mana-kb in Urungi to share layers and dashboards/reports > moving mana to gitlab means "linking" mana-kb & Koha in many ppl's mind. So > harder to expand it to other software. > > Both pro & cons are interesting and legit. My final opinion is not made. I am not insisting on Bugzilla or some other place, but I think we should have a clear workflow on where to report enhancements and bugs :) That said I would love some feedback on the open Mana bug reports, currently all linked to bug 17047. Especially bug 22210.
OK, got it and agreed regarding the bugzilla suggestion Product "mana-kb" created, with one component (mana-kb server) default assignee = koha-bugs Regarding a move to git.koha-community.org, I also agree. If the project needs to become independent one day, it will always be possible to move to mana-kb-project.org or something like that. I can't do that myself, so Joubu or Martin, feel free.
I am going to create koha-mana on gitlab.
(In reply to Jonathan Druart from comment #11) > I am going to create koha-mana on gitlab. https://gitlab.com/koha-community/koha-mana
(In reply to Paul Poulain from comment #10) > OK, got it and agreed regarding the bugzilla suggestion > > Product "mana-kb" created, with one component (mana-kb server) > default assignee = koha-bugs Why not just a component in Project infrastructure?
Thanks guys, this really looks like it's moving in the right directions now. :)
(In reply to Katrin Fischer from comment #13) > (In reply to Paul Poulain from comment #10) > > OK, got it and agreed regarding the bugzilla suggestion > > > > Product "mana-kb" created, with one component (mana-kb server) > > default assignee = koha-bugs > > Why not just a component in Project infrastructure? What about that, Paul?
It just seemed to me to be more logical. And that does not make a big difference.
(In reply to Paul Poulain from comment #16) > It just seemed to me to be more logical. And that does not make a big > difference. I don't mind much, it was just different to what I had in mind. I'd still really like to get a comment on bug 22210 from Biblibre.
Discussed during the last dev meeting: I moved the 4 bugs from the Mana-kb product to a new Project infrastructure > Mana-kb (server) Removed the Mana-kb product Then created a Koha > Mana-kb component for Mana related code inside Koha.