Page MenuHomePhabricator

Herald rule for Community Tech
Closed, ResolvedPublic

Description

Not sure if this is appropriate use of Herald, but what we would like is:

Some of us do get emails when tasks are created for these projects, but as a team we are trying to make sure take responsibility for maintenance and support of our tools. This Herald rule would force us to discuss each task at our sprint plannings.

Thanks!

Event Timeline

I've renamed that project, and given it the alias of MediaWiki-extensions-GlobalPreferences. Should work now.

Aklapper claimed this task.

Created H260:

  • When all of these conditions are met:
    • Projects include any of CopyPatrol, ia-upload, XTools, Tool-Pageviews, MediaWiki-extensions-PageAssessments, MediaWiki-extensions-CodeMirror, MediaWiki-extensions-GlobalPreferences
  • Take these actions the first time this rule matches:
    • Add projects: Community-Tech.

Note that this rule is not applied retroactively. You could mass-add the tag to tasks if wanted.

We need to modify this. It should only add Community-Tech if the task isn't already assigned to Community-Tech-Sprint. Hope that's possible.

(Which makes me wonder why Community-Tech-Sprint is not a subproject of Community-Tech, but alright :) Rule adjusted accordingly.

@Aklapper Sorry, could we actually remove XTools from this rule? Unlike the other tools, XTools has a dedicated team (myself included) that is there to respond to requests. The auto-tagging of Community-Tech is proving to be more often than not undesirable. I can simply manually add the tag if appropriate. Thank you!

@Aklapper Sorry, could we actually remove XTools from this rule? Unlike the other tools, XTools has a dedicated team (myself included) that is there to respond to requests. The auto-tagging of Community-Tech is proving to be more often than not undesirable. I can simply manually add the tag if appropriate. Thank you!

I removed Xtools.