Mat, I have questions to raise aloud:
1. Would this license comply with OSD?
2. Should the OSI licensing board consider the above question?
3. Who does this benefit and how?
The first question hinges upon the interpretation of the license text. It’s
not carefully worded, requiring you to explain t
there can still use the code.
I’m not suggesting the OSI consider this license as an open source
candidate. I’m suggesting that if employees at Big Companies encounter code
licensed under this license, they can be glad they are people, and people
get to use this code for whatever they wish.
Gil
I wanted to share a thought based on the initiation of this discussion
thread (which I agree with). Forgive the length.
TL;DR: Technologists are called by moral inclination to address larger
social concerns related to technology. OSI’s licenses can’t help us in
these discussions. I use more words
FWIW I thought the zLib license was a good alternative for this use-case
(e.g. sample code that you expect people to use, modify and you don't want
to be attributed). But MIT-0 has the Warranty disclaimer. Seems better for
that reason.
Gil Yehuda: I help with external technology engagement
f your head! Your brains are laying on the ground in little
bloody pieces! Now I ask ya. Would you give a f@#$ what kind of pants the
son of a bitch who shot you was wearing?
I assume that victims of human rights abuse feel similarly about the
license text in our source code.
Gil Yehuda: I hel
I'll say "no, dear, I made sure that
the license was still OSI-approved."
I think part of the issue here is that in the face of real human issues,
this seems like a misuse of energy. Licenses manage the use of copyright
rights. We fight genocide with laws, with armies, maybe a
or companies to commoditize their competitors, and
for software purchasers to avoid vendor-lock in. It's all that and more.
Gil Yehuda: I help with external technology engagement
On Thu, Mar 19, 2020 at 12:54 PM Tobie Langel wrote:
> On Thu, Mar 19, 2020 at 2:18 PM Jim Jagielski
I'd like to learn if either is in play as a motivation, or if it is
something else. Perhaps someone with insight into and speaks on behalf of
the Ethical Source Movement can help clarify. It makes a difference.
Gil Yehuda: I help with external technology engagement
On Thu, Mar 19, 2020
proceed developing and enhancing the Ethical Source
movement materials and work with the Source-available movement to refine
their categories such that Ethical Source is best understood as a
source-available scheme? I believe that's what it seeks to be.
Gil Yehuda: I help with external technology
'm asking because I really want to
understand what processes you are recommending OSI use that you believe
would result in the outcomes you are looking for.
Gil Yehuda: I help with external technology engagement
On Wed, Mar 18, 2020 at 9:32 AM Tobie Langel wrote:
> On Tue, Mar 17, 20
t is hard to measure.
Clearly though, some people want a conversation about this, and others
don't. Given this is a conversation list, we're having a conversation.
Gil Yehuda: I help with external technology engagement
On Tue, Mar 17, 2020 at 6:08 PM McCoy Smith wrote:
> -Orig
pushback about doing so -- either in defense of the toxic
statement or in retribution for the assumed attack I was making. This is a
tough conversation to have in the open, I hope your blog is well received
by your readers. I look forward to reading it too.
Thanks again.
Gil Yehuda: I help with
rce (not
a licensing issue, more of a code of conduct thing).
Neither use case fits into the current OSD formula.The business-revenue use
case seems to be best addressed by what people refer to as 'source
available with restrictions' licenses, a.k.a 'not fully open', 'faux-
ords. Sorry to distract from the conversation.
Gil Yehuda: I help with external technology engagement
On Wed, Mar 11, 2020 at 6:05 PM Josh Berkus wrote:
> On 3/11/20 2:33 PM, Gil Yehuda via License-discuss wrote:
> > This topic is very important and we're all passionate about
toward our goals when we
focus on improving *open source* licensing.
Gil Yehuda: I help with external technology engagement
On Wed, Mar 11, 2020 at 4:50 PM Josh Berkus wrote:
> On 3/11/20 1:09 PM, Russell McOrmond wrote:
> > On Wed, Mar 11, 2020 at 9:42 AM Josh Berkus > <mailt
pproach
so that their success is not predicated on exploiting the open source
movement.
Gil Yehuda
On Tue, Mar 10, 2020 at 9:41 AM Coraline Ada Ehmke
wrote:
> I’ve been trying to cultivate the ability to extract actionable and
> constructive feedback from even rude, confrontational, di
mbers can't really tell if this is or is not an attack. So my advice to
the OSI is to request the ESM to come back to the table when they have
their message more polished. It will be better for the ESM (they'll be
considered on the merits of their actual message, not their previous
rhetoric),
case than we typically talk about, but I bring it to
show that some people are attached to their code since they invest
considerable energy into it -- and fear that letting go removes their
control of the code. Indeed this is the reality of the corporate-employed
engineer -- but it's not always the wa
tanding the different ways in which people feel
ownership of their work and how it relates to their views on licenses.
Sean, your "kids" analogy is very helpful as it can explain quite the range
of relationships people have with their code.
I hope to hear, thanks.
Gil Yehuda: I help w
27;s solution, a solution discovered
hundreds of years ago. I'm encoding it in a syntax someone else specified.
My solution may be novel to me, but not to others. So what is it that
attaches me to code such that I decide the terms under which you use it in
your solution?
Gil Yeh
me suggest that OSI members review the candidates who are running for
the 2020 Board of Directors for the OSI and consider their vote
https://wiki.opensource.org/bin/Main/OSI+Board+of+Directors/Board+Member+Elections/2020+Individual+and+Affiliate+Elections/
Gil Yehuda: I help with external
power to you. But unless one of those definitions changes, I
don't think that's going to happen. IMO these should be treated as separate
endeavors with separate goals.
Gil Yehuda: I help with external technology engagement
>From the Open Source Program Office
<https://developer.yaho
rit of understanding licensing mechanisms better, I'm still
curious if someone can get away with creating a license that technically
conforms with the OSD but creates the chilling effects that we'd all want
to avoid (e.g. imagine what someone could put in their notice or license
preamble).
Gil Y
under the terms of the...
Gil Yehuda
On Fri, Feb 21, 2020 at 2:33 PM Jim Jagielski wrote:
> Which is fine. It's their code and they can license it however they want.
> They just can't call it Open Source.
>
> On Feb 21, 2020, at 11:24 AM, Brendan Hickey
> wrote:
>
>
the concept "their code" since this was a
team effort.
Gil Yehuda: I help with external technology engagement
>From the Open Source Program Office
<https://developer.yahoo.com/opensource/docs/> at Verizon Media
On Fri, Feb 14, 2020 at 7:14 AM Lukas Atkinson
wrote:
> Yet, thi
;m pretty sure, thankfully). It was annoying
since it meant we had to look carefully at a repo and see that the license
headers were not consistent.
Gil Yehuda: I help with external technology engagement
>From the Open Source Program Office
<https://developer.yahoo.com/opensource/docs/> a
DQIJmxRI (tl;dw: Die Heretic Die). I
think this could be presented to introduce any discussion about open source
licenses.
Gil Yehuda: I help with external technology engagement
>From the Open Source Program Office
<https://developer.yahoo.com/opensource/docs/> at Yahoo / Verizon Media
O
from it.
However, your need to assert that as an individual, you place yourself in
yet another category that was not properly captured in my high-level
summary is a great signal to Bruce that his plans will face exactly these
headwinds.
Gil Yehuda: I help with external technology engagement
>
its turf and know
that others are not over-claiming.
tl;dr: People who say "one size fits most" mean "one size fits me."
Gil Yehuda: I help with external technology engagement
>From the Open Source Program Office
<https://developer.yahoo.com/opensource/docs/> at Yaho
end of the day, it's not
vegetarian. Just call it what it is. Meat eaters will enjoy it and
vegetarians will thank you for honest labeling.
Gil Yehuda: I help with external technology engagement
>From the Open Source Program Office
<https://developer.yahoo.com/opensource/docs/> at Yahoo
in return. But please don't put it in a legally binding license agreement
since I don't want to be obligated to tell you what I do.
Gil Yehuda: I help with external technology engagement
>From the Open Source Program Office
<https://developer.yahoo.com/opensource/docs/> at Yahoo -
only do things I'm proud of. But he didn't put it in a legal text.
I agree with your sentiment. I caution your implementation.
Gil Yehuda: I help with external technology engagement
>From the Open Source Program Office
<https://developer.yahoo.com/opensource/docs/> at Yahoo -->
ur readme file. Say "We do the
right thing. We are proud of what we do. We give at least $12 a year to
charity as our way to perform Da'ana... We encourage users of our source
code to do the same and make the world a better place." That can't hurt,
it's a declaration, not
e editions"), but who use the tools
created by those who do not, in order to convert interest into revenue from
employees who don't quite understand the parameters of these licenses.
Gil Yehuda
On Wed, Jan 23, 2019 at 3:30 PM Bruce Perens wrote:
>
>
> On Wed, Jan 23, 2019 at 1
imacy* since it
usually implies the invitation to know each other without doubts, and in
this case, it feels like kissing with eyes open, looking around.
*Gil Yehuda*
On Wed, Jan 23, 2019 at 11:39 AM John Cowan wrote:
>
>
> On Wed, Jan 23, 2019 at 1:27 AM Bruce Perens wrote:
>
> It
n source?
Also can you elaborate on concerns you have about the text you shared?
*Gil Yehuda: *I help with external technology engagement
On Tue, Jan 15, 2019 at 5:43 PM Christopher Sean Morrison via
License-discuss wrote:
>
> Relevant to the recent discussions about Government Open So
e for this very reason.
*Gil Yehuda: *I run the open source program office at Yahoo --> Oath -->
Verizon Media.
On Thu, Jan 10, 2019 at 4:42 PM Luis Villa wrote:
> On Thu, Jan 10, 2019 at 12:43 PM John Cowan wrote:
>
>>
>> On Thu, Jan 10, 2019 at 11:36 AM Gil Yehuda v
ns.
(Again, I'm not seeking legal advice. But I'd love to hear informed
perspectives on how to read this phrase properly.)
*Gil Yehuda: *I run the open source program office at Yahoo --> Oath
--> Verizon
Media
___
License
.)? Do CLA
signature websites need to have user consent terms, etc?
Does anyone here have a pointer to a clear statement about how GDPR impacts
the little things we do in the world of open source -- like CLA management?
Thanks.
*Gil Yehuda: *I help with externally facing technology at Oath.
On Tue, Aug 1
39 matches
Mail list logo
