News for hackers. Stuff that matters.
Re:Give up GitHub: The time has come by naikrovek on Thursday June 30, 2022 @04:53PM (#31938474)
I want to know what stuff you guys are putting in public GitHub FOSS repos that you don't want replicated in any way...

I also want to know why people think their code is so special that no one else could have ever come up with it independently. Each and every opponent of Copilot is the best developer ever, I guess?

That said, I don't understand the choice to use GPL for any reason, so maybe I'm not equipped to understand the arguments against Copilot. Forcing your code to be open forever isn't freedom, it's the omission of freedom. Someone using your (for example) MIT-licensed code in a closed-source commercial software project doesn't "un-free" the code you released; your code is still exactly as open and as available as it was before, and zero freedoms were lost by anyone.

Re:Give up GitHub: The time has come by JoshTriplett on Thursday June 30, 2022 @05:54PM (#31939165)
> I want to know what stuff you guys are putting in public GitHub FOSS repos that you don't want replicated in any way...

Please feel free to use my code in any way that its license permits: attribution for the permissive licenses, share-and-share-alike for the copyleft licenses. Those license terms are the price of the code, no different from a proprietary product's "this costs $x" or "this costs $x/month". I'm happy to give away most of what I work on every day, and I ask that people 1) give credit, and 2) in some cases, share under the same terms, and 3) in many cases, don't sue me or other users of code I've written over software patents (which shouldn't exist).

If the day comes that copyright goes away, and we can freely copy and share the code of any currently proprietary software and other works, I'd celebrate that. Until then, I don't want an asymmetric situation in which proprietary licenses must be adhered to but Open Source licenses are ignored.

Re:Give up GitHub: The time has come by pabs3 on Friday July 01, 2022 @01:57AM (#31942877)
If copyright goes away, that won't magically make the source code of all proprietary software public. The only thing that will be liberated is existing shared-source software.
Re:Give up GitHub: The time has come by account42 on Friday July 01, 2022 @07:10AM (#31944772)
It won't magically make the source code appear but it will allow

a) Those who do have the source code to share it. Sometimes the source code is available but it can still not be freely used and/or shared.

b) Allow modifications and redistribution of the binary artefacts, which for is sufficient for many goals.

c) Remove all concerns with reverse engineering and allow e.g. decompiling programs and sharing that source.

Also, remember that the GPL already does not make source available externally if the modfications are only used internally.

Re:Give up GitHub: The time has come by notpushkin on Friday July 01, 2022 @07:12AM (#31944791)
It will make reverse-engineering (non-clean room, even) legal, though.
Re:Give up GitHub: The time has come by pabs3 on Sunday July 03, 2022 @02:36AM (#31965607)
That could be prevented by EULAs though.
Re:Give up GitHub: The time has come by chlorion on Thursday June 30, 2022 @07:37PM (#31940148)
>I want to know what stuff you guys are putting in public GitHub FOSS repos that you don't want replicated in any way...

Nobody has claimed that they want this. People just want derived work to adhere to the license they chose for their project.

>I also want to know why people think their code is so special that no one else could have ever come up with it independently. Each and every opponent of Copilot is the best developer ever, I guess?

Would you feel the same way about ripping off game assets, or music?

I think you just have an axe to grind with free software in general based on your messages and the general tone. Just because you don't understand it doesn't mean that the ideas are invalid.

I am also curious why copyright laws should protect proprietary software, music, games, writing, etc but not apply to my software, even if it isn't the highest quality work?

Re:Give up GitHub: The time has come by sossles on Thursday June 30, 2022 @09:00PM (#31940800)
At one point does AI recreating patterns it has seen from reading source code count as a derived work? What if a human learns to code by reading only GPLed code, does all the code they write fall under GPL as a derived work now?
Re:Give up GitHub: The time has come by natefinch on Thursday June 30, 2022 @10:24PM (#31941482)
Re:Give up GitHub: The time has come by notpushkin on Friday July 01, 2022 @07:31AM (#31944913)
> “If you look at the GitHub Terms of Service, no matter what license you use, you give GitHub the right to host your code and to use your code to improve their products and features,” [Kate] Downing, [an IP lawyer specializing in FOSS compliance] says. “So with respect to code that’s already on GitHub, I think the answer to the question of copyright infringement is fairly straightforward.”

This has some interesting implications – for example, it means I can't mirror somebody else's (open source) code on GitHub without their explicit agreement.

Re:Give up GitHub: The time has come by CRConrad on Saturday July 02, 2022 @06:58PM (#31963264)
> > “If you look at the GitHub Terms of Service, no matter what license you use, you give GitHub the right to host your code and to use your code to improve their products and features,” [Kate] Downing, [an IP lawyer specializing in FOSS compliance] says. “So with respect to code that’s already on GitHub, I think the answer to the question of copyright infringement is fairly straightforward.”

So any code uploaded by someone other than the copyright holder renders someone liable to be sued for copyright infringement, AFAICS. The only question is whom it makes liable -- the uploader, GitHub (=Microsoft!), or both?

I can see arguments either way: The uploader is clearly infringing by giving away a right that isn't theirs to give. But so is GitHub / Microsoft, for using a "right" they haven't been properly given. So I'm provisionally leaning towards "both".

> I can't mirror somebody else's (open source) code on GitHub without their explicit agreement.

Who is doing the "mirroring" -- you, in uploading the code, or GitHub / Microsoft in actually hosting it, keeping it available for download from their "mirror"[1] site?

___

[1]: Is that even the correct terminology nowadays, when AIUI for lots of projects GitHub is their primary code repository?

Re:Give up GitHub: The time has come by danaris on Friday July 01, 2022 @09:03AM (#31945802)
How so? I'm not seeing any language in there that implies exclusivity...
Re:Give up GitHub: The time has come by natefinch on Friday July 01, 2022 @01:52PM (#31950099)
Presumably because you don't have the right to grant github those permissions, only the copyright owner does.
Re:Give up GitHub: The time has come by CRConrad on Saturday July 02, 2022 @06:26PM (#31962993)
So GitHub should immediately take down (and remove from their Copilot learning model!) all *GPL code uploaded by anyone but the ("primary"?) copyright holder.
Re:Give up GitHub: The time has come by janosdebugs on Friday July 01, 2022 @12:33AM (#31942400)
There's one thing I'm missing from all these discussions and posts: is the generated code even copyrightable? IANAL, but code snippets often fall under the "scènes à faire" doctrine (everybody would do it in a similar way), in which case it's not. https://en.m.wikipedia.org/wiki/Sc%C3%A8nes_%C3%A0_faire
Re:Give up GitHub: The time has come by pabs3 on Friday July 01, 2022 @01:59AM (#31942889)
GitHub seems to think it is copyrightable, personally I doubt it is, simply because a human didn't create it and the process it was created by was automatic with no creativity.
Re:Give up GitHub: The time has come by natefinch on Friday July 01, 2022 @09:03AM (#31945803)
Well, if the entire thing was generated, then no (according to the first link I posted above), since it was not produced by a human. However, no useful program is going to be entirely written by an AI, so any real program would have quite a lot of user input (I regularly will take what copilot suggests and then tweak it to what I specifically want). And then, yeah, it's copyrightable.

Also, there's no way for anyone to know what portion of code that I commit was hand written vs. generated, so you kind of have to treat it all as written by the committer anyway.

Though this does bring up interesting questions about what happens with things like automated PRs that fix bugs / update dependencies... are those then non-copyrightable? ¯\_(ツ)_/¯

Re:Give up GitHub: The time has come by janosdebugs on Friday July 08, 2022 @01:42AM (#32023727)
Here's the kicker: your modified code snippet may still not be copyrightable if it's generic enough that everyone would do it in a similar manner.

Just as much as a hero riding off into the sunset is not copyrightable in a movie script. However, a hero riding off into the sunset with bananas in the pistol holsters would be.

This is what I would want to hear more about when discussing if Copilot violates copyright.

Re:Give up GitHub: The time has come by josephcsible on Thursday June 30, 2022 @06:31PM (#31939535)
> Forcing your code to be open forever isn't freedom, it's the omission of freedom.

This isn't true. As an analogy, consider that forcing people to not own slaves isn't the omission of freedom. See also https://www.gnu.org/philosophy/freedom-or-power.en.html

Re:Give up GitHub: The time has come by entropi on Friday July 01, 2022 @05:49AM (#31944280)
Code is not sentient, has no human rights, masters don't create slaves out of caffeine, etc. etc. This analogy does not hold at all in my opinion.
Re:Give up GitHub: The time has come by npteljes on Friday July 01, 2022 @08:40AM (#31945585)
No, it's a good analogy, because it's not between the similarity of people and code. The cases are similar, because in both you restrict freedom to enable freedom.
Re:Give up GitHub: The time has come by CRConrad on Saturday July 02, 2022 @06:41PM (#31963135)
Making source code available and not requiring the same of those who use it is a temporary fleeting freedom that soon turns into lack of freedom.

Like thinking you're ending slavery by freeing all the current slaves but not making it illegal to own, buy, and sell slaves, or capture previously free people into slavery. Guess if you'd have slavery again very soon?

The analogy is about freedom vs lack thereof, not manual labour vs software. And as you see, it works very well.

Re:Give up GitHub: The time has come by biztos on Thursday June 30, 2022 @06:18PM (#31939401)
> their code is so special that no one else could have ever come up with it independently

I'm worried about exactly the opposite: having Copilot help me write code that seems quite generic to me, but which in fact makes my code subject to a license I don't even know about, and/or simply violates copyright.

For an open-source project this could be embarrassing but probably fixable. It gets more complicated if FAANG is doing due diligence on your company. I can see Copilot being both an accelerant and, later, a liability for startups.

Re:Give up GitHub: The time has come by natefinch on Thursday June 30, 2022 @06:40PM (#31939613)
There's a setting on GitHub that blocks any suggestions that exactly match code in the training set. I doubt you'd ever get in trouble for code that was similar in structure but different variables etc from existing licensed code (especially since most small snippets of code are not terribly unique to begin with).
Re:Give up GitHub: The time has come by grayclhn on Thursday June 30, 2022 @07:38PM (#31940163)
I mean, it's nice that they have a setting for the bare minimum a lazy undergrad would do to avoid getting caught for plagarism — replace some of the words in the copied paragraph with replacements from a thesaurus. It's not something I'd personally expect to hold up under real scrutiny though.
Re:Give up GitHub: The time has come by biztos on Thursday June 30, 2022 @07:25PM (#31940035)
AFAIK that's not enough, for instance see the long-standing industry practice that people working on the Important Stuff are not allowed to ever look at the source code of the Direct Competitor; or clean-room reverse engineering, etc.

I guess time will tell how much acquiring companies (my worry) care about Copilot. Given the difficulty hiring good devs, and the productivity level of body-shop devs, I see it getting a whole lot of use very soon, acknowledged or not.

Re:Give up GitHub: The time has come by natefinch on Thursday June 30, 2022 @10:19PM (#31941448)
There's a big difference between reverse engineering (i.e. intentionally writing software that behaves identically to another piece of software), and writing your own code to solve your own problem that may superficially contain small portions of the similar logic as some other project. Copyrighted code has to be sufficiently creative and unique to qualify, otherwise after the first person wrote code to parse json from a web request, no one else would be able to do the same thing.
Re:Give up GitHub: The time has come by skjoldr on Thursday June 30, 2022 @07:31PM (#31940091)
Then Microsoft should write this as a legal statement on their part that they will take responsibility for. But I doubt they will ever do that.
Re:Give up GitHub: The time has come by naikrovek on Thursday June 30, 2022 @11:11PM (#31941853)
Microsoft is not the author of the software that copilot helps produce. the person sitting at the keyboard using copilot is the author.
Re:Give up GitHub: The time has come by bilekas on Friday July 01, 2022 @02:19AM (#31943026)
This is a bit like saying if you hire a freelancer to do some work then you're the author of that work. I'm not too sure i agree with that.
Re:Give up GitHub: The time has come by gerikson on Tuesday July 05, 2022 @01:26AM (#31984636)
Re:Give up GitHub: The time has come by bilekas on Tuesday July 05, 2022 @03:09PM (#31992411)
Kind of interesting.. I would like to point out this seems to be specific for the US.

But also.. In that case, when I commission an artist to paint my portrait, surely I can't claim to be the artist.. But I'm no lawyer.

I'm not sure there is a contractual agreement in GitHub's co-pilot that says: "Any code you write here is commissioned work". But honestly I didn't read the T&C's.

So I think you MAY have debunked my analogy, but not the main reason for the analogy.

Re:Give up GitHub: The time has come by pabs3 on Friday July 01, 2022 @02:00AM (#31942900)
How is copilot not the author?
Re:Give up GitHub: The time has come by natefinch on Friday July 01, 2022 @01:53PM (#31950116)
Copilot is software, it can't be the author, just like the OS isn't the author when you copy and paste. Authors have to be humans.
Re:Give up GitHub: The time has come by pabs3 on Friday July 01, 2022 @08:47PM (#31954889)
Copy and paste doesn't really write code, just copies it from one place to another. Copilot on the other hand does generate new potentially novel code.
Re:Give up GitHub: The time has come by yucky on Thursday June 30, 2022 @10:06PM (#31941345)
It does sound like the value of code creators is going to soon see significant downward pressure.
Re:Give up GitHub: The time has come by natefinch on Thursday June 30, 2022 @10:22PM (#31941466)
I'm sure that's what people said when they went from punch cards to assembly, and from assembly to C, and from C to Java.... and yet, here we are. Tools that let us write higher level code faster, just allow us to create more complicated software in a reasonable amount of time.
Re:Give up GitHub: The time has come by yucky on Thursday June 30, 2022 @11:12PM (#31941861)
I think the argument is now it takes considerably less brain power to do, thereby increasing the labor pool and devaluing the output.
Re:Give up GitHub: The time has come by natefinch on Friday July 01, 2022 @12:02AM (#31942199)
That's still 100% true of the examples I mentioned. There's always a higher level to consider. When we moved to C, we could stop worrying about what registers we were using. When we moved to python/Java we could stop worrying about managing memory. When we moved to web frameworks we stoping writing the guts of our servers. And if anything, programmers have become even better paid, despite so many more people in the industry.
Re:Give up GitHub: The time has come by Naracion on Friday July 01, 2022 @06:22AM (#31944489)
I agree with you--however, programmers have not become even better paid because society values programmers. They have become better paid because software is a relatively new artefact in human society which has taken the human life by storm, which has made software companies immensely profitable, which meant more companies wanted to create software and attract the people that could help them do it.

As software takes a back seat (or at least a "normal" seat) in society, would we see a normalization of income? Could this be hastened by the development and introduction of tools such as copilot?

Potentially, unless there are new / better things that humans can claim they can provide compared to AI tools. This is the point where I think you and I agree, and I think it's your primary argument in any case (unless I'm mistaken).

Re:Give up GitHub: The time has come by natefinch on Friday July 01, 2022 @11:01AM (#31947315)
AI can code low level stuff. This one function. This small piece of logic. What it can't do is conceive of how to take a bunch of different functions and put them together to produce an actual product. It can't tell you if you should use postges or mongo. Programmers will always be needed, we'll just move up the stack, and we'll produce more value per hour of our work, justifying our high salaries.

Compare the visible output of someone writing in assembly vs someone writing on top of a modern web framework. Is assembly harder? Yeah. But the web framework is going to give you a usable product in a fraction of the time with way more features. And that's worth more money to the company you work for.

It's always going to be a knowledge worker's job. It's always going to reward experience and creativity and attention to detail. A lot of programming is looking at the world, seeing a gap in what exists, and figuring out what best fits that gap. An AI can't do that. Programming is making 1000 tiny decisions that can't possibly be specified completely by a product manager and need a human to weigh the tradeoffs.

Re:Give up GitHub: The time has come by CRConrad on Saturday July 02, 2022 @07:04PM (#31963311)
> AI can code low level stuff. This one function. This small piece of logic. What it can't do is conceive of how to take a bunch of different functions and put them together to produce an actual product.

Thats what everybody in the chess world said: "AI can decide low level stuff. This one move. This small attack on a rook. What it can't do is conceive of how to take a bunch of different tactics and put them together to produce a game of chess."

...Until Deep Blue beat Garry Kasparov.

> It can't tell you if you should use postges or mongo.

Yeah, and then came: "It may be able to play chess, but it can't tell you how to play Go."

Look how that went.

Re:Give up GitHub: The time has come by janosdebugs on Friday July 01, 2022 @12:38AM (#31942432)
The hard part about writing code isn't "how to write a for loop" and similar trivial things. Copilot make this process faster, but the hard part is still organizing your code so that it doesn't become a steaming pile of cowdung a few iterations down the line. That Copilot does not do for you.

So, unless you are a code monkey punching code into autogenerated skaffolding all day, your job is safe.

Re:Give up GitHub: The time has come by bonzini on Thursday June 30, 2022 @05:24PM (#31938817)
Forcing your code to be open forever is guaranteeing freedom of all users of my code, both direct and indirect. Developers don't need to have any more freedoms than other users.
Re:Give up GitHub: The time has come by naikrovek on Thursday June 30, 2022 @05:42PM (#31939005)
> Forcing your code to be open forever is guaranteeing freedom of all users of [your] code

No, that’s forcing restriction on all users of your code.

Usage restriction is the opposite of freedom…

Forcing all of your code to be GPL is like saying “I am on a diet, so now I will force everyone else be on the same diet. Freedom!”

Re:Give up GitHub: The time has come by PeterisP on Thursday June 30, 2022 @05:49PM (#31939079)
MIT license permits you to deny your users the ability to read and modify the previously open code.

GPL license ensures that your users will keep the same freedoms that you got.

Of course, there's an inherent conflict - the freedom to oppress others is incompatible with freedom from oppression.

Re:Give up GitHub: The time has come by UncleEntity on Thursday June 30, 2022 @06:32PM (#31939552)
> Forcing all of your code to be GPL is like saying “I am on a diet, so now I will force everyone else be on the same diet. Freedom!”

Nobody is forcing anyone to use the code.

If they chose to use it they have to abide by the licensing terms because that’s how it works. If the people laboring for free to produce this code don’t want it to be used in a proprietary application then tough luck, write the code yourself.

Every time the GPL comes up someone drags out this same old dead horse to beat on a little bit more.

Re:Give up GitHub: The time has come by redeeman on Thursday June 30, 2022 @07:07PM (#31939857)
> Nobody is forcing anyone to use the code.

until the time comes when a tax department gets the funny idea to use it, and forced you to use it, or people with guns come to your door and haul you away in the morning.

(edit: formatting)

Re:Give up GitHub: The time has come by 3np on Thursday June 30, 2022 @07:52PM (#31940272)
I really can't see the code being GPL being an issue in that case. What license would you have preferred?
Re:Give up GitHub: The time has come by redeeman on Friday July 01, 2022 @07:01PM (#31954145)
its not about whether its a problem in real life, its about whether the end user might be forced to use a product, which IS a thing, that that is the ONLY point I made
Re:Give up GitHub: The time has come by Volundr on Friday July 01, 2022 @11:41AM (#31947991)
Do you have an example of someone being forced to incorporate GPLed code into their software at gunpoint, or is this a wildly hypothetical scenario?
Re:Give up GitHub: The time has come by redeeman on Friday July 01, 2022 @07:01PM (#31954136)
of course not, but the point was about end users
Re:Give up GitHub: The time has come by keonix on Friday July 01, 2022 @07:30PM (#31954395)
GPL restricts only developers. As an end user restrictions don't even apply to you
Re:Give up GitHub: The time has come by cobbzilla on Friday July 01, 2022 @05:34AM (#31944188)
> Forcing all of your code to be GPL is like saying “I am on a diet, so now I will force everyone else be on the same diet. Freedom!”

This is a terrible analogy. Here’s a better one: I’m holding a potluck. If you decide to come, you can eat all you want. If you take food from my event, you can’t hoard it, you must share it, even if you’ve “made it better” by changing it somehow after you left.

Don’t like my rules? OK, don’t come to my potluck.

Re:Give up GitHub: The time has come by TheDong on Thursday June 30, 2022 @05:48PM (#31939072)
What you are pointing out is similar to "the paradox of tolerance" https://en.wikipedia.org/wiki/Paradox_of_tolerance

By analogy, there is a law against me putting handcuffs on another, and in fact the police would stop me from doing so. Did the police protect freedom? Aren't they restricting me from handcuffing others?

In a similar manner, under the MIT I can restrict my users from modifying and compiling my source code. Is a license that means I have to let my users modify code restricting freedom? Isn't it ensuring freedom of others, in the same way that making laws of "you shall not handcuff others for no reason" is ensuring freedom of others?

Re:Give up GitHub: The time has come by blacklight on Friday July 01, 2022 @09:05AM (#31945821)
Let me provide you with a counter-example.

Suppose that there's a law that states that water and access to it is always supposed to remain public, because water is a public good.

Suppose that someone comes tomorrow and starts claiming ownership of all the water springs in your country, he becomes the only entry point to get water, and you have to pay him a fee every time you open a tap.

Is he still free to do so? In other words, is the freedom of someone who restrict the freedoms for everyone else still a form of freedom that is worth even considering, let alone respecting?

Because the foundation of your ideas is exactly the reason why capitalism fucked things up and just let a bunch of jerks get rich without merit.

Re:Give up GitHub: The time has come by smcameron on Friday July 01, 2022 @01:52AM (#31942849)
> I want to know what stuff you guys are putting in public GitHub FOSS repos that you don't want replicated in any way...

What a disingenous reply. FOSS licenses do not grant ability to replicate "in any way" that you wish. You still have to comply with the license terms. What the hell is wrong with you?

> I don't understand the choice to use GPL for any reason ...

The reason is people like YOU.

Re:Give up GitHub: The time has come by toofy on Thursday June 30, 2022 @08:40PM (#31940663)
of course that’s freedom. if you say to me “you can’t choose to share your code” you are quite literally taking away my freedom.

either code is owned by its licensors or it isn’t.

> I also want to know why people think their code is so special that no one else could have ever come up with it independently.

I’ve never heard anyone argue this in the real world, ever —and i’ve been involved in this space for years.

If someone doesn’t want our code, then they can go ahead and write their own from scratch. We’re certainly not stopping them.

many people do seem upset at us that we’re sharing code, tho. particularly that group who primarily make their fortunes from other people’s work.

Re:Give up GitHub: The time has come by mr_toad on Thursday June 30, 2022 @09:55PM (#31941259)
> Someone using your (for example) MIT-licensed code in a closed-source commercial software project doesn't "un-free" the code

It’s the users of that closed-source commercial software that lose freedoms.

How many times does it have to be stated? GPL is for the users.

Re:Give up GitHub: The time has come by justjosias on Friday July 01, 2022 @12:12AM (#31942266)
Also note: Copilot violates the attribution requirements of permissive licenses like MIT as well. Even if you put your code on GitHub with the intent of it being freely used in proprietary software, attribution is still a fair demand.
Re:Give up GitHub: The time has come by janosdebugs on Friday July 01, 2022 @12:40AM (#31942448)
That assumes the code snippets being copyrightable and nor fair use.
Re:Give up GitHub: The time has come by blacklight on Friday July 01, 2022 @09:00AM (#31945775)
Just to clarify: you seem to believe that most of our code isn't good enough, so copying it is not a big deal.

Do you feel the same about other creative processes as well? Can I rip a Justin Bieber's song and say that it's mine just because it's a shitty song anyway, so who cares? Or does this only apply to software because software is somehow an "inferior" art? Do licenses even have any legal value to you?

Re:Give up GitHub: The time has come by WalterBright on Thursday June 30, 2022 @05:44PM (#31939033)
The D language uses the Boost license because it is the least restrictive. Anyone is free to use it in closed-source non-free commercial apps if they like, or Open Source if they like.
Re:Give up GitHub: The time has come by bombcar on Thursday June 30, 2022 @05:52PM (#31939122)
How is Boost different from something like 0-clause BSD?
Re:Give up GitHub: The time has come by WalterBright on Thursday June 30, 2022 @07:46PM (#31940228)
I don't know what 0-clause BSD is. The Boost license is:

Boost Software License - Version 1.0 - August 17th, 2003

Permission is hereby granted, free of charge, to any person or organization obtaining a copy of the software and accompanying documentation covered by this license (the "Software") to use, reproduce, display, distribute, execute, and transmit the Software, and to prepare derivative works of the Software, and to permit third-parties to whom the Software is furnished to do so, all subject to the following:

The copyright notices in the Software and this entire statement, including the above license grant, this restriction and the following disclaimer, must be included in all copies of the Software, in whole or in part, and all derivative works of the Software, unless such copies or derivative works are solely in the form of machine-executable object code generated by a source language processor.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE FOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Re:Give up GitHub: The time has come by lovelymono on Thursday June 30, 2022 @08:39PM (#31940652)
0-clause BSD goes even further, and completely omits the attribution requirement:

   Permission to use, copy, modify, and/or distribute this software for any
   purpose with or without fee is hereby granted.

   THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH
   REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
   AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT,
   INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
   LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR
   OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
   PERFORMANCE OF THIS SOFTWARE.
Re:Give up GitHub: The time has come by bombcar on Thursday June 30, 2022 @08:43PM (#31940686)
Ah, so boost is somewhere between zero and one clause BSD.
Re:Give up GitHub: The time has come by notpushkin on Friday July 01, 2022 @07:44AM (#31945031)
One major difference between Boost and e. g. MIT is, Boost allows you to omit attribution in binary form (but not source form).
Re:Give up GitHub: The time has come by elcomet on Thursday June 30, 2022 @09:01PM (#31940805)
This is a very "american" definition of freedom, which is basically, just let me do what I want.

GPL uses a different definition of freedom, which I prefer. They look at consequences of restrictions / permissions, and their implication on freedom (not just for me, but for everyone). So some restrictions can lead to actually more freedom, while some permissions can actually decrease freedom.

This is similar to gun-control. While it reduces freedom for gun owners, it allows everyone to be more free of hanging out anywhere they want without being afraid of being shot. Similar arguments can be made for vaccine mandates.

So GPL restricts usage of software because in the long term it gives back power to users, which will be more free.

Re:Give up GitHub: The time has come by BlitzGeology91 on Friday July 01, 2022 @08:14PM (#31954688)
> This is a very "american" definition of freedom, which is basically, just let me do what I want.

Eh. I see what you’re saying about gun control, but the idea that “some restrictions can lead to actually more freedom, while some permissions can actually decrease freedom” is actually very American.

The free software movement says that everyone deserves software freedom. The Declaration of Independence similarly says “We hold these truths to be self-evident, that all men are created equal, that they are endowed by their Creator with certain unalienable Rights, that among these are Life, Liberty and the pursuit of Happiness.” While I haven’t found a source confirming it, I think that the founders believed that the freedom of speech was one of these unalienable rights.

The GPL puts restrictions in place to make sure that downstream projects give users software freedom. The Constitution put restrictions in place to ensure that the federal (and nowadays the entire) government doesn’t interfere with our unalienable rights.

Take a look at how the first amendment is worded:

“Congress shall make no law respecting an establishment of religion, or prohibiting the free exercise thereof; or abridging the freedom of speech, or of the press; or the right of the people peaceably to assemble, and to petition the Government for a redress of grievances.”

The first amendment does not grant the freedom of speech because it doesn’t need to be granted. From the founders’ perspective, god already grants the freedom of speech to everyone forever. The key phrase here is “Congress shall make no law”. The first amendment is restricting Congress to ensure freedom.

The idea that “some permissions can actually decrease freedom” is also present in the Constitution. For example, take a look at Article I sections 8 and 9. The framers of the Constitution could have given Congress the power to pass any law. Instead, they chose to specifically enumerate what Congress can and cannot do.

Perhaps, though, most Americans don’t know much about our founding and think that freedom=just let me do what I want. I don’t know.

Re:Give up GitHub: The time has come by elcomet on Sunday July 03, 2022 @12:55AM (#31965181)
Thanks to put things in context, that was quite interesting!
Re:Give up GitHub: The time has come by zzo38computer on Thursday June 30, 2022 @11:55PM (#31942153)
I think GPL is a good idea (and ensures that everyone is having the freedom from a modified version of the code, and other things that it protects users from), but there is some problem too, such as I think it can be complicated to deal with.

For this reason, I had idea to make up a new license (although I will not write most of my ideas here but will do so elsewhere). But, its main working would be: mostly you can do whatever you want (including omitting attribution and copyright notices) without worrying about the license, but you cannot use legal processes (such as lawsuits, DMCA, etc) to prohibit these freedoms to any downstream recipients (regardless of how many). The license would also ensure patents can be used freely, disclaimer of warranty (if the license is included in the copy and the recipient has not paid for the copy), and some other things to ensure freedom (although there can be some restrictions on the use of trademarks (e.g. to avoid false advertising), and some things to avoid working around the freedoms in certain ways). You can be forgiven any number of times, though; the license will not be terminated. Furthermore, for a practical reason of license compatibility, relicensing by GPL3 and AGPL3 (and possibly also CC-BY-SA 4.0, for works other than computer programs) are also allowed, as long as you have a copy of the source code and can satisfy the terms of those licenses.

Re:Give up GitHub: The time has come by gerdesj on Thursday June 30, 2022 @07:01PM (#31939797)
"I also want to know why people think their code is so special that no one else could have ever come up with it independently. "

Really? What exactly does this CoPilot thing actually spit out? I can't help but think that it spits out near verbatim, which in the UK is probably dodgy on Copywrite.

You then go on to decide that the GPL isn't for you. That's fine. You even explain that you are ill-equipped for something. That too is fine.

You are not a fan of free or "libre" stuff. That comes across loud and clear. Thank you.

Re:Give up GitHub: The time has come by jen20 on Thursday June 30, 2022 @10:36PM (#31941575)
"Replicating" it is fine. Violating the license is not.
Re:Give up GitHub: The time has come by CRConrad on Saturday July 02, 2022 @06:33PM (#31963054)
> Forcing your code to be open forever isn't freedom, it's the omission of freedom.

On the contrary, forcing your code to be open forever is the only way to preserve freedom.

Re:Give up GitHub: The time has come by npteljes on Friday July 01, 2022 @08:38AM (#31945560)
Forcing the code to be open is the kind of freedom where restricting locally something enables the freedom globally. Granting the freedom to do whatever with the code will make the code end up used in closed ways, empowering those who close the code.

A similar line of thought is the "paradox of tolerance", which posits that if a society tolerates the intolerant, the tolerance of that society will lessen.

https://en.wikipedia.org/wiki/Paradox_of_tolerance

Re:Give up GitHub: The time has come by CRConrad on Saturday July 02, 2022 @07:11PM (#31963357)
Second, shorter reply:

> I don't understand the choice to use GPL for any reason

No, you just don't understand the GPL.

Or, for some reason, pretend not to.

Re:Give up GitHub: The time has come by mountainriver on Friday July 01, 2022 @09:28AM (#31946054)
Exactly, this is such griping nonsense from people who are scared of where the industry is heading.
Re:Give up GitHub: The time has come by UmbertoNoEco on Thursday June 30, 2022 @06:36PM (#31939585)
I love how you direct the question to the people putting their code out in their open and not to Microsoft. What is so special about Clippy et al?
Re:Give up GitHub: The time has come by hinkley on Thursday June 30, 2022 @09:12PM (#31940893)
Skipped right over the question on the table and asked a whole bunch of passive aggressive questions.

Truly a classic.

Re:Give up GitHub: The time has come by CRConrad on Saturday July 02, 2022 @07:16PM (#31963388)
You mean skipped right over the moronic statement thinly veiled as a question on the table? As if it deserved better.
Re:Give up GitHub: The time has come by nojito on Thursday June 30, 2022 @04:55PM (#31938505)
GPL is one of the least free licenses out there.
Re:Give up GitHub: The time has come by ssddanbrown on Thursday June 30, 2022 @05:25PM (#31938822)
Freedom of the code to its users vs Freedom of the users of the code
Re:Give up GitHub: The time has come by nojito on Thursday June 30, 2022 @09:42PM (#31941136)
There's no difference. Freedom is freedom. Adding qualifications to it inherently makes it less free.
Re:Give up GitHub: The time has come by danaris on Friday July 01, 2022 @09:32AM (#31946102)
Freedom is not, and cannot be, an absolute. If I am 100% free, that by definition restricts the freedom of others (for instance, if I am free to punch you in the face, you are not free to not be punched in the face; if I am free to own you as a slave, you thus lose a lot of freedoms).

Determining what freedom should mean is not, and has never been, a simple matter of "well, if you make any restrictions on it, then it's not real freedom, so everyone just gets to be free!" It's all about finding balance, and dealing with nuance, and all that frustrating hard stuff.

Re:Give up GitHub: The time has come by sangnoir on Thursday June 30, 2022 @11:34PM (#31942023)
Whose freedom a license guarantees is a fundamental difference, as the freedoms can be in conflict.

Which is a freer society: one that restricts late night partiers from playing loud music in residential areas, or the one that does not?