Copperhead spends it's time where it counts: creating partnerships, keeping up to date with the latest security and enabling a community. Something we don't do is call people scumbags on Twitter.
twitter.com/DanielMicay/st
Conversation
CopperheadOS used to be ahead in terms of security, not just keeping up-to-date.
While I don’t support the way handled the situation you linked, why bring this up? It has nothing to do with CopperheadOS nor GrapheneOS. 1/
2
it actually has *everything* to do with CopperheadOS. Toxic behavior is contagious.
1
Toxic behaviour as in threatening contributors to the GrapheneOS project by copy striking their own contributions? See renlord.com/posts/2020-03-
2
1
Part of my roles and responsibilities as the CEO is protection of Copperhead IP. This site asserts a bunch of false, non-lawyer legal claims about Daniel's code which makes it a bad example.
2
IP protection itself is a toxic concept, specially in open source
2
James has taken the path of fraudulently claiming ownership over our work since they aren't capable of doing anything more than poorly ripping it off. I own all of the code that I wrote for CopperheadOS.
1
1
Some facts: I never had any work contracts to do work on it for Copperhead, and I never had an employment agreement or salary. I was not an employee of the company. James thinks he can retroactively go back and rewrite history to his benefit but it doesn't work that way at all.
1
1
There was never any copyright assignment. The commits were clearly authored by me and attributed to me, using my personal email address. I used the company email address only for company business. The open source project was not company business. It started before Copperhead.
1
It was explicitly agreed upon that it would be an open source project supported by the company, with the company building a business around it. There was explicitly no copyright assignment. James never believed in open source but was the agreement between the 3 of us ().
1
1
It was explicitly agreed upon that developers working on the open source project would own their work on it, i.e. there would be no copyright assignment. The project was started in 2014, including incorporating previous work of mine. The company was incorporated in late 2015.
The three of us signed a contract for incorporation and later on the shares were divided 50-50 via a shareholder's agreement since wasn't involved anymore. James and I both paid $500 for our shares. I never assigned ownership of any code to the company. Absolutely not.
1
Also, not only did James regularly acknowledge that I owned the code I was writing for the open source project, but he was fully aware that I was contributing it upstream as the individual owning the code. I signed contracts with Google and others asserting ownership of it.
1
1
Show replies