Replies: 1 comment 2 replies
|
I’d be very happy to have your help! One thing to note is that I sometimes make large changes or refactor a lot of code at once, so there could be some merge conflicts. It would be great if you could create an issue for each feature or bug you’re working on. That way, I’ll know which parts you’re working on and can try to avoid changing them. We can start with some smaller features or bug fixes and go from there. Thanks for offering to contribute! You can join the Discord and add me as friend, we discuss online. https://discord.gg/RQWcS6DEEe |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Good day fellow developers! I have been a software engineer and all-around geek for 25+ years. I recently switched to Graphene OS, and am actively divorcing myself from Google entirely. This journey has led me to "PlainApp". I am very happy to have such a useful tool, however, I have been struggling with a LOT of issues (primarily race conditions, messages disappearing or only showing up on one side, state bugs, etc...).
I'd like to start heavily focusing more on assisting with the development and bug fixes of this open-source project. However, I have had some seriously negative encounters dozens of times on GitHub while attempting to contribute to open-source projects... so this time, I figured I would just drop a line and ask: Will it be appreciated (or not) if I jump in, and start submitting PRs regularly to fix bugs, improve features, etc...? I'll be using my Codex bot to do so, but will be happy to follow coding standards, PR formats, or anything else the team would request.
Will extra help be appreciated, or frowned upon? One can never tell on GitHub anymore. 🤷🏻♂️
All reactions