News for hackers. Stuff that matters.
Re:Leantime: Open-Source Jira Alternative by kyaghmour on Monday October 09, 2023 @11:01AM (#37821163)
I was interested ... until I saw it was licensed under Affero :/
Re:Leantime: Open-Source Jira Alternative by intheleantime on Monday October 09, 2023 @11:35AM (#37821503)
How come? The practical difference between AGPL and GPL is that the term "distribution" now includes distribution via network aka SaaS.

Now I can see how this might be a problem for code libraries, infrastructure system etc but the only reason to worry about AGPL in an end user application context is the desire to repackage and sell commercially. Aka do the Amazon thing.

Re:Leantime: Open-Source Jira Alternative by jddj on Monday October 09, 2023 @11:43AM (#37821599)
It's the obligatory copyleft is not free software astroturfing comment.

Prompt is here: https://news.ycombinator.com/item?id=37611571

--

More seriously and charitably though, affero is vaguely scary because there's a (perhaps misunderstood, but I can understand) feeling that if you cooperate with it in any way in the backend and then a value-added product of that interaction makes it to a user of yours then you're up for copyright infringement.

This isn't a reason not to release under affero, nor is it a bad thing that entities producing non-free software need to take care what they leverage, but I can see how the decision could be made to avoid using agpl style software whereever possible to err on the side of caution.

A good example is ghostscript. At what point does an app converting PDFs to images (to display thumbnails, for example) as a small part of its workflow become an aggregate of that free software? According to the faq it ends up being a fairly subjective question of form and intent. Syscalls or static linking? Etc.

[dead]
Re:Leantime: Open-Source Jira Alternative by ljf on Tuesday October 10, 2023 @04:27PM (#37837019)
Hey - guessing you are banned (or shadow banned) for making a 2nd account to comment on a thread/submission you posted on another account. Was there a good reason to do that?
Re:Leantime: Open-Source Jira Alternative by ljf on Wednesday October 11, 2023 @09:03AM (#37843846)
Reply to parent, as I cannot reply to there sub reply to me:

As I could not reply to your other thread as you were banned

Re:Leantime: Open-Source Jira Alternative by jddj on Wednesday October 11, 2023 @04:08AM (#37842060)
Unfortunately I'm not a lawyer and wouldn't want to mislead anyone.

The best I can do is direct people to the GNU FAQs on the topic

Re:Leantime: Open-Source Jira Alternative by bilekas on Monday October 09, 2023 @11:25AM (#37821406)
I am really not savvy with the open source licenses, but why did you dislike the Affery license model ?
Re:Leantime: Open-Source Jira Alternative by _ZeD_ on Monday October 09, 2023 @11:34AM (#37821496)
this tool cannot be jeff'd
Re:Leantime: Open-Source Jira Alternative by kyaghmour on Monday October 09, 2023 @01:25PM (#37822844)
Here's from Leantime's own FAQ (https://leantime.io/pricing/): "We are GPL-2 and require code updates to be submitted back to the core code. We offer Enterprise licenses if you’d like to modify the code to use for company use."
Re:Leantime: Open-Source Jira Alternative by johandicap on Monday October 09, 2023 @01:50PM (#37823152)
Under GPL-2, is the company not allowed to modify the code for internal (company) use given they avoid publishing or distributing these modifications?
Re:Leantime: Open-Source Jira Alternative by broskees on Monday October 09, 2023 @11:43AM (#37821604)
What's wrong with AGPL?
Re:Leantime: Open-Source Jira Alternative by kyaghmour on Monday October 09, 2023 @01:04PM (#37822576)
Affero is effectively bait-and-switch.
Re:Leantime: Open-Source Jira Alternative by intheleantime on Monday October 09, 2023 @01:14PM (#37822699)
That is BS. Affero is not any different to GPL but the fact that network distribution is included in its definition of "distributing software" and having to relicense under the same license.

Where do you even get this from?

Re:Leantime: Open-Source Jira Alternative by kyaghmour on Monday October 09, 2023 @01:23PM (#37822812)
Call it what makes you warm and fuzzy.

Here's from Leantime's own FAQ (https://leantime.io/pricing/): "We are GPL-2 and require code updates to be submitted back to the core code. We offer Enterprise licenses if you’d like to modify the code to use for company use."

The pattern is effectively always the same. Many companies use this license to offer a free version while offering a "way out" by providing an "enterprise license". They get you hooked because it's open source. But as soon as you want to customize and keep the changes, they want to charge you.

It's a matter of personal choice. I choose NOT to use any Affero licensed software if I can help it.

Re:Leantime: Open-Source Jira Alternative by intheleantime on Monday October 09, 2023 @01:38PM (#37823019)
I think there is a misunderstanding of the license(s) here:

"But as soon as you want to customize and keep the changes, they want to charge you"

Neither GPL nor AGPL require you to submit anything back (or charges you) for changes made to your system for your own usage. Even if it is within a company. It is about preventing distributing derivates to the public under closed source licenses.

You can even have and keep changes (unpublished) for you entire organization without having to contribute back. It is when you distribute it back to public that you have to license the changes under the same license.

There is no baiting here.

Re:Leantime: Open-Source Jira Alternative by kyaghmour on Monday October 09, 2023 @02:18PM (#37823424)
Have you actually read the Affero license?

From section 13: "Notwithstanding any other provision of this License, if you modify the Program, your modified version must prominently offer all users interacting with it remotely through a computer network (if your version supports such interaction) an opportunity to receive the Corresponding Source of your version by providing access to the Corresponding Source from a network server at no charge, through some standard or customary means of facilitating copying of software."

Your statement is incorrect: "You can even have and keep changes (unpublished) for you entire organization without having to contribute back. It is when you distribute it back to public that you have to license the changes under the same license."

Even *HOSTING* a private instance puts you under Affero. Even if the instance isn't public, if you so much as have a contractor remotely accessing an internal deployment of a customized Affero-licensed software then they can ask for this customization.

https://www.gnu.org/licenses/agpl-3.0.en.html

Re:Leantime: Open-Source Jira Alternative by intheleantime on Monday October 09, 2023 @03:05PM (#37823986)
"You can even have and keep changes (unpublished) for you entire organization " -- add to that that the organization should have access to the source code, yes. That doesn't mean that you need to publish the code outside of your organization.

" Even if the instance isn't public, if you so much as have a contractor remotely accessing " -- Correct, now you are distributing the software to the "public" external to your own needs.

Re:Leantime: Open-Source Jira Alternative by kyaghmour on Monday October 09, 2023 @03:09PM (#37824049)
"interacting with it remotely through a computer network" isn't "distributing", it's hosting. Companies providing software under Affero licenses love to play with words. That's fine. It remains a bad license for users. I choose not to use any software licensed under its terms.
Re:Leantime: Open-Source Jira Alternative by mqus on Monday October 09, 2023 @03:36PM (#37824429)
> But as soon as you want to customize and keep the changes, they want to charge you.

But afaik you only have to provide the source to your users? You're never obligated to contribute back? So if you make in-house changes, this shouldn't matter much.

Re:Leantime: Open-Source Jira Alternative by mqus on Monday October 09, 2023 @03:40PM (#37824483)
Which license is then not bait-and-switch? Imho it is only that if they put all contributors under CLAs (they do) and even then this is a problem with the CLA, not the AGPL.