From ae6649c1b6d0acd0061cae4059f7cc4dd1f164b2 Mon Sep 17 00:00:00 2001 From: Andrew Senetar Date: Sat, 19 Mar 2022 17:19:28 -0500 Subject: [PATCH] Updated Get involved (markdown) --- Get-involved.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Get-involved.md b/Get-involved.md index 104284e..14d8036 100644 --- a/Get-involved.md +++ b/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). \ No newline at end of file +In any case, don't hesitate to reach out. \ No newline at end of file