Hi everyone,
Thanks for the discussion.
Another quick update -
I found out these non-open source licenses which on the other hand are not
completely closed:
https://commonsclause.com
https://polyformproject.org
We're also considering them. Even though they're not open source by OSI, in
some cases
On 09/08/2019 15:57, Gil Yehuda via License-discuss wrote:
Depending on what you mean "dual,"
Dual in the context of open source software generally means that you
licence it under two alternative sets of terms and the licensee can
chose which of those sets of terms to honour. Typically they
On Friday, 9 August 2019 15:42:16 CEST Russell McOrmond wrote:
> I'm wondering if anyone can help explain to me what they see as the
> difference between the forced public disclosure of private modifications of
> software, and registration of mere usage, private modification, or public
> discloseof
I believe this group is about discussing licenses, and not giving legal
advice about what you can or should do. In that context: "Can I release the
software under a dual license: AGPL and my modified Apache?" yes, you can
do whatever you please with your code. However the world will recognize
that
Related question -
Can I release the software under a dual license: AGPL and my modified
Apache?
Assuming my modified Apache is not open source by OSI, would the code still
be open source by OSI because it's also licensed under AGPL?
If so, then we end up with either:
* Disclose any modifications
To Ofer's new suggestion making registration a condition: no. That does not
work, either by the letter or, or the spirit of, open source.
I'd *love* to know who uses our code. If we run a meetup for an open source
project we run, we ask people on our message boards to speak (and they tell
us they
It
On Fri, Aug 9, 2019 at 6:46 AM Johnny A. Solbu wrote:
> Then you are effectively demanding registration.
> That is still not allowed in Free and Open Source software, meaning, that
> makes it Not Free and Open Source.
> I belive the Free Software Foundation would even call it proprietary.
>
>
On Friday 09 August 2019 09:29, Ofer wrote:
> What if I drop the ethics part and drop the 1$ support minimum?
> The license will only require that users of the code will add themselves to
> a file in the repo with the following fields:
> * Company/individual name
> * Description of how the soft
Thanks for the feedback everyone.
What if I drop the ethics part and drop the 1$ support minimum?
The license will only require that users of the code will add themselves to
a file in the repo with the following fields:
* Company/individual name
* Description of how the software is used
* Su
On Thu, Aug 8, 2019, 11:44 Ofer wrote:
> Let me clarify, I don't determine that, you do :-)
> You use the code, you "Make sure your use of the software complies with
> your own ethical standards", and you decide on the support $ amount.
>
You appear to have confused readme.txt and license.txt .
>
> Let me clarify, I don't determine that [ my company was ethical enough
> or pledged enough support for us to continue to use your code], you do
> :-)
>
You use the code, you "Make sure your use of the software complies with
> your own ethical standards", and you decide on the support $ amount.
On Thu, 8 Aug 2019 at 17:36, Gil Yehuda via License-discuss <
license-discuss@lists.opensource.org> wrote:
> >I'd love to know what you think of the whole thing.
>
> tl;dr: It's difficult to control other people's actions. Instead, seek
> acceptable outcome for yourself, and inspire goodness in ot
>I'd love to know what you think of the whole thing.
tl;dr: It's difficult to control other people's actions. Instead, seek
acceptable outcome for yourself, and inspire goodness in others.
You explain "I'd like to open source my company's code, but, I'm worried my
code will be misused." which is
On Thu, Aug 8, 2019, 09:31 Ofer wrote:
> Hi everyone,
> I'm a developer, now turned startup founder, so not much legal background
> except my own curiosity.
>
> I'd like to open source my company's code, but, I'm worried my code will
> be misused.
>
It sounds like you don't want to open source y
14 matches
Mail list logo