Define the titling, and adding to issues/PRs

[Szelethus]

Tags/labels (basically keywords) are an easy way for anyone to identify the key aims of a patch/issue quickly. We should decide on how we want to do it.

Scope:

1. Decide the titling guidelines. Maybe .gitmessage?
2. Decide on tags/labels. Maybe GitHub labels?

DoD

1. Either CONTRIBUTING or .gitmessages is changed/added accordingly
2. Initial set of labels/tags are defined and either added to CONTRIBUTING or to Github (but not both)

[nettle]

Please excuse my ignorance, but what is the meaning of titling here?
Is it about the rules on how to format the title? The summary of git commit message or GitHub issue?

May I suggest just keep the title simple? Just short summary, starting from capital letter.

As to git commit message Summary here are just well-known points:

• Conciseness: It should be brief and to the point, ideally under 50 characters
• Imperative Mood: It should be written in the imperative mood, as if giving a command (e.g., "Fix bug," "Add feature," "Refactor code").
• Capitalization: The first letter of the summary line should be capitalized.
• No Period: It should not end with a period.
• Separation from Body: The summary should be separated from the message body by a blank line.
• Focus on "What": The summary should describe what the commit does, rather than how it does it. The "how" can be detailed in the commit message body if needed.

[nettle]

If we are thinking about labels?
May I suggest just use GitHub labels?
In this case we do not need to add them anywhere except GitHub which is perfect as of me!