Skip to content

Latest commit

 

History

History
76 lines (47 loc) · 3.03 KB

CONTRIBUTE.md

File metadata and controls

76 lines (47 loc) · 3.03 KB
Raw

Contribute.md

Team members

Learn & listen

All communication regarding this project happens through Github. You can find the https://github.com/glompix/InjectCC/wiki and [https://github.com/glompix/InjectCC/issues](Outstanding Issues) there. Tweet @glompix if you have any questions.

Adding new features

This section includes advice on how to build new features for the project & what kind of process it includes.

  • This is how we like people to add new features: TODO (wiki article? txt files + pull?)
  • Here are some specifics on the coding style we prefer: TODO (stick with VS default formatting)
  • This is how you send your pull request: TODO
  • You should include the following tests: TODO
  • These are the updates we hope you make to the changelog: TODO

Though I really love working on this project, I love my girlfriend and DotA more. I usually respond quickly, just not on the weekends.

Bug triage

This sections explains how bug triaging is done for your project. Help beginners by including examples to good bug reports and providing them questions they should look to answer.

  • You can help report bugs by filing them here:

  • You can look through the existing bugs here:

  • Look at existing bugs and help us understand if ** The bug is reproducible? Is it reproducible in other environments (browsers)? What are the steps to reproduce?

  • You can close fixed bugs by testing old tickets to see if they are happening

  • You can update our change log here

  • You can remove duplicate bug reports

Beta testing

This section explains if your project needs beta testing. Explain why early releases require heavy testing and how they can help with specially across browsers and on different hardware.

  • For our project you can find the roadmap and features that require testing from here:

Translations

This section includes any instructions or translation needs your project has.

  • You can help us translate our project here:

Documentation

This section includes any help you need with the documentation and where it can be found. Code needs explanation, and sometimes those who know the code well have trouble explaining it to someone just getting into it.

  • Help us with documentation here

Community

This section includes ideas on how non-developers can help with the project. Here's a few examples:

  • You can help us answer questions our users have here:

  • You can help build and design our website here:

  • You can help write blog posts about the project by:

  • You can help with newsletters and internal communications by:

  • Create an example of the project in real world by building something or showing what others have built.

  • Write about other people’s projects based on this project. Show how it’s used in daily life. Take screenshots and make videos!

Your first bugfix

This section should help a person get started with their very first bug fix and thinking through the problem.

  • If you have further questions, contact: