Centralize and move to gitlab

classic Classic list List threaded Threaded
17 messages Options
Reply | Threaded
Open this post in threaded view
|

Centralize and move to gitlab

Jonathan Druart
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)

_______________________________________________
Koha-devel mailing list
[hidden email]
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/
Reply | Threaded
Open this post in threaded view
|

Re: Centralize and move to gitlab

Mark Tompsett
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
[hidden email]
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/
Reply | Threaded
Open this post in threaded view
|

Re: Centralize and move to gitlab

Tomas Cohen Arazi
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 (<[hidden email]>) 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
[hidden email]
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)
✆ +54 9351 3513384
GPG: B2F3C15F

_______________________________________________
Koha-devel mailing list
[hidden email]
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/
Reply | Threaded
Open this post in threaded view
|

Re: Centralize and move to gitlab

Josef Moravec
+1 from me too ;)



st 24. 1. 2018 v 0:53 odesílatel Tomas Cohen Arazi <[hidden email]> napsal:
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 (<[hidden email]>) 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
[hidden email]
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)
✆ <a href="tel:+54%209%20351%20351-3384" value="+5493513513384" target="_blank">+54 9351 3513384
GPG: B2F3C15F
_______________________________________________
Koha-devel mailing list
[hidden email]
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/

_______________________________________________
Koha-devel mailing list
[hidden email]
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/
Reply | Threaded
Open this post in threaded view
|

Re: Centralize and move to gitlab

Julian Maurice
In reply to this post by Jonathan Druart
+1

Other repositories that could benefit from moving to gitlab:
- git-bz
- koct-webext (which is currently hosted at git.biblibre.com)

Le 23/01/2018 à 20:46, Jonathan Druart a écrit :

> 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)
> CI file for the manual:
> https://gitlab.com/koha-community-devs-users/kohadocs/blob/master/.gitlab-ci.yml
>
> Any pros/cons?
>
> Cheers,
> Jonathan
>
> (No troll please)
>
>
> _______________________________________________
> Koha-devel mailing list
> [hidden email]
> 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/
>

--
Julian Maurice <[hidden email]>
BibLibre
_______________________________________________
Koha-devel mailing list
[hidden email]
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/
Reply | Threaded
Open this post in threaded view
|

Re: Centralize and move to gitlab

Fridolin SOMERS
In reply to this post by Jonathan Druart
Hi,

We at Biblibre are using gitlab for some time : http://git.biblibre.com/

Its fun but we have some issues.
First note that repo can not be accessed by GIT protocol, only SSH and HTTP.
Then we add issues with repo having to much branches (around 300).

We are now moving to gitea https://try.gitea.io/

Have a look.

Regards,

Le 23/01/2018 à 20:46, Jonathan Druart a écrit :

> 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)
> CI file for the manual:
> https://gitlab.com/koha-community-devs-users/kohadocs/blob/master/.gitlab-ci.yml
>
> Any pros/cons?
>
> Cheers,
> Jonathan
>
> (No troll please)
>
>
>
> _______________________________________________
> Koha-devel mailing list
> [hidden email]
> 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/
>

--
Fridolin SOMERS <[hidden email]>
BibLibre - software and system maintainer
_______________________________________________
Koha-devel mailing list
[hidden email]
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/
Reply | Threaded
Open this post in threaded view
|

Re: Centralize and move to gitlab

Kyle Hall
In reply to this post by Jonathan Druart
That sounds great! +1 from me!



http://www.kylehall.info
ByWater Solutions ( http://bywatersolutions.com )
Meadville Public Library ( http://www.meadvillelibrary.org )
Crawford County Federated Library System ( http://www.ccfls.org )

On Tue, Jan 23, 2018 at 2:46 PM, Jonathan Druart <[hidden email]> 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)

_______________________________________________
Koha-devel mailing list
[hidden email]
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/


_______________________________________________
Koha-devel mailing list
[hidden email]
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/
Reply | Threaded
Open this post in threaded view
|

Re: Centralize and move to gitlab

Victor Grousset
In reply to this post by Jonathan Druart
+1


On 25/01/2018 15:57, Fridolin SOMERS wrote:
 > We at Biblibre are using gitlab for some time : http://git.biblibre.com/
 >
 > Its fun but we have some issues.
 > First note that repo can not be accessed by GIT protocol, only SSH and
 > HTTP.

It seems that it should be working.
https://gitlab.com/gitlab-com/support-forum/issues/104

Although `git clone git://gitlab.com/tuxayo/koha.git` timeouts for me.
Maybe there is a network problem similar to the one described in the issue.

 > Then we add issues with repo having to much branches (around 300).

Note that we are running version 6.8.1 (April 2014)
So part of our feedback (hopefully) doesn't apply to the latest versions.

Here are two repo for those wanting to try some performance demanding
scenarios
https://gitlab.com/tuxayo/koha/ # lot of commits and tags
https://framagit.org/tuxayo/openADS  # lots of branches
(I remember that some things were still slow few month ago so part of
the feedback is accurate with 300 branches and 100 tags)


Cheers,

--
Victor Grousset, dev support/maintenance
BibLibre, Services en logiciels libres pour les bibliothèques
BibLibre, Libre/Open Source software and services for libraries
_______________________________________________
Koha-devel mailing list
[hidden email]
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/
Reply | Threaded
Open this post in threaded view
|

Re: Centralize and move to gitlab

Katrin Fischer-2
In reply to this post by Jonathan Druart

+1


On 23.01.2018 20:46, Jonathan Druart 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)


_______________________________________________
Koha-devel mailing list
[hidden email]
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/


_______________________________________________
Koha-devel mailing list
[hidden email]
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/
Reply | Threaded
Open this post in threaded view
|

Re: Centralize and move to gitlab

Fridolin SOMERS
In reply to this post by Victor Grousset
Thanks a lot Victor for theses checks.
So an up-to-date version will be cool :)

Le 26/01/2018 à 18:18, Victor Grousset a écrit :

> +1
>
>
> On 25/01/2018 15:57, Fridolin SOMERS wrote:
>  > We at Biblibre are using gitlab for some time : http://git.biblibre.com/
>  >
>  > Its fun but we have some issues.
>  > First note that repo can not be accessed by GIT protocol, only SSH and
>  > HTTP.
>
> It seems that it should be working.
> https://gitlab.com/gitlab-com/support-forum/issues/104
>
> Although `git clone git://gitlab.com/tuxayo/koha.git` timeouts for me.
> Maybe there is a network problem similar to the one described in the issue.
>
>  > Then we add issues with repo having to much branches (around 300).
>
> Note that we are running version 6.8.1 (April 2014)
> So part of our feedback (hopefully) doesn't apply to the latest versions.
>
> Here are two repo for those wanting to try some performance demanding
> scenarios
> https://gitlab.com/tuxayo/koha/ # lot of commits and tags
> https://framagit.org/tuxayo/openADS  # lots of branches
> (I remember that some things were still slow few month ago so part of
> the feedback is accurate with 300 branches and 100 tags)
>
>
> Cheers,
>

--
Fridolin SOMERS <[hidden email]>
BibLibre - software and system maintainer
_______________________________________________
Koha-devel mailing list
[hidden email]
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/
Reply | Threaded
Open this post in threaded view
|

Re: Centralize and move to gitlab

Jonathan Druart
In reply to this post by Jonathan Druart
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

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 <[hidden email]> 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)

_______________________________________________
Koha-devel mailing list
[hidden email]
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/
Reply | Threaded
Open this post in threaded view
|

Re: Centralize and move to gitlab

Kyle Hall
In reply to this post by Katrin Fischer-2
+1


On Sun, Jan 28, 2018 at 6:31 AM, Katrin Fischer <[hidden email]> wrote:

+1


On 23.01.2018 20:46, Jonathan Druart 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)


_______________________________________________
Koha-devel mailing list
[hidden email]
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/


_______________________________________________
Koha-devel mailing list
[hidden email]
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/


_______________________________________________
Koha-devel mailing list
[hidden email]
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/
Reply | Threaded
Open this post in threaded view
|

Re: Centralize and move to gitlab

Tomas Cohen Arazi
KohaDevBox has been marked as obsolete as you suggested!


El vie., 22 jun. 2018 a las 15:02, Kyle Hall (<[hidden email]>) escribió:
+1
http://www.kylehall.info
ByWater Solutions ( http://bywatersolutions.com )
Meadville Public Library ( http://www.meadvillelibrary.org )
Crawford County Federated Library System ( http://www.ccfls.org )

On Sun, Jan 28, 2018 at 6:31 AM, Katrin Fischer <[hidden email]> wrote:

+1


On 23.01.2018 20:46, Jonathan Druart 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)


_______________________________________________
Koha-devel mailing list
[hidden email]
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/


_______________________________________________
Koha-devel mailing list
[hidden email]
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/

_______________________________________________
Koha-devel mailing list
[hidden email]
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)
✆ +54 9351 3513384
GPG: B2F3C15F

_______________________________________________
Koha-devel mailing list
[hidden email]
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/
Reply | Threaded
Open this post in threaded view
|

Re: Centralize and move to gitlab

Mark Tompsett
Greetings,
 
Will gitify and git-bz be moved as well? Kohadevbox is still using the github of those.
 
GPML,
Mark Tompsett

_______________________________________________
Koha-devel mailing list
[hidden email]
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/
Reply | Threaded
Open this post in threaded view
|

Re: Centralize and move to gitlab

MartinRenvoize
Well spotted Mark, would be good to get those moved too :)

Martin Renvoize

Development Manager


 

T: +44 (0) 1483 378728

F: +44 (0) 800 756 6384

E: [hidden email]

www.ptfs-europe.com

 



Registered in the United Kingdom No. 06416372   VAT Reg No. 925 7211 30


The information contained in this email message may be privileged, confidential and protected from disclosure. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited. If you think that you have received this email message in error, please email the sender at [hidden email]



On 23 June 2018 at 03:17, Mark Tompsett <[hidden email]> wrote:
Greetings,
 
Will gitify and git-bz be moved as well? Kohadevbox is still using the github of those.
 
GPML,
Mark Tompsett

_______________________________________________
Koha-devel mailing list
[hidden email]
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/


_______________________________________________
Koha-devel mailing list
[hidden email]
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/
Reply | Threaded
Open this post in threaded view
|

Re: Centralize and move to gitlab

Jonathan Druart
git-bz and kohadevbox have been moved as well!

On Mon, 25 Jun 2018 at 09:43 Renvoize, Martin <[hidden email]> wrote:
Well spotted Mark, would be good to get those moved too :)

Martin Renvoize

Development Manager


 

T: <a href="tel:+44%201483%20378728" value="+441483378728" target="_blank">+44 (0) 1483 378728

F: <a href="tel:+44%20800%20756%206384" value="+448007566384" target="_blank">+44 (0) 800 756 6384

E: [hidden email]

www.ptfs-europe.com

 



Registered in the United Kingdom No. 06416372   VAT Reg No. 925 7211 30


The information contained in this email message may be privileged, confidential and protected from disclosure. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited. If you think that you have received this email message in error, please email the sender at [hidden email]



On 23 June 2018 at 03:17, Mark Tompsett <[hidden email]> wrote:
Greetings,
 
Will gitify and git-bz be moved as well? Kohadevbox is still using the github of those.
 
GPML,
Mark Tompsett

_______________________________________________
Koha-devel mailing list
[hidden email]
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/

_______________________________________________
Koha-devel mailing list
[hidden email]
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/

_______________________________________________
Koha-devel mailing list
[hidden email]
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/
Reply | Threaded
Open this post in threaded view
|

Re: Centralize and move to gitlab

MartinRenvoize
Should the contribs repo also be moved/mirrored on gitlab too?

Martin Renvoize

Development Team Manager


 

T: +44 (0) 1483 378728

F: +44 (0) 800 756 6384

E: [hidden email]

www.ptfs-europe.com

 



Registered in the United Kingdom No. 06416372   VAT Reg No. 925 7211 30


The information contained in this email message may be privileged, confidential and protected from disclosure. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited. If you think that you have received this email message in error, please email the sender at [hidden email]




On Wed, 11 Jul 2018 at 20:47, Jonathan Druart <[hidden email]> wrote:
git-bz and kohadevbox have been moved as well!

On Mon, 25 Jun 2018 at 09:43 Renvoize, Martin <[hidden email]> wrote:
Well spotted Mark, would be good to get those moved too :)

Martin Renvoize

Development Manager


 

T: <a href="tel:+44%201483%20378728" value="+441483378728" target="_blank">+44 (0) 1483 378728

F: <a href="tel:+44%20800%20756%206384" value="+448007566384" target="_blank">+44 (0) 800 756 6384

E: [hidden email]

www.ptfs-europe.com

 



Registered in the United Kingdom No. 06416372   VAT Reg No. 925 7211 30


The information contained in this email message may be privileged, confidential and protected from disclosure. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited. If you think that you have received this email message in error, please email the sender at [hidden email]



On 23 June 2018 at 03:17, Mark Tompsett <[hidden email]> wrote:
Greetings,
 
Will gitify and git-bz be moved as well? Kohadevbox is still using the github of those.
 
GPML,
Mark Tompsett

_______________________________________________
Koha-devel mailing list
[hidden email]
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/

_______________________________________________
Koha-devel mailing list
[hidden email]
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/

_______________________________________________
Koha-devel mailing list
[hidden email]
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/