FWIW the assumption that mail is involved seems to be flawed to me:
- if we imagine a dash in LP with 'things you should do', that could
(right now) include:
- bugs directly assigned
- code review directly requested
- blueprints directly assigned, or direct sign-off
and 'things your teams should do':
- archive queue admin
- bugs assigned to teams
- code review not yet claimed
etc
It seems plausible to me that 'request input' is a useful concept for
bugs ('is the proposed approach right?', 'can you please confirm that
X happens'), code review (as a super-set of 'request review'),
blueprints ('its time for the sign off now please'), distro queue
processing ('please explain where you want XYZ binary to go'),
projects ('X looks like proprietary code, can you please either make
it open or buy a subscription'), and so forth.
FWIW the assumption that mail is involved seems to be flawed to me:
- if we imagine a dash in LP with 'things you should do', that could
(right now) include:
- bugs directly assigned
- code review directly requested
- blueprints directly assigned, or direct sign-off
and 'things your teams should do':
- archive queue admin
- bugs assigned to teams
- code review not yet claimed
etc
It seems plausible to me that 'request input' is a useful concept for
bugs ('is the proposed approach right?', 'can you please confirm that
X happens'), code review (as a super-set of 'request review'),
blueprints ('its time for the sign off now please'), distro queue
processing ('please explain where you want XYZ binary to go'),
projects ('X looks like proprietary code, can you please either make
it open or buy a subscription'), and so forth.
-Rob