https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22487 --- Comment #1 from Jonathan Druart <jonathan.druart@bugs.koha-community.org> --- About Bugzilla: "Project infrastructure > Bugzilla" ? About Mana: "Koha > Mana" (i.e. Mana code integreated to Koha) or you are talking about the server code? -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22487 Jonathan Druart <jonathan.druart@bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Release tools |Bugzilla --- Comment #3 from Jonathan Druart <jonathan.druart@bugs.koha-community.org> --- (In reply to Katrin Fischer from comment #2)

yes, Project infrastructure > Bugzilla

Done! -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22487 --- Comment #5 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- (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. -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22487 --- Comment #7 from Jonathan Druart <jonathan.druart@bugs.koha-community.org> --- (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? -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22487 --- Comment #8 from Paul Poulain <paul.poulain@biblibre.com> --- 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. -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22487 Paul Poulain <paul.poulain@biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alex.arnaud@biblibre.com --- Comment #10 from Paul Poulain <paul.poulain@biblibre.com> --- 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. -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22487 --- Comment #12 from Jonathan Druart <jonathan.druart@bugs.koha-community.org> --- (In reply to Jonathan Druart from comment #11)

I am going to create koha-mana on gitlab.

https://gitlab.com/koha-community/koha-mana -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22487 --- Comment #14 from Martin Renvoize <martin.renvoize@ptfs-europe.com> --- Thanks guys, this really looks like it's moving in the right directions now. :) -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22487 Jonathan Druart <jonathan.druart@bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |--- Status|RESOLVED |REOPENED --- Comment #15 from Jonathan Druart <jonathan.druart@bugs.koha-community.org> --- (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? -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22487 --- Comment #16 from Paul Poulain <paul.poulain@biblibre.com> --- It just seemed to me to be more logical. And that does not make a big difference. -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22487 Jonathan Druart <jonathan.druart@bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|In Discussion |RESOLVED --- Comment #18 from Jonathan Druart <jonathan.druart@bugs.koha-community.org> --- 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. -- You are receiving this mail because: You are watching all bug changes.