All the angst over the definition of "open source" is mirrored in the fight we will soon have over "proprietary". There's a meaningful difference between traditional proprietary models and "don't compete w me" licenses even if we sometimes lump them together.https://twitter.com/VanL/status/1174759891711483904 …
-
-
Replying to @jamesvasile
And there is a difference between traditional proprietary licenses and Do No Harm (DNH) licenses. There's a spectrum between "proprietary" and "open source" that includes thing like "source available."
2 replies 0 retweets 2 likes -
Replying to @mmillions @jamesvasile
But something that's unclear is that "source available" isn't a "middle-ground" of level-of-okayness, it's in general more dangerous than traditional proprietary software; the ability to "see code" that there aren't real rights for community contribution is a dangerous trap IMO
2 replies 0 retweets 1 like -
Replying to @dustyweb @jamesvasile
I agree that it's not a middle ground. DNH and source available are on a spectrum of "freeness" between proprietary and free/open, in as much as they give you more freedoms, even if you're not getting -all- the freedoms.
1 reply 0 retweets 0 likes -
Replying to @mmillions @jamesvasile
I am actually arguing to the contrary: I consider them less free than no-source-available!
2 replies 0 retweets 0 likes -
I am actively afraid of being exposed to "source available" code, because that's information and ideas that I have now seen but cannot use in my work on free software
1 reply 0 retweets 0 likes -
Replying to @dustyweb @jamesvasile
I was thinking about this. On the other hand, as an end user, I like the idea that by seeing code I can better understand and consent to what I am choosing to use.
1 reply 0 retweets 0 likes -
My understanding of current case law around this is that you can use ideas you see in other source code (even closed code) in your free software code, as long as you reimplement it. No copy/paste - the text is subject to copyright but the ideas are not.
2 replies 0 retweets 0 likes
Once you've seen it, it's hard to prove you didn't copy it, especially if best practices lead you to similar solutions. Unconscious copying is also a thing. Clean rooming exists to put your code above reproach.
-
-
Replying to @jamesvasile @sarahmei and
I believe you are discussing this new trend in (proposed) licenses that promote Available Source Software
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.