Despite instructions and links to the community forum on the GitHub repo [1] it is almost certainly a complete waste of your time to bother getting to know how to build, modify, and submit PRs to Signal for the iOS app.<p>Good quality PRs languish for years, half-ignored at best, despite comments from users and even ocassionally Signal employees that they are looked at.<p>The iOS app is in dire need of some improvements which many users have been contributing only to have their time completely wasted. I myself contributed a small change that would make it practical to delete all media from a chat.<p>I'm witholding donations until this situation improves.<p>[1] https://github.com/signalapp/Signal-iOS
To be fair, that's often the case with open source stuff. And though I understand the frustration, it is kind of the deal.<p>Google makes AOSP open source not because they want to spend resources on your contributions, but for control. Pretty sure it's similar in many other projects like Flutter, Protobuf, gRPC, ... And not only Google, of course.<p>Signal is open source for security reasons: they want people to be able to audit the code. Definitely not to spend resources reviewing community contributions.<p>I know it sucks: I have spent time contributing perfectly valid features to open source projects that were never even reviewed. But on the other hand I have seen people try to contribute big PRs to projects I maintain and I am just not paid to adopt (and later maintain) their code.<p>Conclusion: unless you contribute something they directly need (a bugfix, or if you are lucky enough to contribute a feature they directly need better and faster than them), then don't bother. But that's valid for most open source projects.