On Thu, Apr 11, 2024 at 10:57 AM Chris B wrote:
> But in the meantime, I want to hear why some other OSS licensed projects have
> Terms, e.g. VSCode is MIT licensed and has terms:
> https://code.visualstudio.com/license
If I'm not mistaken, in that case (perhaps less than all?) the source
code
Thanks, Philippe and others!
Useful content for me to go through. I think the biggest issue that I am
hearing is the separation of what is "paid content".
The goal for me was to *allow individuals and business*
- to use the software freely
- to modify the software if needed to meet their needs
A
Thanks for the responses! Just to be clear, I want to allow anyone to take
the free and open source version and be able to modify it and use it for
commercial purposes. From what I understand from the discussion, i need to
be explicit about what paid features are (even though it's obvious in the
pr
Hi Chris:
On Sat, Apr 6, 2024 at 11:32 AM Chris B wrote:
> I am an open source project maintainer and I was referred to this
> mailing list recently as a good place to ask questions.
>
> I was recently told by a community member that I should not be using
> the term "Open Source" as it has legal
On 09/04/2024 14:30, John Sullivan wrote:
You say "commercial" here but I think you mean "proprietary" right?
Since the GPL says commercial as in "for a fee" redistribution is
allowed.
Well corrected, although it all goes towards the point that "paid
version" is too vague.
On 07/04/2024 04:37, Justin Clift wrote:
- Unless provided with a written agreement, no persons are
permitted to redistribute another paid version of CapRover.
"paid version" needs defining. Any requirement that all distribution be
free of charge would be invalid. Furthermore, any rest
Hi all!
I am an open source project maintainer and I was referred to this
mailing list recently as a good place to ask questions.
I was recently told by a community member that I should not be using
the term "Open Source" as it has legal implications and the project
doesn't fully embrace tha
Atwood atwo...@amazon.com<mailto:atwo...@amazon.com>
Principal Engineer, Open Source Program Office, Amazon.com
+12066042198
From: License-discuss On Behalf
Of Chris B
Sent: Friday, April 5, 2024 9:07 PM
To: license-discuss@lists.opensource.org
Subject: [EXTERNAL] [License-discuss] Open
On Fri, Apr 5, 2024, at 23:07, Chris B wrote:
> Hi all!
>
> I am an open source project maintainer and I was referred to this mailing
> list recently as a good place to ask questions.
>
> I was recently told by a community member that I should not be using the term
> "Open Source" as it has le
Hi all!
I am an open source project maintainer and I was referred to this mailing
list recently as a good place to ask questions.
I was recently told by a community member that I should not be using the
term "Open Source" as it has legal implications and the project doesn't
fully embrace that ter
10 matches
Mail list logo
