[RFC] Using main cmssw repository for L1Tracking development

[iarspider]

As discussed during yesterday's Core Software meeting, we propose the following solution for better integration of L1Tracking development in CMSSW:

• Create a new category (similar to, e.g. heterogeneous) and add these pacakges to it: L1Trigger/TrackFindingTracklet, L1Trigger/TrackFindingTMTT, L1Trigger/TrackerTFP, L1Trigger/TrackerDTC, L1Trigger/TrackTrigger, DataFormats/L1TrackTrigger
  • These packages currently are in l1 category, we can move them out
• Add corresponding experts to that category
• Add special tests (similar to, e.g., gpu) that can be requested in addition to regular tests

This way, when a PR is opened that changes files under these packages, only the relevant experts will be notified, and their signature will be required to merge the PR.

@tomalin FYI

[cmsbuild]

cms-bot internal usage

[cmsbuild]

A new Issue was created by @iarspider.

@Dr15Jones, @antoniovilela, @makortel, @mandrenguyen, @rappoccio, @sextonkennedy, @smuzaffar can you please review it and eventually sign/assign? Thanks.

cms-bot commands are listed here

[smuzaffar]

thanks @iarspider for opening this issue.

These packages currently are in l1 category, we can move them out

The should remain under l1. We just add these packages under new l1track too

[smuzaffar]

type doc

[smuzaffar]

Add special tests (similar to, e.g., gpu) that can be requested in addition to regular tests

@tomalin , for additional l1track tests, we need to teach bot how to recognize it and what to run. You can see https://github.com/cms-sw/cms-bot/pull/2354 and https://github.com/cms-sw/cms-bot/pull/2240 as examples for running enable and run extra PR test. @cms-sw/externals-l2 can take care of it if you point us your current test ( run via gitlab ci) Or feel free to open cms-bot PR

[makortel]

assign l1

[cmsbuild]

New categories assigned: l1

@aloeliger,@epalencia you have been requested to review this Pull request/Issue and eventually sign? Thanks