Choose a license

[nico-abram]

I apologize if you already have a license and I missed it (I couldn't find one)

[rui314]

I haven't made my mind yet as to the license of this software. I want to make money from this software if I can, but at the same time I want this to be used as widely as possible. Ideally, if I can find a sponsor who will "purchase" this entire program (not a copy of it) and release it under the MIT license or something, it would be great. But if I release this under the MIT license from the beginning, no one has to do that in the first place. So, this is not an easy problem for me.

At this moment, I'm not too worried about not choosing a license. License matters when a program becomes something that people want to use, and IMO mold hasn't reached that point. This is still just my hobby, experimental project.

[rui314]

Beside the license issue, I believe it is too early to create a package for mold. It's too experimental.

[tux3]

A note to any hypothetical person in the business of pedantically following copyright law: according to GitHub's choosealicense.com and this StackOverflow Q/A, the GitHub ToS only guarantee that the code can be viewed publicly, and forked on GitHub.

In theory mondane things like making a local git clone or running the program are not allowed without acquiring a personal license.

Of course there are disturbing reports that international copyright law silliness rarely stops individual users, but I couldn't possibly confirm or deny that =)

[xyproto]

In addition to this, Linux distros need to be careful not to become Pirate Linux distros. A license file helps a lot.

[ssokolow]

Just a data point here. I'm very particular about using only free/libre tooling (ie. tooling under licenses that meet criteria like the Debian Free Software Guidelines and the Open Source Definition) for my modern projects, so I'm waiting to see what license this winds up under before touching mold at all, despite otherwise taking every opportunity I can find to speed up my Rust edit-compile-run cycle.

(I say "my modern projects" because I made an exception for Open Watcom C/C++'s "too copyleft" license for DOS hobby projects and I'm still split on whether to do my Windows 3.1 retro-hobby programming exclusively in Open Watcom C/C++ or to use my New Old Stock copy of Borland Delphi 1.x for rapid prototyping and risk not having time to rewrite in C when I release the source for others hobbyists to hack on. Likewise, I might make a very limited exception for my vintage copies of QuickBasic 4.5 and Visual Basic 3.0 just for the nostalgia factor of using things I always wanted as a kid.)

[rui314]

Folks, I just added a LICENSE file to the project so that you guys can clone this repo and use the resulting executable without having legal concerns. mold is now available under the GNU AGPLv3, which is an OSI-approved open-source license. You can copy, build, use, distribute or make any modifications to a forked copy as long under the terms of AGPLv3.

[ssokolow]

Thanks. I'll put trying it out on the tail end of the TODO list I'm hoping to reach the end of today.

[joshcangit]

I guess AGPLv3 is OK. I think having Apache-2.0 or MIT license is better.

If mold had to go, I hope it would be in good hands. Would be cool if mold would become part of Clang LLVM.

I dread seeing this project become proprietary software.

[rui314]

I haven't decided anything, but I understand your concern. At the same time, I want you to understand that I've spent hundreds of thousands dollars if not a million for this project already if you include opportunity costs. When you ask me to relicense it under Apache or MIT, you are asking me to give it up completely and effectively donate it to the public for free. I'd like you to take a moment to realize that.

I'll freeze this bug since this isn't a bug.