As part of open-telemetry/community#847 the TC with the help of the experienced members will write "How to" guides that explain how to submit proposals and make changes happen in the specification repo. It is currently not clear for many members who want to add to the specification how to navigate this process.

We would like to have "How to" guides to be part of our "Contributing" documentation. The guides need to be specific, describe the process from start to the end (success or rejection) for each particular class of changes (e.g. "How to add a semantic convention"). It is important for contributors to understand clear actions they can take to progress a contribution. The aim is to have minimum ambiguity, but also leave enough flexibility in the process to make it useful.

Here is the preliminary list of topics for guides (create an issue to track each individually):

• Write "How to add a new attribute to semantic conventions" #1990
• Write "How to add a new set of semantic conventions (a new concept)" #1991
• Write "How to modify semantic conventions" semantic-conventions#2253
• Write "How to make a proposal for a new API" #1993
• Write "How to make progress on proposals that do not initially generate enough interest/comments." #1994

I also encourage TC, spec approvers or any other member to propose additional topics for "how to" guides.

Current members who have experience with the topic will write the guides (likely will be done by TC members and spec approvers).