Re: Information regarding upcoming Gitlab Migration

[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 forks), find the necessary repository
> and perform the clone as appropriate for you. Should it find multiple
> results it would output it's results and then exit with a failure
> (giving you names and the clone urls to pick from manually)

That'd actually be pretty cool.

As a standalone script it'd be useful to migrate existing checkouts, so that's 
shooting two birds in one foot. And then you can have a somewhat structured 
namespace, still with simple lookup and unstructured names (until, as Bhushan 
points out in a different message in this thread, you get non-unique labels 
when decomposing structures names).


[ade]


signature.asc
Description: This is a digitally signed message part.

Information regarding upcoming Gitlab Migration: clarifications

[Bhushan Shah]

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 dropped the
  namespace- part from their name which we have added. While currently
  this does not result in the naming conflict right away, we realize
  this will cause it at one point, for example,

  maui-dialer -> maui/dialer
  plasma-dialer -> plasma-mobile/dialer

  To minimize the impact of the Gitlab move we won't be doing such
  renames which introduce non-unique names right away. But we would
  prefer if the existing tooling or infrastructure is ready for this
  kind of cases at later point. Only way to enforce non-unique naming is
  one big KDE/ subgroup which we want to avoid.

  Current naming in the repo-metadata branch[1] I've pointed does not
  reflect those renames, as we are not planning to do those renames
  right away during gitlab move, but at a later stage.

- Existing configurations: we want to reduce impact on existing release
  schedule, and existing developer workflow,  therefore we will continue
  to privide the existing anongit.kde.org and git.kde.org (although this
  will be read-only) with current flat structuring for 3 weeks after
  actual migration, which will keep the existing scripts/clones working
  enough to give developers time to change to the new structure.

  We will also try to provide a script which allows you to migrate your
  existing clones to new repo paths and as mentioned by Ben in other
  message, potentially a git-kde script which would allow you to clone
  individual repository without knowing it's namespace (provided that
  there is no conflict of it's name). like "git kde karchive"

- Translations: we will co-ordinate with the translations team to let
  them adapt their tooling to updated structure as this requires changes
  on their side how translations are stored in svn repository

Thanks!

[1] 
https://cgit.kde.org/sysadmin/repo-metadata.git/tree/projects-invent?h=bshah/invent

-- 
Bhushan Shah
http://blog.bshah.in
IRC Nick : bshah on Freenode
GPG key fingerprint : 0AAC 775B B643 7A8D 9AF7 A3AC FE07 8411 7FBC E11D


signature.asc
Description: PGP signature