Voting starts in March for the Drupal Association Board election.
following the proposal to add Flag module to the Issue tracker, to provide subscribe/unsubscribe links, and the proposal to add remove Actions/Triggers from D8 core (advanced with add Rules to D8 core), i'm presenting an idea:
add Rules module to perform some or all conditional actions when certain events occur, for the drupal.org issue tracker.
following the subscribe/unsubscribe idea logic, Rules for example, could optionally perform email actions, when new comments are added, or on schedule to save resources and reduce amount of mails (like say just once a day with a resume, taken from a View)
... that View being imported to Rules with Rules Views Integration, which allows Rules to execute/include Views and Views to execute Rules.
other things Rules could do:
* co-work with Cache Actions to issue a cleanup on specific caches on Drupal, Views and Panels, assigned to the nid/cid being affected by the Flag
* have Rules and Cache Actions work with Fivestar, Rate and other Voting API modules through Voting Rules.
* alert project maintainers when issues are created
* alert users when their issues are closed
* anything Actions/Triggers already does
there are some supporters of Rules to be used in Core and/or on drupal.org, but there is also some against it, stating that Actions/Triggers is enough, and Rules is too immature and complex.
personally, i think Rules is complex, yes, but it's also mature, not immature, and much, much more powerful. it integrates Token module (something Token Actions in Token bundle also does for Actions), but goes further with PHP support for example, plus much, much more.
let me also state, that while being complex, documentation does exist, and the module does work. once you get the hang on it, it's actually easy to work with it.
regarding support from other modules,
lots of modules supporting Rules have been developed, plus a plethora of integrations.
for example, Drupal Commerce and Ubercart have moved into Rules, and ignored Actions in their planning. and Cache Actions, for example, does not support Actions... only Rules.
the ecosystem is big and gets bigger all the time - many if not all of the major players already support both Actions and Rules.
Rules is also considered by many people, the future of conditional actions in drupal, to supersede Actions and Triggers, Workflow-ng, Conditional Actions and other older modules.
IMO, besides the advantages stated above, as Rules' development goes on and the project is quite active and supported and stable, it makes it a good candidate for drupal.org.
more about rules: