Hi Jeremy, There is one thing at Patchwork that imposes a very high overload on my knees: the lack of a proper way to delegate work to project collaborators.
I receive more than 1,000 patches per Kernel cycle, and manage about 300 different drivers, with 20+ driver maintainers. Yet, I have to manually work on all patches at Patchwork and have a separate control to delegate stuff, as the way it currently implements delegation is not ok, due to a few reasons: 1) I'm using kernel.org facilities for Patchwork. As a project owner, I cannot give anyone else any extra permission. I'm forced to contact kernel.org manager, if I want do do it; 2) the way delegates currently works is at all-or-nothing basis: or somebody else will co-own the project, or will have only read-only access; 3) There's no way to store a "comment" about the current status. What I'd like to have there is a way where I, as the project owner, can delegate a patch set to one of the project contributors (general rule: the driver maintainer, but it would be nice to be just allowed to delegate a patch to any of the project contributors). At the time I delegate a patch to someone's else, I want to be able to update some "comment" field that would allow me to later remind why I've delegated that patch. Same when a patch is rejected, it would be nice to use the "comment" field to indicate the reason why. The delegated contributor should be allowed to modify the status only for the delegated patch. Could you work on a way to implement those? I'm not a python developer, and with all the overload I'm currently having, it is unlikely that I'll find any time soon to propose a patchset for it. Thanks, Mauro _______________________________________________ Patchwork mailing list [email protected] https://lists.ozlabs.org/listinfo/patchwork
