Final's avatar
Final final@stacker.news 1 month ago
You can see the individual pull requests for how many people have worked on the app and that there's people discussing what to do. There's people involved in every step or the development testing for quality. Here's the largest:
GitHub
Rewrite Conversation screen with Kotlin and Compose by RankoR · Pull Request #109 · GrapheneOS/Messaging
First (of 3) PR with Conversation screen rewritten with Kotlin and Compose. I've split it into 3 PRs: This one, containing the main code chang...
 The leading apps dev has around a decade and a half of experience in developing on the Android platform alone. His contributions so far have been incredible. We have a broad access to many LLMs for security testing, including cyber-enabled models for dual-use. It's not actually writing the code of GrapheneOS much. It would be poor to willingly dumb ourselves down when companies such as Cellebrite are devoting teams to creating AI tooling to reverse engineer mobile devices to try and exploit them.
↑ Parent

Replies (1)

Final's avatar
Final final@stacker.news 1 month ago
GrapheneOS is open source so we expect access to that code to be available to anyone including who we don't like. There have been malicious forks. Someone could easily mirror the code to GitHub had it not been there already. Someone can also automated mirror the repos from our GitHub and GitLab elsewhere if they don't like the platforms. For a lot of open source projects, finding the talent is harder than funding. GrapheneOS is getting kinda popular now so there's a fan base and funding behind it even if it comes at a consequence of getting mentioned on mainstream news for clicks and hype. The best developers are obviously living the dream with big tech salaries which no one can blame them for taking it. We have enough to hire multiple people, it's just they need to fit what developers want and have the GrapheneOS attitude and 'culture'.
↑