A quick update to let you know that we have:
- kohadevbox
- koha-testing-docker
- koha-release-notes
- release-tools
- koha-dashboard
- koha-manual (was kohadocs)
now moved to gitlab/koha-community

https://gitlab.com/koha-community
If you have the necessary permissions on former locations it may be great to mirror these new ones.
Or, mark them as "obsolete", for instance on https://gitlab.com/koha-community-devs-users/kohadocs/ I have blanked the README with a "This repository is obsolete" notice. Also the project as been marked as "archived" (gitlab feature IIRC)

On Tue, 23 Jan 2018 at 16:46 Jonathan Druart <jonathan.druart@bugs.koha-community.org> wrote:
Hi devs,

(Spoiler: I am not talking about a move from bugzilla to gitlab for the Koha git repo)

Just a quick comment: gitlab has the ability to move projects with all the issues.

From the export page of a project, they say:
"""
The following items will be exported:
Project and wiki repositories
Project uploads
Project configuration including web hooks and services
Issues with comments, merge requests with diffs and comments, labels, milestones, snippets, and other project entities
"""

So that will be easy to move (already discussed with Chris, will do in May)
* koha-community-devs-users/kohadocs to koha-community/kohadocs
* https://gitlab.com/koha-dashboard/koha-dashboard to koha-community/koha-dashboard

And the ones from github too:
* joubu/koha-misc4dev to koha-community/koha-misc4dev
* Koha-Community/qa-test-tools to koha-community/qa-test-tools

Then, maybe:
koha-testing-docker
koha-release-notes
kohadevbox
koha-howto

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'). I would also like to generate a CI configuration for some of them.
CI file for Koha: https://tree.taiga.io/project/joubu-koha-rm-1711/us/146 (I am going to submit that on bugzilla soon)

Any pros/cons?

Cheers,
Jonathan

(No troll please)