Best Practices: Issues

Best Practices

1. Ensure there is not another open issue that addresses the same or similar concerns.
2. Label the Issue appropriately. If a Label does not exist, please create it and add a description of its meaning to this wiki page. Do not use excessive quantities of Labels.
3. If you are going to definitively work on it, then assign the Issue to yourself. If someone asks you to make an Issue, or it's someone's responsibility (broken previous push), then assign to somebody else.

Labels

• high priority indicates an especially above-standard importance
• low priority indicates an especially substandard importance
• bug indicates an error or fault in the software
• content indicates something related to the content in the website
• enhancement indicates a new feature or a new addition to a feature to the website
• fix indicates that there is a suggested fix in the body
• problem indicates that something is not necessarily a "bug" but is still wrong
• duplicate indicates that the issue is a duplicate of another (and should be closed)
• question indicates that the poster of the issue would like feedback or help
• things to keep in mind indicates that there is a pressing concern to update a gem, or something of the sort
• update indicates an update that needs to occur
• feedback indicates suggestions from an outside source
• wontfix indicates that the issue is not going to be fixed, or is not an issue
• meta indicates that the issue relates to team8.github.io Issues
• wiki indicates that the issue relates to team8.github.io Wiki
• best practice indicates that the issue relates to a best practice for development or setup
• team functioning indicates that the issue relates to a way the web team functions