The following Herald rules would be useful:
Thanks!
Any admin can do that.
Hmm, I could imagine all the "Language-Q1-2016-17 Sprint *" tags to be subprojects or milestones instead and not require a Herald rule... :) But not trivial to fix now, just for next quarter please.
Created H179.
That quarter is over and I'm not going to apply those tags to any new tasks, so they can probably be reused.
In the light of T140605#2509316 and T141703: Review and consolidate current Herald rules could you please next time think before hurry? Thank you.
Since @Aklapper created new rule instead of reusing this one, can I archive it then (cf. T141703: Review and consolidate current Herald rules)?
@Danny_B: Regarding "hurry", task has been open for 13 days and Amir rightfully pinged on this task. Regarding "think", please read, understand, and acknowledge https://www.mediawiki.org/wiki/Bug_management/Phabricator_etiquette before any further activity in Phabricator. This is your second warning. Thanks for keeping Phabricator a respectful place.
Yes, he pinged you, but I've put the comment here which you ignored.
Regarding "think", please read, understand, and acknowledge https://www.mediawiki.org/wiki/Bug_management/Phabricator_etiquette before any further activity in Phabricator. This is your second warning. Thanks for keeping Phabricator a respectful place.
Can you please refrain from such threats? It's regular Czech saying. Thanks for keeping Phabricator a respectful place.
@Danny_B: I did not "ignore" a comment and I'd appreciate if you were more careful with your choice of words. I did miss your comment and actions in those 7 minutes that I was fixing this task, as I already wrote in T140605#2509390 (which you probably missed?).
Can you please refreain from such threats?
Such warnings (or "threats" as you seem to call it) can be avoided by choosing respectful tone and words - again, please see and follow the Etiquette if you'd like to avoid receiving "threats". Thanks for your understanding and cooperation.
So to quote the document you're referring to:
If you see someone not following these guidelines or not being productive:
- The first step is to contact them. This can be done through private email in minor cases, or in public in major cases to avoid any later assumptions of tolerated behavior.
We're both on IRC, there is Conpherence, there is email, but you still had to create this discussion publicly... :-/ If you contacted me on IRC, I would be perhaps totally willing to edit or remove the comment you didn't like considering the fact of edit conflict, which I obviously noticed (cf. T140605#2509396). Now you're only creating Streissand effect instead.
- Be informative – Tell what they are doing what they should not do. If pertinent, make them aware of this document.
Besides I don't see anything wrong on telling you that you acted wrong way in general, I don't even see how such notice would fall under anything written in that document. I don't see any relevant part of your posts following this point.
- Be catalytic – Tell what they should do instead. Occasionally this may be encouraging and motivating, better than a dense list of "rules".
I don't see any such action on your side as well.
So as we say in Czech: "if you say A, you also have to say B" - in other words: you can not cherry pick from rules and guidelines just what is handy to you at the moment. You have to follow them too.
Re "threats" vs. "warnings" - warnings are always threats of punishments, otherwise they wouldn't be warnings, but notices.
Anyway, besides this whole thread is off topic to this task, it is also heavily overreacted.
[offtopic]
See second part of the last quoted sentence...
If you contacted me on IRC, I would be perhaps totally willing to edit or remove the comment you didn't like considering the fact of edit conflict, which I obviously noticed (cf. T140605#2509396). Now you're only creating Streissand effect instead.
You can edit or remove comments but that's unrelated to (and does not improve) the general issue.
- Be informative – Tell what they are doing what they should not do.
- Be catalytic – Tell what they should do instead.
I don't see any such action on your side as well.
Do not reply to community members by telling them to "think first" as it implies that they had not. Instead, please criticize ideas instead of people.
Hope this helps. :)
I'd like to point out that global herald rules have a cost to execute which is non-trivial and adding an ever-increasing number of rules for recurring things like sprints / milestones will end in madness. We already spend over 100ms on processing herald rules for every new task submitted. We simply can't add 100s of new herald rules for every niche use-case that people come up with.
Indeed. (I'll add my general comment to T141703.)
I've archived H151 as per T140605#2509389 above.