docs: add community contribution guides

[Supull]

Fixes #6828

• Add Community-Contributing overview
• Add Reporting-An-Issue how-to
• Add Making-A-Pull-Request how-to
• Add Reviewing-A-Pull-Request how-to
• Add Triaging-An-Issue how-to
• Link all new guides in Contributing.rst toctree
• Update Contact.rst to link new guides
• Update index.rst to mention community guides
• Add quick start section to Contributing-To-ROS-2-Documentation.rst
• Add language summary table to Code-Style-Language-Versions.rst

Did you use Generative AI?

Gemini used to help write the new RST files with better wording.

Additional Information

No new dependencies. Build passes with no warnings or errors.

[fujitatomoya]

i'm not against adding contribution guides in principle, but this is fairly standard Git/GitHub workflow that's already well documented elsewhere. i'd rather not maintain generic workflow docs in this repo unless they capture procedures or rules specific to ROS 2 contributions. let's hear more feedback on this.

[Supull]

i'm not against adding contribution guides in principle, but this is fairly standard Git/GitHub workflow that's already well documented elsewhere. i'd rather not maintain generic workflow docs in this repo unless they capture procedures or rules specific to ROS 2 contributions. let's hear more feedback on this.

Thanks for the feedback I will keep an eye on the discussion

[kscottz]

Thanks a bunch @Supull. We actually have some help from a contractor putting together a more in depth series on contribution. We would really value some feedback on that front. You are more than welcome to review #6901 and #6892.

[Supull]

Thanks a bunch @Supull. We actually have some help from a contractor putting together a more in depth series on contribution. We would really value some feedback on that front. You are more than welcome to review #6901 and #6892.

Thanks @kscottz I am happy to take a look. I'll review #6901 and #6892 and leave feedback there.

[RachelPotts]

@Supull and @kscottz
We've taken a look at these, and there's a lot of overlap with a package of work we're quite advanced with already.
We'll do a skim for anything that can obviously be incorporated there, but the most effective thing will be to take a look at our PRs and add your comments there about any essentials that aren't covered.
Listed by article:
These are already deep in review:

• Contributing to ROS 2 Documentation (ready to merge, I believe) - 3di | Contributing to ros2 documentation #6835
• Making a Pull Request - 3di | Making and reviewing a pull request #6892
• • Reviewing a pull request - 3di | Making and reviewing a pull request #6892
• Reporting an Issue - 3di | Triaging and reporting an issue #6901
• Triaging an issue - 3di | Triaging and reporting an issue #6901

PR coming soon (today/tomorrow) - I've checked these and I think we've already covered everything, though our approach is a bit different:

• Community-contributing
• Contact

Changes planned, but only after everything else is merged - we'll make sure the proposed change is taken into account when we do this:

• Index

No significant changes planned to this one:

• Code-Style-Language_versions

[Supull]

Thanks for the context! Happy to close this in favour of your PRs. I'll leave comments on #6892 and #6901 if I spot anything missing.

[RachelPotts]

Thanks for the context! Happy to close this in favour of your PRs. I'll leave comments on #6892 and #6901 if I spot anything missing.

Ok! Maybe still helpful for you to make the change just on Code-Style-Language_versions as we won't be touching that.