Re: Information regarding upcoming Gitlab Migration: clarifications

2020-05-02 Thread Michael Pyne
On Fri, May 01, 2020 at 09:25:18AM -0400, Allen Winter wrote: > On Thursday, April 30, 2020 5:15:43 PM EDT Albert Astals Cid wrote: > > El dijous, 30 d’abril de 2020, a les 21:31:02 CEST, Ben Cooksley va > > escriure: > > > On Fri, May 1, 2020 at 6:04 AM Ivan Čukić wrote: > > > > > > > > > We

Re: Information regarding upcoming Gitlab Migration

2020-05-02 Thread Ben Cooksley
On Sun, May 3, 2020 at 2:13 AM Michał Policht wrote: > > Hi all, Hi Michal, > > Sorry for late response, but project "cutehmi" fits into "sdk" category > better than "applications" (technically it's a framework, but I guess > "frameorks" is reserved for well integrated KDE Frameworks). I have

Re: Information regarding upcoming Gitlab Migration

2020-05-02 Thread Michał Policht
Hi all, Sorry for late response, but project "cutehmi" fits into "sdk" category better than "applications" (technically it's a framework, but I guess "frameorks" is reserved for well integrated KDE Frameworks). Speaking generally on subject, categorization is always problematic. Categories

Re: Information regarding upcoming Gitlab Migration

2020-05-02 Thread Alexander Potashev
On Fri, May 1, 2020 at 10:14 PM Ben Cooksley wrote: > On Sat, May 2, 2020 at 6:17 AM Alexander Potashev > wrote: > > I have a similar use case. Sometimes I need to share a URL to a > > project. For this purpose I used to share e.g. > > https://cgit.kde.org/releaseme.git/about > > > > Does this

Re: Information regarding upcoming Gitlab Migration

2020-05-01 Thread Ben Cooksley
On Sat, May 2, 2020 at 9:04 AM Nate Graham wrote: > > On 5/1/20 2:09 PM, Ben Cooksley wrote: > > Unfortunately sharing of projects/repositories across groups does not > > impact on tasks and reviews. > > This means that merge requests for Planet (which is currently shared > > with "KDE") do not

Re: Information regarding upcoming Gitlab Migration

2020-05-01 Thread Nate Graham
On 5/1/20 2:09 PM, Ben Cooksley wrote: Unfortunately sharing of projects/repositories across groups does not impact on tasks and reviews. This means that merge requests for Planet (which is currently shared with "KDE") do not show up in the list of merge requests for "KDE". Sharing repositories

Re: Information regarding upcoming Gitlab Migration

2020-05-01 Thread Ben Cooksley
On Sat, May 2, 2020 at 6:17 AM Alexander Potashev wrote: > > On Tue, Apr 28, 2020 at 6:47 AM Bhushan Shah wrote: > > Use case 4 : Tom is a student in Germany and is interested in > > contributing to wikitolearn, and he asks where can I find code of the > > wikitolearn? > > Hi, Hi Alexander, >

Re: Information regarding upcoming Gitlab Migration

2020-05-01 Thread Ben Cooksley
On Sat, May 2, 2020 at 2:33 AM Adriaan de Groot wrote: > > On 2020 mayula d. 1id 07:08:41 CEST Ben Cooksley wrote: > > On Fri, May 1, 2020 at 2:46 AM Nate Graham wrote: > > > If I'm understanding things, we have solutions to most or all of the > > > objections raised so far: > > > > > > -

Re: Information regarding upcoming Gitlab Migration

2020-05-01 Thread Nicolás Alvarez
> On 1 May 2020, at 15:17, Alexander Potashev wrote: > > On Tue, Apr 28, 2020 at 6:47 AM Bhushan Shah wrote: >> Use case 4 : Tom is a student in Germany and is interested in >> contributing to wikitolearn, and he asks where can I find code of the >> wikitolearn? > > Hi, > > I have a

Re: Information regarding upcoming Gitlab Migration

2020-05-01 Thread Alexander Potashev
On Tue, Apr 28, 2020 at 6:47 AM Bhushan Shah wrote: > Use case 4 : Tom is a student in Germany and is interested in > contributing to wikitolearn, and he asks where can I find code of the > wikitolearn? Hi, I have a similar use case. Sometimes I need to share a URL to a project. For this

Re: Information regarding upcoming Gitlab Migration: clarifications

2020-05-01 Thread Luigi Toscano
Ben Cooksley ha scritto: > On Fri, May 1, 2020 at 4:38 PM Nate Graham wrote: >> >> >> >> On 4/30/20 5:59 PM, Aleix Pol wrote: >>> El jue., 30 de abr. de 2020 a la(s) 18:15, Albert Astals Cid Am I the only person that just has all the repos on the same folder? I thought it was the

Re: Information regarding upcoming Gitlab Migration: clarifications

2020-05-01 Thread Nate Graham
On 5/1/20 9:02 AM, Johan Ouwerkerk wrote: No, that is not the default. Actually, it is: https://invent.kde.org/kde/kdesrc-build/-/blob/master/kdesrc-build-setup#L389 and download all repos into ~/kde/src without any of the levels of hierarchy. But it is sufficiently common that there

Re: Information regarding upcoming Gitlab Migration: clarifications

2020-05-01 Thread Johan Ouwerkerk
On Fri, May 1, 2020 at 6:38 AM Nate Graham wrote: > > On 4/30/20 5:59 PM, Aleix Pol wrote: > > El jue., 30 de abr. de 2020 a la(s) 18:15, Albert Astals Cid > >> Am I the only person that just has all the repos on the same folder? I > >> thought it was the common thing to do :? > > > > I do too >

Re: Information regarding upcoming Gitlab Migration: clarifications

2020-05-01 Thread Aleix Pol
On Fri, May 1, 2020 at 7:18 AM Ben Cooksley wrote: > > On Fri, May 1, 2020 at 4:38 PM Nate Graham wrote: > > > > > > > > On 4/30/20 5:59 PM, Aleix Pol wrote: > > > El jue., 30 de abr. de 2020 a la(s) 18:15, Albert Astals Cid > > >> Am I the only person that just has all the repos on the same

Re: Information regarding upcoming Gitlab Migration: clarifications

2020-05-01 Thread Allen Winter
On Thursday, April 30, 2020 5:15:43 PM EDT Albert Astals Cid wrote: > El dijous, 30 d’abril de 2020, a les 21:31:02 CEST, Ben Cooksley va escriure: > > On Fri, May 1, 2020 at 6:04 AM Ivan Čukić wrote: > > > > > > > We have made a big fuss in the past about having different projects > > > > that

Re: Information regarding upcoming Gitlab Migration: clarifications

2020-05-01 Thread Nate Graham
On 4/30/20 11:17 PM, Ben Cooksley wrote: Not necessarily. Git allows you to override the name that the local folder is called when cloning, so there is no reason why we can't specify something in the metadata to override the local name that the folder gets called in your local checkout

Re: Information regarding upcoming Gitlab Migration

2020-04-30 Thread Ben Cooksley
On Fri, May 1, 2020 at 2:46 AM Nate Graham wrote: > > If I'm understanding things, we have solutions to most or all of the > objections raised so far: > > - Projects will be allowed to live in--or at least appear in--multiple > top-level groups (e.g. plasma-framework could appear in both the >

Re: Information regarding upcoming Gitlab Migration: clarifications

2020-04-30 Thread Nate Graham
On 4/30/20 5:59 PM, Aleix Pol wrote: El jue., 30 de abr. de 2020 a la(s) 18:15, Albert Astals Cid Am I the only person that just has all the repos on the same folder? I thought it was the common thing to do :? I do too Same here. kdesrc-build's default settings do this, and download all

Re: Information regarding upcoming Gitlab Migration: clarifications

2020-04-30 Thread Aleix Pol
On Fri, May 1, 2020 at 1:08 AM Nicolás Alvarez wrote: > > El jue., 30 de abr. de 2020 a la(s) 18:15, Albert Astals Cid > (aa...@kde.org) escribió: > > > > El dijous, 30 d’abril de 2020, a les 21:31:02 CEST, Ben Cooksley va > > escriure: > > > On Fri, May 1, 2020 at 6:04 AM Ivan Čukić wrote: > >

Re: Information regarding upcoming Gitlab Migration: clarifications

2020-04-30 Thread Nicolás Alvarez
El jue., 30 de abr. de 2020 a la(s) 18:15, Albert Astals Cid (aa...@kde.org) escribió: > > El dijous, 30 d’abril de 2020, a les 21:31:02 CEST, Ben Cooksley va escriure: > > On Fri, May 1, 2020 at 6:04 AM Ivan Čukić wrote: > > > > > > > We have made a big fuss in the past about having different

Re: Information regarding upcoming Gitlab Migration: clarifications

2020-04-30 Thread Albert Astals Cid
El dijous, 30 d’abril de 2020, a les 21:31:02 CEST, Ben Cooksley va escriure: > On Fri, May 1, 2020 at 6:04 AM Ivan Čukić wrote: > > > > > We have made a big fuss in the past about having different projects > > > that do the same thing and now we'll have that but also we'll have > > > several

Re: Information regarding upcoming Gitlab Migration: clarifications

2020-04-30 Thread Ben Cooksley
On Fri, May 1, 2020 at 5:58 AM Nate Graham wrote: > > > > On 4/30/20 11:43 AM, Aleix Pol wrote: > > IMHO needing tools ad-hoc to KDE development can be a barrier of entrance. > > I feel like these things make us look distant, it's important that > > people's skills translate automatically when

Re: Information regarding upcoming Gitlab Migration: clarifications

2020-04-30 Thread Ben Cooksley
On Fri, May 1, 2020 at 6:04 AM Ivan Čukić wrote: > > > We have made a big fuss in the past about having different projects > > that do the same thing and now we'll have that but also we'll have > > several projects with the same name? > > It really feels off to me and I wonder if this is related

Re: Information regarding upcoming Gitlab Migration: clarifications

2020-04-30 Thread Ben Cooksley
On Fri, May 1, 2020 at 5:44 AM Aleix Pol wrote: > > On Wed, Apr 29, 2020 at 12:25 PM Bhushan Shah wrote: > > > > Good afternoon, > > > > [Please keep sysad...@kde.org list or bs...@kde.org in the CC for > > replies] > > > > I want to clarify some bits for which we have gotten a questions about,

Re: Information regarding upcoming Gitlab Migration: clarifications

2020-04-30 Thread Ivan Čukić
> We have made a big fuss in the past about having different projects > that do the same thing and now we'll have that but also we'll have > several projects with the same name? > It really feels off to me and I wonder if this is related to the move to > gitlab. +1 to both sentiments - that

Re: Information regarding upcoming Gitlab Migration: clarifications

2020-04-30 Thread Nate Graham
On 4/30/20 11:43 AM, Aleix Pol wrote: IMHO needing tools ad-hoc to KDE development can be a barrier of entrance. I feel like these things make us look distant, it's important that people's skills translate automatically when they want to get started. True, but if you're a new contributor,

Re: Information regarding upcoming Gitlab Migration: clarifications

2020-04-30 Thread Aleix Pol
On Wed, Apr 29, 2020 at 12:25 PM Bhushan Shah wrote: > > Good afternoon, > > [Please keep sysad...@kde.org list or bs...@kde.org in the CC for > replies] > > I want to clarify some bits for which we have gotten a questions about, > > - Non unique naming: There's some teams which prefer if we

Re: Information regarding upcoming Gitlab Migration

2020-04-30 Thread Nate Graham
If I'm understanding things, we have solutions to most or all of the objections raised so far: - Projects will be allowed to live in--or at least appear in--multiple top-level groups (e.g. plasma-framework could appear in both the Frameworks top-level group and also the Plasma top-level

Re: Information regarding upcoming Gitlab Migration: clarifications

2020-04-30 Thread Marco Martin
+1 Those proposals seems sensible to me -- Marco Martin On Wed, Apr 29, 2020 at 12:25 PM Bhushan Shah wrote: > > Good afternoon, > > [Please keep sysad...@kde.org list or bs...@kde.org in the CC for > replies] > > I want to clarify some bits for which we have gotten a questions about, > > -

Re: Information regarding upcoming Gitlab Migration

2020-04-29 Thread Ben Cooksley
On Thu, Apr 30, 2020 at 4:17 AM Nicolás Alvarez wrote: > > > > El 29 abr. 2020, a la(s) 11:19, Boudewijn Rempt escribió: > > > > On woensdag 29 april 2020 15:16:12 CEST Adriaan de Groot wrote: > >>> On 2020 prilula d. 29id 06:46:55 CEST Bhushan Shah wrote: > >>> We have gotten a request for

Re: Information regarding upcoming Gitlab Migration

2020-04-29 Thread Ben Cooksley
On Thu, Apr 30, 2020 at 6:16 AM Boudewijn Rempt wrote: > > On woensdag 29 april 2020 18:17:05 CEST Nicolás Alvarez wrote: > > > > My understanding is that there is a workboard per repository *and* another > > per group. > > > > Now, how big do we make the group workboard? All of KDE? A smaller

Re: Information regarding upcoming Gitlab Migration

2020-04-29 Thread Boudewijn Rempt
On woensdag 29 april 2020 18:17:05 CEST Nicolás Alvarez wrote: > > My understanding is that there is a workboard per repository *and* another > per group. > > Now, how big do we make the group workboard? All of KDE? A smaller category? > That is the question. Ah, that makes more sense. I

Re: Information regarding upcoming Gitlab Migration

2020-04-29 Thread Carl Schwan
Ok after a small chat with the Bhushan I learned that the plan is to use gitlab-triage instead of project labels. This should be way more powerful :D Sorry for the trouble Carl ‐‐‐ Original Message ‐‐‐ Le mercredi, avril 29, 2020 2:37 PM, Carl Schwan a écrit : > Hi Sysadmins, > >

Re: Information regarding upcoming Gitlab Migration

2020-04-29 Thread Nicolás Alvarez
> El 29 abr. 2020, a la(s) 11:19, Boudewijn Rempt escribió: > > On woensdag 29 april 2020 15:16:12 CEST Adriaan de Groot wrote: >>> On 2020 prilula d. 29id 06:46:55 CEST Bhushan Shah wrote: >>> We have gotten a request for namespacing from projects on multiple >>> occassion, in cgit our

Re: Information regarding upcoming Gitlab Migration

2020-04-29 Thread Michael Reeves
If your looking for an example of a project/repo level workboard look here. https://invent.kde.org/kde/kdiff3/-/boards. Just did a quick check this is indeed specific to kdiff3. Labels can also be created at this level. The board is completely customizable. On Wed, Apr 29, 2020, 11:21 AM Michael

Re: Information regarding upcoming Gitlab Migration

2020-04-29 Thread Michael Reeves
On Wed, Apr 29, 2020, 10:19 AM Boudewijn Rempt wrote: > On woensdag 29 april 2020 15:16:12 CEST Adriaan de Groot wrote: > > On 2020 prilula d. 29id 06:46:55 CEST Bhushan Shah wrote: > > > We have gotten a request for namespacing from projects on multiple > > > occassion, in cgit our workaround

Re: Information regarding upcoming Gitlab Migration

2020-04-29 Thread Carl Schwan
Hi Sysadmins, since we are speaking about workboard for groups, what is the plan for groups that don't work on a single project but on all of the KDE projects (e.g. VDG, documentation, localization, websites)? I experimented a bit with project tags

Re: Information regarding upcoming Gitlab Migration

2020-04-29 Thread Adriaan de Groot
On 2020 prilula d. 29id 06:46:55 CEST Bhushan Shah wrote: > We have gotten a request for namespacing from projects on multiple > occassion, in cgit our workaround has always been that we prefix the > repo name with namespace- (i.e wikitolearn-courses-backend). > > While this works out with our

Re: Information regarding upcoming Gitlab Migration

2020-04-29 Thread Adriaan de Groot
On 2020 prilula d. 28id 13:35:22 CEST Ben Cooksley wrote: > Would some form of git alias/custom command script that works similar > to the following be suitable? > > git kde-clone skrooge > > That script would then search the appropriate groups (ignoring any > personal repositories including

Re: Information regarding upcoming Gitlab Migration

2020-04-28 Thread Bhushan Shah
Hello Johan, On Tue, Apr 28, 2020 at 06:18:14PM +0200, Johan Ouwerkerk wrote: > I would like to propose that the sysadmin team pick the layout that is > easiest to *implement*, which I suspect is also the most like what we > have now, and that we live with that. Unless there is a pressing need, >

Re: Information regarding upcoming Gitlab Migration

2020-04-28 Thread Dan Leinir Turthra Jensen
On Monday, 27 April 2020 21:25:09 BST Albert Astals Cid wrote: > El dilluns, 27 d’abril de 2020, a les 13:58:02 CEST, Bhushan Shah va escriure: > > In part I am mostly re-iterating what Ben already mentioned in different > > messages. > > > > On Mon, Apr 27, 2020 at 12:38:42PM +0200, Aleix Pol

Re: Information regarding upcoming Gitlab Migration

2020-04-28 Thread Johan Ouwerkerk
On Tue, Apr 28, 2020 at 1:09 PM Adriaan de Groot wrote: > > One actor is "tooling", as Albert has pointed out. Whatever the resulting > structure is, it needs to be communicated to tool authors on time for tools to > be updated, released, and rolled out for use. Tools mentioned so far: > -

Re: Information regarding upcoming Gitlab Migration

2020-04-28 Thread Bhushan Shah
Hi Adriaan, On Tue, Apr 28, 2020 at 01:08:33PM +0200, Adriaan de Groot wrote: > A tool-like actor that I don't think has been mentioned so far is "existing > checkouts". I have a src/kde with all the bits I've looked at "recently". > There may even be some SVN checkouts there -- I'm willing to

Re: Information regarding upcoming Gitlab Migration

2020-04-28 Thread Ben Cooksley
On Tue, Apr 28, 2020 at 11:09 PM Adriaan de Groot wrote: > > There are a whole bunch of considerations and use-cases being discussed at > once in this thread, and Leinir's post made me think a bit about different > actors can interact with "the collection of repositories". > > One actor is

Re: Information regarding upcoming Gitlab Migration

2020-04-28 Thread Adriaan de Groot
There are a whole bunch of considerations and use-cases being discussed at once in this thread, and Leinir's post made me think a bit about different actors can interact with "the collection of repositories". One actor is "tooling", as Albert has pointed out. Whatever the resulting structure

Re: Information regarding upcoming Gitlab Migration

2020-04-27 Thread Bhushan Shah
Hi Olivier, On Mon, Apr 27, 2020 at 10:49:46PM +0200, Olivier Churlaud wrote: > >Because in order to search for something, you need to know it exists. > > > >If you are just casually browsing, then the search can't help you. > > I don't think people casually browse our repos. What use case is

Re: Information regarding upcoming Gitlab Migration

2020-04-27 Thread Bhushan Shah
Hi Ingo, On Mon, Apr 27, 2020 at 03:46:13PM +0200, Ingo Klöcker wrote: > > > I'm sorry, but I don't think that this is solved by your proposal for the > > > KDE PIM projects because not everything related to KDE PIM (e.g. relevant > > > frameworks like kcontacts, kholidays, kpeople and soon kdav)

Re: Information regarding upcoming Gitlab Migration

2020-04-27 Thread Olivier Churlaud
Le 27 avril 2020 22:33:12 GMT+02:00, Ben Cooksley a écrit : >On Tue, Apr 28, 2020 at 8:31 AM Albert Astals Cid >wrote: >> >> El dilluns, 27 d’abril de 2020, a les 13:19:07 CEST, Ben Cooksley va >escriure: >> > On Mon, Apr 27, 2020 at 11:12 PM Olivier Churlaud > wrote: >> > > >> > > Hi, >> > >

Re: Information regarding upcoming Gitlab Migration

2020-04-27 Thread Albert Astals Cid
El dilluns, 27 d’abril de 2020, a les 3:40:01 CEST, Bhushan Shah va escriure: > [Please keep sysad...@kde.org list or bs...@kde.org in the CC for > replies] > > Hello Community members, > > In view of upcoming Gitlab migration, we sysadmin team wants to share > the recommended structuring for

Re: Information regarding upcoming Gitlab Migration

2020-04-27 Thread Ben Cooksley
On Tue, Apr 28, 2020 at 8:31 AM Albert Astals Cid wrote: > > El dilluns, 27 d’abril de 2020, a les 13:19:07 CEST, Ben Cooksley va escriure: > > On Mon, Apr 27, 2020 at 11:12 PM Olivier Churlaud > > wrote: > > > > > > Hi, > > > > > > Le lundi 27 avril 2020, 12:38:42 CEST Aleix Pol a écrit : > >

Re: Information regarding upcoming Gitlab Migration

2020-04-27 Thread Albert Astals Cid
El dilluns, 27 d’abril de 2020, a les 13:19:07 CEST, Ben Cooksley va escriure: > On Mon, Apr 27, 2020 at 11:12 PM Olivier Churlaud > wrote: > > > > Hi, > > > > Le lundi 27 avril 2020, 12:38:42 CEST Aleix Pol a écrit : > > > On Mon, Apr 27, 2020 at 3:41 AM Bhushan Shah wrote: > > > > > > > >

Re: Information regarding upcoming Gitlab Migration

2020-04-27 Thread Albert Astals Cid
El dilluns, 27 d’abril de 2020, a les 13:58:02 CEST, Bhushan Shah va escriure: > In part I am mostly re-iterating what Ben already mentioned in different > messages. > > On Mon, Apr 27, 2020 at 12:38:42PM +0200, Aleix Pol wrote: > > Does this mean that to clone it we'll have to go "git clone > >

Re: Information regarding upcoming Gitlab Migration

2020-04-27 Thread Ben Cooksley
On Tue, Apr 28, 2020 at 1:46 AM Nate Graham wrote: > > > > On 4/27/20 4:38 AM, Aleix Pol wrote: > > Does this mean that to clone it we'll have to go "git clone > > kde:games/knetwalk" or something along the lines? > > > > If that's the case I'd much prefer if we didn't do this, at the moment > >

Re: Information regarding upcoming Gitlab Migration

2020-04-27 Thread Ben Cooksley
On Tue, Apr 28, 2020 at 12:04 AM Ingo Klöcker wrote: > > On Montag, 27. April 2020 13:19:07 CEST Ben Cooksley wrote: > > That requires that you know it exists. We have 1,043 mainline > > repositories at the moment, which translates to 53 pages of projects > > under a flat structure system. > >

Re: Information regarding upcoming Gitlab Migration

2020-04-27 Thread Rolf Eike Beer
Bhushan Shah wrote: I've worked on draft "move" of the current set of the repositories in their respective subgroups at the repo-metadata project's branch [1]. You can browse the directory structure to get idea of how final structure on Gitlab would look like. No objection, just a request for

Re: Information regarding upcoming Gitlab Migration

2020-04-27 Thread Nate Graham
On 4/27/20 7:46 AM, Ingo Klöcker wrote: On Montag, 27. April 2020 14:10:55 CEST Bhushan Shah wrote: This is something which can be easily solved by Gitlab, Gitlab offers a solution where project can be shared with another group. So e.g. sharing kcontacts with kdepim should be possible, then

Re: Information regarding upcoming Gitlab Migration

2020-04-27 Thread Johan Ouwerkerk
On Mon, Apr 27, 2020 at 2:32 PM Piyush Aggarwal wrote: > > How long do redirects like this one work? If they will keep working > indefinitely, then maybe we can have all the repos at flat URLs for once and > then move them to respective subgroups? I don't think this works if you want $repo to

Re: Information regarding upcoming Gitlab Migration

2020-04-27 Thread Johan Ouwerkerk
On Mon, Apr 27, 2020 at 3:30 PM Luigi Toscano wrote: > > Bhushan Shah ha scritto: > > > - But most importantly, this breaks with the non-unique leaf repository > > names feature offered by the proposed structure. So, There could be > > maui/documentation and wikitolearn/documentation. But we

Re: Information regarding upcoming Gitlab Migration

2020-04-27 Thread Nate Graham
On 4/27/20 7:52 AM, Nate Graham wrote: On 4/27/20 7:46 AM, Ingo Klöcker wrote: On Montag, 27. April 2020 14:10:55 CEST Bhushan Shah wrote: This is something which can be easily solved by Gitlab, Gitlab offers a solution where project can be shared with another group. So e.g. sharing

Re: Information regarding upcoming Gitlab Migration

2020-04-27 Thread Ingo Klöcker
On Montag, 27. April 2020 14:10:55 CEST Bhushan Shah wrote: > [adding sysad...@kde.org in CC, please make sure you keep it in CC] > > On Mon, Apr 27, 2020 at 02:03:48PM +0200, Ingo Klöcker wrote: > > On Montag, 27. April 2020 13:19:07 CEST Ben Cooksley wrote: > > > That requires that you know it

Re: Information regarding upcoming Gitlab Migration

2020-04-27 Thread Nate Graham
On 4/27/20 4:38 AM, Aleix Pol wrote: Does this mean that to clone it we'll have to go "git clone kde:games/knetwalk" or something along the lines? If that's the case I'd much prefer if we didn't do this, at the moment it's already uncomfortable for me to remember the URL for some of the

Re: Information regarding upcoming Gitlab Migration

2020-04-27 Thread Luigi Toscano
Bhushan Shah ha scritto: > - But most importantly, this breaks with the non-unique leaf repository > names feature offered by the proposed structure. So, There could be > maui/documentation and wikitolearn/documentation. But we would have > single KDE/documentation redirect Just to

Re: Information regarding upcoming Gitlab Migration

2020-04-27 Thread Bhushan Shah
On Mon, Apr 27, 2020 at 06:02:19PM +0530, Piyush Aggarwal wrote: > How long do redirects like this one work? If they will keep working > indefinitely, then maybe we can have all the repos at flat URLs for once > and then move them to respective subgroups? That way we will have access to > our

Re: Information regarding upcoming Gitlab Migration

2020-04-27 Thread Piyush Aggarwal
On Mon, 27 Apr, 2020, 5:57 pm Bhushan Shah, wrote: > Hello > > On Mon, Apr 27, 2020 at 02:10:11PM +0200, Boudewijn Rempt wrote: > > On maandag 27 april 2020 03:40:01 CEST Bhushan Shah wrote: > > > > > [1] > https://cgit.kde.org/sysadmin/repo-metadata.git/tree/projects-invent?h=bshah/invent > > >

Re: Information regarding upcoming Gitlab Migration

2020-04-27 Thread Boudewijn Rempt
On maandag 27 april 2020 14:26:16 CEST Bhushan Shah wrote: > > I have to admit, I also dread updating instructions and checkouts > > everywhere from invent.kde.org/kde/krita to invent.kde.org/graphics/krita... > > You don't really have to update the URL, since this project was already > on

Re: Information regarding upcoming Gitlab Migration

2020-04-27 Thread Bhushan Shah
Hello On Mon, Apr 27, 2020 at 02:10:11PM +0200, Boudewijn Rempt wrote: > On maandag 27 april 2020 03:40:01 CEST Bhushan Shah wrote: > > > [1] > > https://cgit.kde.org/sysadmin/repo-metadata.git/tree/projects-invent?h=bshah/invent > > Maybe it would make sense to keep a kde top-level group for

Re: Information regarding upcoming Gitlab Migration

2020-04-27 Thread Bhushan Shah
[adding sysad...@kde.org in CC, please make sure you keep it in CC] On Mon, Apr 27, 2020 at 02:03:48PM +0200, Ingo Klöcker wrote: > On Montag, 27. April 2020 13:19:07 CEST Ben Cooksley wrote: > > That requires that you know it exists. We have 1,043 mainline > > repositories at the moment, which

Re: Information regarding upcoming Gitlab Migration

2020-04-27 Thread Ingo Klöcker
On Montag, 27. April 2020 13:19:07 CEST Ben Cooksley wrote: > That requires that you know it exists. We have 1,043 mainline > repositories at the moment, which translates to 53 pages of projects > under a flat structure system. > Reality is nobody is going to page through that looking for

Re: Information regarding upcoming Gitlab Migration

2020-04-27 Thread Bhushan Shah
In part I am mostly re-iterating what Ben already mentioned in different messages. On Mon, Apr 27, 2020 at 12:38:42PM +0200, Aleix Pol wrote: > Does this mean that to clone it we'll have to go "git clone > kde:games/knetwalk" or something along the lines? Yes [Rest of message is with sysadmin

Re: Information regarding upcoming Gitlab Migration

2020-04-27 Thread Olivier Churlaud
Le lundi 27 avril 2020, 13:19:07 CEST Ben Cooksley a écrit : > On Mon, Apr 27, 2020 at 11:12 PM Olivier Churlaud > wrote: > > > > Hi, > > > > Le lundi 27 avril 2020, 12:38:42 CEST Aleix Pol a écrit : > > > On Mon, Apr 27, 2020 at 3:41 AM Bhushan Shah wrote: > > > > > > > > [Please keep

Re: Information regarding upcoming Gitlab Migration

2020-04-27 Thread Ben Cooksley
On Mon, Apr 27, 2020 at 11:12 PM Olivier Churlaud wrote: > > Hi, > > Le lundi 27 avril 2020, 12:38:42 CEST Aleix Pol a écrit : > > On Mon, Apr 27, 2020 at 3:41 AM Bhushan Shah wrote: > > > > > > [Please keep sysad...@kde.org list or bs...@kde.org in the CC for > > > replies] > > > > > > Hello

Re: Information regarding upcoming Gitlab Migration

2020-04-27 Thread Aleix Pol
On Mon, Apr 27, 2020 at 12:55 PM Ben Cooksley wrote: > > On Mon, Apr 27, 2020 at 10:39 PM Aleix Pol wrote: > > > > On Mon, Apr 27, 2020 at 3:41 AM Bhushan Shah wrote: > > > > > > [Please keep sysad...@kde.org list or bs...@kde.org in the CC for > > > replies] > > > > > > Hello Community

Re: Information regarding upcoming Gitlab Migration

2020-04-27 Thread Olivier Churlaud
Hi, Le lundi 27 avril 2020, 12:38:42 CEST Aleix Pol a écrit : > On Mon, Apr 27, 2020 at 3:41 AM Bhushan Shah wrote: > > > > [Please keep sysad...@kde.org list or bs...@kde.org in the CC for > > replies] > > > > Hello Community members, > > > > In view of upcoming Gitlab migration, we sysadmin

Re: Information regarding upcoming Gitlab Migration

2020-04-27 Thread Ben Cooksley
On Mon, Apr 27, 2020 at 10:50 PM Piyush Aggarwal wrote: > > > > On Mon, 27 Apr, 2020, 4:09 pm Aleix Pol, wrote: >> >> On Mon, Apr 27, 2020 at 3:41 AM Bhushan Shah wrote: >> > >> > [Please keep sysad...@kde.org list or bs...@kde.org in the CC for >> > replies] >> > >> > Hello Community members,

Re: Information regarding upcoming Gitlab Migration

2020-04-27 Thread Ben Cooksley
On Mon, Apr 27, 2020 at 10:39 PM Aleix Pol wrote: > > On Mon, Apr 27, 2020 at 3:41 AM Bhushan Shah wrote: > > > > [Please keep sysad...@kde.org list or bs...@kde.org in the CC for > > replies] > > > > Hello Community members, > > > > In view of upcoming Gitlab migration, we sysadmin team wants

Re: Information regarding upcoming Gitlab Migration

2020-04-27 Thread Piyush Aggarwal
On Mon, 27 Apr, 2020, 4:09 pm Aleix Pol, wrote: > On Mon, Apr 27, 2020 at 3:41 AM Bhushan Shah wrote: > > > > [Please keep sysad...@kde.org list or bs...@kde.org in the CC for > > replies] > > > > Hello Community members, > > > > In view of upcoming Gitlab migration, we sysadmin team wants to

Re: Information regarding upcoming Gitlab Migration

2020-04-27 Thread Aleix Pol
On Mon, Apr 27, 2020 at 3:41 AM Bhushan Shah wrote: > > [Please keep sysad...@kde.org list or bs...@kde.org in the CC for > replies] > > Hello Community members, > > In view of upcoming Gitlab migration, we sysadmin team wants to share > the recommended structuring for the repositories on Gitlab.

Re: Information regarding upcoming Gitlab Migration

2020-04-27 Thread Ben Cooksley
On Mon, Apr 27, 2020 at 7:26 PM Ilya Bizyaev wrote: > > Hello Bhushan! > > Thank you for you work on the Gitlab migration! > > The lists look good! Here are some ideas that I have, in case you think they > can be considered before we transition: > • The "applications" category is somewhat

Re: Information regarding upcoming Gitlab Migration

2020-04-27 Thread Ilya Bizyaev
Hello Bhushan! Thank you for you work on the Gitlab migration! The lists look good! Here are some ideas that I have, in case you think they can be considered before we transition: • The "applications" category is somewhat misleading to me: it does not include all KDE applications, and not

Re: Information regarding upcoming Gitlab Migration

2020-04-27 Thread Ben Cooksley
On Mon, Apr 27, 2020 at 6:33 PM Rolf Eike Beer wrote: > > Bhushan Shah wrote: > > > I've worked on draft "move" of the current set of the repositories in > > their respective subgroups at the repo-metadata project's branch [1]. > > You can browse the directory structure to get idea of how final