Hey, > But just in curiosity, why do you need maintainership of my repo? Isn't it > possible to just fork my projects to KDE team or do you plan to directly > move it to Debian Qt/KDE team?
Sure fork is always possible. With a move all links will be forwarded automatically by gitlab and it is not shown, that the Qt/KDE team repo is a fork of ybx332's. And with a fork we would need to care about what happens if ybx332 delete their repo in future? In the end it we know a move works great and is known, so it is our best practice to use move instead of a fork ;) Regards, hefee
signature.asc
Description: This is a digitally signed message part.
-- https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-kde-talk
