Hi everyone! Almost two weeks ago we had an IRC meeting to define some of the 
stuff we need[ed] to do to migrate to salsa.debian.org.

**PLEASE** note that most of the stuff here applies to qt/* and kde/* (read 
below). *-extras might take different approaches. If in doubt, ask.

We've created a [gobby page] to add up the subjects at hand and also the 
decistions we took.

[gobby page] <https://gobby.debian.org/export/Teams/KDE/salsa>

In this mail I would like to wrap-up all that.

= Team name: switched to qt-kde-team

= Subgroups: created kde, kde-extras, qt, qt-extras (for their specific 
meaning read below).

= Admins: for now pino, maxy, mitya57 and I. This is of course something that 
has to be reviewed from time to time.

= Repos migrations to salsa.d.o: they are being done per subgroup "mostly":
  - qt: already migrated.
  - kde: as far as I understand has been fully migrated, but please check with 
mitya57, pino and maxy.
  - qt-extras: already migrated.
  - kde-extras: AFAIU most of the git repos have been migrated, we are still 
missing the ones in SVN. Pino strongly recommended to use svn-all-fast-export 
aka svn2git for this job. Again *please* check.

= Current alioth members: we [can't migrate] them, so everyone wanting access 
must create a user and ask for permission to join.

[can't migrate] <https://wiki.debian.org/Salsa/Doc#Import_members_of_a_team>

DDs keep their login name, others might change. This is not up to us but came 
with the system.

= Hooks
  - In salsa.d.o we can not keep using our old hooks. For that we need
    - Neon will need to create a WebHook if they want to keep receiving commit
    notifications from us.
    - We did not check which of our current hooks needs to get a port...
  - Irker (IRC gateway) We agreed to enable it at very least per subgroup on a
    different channel for each of them... if someone ask for it.
    For example qt/* could be enabled into #debian-qt-commits, kde/* in
    #debian-kde-commits, etc. Note: this names are just for the purpose of an
  - tagpending: we agreed to enable it, but sadly it could not be done by API
    while importing them, so it needs to be done by hand. Up to now and to the
    best of my knowledge only qt/* has it enabled for all it's repos.

= Issues: we have Debian's BTS, so we will not enable them.

= Merge request strategy: we decided upon "Fast-forward merge":

  No merge commits are created and all merges are fast-forwarded, which means
  that merging is only allowed if the branch could be fast-forwarded. 
  When fast-forward merge is not possible, the user is given the option to

Sadly this also could not be enabled through API, so it needs manual setting. 
TTBOMK only qt/*, www and pkg-kde-tools have it already enabled.

= Branches: we will keep our current standard: master is unstable (except 
maybe for packages just entering the archive trough experimental), 
experimental, <release codename>-backports, etc.

= After moving a repo:
  - Be sure to set up [ALiothRewriter] if needed.
  - Update Vcs-* fields to https://wiki.debian.org/Salsa/
    Take into account that there is *no* need to do uploads just for this!!!
  - Enable the tagpending webhook.
  - Enable the "Fast-forward merge" strategy. 

[AliothRewriter] <https://salsa.debian.org/salsa/AliothRewriter>

= Mailing lists
- pkg-kde-talk and pkg-kde-extras will be migrated to alioth-lists.debian.net. 
I have already asked alioth-lists admins for this.

= Website: as described in my previous mail to this very list.

OK, so up to this point it's what we decided on the meeting. Some other stuff 
got around after that:

= Krap replacement: new subgroup, now called 3rdparty.

= subgroups descriptions

This is something that sadly did not anticipate on time. From all the 
subgroups and TTBOMK only qt and 3rdparty have been properly decided upon. 
More info at gobby. Maybe we should try another IRC meeting for this?

If you've got to this point, thanks for reading ;-)

The box said 'Requires Windows 95 or better'. So I installed Linux.

Lisandro Damián Nicanor Pérez Meyer

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


Reply via email to