Add Section Heading “I want to report a software or documentation issue I have found”

This looks pretty good to me!

I'm not sure what you mean in comment #2 about "ownership"... but I think it would be good to mention that each sub-project within the Drupal community has its own issue area.

I think it might also be good to avoid use of the word "queue" without explaining it. We do call them issue queues, but that could be confusing to a new member of the community coming to the page.

So, I suggest this revision for the second sentence and third paragraph:

Each project on Drupal.org (Drupal Core, modules, themes, and distributions) has its own public area for issue tracking, known as an issue queue, where anyone can report and collaborate on fixing issues. Security issues are handled in a separate, confidential issue queue, to ensure that they are fixed before vulnerabilities become public.

Then in the list of groups actively involved, I would add
* Maintainers of individual modules, themes, and distributions

On the beta page there seems to be a strange <br> tag.

<a href="/security-team/report-issue">using<br>
                    their guide</a>

And another one:

<a href="https://drupalslack.herokuapp.com/">sign up to<br>
                    drupal.slack.com</a>

Added capital letters to the "You can connect with other members" unordered list.

Fix a couple of typos in the text, and made the bullet list more consistent with its header (which ends in "... through:".

Also... the link to report security issues... one place it is /security-team/report-issue and in another it is node/101494. ???

https://www.drupal.org/node/101494 can be replaced by: https://www.drupal.org/security-team/report-issue since it has a clean URL =)

This looks excellent to me! I think it is probably ready for RTBC?

Yes looks good!

I'm wondering if it makes sense to change the name of this section to "I want to report an issue with the software or documentation" so that it's more clear that this is distinct from reporting code of conduct or other issues?

I think that is an excellent idea. Way to go, channeling the Drupal newcomer who may not understand that by 'issue' we mean something very specific!

Also, since you bring up documentation issues, we should add some notes about that, because it may not be obvious how/where to report docs issues. So, I added some content there.

Also updated for the new chat standard text... needs review again!

I think it's nearly there. But if I'm a newcomer who finds this page, I may think "where do I find the maintainers of individual modules? or of Core? or of this site itself?" Is there a page or graphic that explains where to see this information? If not, would a screenshot be helpful? Do maintainers get messages via d.o contact form currently? If so, mentioning etiquette on using Contact form would be helpful here or on a subsequent page.

Setting to Needs Work for #20.

My thoughts on that: Good point!

As a contrib maintainer, I want to have people who think they have found a problem with the software to create an issue. I absolutely do not want them to contact me using my d.o contact form. I consider that to be somewhat rude, because then I have to create an issue so that I can track the problem, so that there is a record of it (even if it's not determined to be an actual software bug, having a record of what someone thought was a bug can be useful for the next person who thinks the same).

I think most contrib maintainers feel the same way, and it's also definitely true for Drupal Core.

So, I think it would be a good idea to put in a sentence or two explaining that contacting the software maintainers directly is not encouraged, rather than just (as this section does now) saying to use the issue queues.

I absolutely do not think we should be highlighting how to figure out who the maintainers of a module are. We really don't want to encourage people to contact them via social media or contact forms. We need the issues.

That is my opinion anyway...

I posted a link to this issue in the #contribute Slack channel, to see if other module/theme/core maintainers have opinions on this (#21 is just my opinion really).

As a contrib maintainer, I want to have people who think they have found a problem with the software to create an issue. I absolutely do not want them to contact me using my d.o contact form. I consider that to be somewhat rude, because then I have to create an issue so that I can track the problem, so that there is a record of it (even if it's not determined to be an actual software bug, having a record of what someone thought was a bug can be useful for the next person who thinks the same).

I agree with this.

Yep, it needs to elaborate because mails could get lost but issues will keep history "forever" (event if report is duplicate)
Moreover contact form has no docs about its usage (I recall only "dealing abandoned projects" case) also people can disable contact form access

OK... assuming most other contrib maintainers agree with me (and I'm sure Core maintainers don't want to get contact form email about bugs!), I'll update the text a bit. Thoughts?

I agree with #21.

Also some modules have more than one active maintainer so contacting directly can be hit/miss. Issues are much more efficient.

I do see a bit of frustration on issue queues when maintainers haven't responded in a while (which has led to me offering to maintain a couple of modules). I think useful meta information here might include:

• What the role of a maintainer is
  • Just check and commit RTBC patches?
  • Review and commit?
  • Fix the entire bug by themselves?
  • Changes from module to module (i.e. avoid assumptions)?
• What sort of timeframes are considered appropriate in this community
  • i.e. please don't demand an answer one hour after posting an issue
• How to get help when you're really stuck
  • Rather than just mention Slack - indicate that it's a good place for real-time support, especially in the #support channel

I know a lot of this is covered elsewhere... but people don't go looking for it :)

Good points in #26. I located some documentation about maintainership, and am adding links to the text. Thoughts?

Oh, regarding "How to get help when you're really stuck"... I think that should be a separate section, and I don't think it's covered in this one, which is about how to report a software or docs bug. Oh yeah, we already have #3004623: Add Section Heading “I want to find help installing and using Drupal”, so I think we should leave it to that section to cover how to get help when you're stuck.

Looks great, makes sense, no further feedback from me :)

Looks very complete to me! Great work.

The text is helpful! Looks great to me!