LizzyFleckenstein03
/
Memeclone
2
1
Fork 1
Code Issues Pull Requests Projects Releases Wiki Activity

Reword 'help for junior devs' section

This commit is contained in:
Lizzy Fleckenstein 2021-10-25 19:48:14 +02:00
parent 7707c3132c
commit c998788435
Signed by: LizzyFleckenstein03
GPG Key ID: 06927A5199D6C9B2
1 changed files with 11 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
CONTRIBUTING.md
View File

@ -128,15 +128,17 @@ If you feel like a problem needs to fixed or you want to make a new
feature, you could start writing the code right away and notifying us feature, you could start writing the code right away and notifying us
when you're done, but it never hurts to discuss things first. If there when you're done, but it never hurts to discuss things first. If there
is no issue on the topic, open one. If there is an issue, tell us that is no issue on the topic, open one. If there is an issue, tell us that
you'd like to take care of it, to avoid duplicate work. Note that we you'd like to take care of it, to avoid duplicate work. We appreciate
appreciate any effort, so even if you are a relatively new programmer, any contributing effort to Mineclone2. If you are a relatively new
you can already contribute to the project - if you have problems or programmer, you can reach us on Discord, Matrix or IRC for questions
questions regarding git, Lua, or the Minetest API - or the MineClone2 about git, Lua, Minetest API, Mineclone2 codebase or anything related
codebase, feel free to ask them on our Discord. By asking us to include to MineClone2. We can help you avoid writing code that would be deemed
your changes in this game, you agree that they fall under the terms of inadequeate, or help you become familiar with Mineclone2 better, or even
the GPLv3, which basically means they will become part of a free help using development tools. By asking us to include your changes in
software. If your code leads to bugs or crashes after being merged, it this game, you agree that they fall under the terms of the GPLv3, which
is your responsibility to fix them as soon as possible. basically means they will become part of a free software. If your code
leads to bugs or crashes after being merged, it is your responsibility
to fix them as soon as possible.
### The recommended workflow ### The recommended workflow
* Fork the repository (in case you have not already) * Fork the repository (in case you have not already)