signature delegation on specific packages
vlimant opened this issue · 4 comments
sparked from the discussion in cms-sw/cmssw#42323 about PhysicsTools/NanoAODTools package that is @cms-sw/xpog-l2 signature, but actually belongs to CAT (@clelange @lenzip) ; would it be possible, instead of creating a CAT signature category, to have that package belong to xpog, with delegated signatures ?
might sound a bit silly, since we'd probably have to create a CAT group in https://github.com/cms-sw/cms-bot/blob/master/categories.py anyways to maintain names
A new Issue was created by @vlimant vlimant.
@Dr15Jones, @perrotta, @dpiparo, @rappoccio, @makortel, @smuzaffar, @antoniovilela can you please review it and eventually sign/assign? Thanks.
cms-bot commands are listed here
Assign core
New categories assigned: core
@Dr15Jones,@smuzaffar,@makortel you have been requested to review this Pull request/Issue and eventually sign? Thanks
@vlimant , PhysicsTools/NanoAODTools is new package and currently there is no one responsible for this. xpog signature on cms-sw/cmssw#42323 are due to changes in PhysicsTools/NanoAOD package. If the new package should belong to CAT then we should just add cat as a new cms-bot category. If it really belongs to xpog then we can add it under xpog and add @clelange @lenzip to the watcher list ( https://github.com/cms-sw/cms-bot/blob/master/watchers.yaml ) so that they can get notifications if someone proposes changes to this package