- 🇺🇸United States gdemet Chicago, USA
Closing out this issue, as work has moved to this ticket and associated sub-tickets: https://www.drupal.org/project/drupal_cwg/issues/3313322 →
Currently the git access agreement states:
To use Drupal's version control systems you, as an individual, must agree to the following
I agree to the Drupal Code Repository Terms of Service.
I have read and will adhere to the Drupal Code of Conduct.
I will cooperate with the Drupal Security Team as needed.
I will only commit code licensed as GPL-2.0+ and non-code assets licensed with GPL friendly licenses to Drupal project repositories.
I will only commit code and resources that I own or am permitted to distribute.
Furthermore, the Code of Conduct → states:
Be considerate.
Our work will be used by other people, and we in turn will depend on the work of others. [..]Be respectful.
The Drupal community and its members treat one another with respect. Everyone can make a valuable contribution to Drupal. [..]Be collaborative.
Collaboration is central to Drupal and to the larger free software community. This collaboration involves individuals working with others in teams within Drupal, teams working with each other within Drupal, and individuals and teams within Drupal working with other projects outside. This collaboration reduces redundancy, and improves the quality of our work. [..]
Given that there are ties between issue activity and marketplace rank, I believe the Code of Conduct should include a mention to follow good issue queue etiquette, as failing to do so can specifically lead to an appearance of game the issue credit system; gaming the system would be neither considerate, respectful nor collaborative.
Examples of gaming the credit system:
While there clearly can be situations where someone new to the various processes and tools might perform some of the above actions, it is hoped that as community members learn issue queue etiquette they not repeat such mistakes. For example, if someone realizes they have only been working on novice tasks for a while they might try looking for something a little larger to work on. Also, if someone is somewhat new to development with git (or development as a whole) they might not realize that they can upload a patch containing changes to more than one file, or commit more than one file change at a time.
Since its introduction the community has not had a wide problem of members attempting to game the issue credits system. However, there have been a few isolated cases of it happening. In the interest of guiding people towards improved behavior, I believe it would be worth specifically calling promoting improved issue queue etiquette and possibly warn people against attempting to game the system.
In summary, by bringing awareness to folks in the Code of Conduct about better issue queue etiquette we could potentially reduce the occurrences of these "issue queue smells" and help coax people away from trying to game the system.
Closed: outdated
Policies
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Closing out this issue, as work has moved to this ticket and associated sub-tickets: https://www.drupal.org/project/drupal_cwg/issues/3313322 →