You can see that GrapheneOS is an open source project with the original developers / repositories. You can see that the new CopperheadOS is a fork of it which hasn't uploaded sources since December 2019, does not use open source licensing and hasn't done privacy/security work.
Conversation
The earliest generation of the project in 2014/2015 started on my personal GitHub account at github.com/thestinger. The repositories now at GrapheneOS are the ones created when moving to AOSP. Some repositories not used for Oreo onwards are still at github.com/AndroidHardeni.
1
Look at the history of the project and what was stated online on reddit.com/r/CopperheadOS, the web site, GitHub, etc. The original central issue tracker is at github.com/AndroidHardeni if you're looking for that. Can easily see it started before Copperhead was incorporated and you..
2
.. can look back on archive.org and see that every commit that I made always had authorship and ownership attributed to me using my personal email address. There was NEVER any attribution or assignment of any of the copyright to Copperhead. Look at them yourself.
2
Use archive.org to look there and the site to confirm everything that I said. It's very easy to confirm that what I'm saying is accurate. You're being incredible disingenuous. Don't understand why you're trying to spin this & misrepresent what I've said / pointed to.
1
Maybe not everyone sees what you see and it is your job to prove your points. You attacked @Pura_Vida_78 for tweeting support. You have your own thing stick to it
1
@Pura_Vida_78 made inaccurate statements about CopperheadOS and GrapheneOS and did not do their due diligence about them. It's their responsibility to do their research and due diligence before making recommendations, promoting something and making statements / comparisons...
1
They made inaccurate statements and did not do their due diligence / research. They're promoting a scammer, fraud and harm being done to open source developers. You're choosing to be complicit in harming an open source developer and are supporting a proprietary fork with DRM...
1
You're the one reviving the thread with your trolling.