arsenetar/dupeguru
1
0
Fork 0
mirror of https://github.com/arsenetar/dupeguru.git synced 2024-12-04 11:59:02 +00:00
Code Releases Wiki Activity

Updated Get involved (markdown)

Andrew Senetar 2022-03-19 17:19:28 -05:00
parent 6e31c83ddd
commit ae6649c1b6
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Get-involved.md

@ -1,4 +1,4 @@
You'd like to get involved in the dupeGuru project but you're not quite sure where to start or whether your skills are needed or where to start? Even though dupeGuru is a "mature" project, there is still plenty of things to do, for developers and non-developers alike. So, if you'd like to get involved in any way with the dupeGuru project, don't hesitate to [contact me](mailto:hsoft@hardcoded.net).
You'd like to get involved in the dupeGuru project but you're not quite sure where to start or whether your skills are needed or where to start? Even though dupeGuru is a "mature" project, there is still plenty of things to do, for developers and non-developers alike. So, if you'd like to get involved in any way with the dupeGuru project, don't hesitate to reach out.
# Tasks for non-developers
@ -14,10 +14,10 @@ You'd like to get involved in the dupeGuru project but you're not quite sure whe
Although dupeGuru is written in Python, Objective-C and a little bit of C, you don't need to know all languages or even to be an expert in any of these languages to make meaningful contributions to dupeGuru. Here are a couple of examples:
**Developer documentation.** I know this code too well to correctly document it anymore. To me, this code is clear, but I know that to a newcomer, it's not. As a newcomer, you are ideally placed to write developer documentation (I started a little bit of it on [this page](https://github.com/hsoft/dupeguru/wiki/Understand-the-source)). Moreover, writing such docs will help you understand the code better, I guess. Any initiative to write/improve devdocs are gladly welcomed.
**Developer documentation.** I know this code too well to correctly document it anymore. To me, this code is clear, but I know that to a newcomer, it's not. As a newcomer, you are ideally placed to write developer documentation (I started a little bit of it on [this page](https://github.com/arsenetar/dupeguru/wiki/Understand-the-source)). Moreover, writing such docs will help you understand the code better, I guess. Any initiative to write/improve devdocs are gladly welcomed.
**Windows packaging.** For now, I use a closed source solution for packaging into MSI files. If you're knowledgable about thins kind of stuff and you know of an open source solution (and ideally, a way to keep the auto-update mechanism in place), come on board!
**Anything else, really.** Got idea? Don't hesitate to add a ticket, or don't hesitate to let me know if you'd like to work on an existing ticket.
In any case, don't hesitate to [contact me](mailto:hsoft@hardcoded.net).
In any case, don't hesitate to reach out.