Sometimes, a well meaning, but ultimately unfruitful, comment can derail an issue's purposes and have a snowball effect for hurting people's feelings.
Project Issue could help with comment validation and workflows, but the underlying factor of etiquette is a matter of interpersonal relations and personal skills of maintaining appropriate level of dialogue and quelling discontent when things take a turn for the worse.
The DCOC → provides a foundation of good standards and is a valuable tool for defining the nature of the community, however it seems that a it doesn't provide enough concrete recommendations for maintaining useful discussion. So adding further documentation with recommendations that target all issue may provide tools that will help all users help each other more effectively.
When these problems arise, one person simply pointing another person to the DCOC may not give a clear enough picture of how they can turn things around, and canned responses can be mildly offensive especially when used improperly. Therefore, identifying situations and behaviors from groups of users and including this documentation with issue queue guides may help build a foundation for a set of recommendations to those users.
Identified situations:
* Over-zealousness on the part of contributors to battle back and forth over metadata
* Quickness from pull-requesters to "take my ball and run", fork, etc when met with resistance on the part of the maintainers
* Inflexibility on the part of maintainers, ie to "won't fix" issues instead of exploring the intents of the submitter and trying to find a satisfactory middle ground or an alternative approach
* Quickness to redefine issues without being respectful or seeking clarification from the submitter
This is an example directed at maintainers:
* If you maintain a project...
- expect to be surprised from your users, both pleasantly and unpleasantly. Your early adopters are very special. They will become the heart of your project if you embrace them. Some users will wish to extend your project and even if the change doesn't strike you as an improvement, it may be because you haven't reached far enough in your dialogue to find something that would be beneficial to you, your users, and a subset of users who ask for a change. The important characteristics of a good maintainer are flexibility, good leadership, and commitment to the cause.
--- Original summary:
Is there an "official" policy or guideline for changing the details of an issue? The topic starter of
#966530: Securing the default login in Drupal →
is (IMHO) disrespectful to the opinion of the majority there. I'm not sure if anyone should take action here, I'm just curious if there is any kind of guideline somewhere.
Fixed
Policies
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Closing out this very old and long-ago fixed issue. The issue queue etiquette page at https://www.drupal.org/docs/develop/issues/issue-procedures-and-etiquett... → addresses the concerns that prompted this issue.
Automatically closed - issue fixed for 2 weeks with no activity.