License files with collaborative Open Source projects?

[Jusas]

Ok, so v4.0 needs a license - and I suppose I could get one by applying for it for an open source non-profit project.

However: how does this work for the contributors? They download the source, and are unable to compile it because they don't have the license file? Would I need to arrange some method of secret sharing so that anyone who wants to compile it has the license?

I guess you wouldn't look too kindly to adding the license file straight to the repo either... 😉
I think the barrier of entry for contributors is going to be too high, and that's definitely something I do not want. But do tell me if I'm missing something substantial here.

[Piedone]

We at Orchard Core have the same issue, please see my comments here: #3132 (comment) I also elaborated a possible solution with a kind of "node-locked" license that's specific to a given project, what would also be more secure than the current approach.

I think everyone working with the source of our project (including all contributors, but also people just exploring the code base and learning from it) getting a build error first and having to apply for an IS license is too high of a barrier of entry.

[JimBobSquarePants]

@Jusas

Users can apply for licenses. This is all documented.

https://docs.sixlabors.com/articles/imagesharp/index.html?tabs=tabid-1#how-to-use-the-license-file

@Piedone

I will not be making changes. License keys are the result of years of systematic abuse and quite frankly I’m starting to get annoyed telling me how I should enforce my own licensing.

I’ve had thousands of open source license key applications since enforcement began that I have honoured so the keys are clearly not a barrier to contribution.

[Skrypt]

Abuse is a big word there. I'm sure after you will rethink about it you will find that you are not that much of a victim. Now, I believe @Piedone made a simple comment. I believe OC is an open source project and to be honest I don't remember that we ever abused of someone.

Now, let's be serious and take a cup of tea all together and rethink about what we can do then.

Thanks for the honest answer.

[JimBobSquarePants]

I’m obviously talking about abuse of the license terms by commercial companies.

@Piedone has made multiple comments on different threads now regarding our licensing approach. None of which are informed.

[Skrypt]

I believe that when we started doing OC, more than10 years ago now, the licence was not there. It evolved over time, and to be honest I just learned that there is now a commercial licence. Then maybe, your move makes sense. Though, it is less common to require a licence for a community open source project. I normally try to find/use MIT licenced projects before anything else. Now, maybe its time to remove ImageSharp from Orchard Core or to start adding a warning in the Media Gallery about the fact that ImageSharp is not free. How about that?

I'm currently rebuilding that Media Gallery with Vue 3 so let me know.