PR doesn't just stand for "Pull Requests"
PR doesn't just stand for "Pull Requests"
Posted Jul 26, 2025 23:15 UTC (Sat) by cyphar (subscriber, #110703)Parent article: Graphene OS: a security-enhanced Android build
Having seen examples of very mild constructive criticism added to the list of "attacks against the project" which are then used as justification for their uncooperative behaviour shows that this is an unfortunate pattern of behaviour. Obviously actual attacks against projects and individuals are unacceptable, but bog-standard criticisms being reframed without context as attacks is also not acceptable behaviour. There's a non-zero chance they will consider this comment to be an attack against them. I find it strange (but unsurprising) that they found this very positive and supportive LWN article to be somehow a mischaracterisation of their project that required responses rivaling the length of the original article (parts of which they appear to have now deleted according to the editor).
For the record, I did really find a lot of the technical work in GrapheneOS very impressive (I miss plenty of the privacy features now that I'm back to "stock" Google-Android), and I was quite happy to work through all of the necessary technical hurdles (apps not working, manually tweaking things to work with problematic apps, etc) to keep using it. Unfortunately, technical work is only one facet of the work necessary to create a thriving community. They would really benefit from hiring a PR person (preferably 10 years ago, but today is good too) -- even if only to have a third party proof-read their public statements.
Posted Jul 31, 2025 2:22 UTC (Thu)
by marcH (subscriber, #57642)
[Link]
Or - even better - such a public person could explain internally why some of these statements should never be written in the first place. Unfortunately, telling someone who pays you what not to do is very hard. Even harder than what to do.
If a project is successful, then it will statistically draw a lot of not-very-smart questions and debates. And that's OK; good leaders let users help each other. They manage their super precious time and provide such answers and corrections only when no one else could. Cause technical experts should focus on expert things, that's how the project is the most productive.
But maybe those contentious public statements are at least from people who stopped contributing technically? Can't tell since developers prefer to stay anonymous to protect themselves from "attacks"... of what nature? Threats or harsh code reviews? We have no idea either.
Also... editing or even deleting stuff published on the internet, really? That does not look serious. Fixing typos, sure; but that's not it.
Sharing a SubscriberLink in public, interesting...
That looks like a lot of weirdness and opacity for a project "opening" Android. Much more than just "developer privacy".
PR doesn't just stand for "Pull Requests"