GitHub repository: steeminator3000/Contribution
Created: 2020-05-21T17:26:01Z
Description: ### Contribution We believe the power of the open source projects and we will always be strong defender of that , Are you like us and want to contribute to Dtube ? Thats great ! Here is a guide to help you , how should you proceed during this process.  ### Coding Several super smart , wise and helpfull people, as well as our CTO have contributed to Dtube. We believe true power of open source projects and if you believe too Join us !  ### How To Contribute Code Join our community . By joining our [chat](https://discord.gg/BcTr97) , you can interact with other developers , or you can use **help** channel when you have questions, ideas, or problems. Identify the component you want to work on. Dtube  has code bases that deal with everything from cryptography and distributed systems to end-user graphic user-interfaces. We use  JavaScript,.  **Get set up.** Each repo has a README with clear instructions on how to get the repo up and running properly. Thanks, Repository Standards! Find something to work on. All actively developed repositories should have issues tagged “Good First Issues” specifically for new contributors. You are also welcome to work on something not currently filed if you have your own idea. Feel free to contact us or leave a message if you are having trouble to find some issue to work on. **Abide coding and commit standards**. Any specific information necessary to know in this regard should be in the project README. ***Commit early and ask questions. Is an issue confusing? Please comment and say so!, don't hesitate to ask questions. Not sure if you’ve got the right approach? Commit your code and we’ll give feedback as soon as possible. Commit it anyway, once you commit, open a pull request. We encourage work-in-progress commits to let us know you’re working on something and to facilitate feedback. **Accept feedback and finish**. Most of the pull requests will be reviewed in couple of days. Once the repository maintainer has approved your contribution, it will get merged and we will really try hard to show our respects by giving out some DTC even if you are really humble and nice person. # Designing Web and application designers are requested to be able to work directly on CSS in the project they’d be contributing to. Please follow the Coding instructions for any website or application you want to improve.  We’re happy to provide assistance if you’re used to working in HTML and CSS but are having trouble getting started. Check out our [chat](https://discord.gg/BcTr9).  # Writing Most written content, and especially all technical writing, will be checked and it will go to source control by our team , to improve our current documentations or create a completely new one.  Identify which website or application it is in. Search for a quoted phrase of the content you want to change (or use the same technique to identify the folder to create a new document in). Edit the content via the GitHub interface and submit it as a pull request. # Translating Translation work is primarily released from time to time and you can contribute anytime from (here)[https://crowdin.com/project/dtube] . Each time we upload our translation files all the current translators in the project will receive a message.  # Testing If you want to contribute without getting directly into the code, one of the best ways you can contribute is testing.  A number of our code bases (dtube dtube dutbe) go through regular release cycles where new versions are shipped every several weeks. Testing pre-release versions is a great way to help us identify issues and create a bug free version.    # Raising Issues All bug reports and feature requests are managed through [GitHub](https://github.com/dtube).  If you’re about to raise an issue because you’ve found a problem with Dtube, or you’d like to request a new feature, or for any other reason, please read this first.  Reporting a Bug A bug is a demonstrable problem that is caused by the code in the repository. Good bug reports are extremely helpful - thank you! Guidelines for bug reports:  Identify the correct repo. See repository overview. While it’s okay if you get this wrong, it’s a big help to us if you get it right. Check if the issue exists. Please do a quick search to see if the issue has been reported (or fixed), including closed tickets. Follow the instructions - When you open an issue inside of GitHub, each repo contains a template for how to create a good bug report. Santa loves people who follow it. Well-specified bug reports save developers lots of time and are appreciated.  ### Feature Requests Feature requests are welcome. Before you submit one be sure to:  Identify the correct repo. Use the Github Issues search and check the feature hasn’t already been requested. Be sure to include closed tickets. Consider whether it’s feasible for us to tackle this feature in the next 6-12 months. The Dtube team is currently stretched thin just adding basic functionality. If this is a nice to have rather than a need, it is probably more clutter than helpful. Make a strong case to convince the project’s leaders of the merits of this feature. Please provide as much detail and context as possible. This means explaining the use case and why it is likely to be common. ### Discussion and Help Sometimes, you may have a problem but an issue isn’t appropriate (or you’re not sure if it’s a real issue).  Join our [chat](https://discord.gg/dtube) talk to others about it.  ### Contribution We offer DTC as a gesture of our appreciation to anyone who contributes to DTube.We will be generous , however most of this is about recognizing and appreciate the help of our community.  The amount of DTube is not typically specified in advance of a contribution, though if you’re particularly motivated by this aspect you are welcome to ask.