El viernes, 16 de febrero de 2018 05:45:33 -03 Boris Pek escribió: > Hi, > > >> Ok. In this case I may suggest you to use workflow similar to one in > >> Debian > >> Perl Group [1]. They do not add extra members to the main group [2], but > >> allow members joining to specific sub-groups (for example, [3]). Though > >> it is only in plans; they have not done the migration from Alioth and it > >> is not even documented yet. > > > > Well, as far as we do understand if someone wants to provide a branch for > > reviewing then [s]he should be at least Developer, which means commit > > access. Not ideal, but a trade off. Of course, feel really free to > > correct me if I'm wrong. > > This is only for a case when member should have push access to the main git > repo. But now this is not necessary if we use GitLab feature Merge Requests.
[snip excelent explanation, thanks for it!] Right, we where expecting to be able to do that but did not know for sure. Well, we need to revisit how we should handle ACLs then. I understand that depending on how a package in extras is maintained the ACL should vary too. > If you have another workflow in mind, please share your thoughts in more > details. Not for now. [snip] > >> 3) As for packages for KDE-extras and Qt-extras: apart from > >> described not "core" projects there are a number of projects which are > >> developed outside of KDE (or Qt) infrastructure [8], but closely related > >> with KDE (or Qt). And they also could (or should) be maintained in Qt/KDE > >> Extras Team. > > > > Mostly "could". As long as it does not interferes with the main reasons of > > being (qt and KDE stuff), it's could. > > Some of them really "should". Few examples from my personal experience: > > 1) Package xembed-sni-proxy [1]. Project initially have been developed on > GitHub [2], but later it was moved in KDE and has become the part of > plasma-workspace. > > 2) Package qtcurve [3]. Project initially have been developed without VCS, > then its development was moved to GitHub [4] and now it is a part of KDE > [5]. Right, problem is when you are in the github stage and don't even think of a project becoming part of KDE. But yes, it's not perfect. -- ¿Qué vamos a hacer esta noche Cerebro? -Lo mismo que todas las noches Pinky... ¡¡¡tratar de conquistar el mundo!!! Pinky y Cerebro. Narf. Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/
signature.asc
Description: This is a digitally signed message part.
-- http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk