= Migration to salsa https://wiki.debian.org/Salsa/Doc = Stuff to check * Naming of the team - mitya57 suggests qt-kde-team ← agreed - Team name = Debian Qt/KDE Team ← agreed - Should we create any subgroups? Suggested: kde, kde-extras, qt and qt-extras ← agreed - Admins: pino, maxy, mitya57 and lisandro - Migration: done per subgroup, put alioth git repos in read only mode after that - Non-admins: should be added as developers * Repos to move - git - How to move https://wiki.debian.org/Salsa/Doc#Import_git_repository - svn - Agreed: try at home and share results. - need to get username to fullname mapping - Use svn-all-fast-export aka svn2git. - Use "debian/" prefix for tags * Migrate all members, or require explicit join requests? Agreed: ask for rejoin - we can't migrate members accroding to https://wiki.debian.org/Salsa/Doc#Import_members_of_a_team - Seems python team achieved it to do it with DDs - Logins are the same for DDs, for guest accounts the login name may change After the move: - check https://salsa.debian.org/salsa/AliothRewriter in order to redirect anonscm urls. - update VCS fields to https://wiki.debian.org/Salsa/Doc#Canonical_Repository_URLs No need to do uploads just for that * Hooks to enable - Irker (IRC gateway)? Agreed: enable it if someone asks for it, but on a separate channel. - tagpending Agreed to enable it (needs manual editing).Done: Qt/*. Can be done with https://salsa.debian.org/mehdi/salsa-scripts * Alioth hooks: should we create/modify webhooks?git checkout pristine-tar * Whether to enable issues (agreed: no issues, we have the BTS) and/or merge request (agreed: yes) * Merge request strategy (merge commits vs. rebase) Agreed on rebase - Is rebasing a good thing in public branches? (it will be very hard to keep history and break workflows, but normaly you can rebase before you merge) Note: rebasing is not about public branches, it is about temporary feature branches which are usually deleted after merging anyway. Done: qt/*, www, pkg-kde-tools * Should we migrate pkg-kde-talk ML to alioth-lists.debian.net? or l-d-o? (it's a simple human ml) Agreed: switch to alioth-lists.d. Lisandro asks for its migration and also for pkg-kde-extras. Status: asked for both lists migrations, although it might be possible that we need another mail for -extras. * use the "standard branch names" ( http://dep.debian.net/deps/dep14/) aka debian/sid, debian/experimental - this is mostly independent to salsa migration and can be done later - please no - but we can use this layout for new git repositories (and those migrated from svn) Agreed that we will keep our current standard, master is unstable, etc. No sources in qt, kde, allowed up to the maintainer in -extras. = Website (currently at pkg-kde.alioth.debian.org) https://wiki.debian.org/Salsa/Doc#Host_project_web_pages Maybe we can use https://about.gitlab.com/features/pages/ + some static pages generator (I have good comments about Pelican, but whatever we can put in GIT). I would suggest something that uses markdown for writing... I like lektor, Pelican also looks nice... - mitya57 has some experience with Pelican, mkdocs and Sphinx, all these are great tools - please not something complex - I agree Agreed: we keep www for now, mitya wants to change the website in the following months = After the meeting = - Consider adding 3rdparty to replace -krap as a subproject like qt, qt-extras, kde and kde-extras. - Consider adding the corresponding rewrites (definitions/qt-kde-team.conf in https://salsa.debian.org/salsa/AliothRewriter) - Decide a criteria to give master level permissions to other contributors Possible definitions of the subprojects: - Qt: the Qt libs proper. - KDE: plasma, kf5, etc. (please someone with the right knowledge complete). Each and every project which is hosted on kde.org, per manifesto (https://manifesto.kde.org/commitments.html) *is* KDE. There is no "core" anymore, even if few projects are more known. Frameworks, Plasma, (the bundle known as) KDE Applications, Krita, Partitionmanager, GCompris, AtCore, KXStitch and so on are all at the same level. So maybe the old division is not good enough anymore. Now, I'm not a DD here so it's just a suggestion: if it's not possible to have sub-subgroups to group big blocks, just go with a flat namespace. - the description already conveys it: Frameworks, Apps, Plasma; the rest is just PR-bullshit which does not apply here, since these groups are only team-internal stuff ← I (Lisandro) agree that the definition should be team-internal more than forced from outside. - even if KDE stays for the "big 3", the description of KDE-extras should be changed then (or split between what is on kde.org and what is not, but no big deal about this; just reflect the meaning of the content). - the name "kde-extras" comes from the old extragear stuff; the team cannot change internal names every time upstream decides to rebrand stuff, especially when the names discussed in this context are internal structure, and as long as people working on it know what's in each, upstream naming/marketing does *NOT* apply - Qt-extras: stuff using Qt but not being Qt proper which someone wants to maintain. - KDE-extras: official KDE stuff not part of the core (please check that!) and/or stuff using kf5 libs that are not official KDE projects. See above. Maybe it can be repurposed as "projects using Frameworks but not part of KDE", but then maybe call it just "extras" and unify it with Qt-extras? grantlee and basket are both Qt 5 applications/libraries, they just differs in the number of linked Qt-based libraries. - 3rdparty: stuff that we maintain because some package in the other subprojects require it, but we are happy to give away if someone asks. Migrated ======== A more up-to-date list is available here: https://salsa.debian.org/salsa/AliothRewriter/blob/master/definitions/qt-kde-team.conf * pkg-kde/qt - sni-qt moved to qt-extras - qt-simulator, qt-sdk, qt-web-runtime, qtdeclarative-render2d, qtenginio not migrated (obsolete) - qt-sdk is in stable, so it should be migrated too (according to lisandro) * pkg-kde/qt-extras: qtav -> qt-extras, gcompris-qt -> kde-extras - kde-req/qca2.git -> qt-extras/qca2 - also libdbusmenu-qt and qjson are migrated from krap to qt-extras * pkg-kde/kde/frameworks/ -> kde/ * pkg-kde/kde/plasma/ -> kde/ * pkg-kde/applications/ (all non-symlinks) -> kde/ * pkg-kde/calligra/ -> kde-extras/ * pkg-kde/kde-extras/: basket colord-kde exiv2 kaffeine kamoso kdeconnect kile kjots knights konversation kronometer krusader libktorrent ktorrent kvirc labplot libaccounts-qt libqaccessibilityclient plasma-applet-redshift-control qapt qt-gstreamer skanlite soundkonverter subtitlecomposer yakuake zanshin * pkg-kde/kde-extras/kde-telepathy/: telepathy-logger-qt telepathy-qt * pkg-kde/kde-req/ polkit-qt-1 -> kde-extras/polkit-qt-1 * repos in root namespace: www pkg-kde-tools pkg-kde-jenkins pkg-kde-dev-scripts Not migrated yet ================ * pkg-kde/attic/ * pkg-kde/deduplication-wastebin/ * pkg-kde/kde-extras/ (the remaining packages) * pkg-kde/kde-extras/kde-telepathy/ (except telepathy-logger-qt telepathy-qt) * pkg-kde/kde-sc/ * pkg-kde/krap/ (should go to qt-kde-team/3rdparty) * repos in root namespace (except www pkg-kde-tools) Results from 2018-02-11 IRC discussion ====================================== - libdbusmenu-qt and qjson should be qt-extras [done] - gcompris-qt should be kde-extras [done] - create a new subgroup 3rdparty [done], migrate krap/ namespace there - put the common tools (pkg-kde-{tools,dev-scripts,jenkins}) to the toplevel group (well, this one actually was from 2018-02-12)