Organise Repository

[Southclaws]

The repo needs some housework in regards to issue labels and standardised naming conventions.

I've settled on [Prefix] for issue names, now to organise labels to reflect these so the prefixes aren't necessary.

This is based off of Scavenge and Survive and Yashas' work on the Pawn compiler repository labels.

Should probably use this: https://github.com/jhare/github-label-copy

Labels can be in a few formats:

• type: subtype
• type:subtype
• Type: Subtype
• Type:Subtype
• [type] subtype
• type/subtype
• Type/Subtype

Not sure which is easier to read yet...

area (blue)

• meta - issues regarding issues themselves and GitHub in general
• repo - repository layout, dot files, etc
• build - the sampctl build and ensure process, dependencies, etc
• code - an actual source code problem, bug, regression, etc
• gameplay - a problem with a gameplay mechanic that isn't related to code bugs

status (yellow)

• confirmed - the bug has been confirmed
• deferred - put off until a later time or depends on something else being solved first
• in-progress - actively being worked on
• duplicate - duplicate of another issue
• invalid - doesn't warrant an issue at all
• cannot reproduce - the bug cannot be repeated by developers, possibly user error
• discuss - requires discussion before further action

type (green)

• question - a question regarding the area the issue is about
• suggestion - a high-level suggestion for an idea, little to no implementation details or roadmap
• proposal - a formal proposal for a new feature or change to a feature that includes implementation details
• bug - unexpected behaviour caused by mistake in code
• regression - bug caused by upstream changes
• optimization - an improvement that relates to performance of the code at runtime

severity - these apply only to type: bug issues

• class-A - (black) a run time error that crashes the server or causes memory corruption
• class-B - (red) significantly impairs its basic functionality or prevents feature access/use
• class-C - (orange) purely visual or gameplay related annoyance, does not impair functionality

others (grey/teal/neutral colour)

• good first issue - good for a new contributor
• help wanted - help wanted from another contributor

pull requests:

• work in progress - pull request should not be merged
• needs test - requires testing
• needs docs - requires documentation
• needs discussion - requires discussion before further action
• needs review - requires another contributor to review