how_to_contribute.rst 6.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111
  1. .. _doc_ways_to_contribute:
  2. How to contribute
  3. =================
  4. The Godot Engine is free and open-source. Like any community-driven project, we rely on volunteer contributions.
  5. On this page we want to showcase the various ways you as users can participate - to help you find the right starting place with the skillset you have.
  6. Because contrary to popular opinion, we need more than just programmers on the project!
  7. Fundraising
  8. -----------
  9. - **Donate**
  10. We created the non-profit `Godot Foundation <https://godot.foundation/>`_ to be able to support the Godot Engine in both matters of finance and administration.
  11. In practice, this means the Foundation hires people to work part-time or full-time on the project.
  12. These jobs include engine development as well as related tasks like code reviews, production management, community & marketing efforts, and more.
  13. With as little as 5 EUR per month, you can help us keep going strong.
  14. Currently, we are intending to hire more core developers, as to cover more ground with full-time specialists that supplement and guide volunteer work.
  15. `Join the Development Fund <https://fund.godotengine.org>`_
  16. - **Donation Drives**
  17. Think about your followers on social media, or other communities you are active in.
  18. Use that reach to remind your social environment that even small contributions can make a difference, especially when done by a great number of people at the same time.
  19. Are you a content creator? Consider adding a link to the `Godot Development Fund <https://fund.godotengine.org>`_ to your descriptions.
  20. If you do live streams, perhaps think about organizing a stream with donation incentives.
  21. .. - **Buy Official Merch**
  22. - **Publish Godot Games.**
  23. You heard right, simply publishing a game #MadeWithGodot can positively impact the well-being of this project.
  24. Your personal success elevates the engine to a viable alternative for other developers, growing the community further.
  25. Additionally, it opens the doors for us to approach industry contacts about possible cooperations.
  26. Technical contributions
  27. -----------------------
  28. - **Report bugs & other issues**
  29. As active users of the engine, you are better equipped to identify bugs and other issues than anyone else.
  30. To let us know about your findings, fill out this `bug report form <https://github.com/godotengine/godot/issues/new/choose>`_ on our GitHub.
  31. Make sure to include as much information as possible to ensure these issues can easily be reproduced by others.
  32. If you are interested in helping keep our bug tracker organized, you can even join the `bugsquad <https://chat.godotengine.org/channel/bugsquad>`_!
  33. - **Test Development Versions**
  34. While it is recommended to use the stable releases for your projects, you can help us test dev releases, betas, and release candidates
  35. by opening a copy of your project in them and checking what problems this introduces or maybe even solves.
  36. Make sure to have a backup ready, since this can produce irreversible changes.
  37. Find recent `development versions <https://godotengine.org/download/preview/>`_ directly on our download page, or linked in their own blog posts.
  38. - **Contribute Engine Code (mainly C++)**
  39. The engine development is mainly coordinated on our `Contributor RocketChat <https://chat.godotengine.org/>`_,
  40. so if you are serious about making PRs you should join us there!
  41. Read more about the **technical submission process**: :ref:`doc_first_steps`
  42. For each subject area of the engine, there is a corresponding team to coordinate the work.
  43. Join the linked chat to get more eyes on your related PR, learn about open todos, or partake in meetings.
  44. For some areas, specialists might even be encouraged to step up as maintainer!
  45. `List of teams <https://godotengine.org/teams/>`_
  46. - **Review Code Contributions**
  47. All pull requests need to be thoroughly reviewed before they can be merged into the master branch.
  48. Help us get a headstart by participating in the code review process.
  49. To get started, chose any `open pull request <https://github.com/godotengine/godot/pulls>`_ and reference our **style guide**: :ref:`doc_pr_review_guidelines`
  50. - **Write Plugins (GDScript, C#, & more)**
  51. Community addons are not directly included in the core engine download or repository, yet they provide essential quality of life upgrades for your fellow game developers.
  52. Upload your plugins to the `Godot Asset Library <https://godotengine.org/asset-library/asset>`_ to make them available to others.
  53. ..
  54. update to talk about Asset Store later
  55. - **Demo projects (GDScript, C#, and making Assets)**
  56. We provide new users with `demo projects <https://github.com/godotengine/godot-demo-projects/>`_ so they can quickly test new features or get familiar with the engine in the first place.
  57. At industry events, we might even exhibit these demo projects to showcase what Godot can do!
  58. Help improve existing projects or supply your own to be added to the pool, and join the `demo channel <https://chat.godotengine.org/channel/demo-content>`_ in the Contributor RocketChat to talk about it.
  59. - **Documentation**
  60. The documentation is one of the most essential parts of any tech project, yet the need to document new features and substantial changes often gets overlooked.
  61. Join the `documentation team <https://chat.godotengine.org/channel/documentation>`_ to improve the Godot Engine with your technical writing skills.
  62. - **Translations (spoken languages other than English)**
  63. Are you interested in making the Godot Engine more accessible to non-English speakers?
  64. Contribute to our `community-translations <https://hosted.weblate.org/projects/godot-engine/godot/>`_.
  65. Community support
  66. -----------------
  67. - **Call for Moderators**
  68. With a community of our size, we need people to step up as volunteer moderators in all kinds of places.
  69. These teams are organized by the Godot Foundation, but would not function without the dedication of active community members like you.
  70. Have a look around your favorite community platform and you might come across open application calls.
  71. - **Answer tech-support questions**
  72. With many new people discovering the Godot Engine recently, the need for peer-to-peer tech-support has never been greater.
  73. See the `Godot website <https://godotengine.org/community>`_ for a list of official and user-supported Godot communities.
  74. - **Create tutorials & more**
  75. How did you get started with the Godot Engine?
  76. Chances are you looked for learning materials outside of what the documentation provides.
  77. Without content creators covering the game development process, there would not be this big of a community today.
  78. Therefore it seemed only right to mention them in a page about important contributions to the project.