Hello, I don't remember if I already suggested this feature, or if it has been suggested in the past already. If that's the case, then sorry for the duplicate.
Over at the Buildroot project, we often handle a fairly long queue of patches in our patchwork, currently around 350+ patches. One thing that I'm missing is a way of triaging/tagging the patches, like which ones are for the current release, which ones are clearly for the next release, etc. Each project probably has different tagging/classification needs. Wouldn't it be useful to create a tagging system which allows to associate an arbitrary list of tags to each patch. This could even replace the delegation feature by adding special tags like "delegate:<account>" to delegate the patch to a certain user. This would also have the benefit of allowing the delegation to more than one user, by simply having several "delegate:<account>" tags on the same patch. This of course should come with filters in the web UI, in order to filter patches depending on the tags that they have. Thoughts? Side question: has the patchwork project considered participating to the Google Summer of Code? I believe patchwork is really a good project for GSoC students: it's using a technology that is worth learning, getting into the internals of patchwork is not too complicated, etc. Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com _______________________________________________ Patchwork mailing list [email protected] https://lists.ozlabs.org/listinfo/patchwork
