this post was submitted on 30 Aug 2024
479 points (98.4% liked)
Technology
59672 readers
4191 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
~~He isn't on the project since last year.~~ androguru Edit: Sorry, meant "he isn't the project lead since last year". He is still part of the GitHub team and actively developing.
That's dubious, since the "former" lead developer is still referring to the project with the pronoun "we" on social media.
You can still be part of a project without being lead, to be part of the "we." Did he contribute and/or is he part of GrapheneOS, yes? So he's part of the "we."
Or does only the lead developer get the "we?" Wouldn't that make it more of an "I" instead?
I was responding to a comment that claimed "he isn't on the project since last year". Based on his activity on social media, he is clearly still in the project.
You should remember that he founded the original CopperheadOS project (from which he was violently ousted by his cofounder) and has been working on it and this for a decade.
His github says otherwise
It states that he is the "Founder of @GrapheneOS", not the current lead developer. So I don't get your point
His activity on GrapheneOS repositories, issues, etc. indicates he's still very active in development and in the community.
IMO he can contribute all he wants. His PRs will still have to go through someone else (i.e. the new maintainer / lead dev). I don't care if he adds new code. That's much appreciated.
Toxicity is more of an issue if you're the maintainer since you have control over the project.