Re: [License-discuss] exploring the attachment between the author and the code

On Sun, Mar 1, 2020 at 11:51 AM Gil Yehuda via License-discuss < license-discuss@lists.opensource.org> wrote: > Thank you Stuart, you are right. The fear of losing control is a big part > of this. Josh, indeed. All code is based on other code. This is why there's > such a conflict. Russel, I'm ask

Re: [License-discuss] exploring the attachment between the author and the code

On 3/1/2020 5:58 PM, Thorsten Glaser wrote: > Is that so in the USA? Here it reads more like the exclusive exploitation > rights belong to the employer when done as part of hired work, but the > moral rights belong to the natural person who created it. There is no legally cognizable moral right i

Re: [License-discuss] exploring the attachment between the author and the code

Gil Yehuda via License-discuss dixit: >Sometimes she'll say, "but it's my code." and I'll say, technically it's This is weird. I can differentiate between author and licensor. >work for hire that you assigned the copyrights to the company, but I Is that so in the USA? Here it reads more like th

Re: [License-discuss] exploring the attachment between the author and the code

Gil, Thanks for asking the question; it is a topic that has always fascinated me. My belief based on my personal experience only is that software may be unusual in authors /not/ feeling that they have a strong sense of ownership of their work, regardless of who the legal owner is. I learned v

Re: [License-discuss] exploring the attachment between the author and the code

Thank you Stuart, you are right. The fear of losing control is a big part of this. Josh, indeed. All code is based on other code. This is why there's such a conflict. Russel, I'm asking about all code authors because there are many ways to view this. A few times a year I get a report of code on Gi

Re: [License-discuss] exploring the attachment between the author and the code

On Fri, Feb 28, 2020 at 11:31 AM Gil Yehuda via License-discuss < license-discuss@lists.opensource.org> wrote: > I'm exploring the psychological relationship between the author of a work, > and the work. i.e. parsing the phrase "my open source code" and would like > your thoughts. > What you appe

Re: [License-discuss] exploring the attachment between the author and the code

On 2/28/20 8:15 AM, Gil Yehuda via License-discuss wrote: > 1. When I use open source code in my solution, I still feel that my > solution is mine (even though others wrote some of it). > 2. When my code is used by others, I don't feel less attached to my > code. It still feels mine. > 3

Re: [License-discuss] exploring the attachment between the author and the code

I'm exploring the psychological relationship between the author of a work, and the work. i.e. parsing the phrase "my open source code" and would like your thoughts. Assume I need an algorithm, say the quadratic formula. Option A

Re: [License-discuss] exploring the attachment between the author and the code

Hi Nicholas, On Fri, Feb 28, 2020, at 14:07, Nicholas Matthew Neft Weinstock wrote: > As an analogy, think about an artist during the Renaissance. Thanks for your analogy. Your text as well as Gil's framing question about "how our creation is used" reminded me of a conversation I had with an art

Re: [License-discuss] exploring the attachment between the author and the code

wns the copyright. I think this is a legal reflection of the emotional connection to the work that persists even after the legal ownership is transferred to a new owner. Thanks, Nicholas Weinstock From: License-discuss On Behalf Of Gil Yehuda via License-discuss Sent: Friday, February 28, 2

Re: [License-discuss] exploring the attachment between the author and the code

e expression? > > > > One last point: I'm only talking about Copyrights. I'm not touching on > Patents because mathematical formulae aren't patentable, so it's not > relevant to this question. > > > -Nick Weinstock > > > > From: License-dis

Re: [License-discuss] exploring the attachment between the author and the code

iscuss Cc: Gil Yehuda Subject: [License-discuss] exploring the attachment between the author and the code I'm exploring the psychological relationship between the author of a work, and the work. i.e. parsing the phrase "my open source code" and would like your thoughts. Assume

Re: [License-discuss] exploring the attachment between the author and the code

> On Feb 28, 2020, at 12:46 PM, Thorsten Glaser wrote: > > It’s mine, I crafted the work, so I have a certain amount of pride > in it (“Werksstolz” in German). However I’m standing on the shoulders > of giants (those who created Unix/BSD, MuseScore, the canon of the > fandom I’m writing fanfics

Re: [License-discuss] exploring the attachment between the author and the code

Christopher Sean Morrison via License-discuss dixit: >This exploration is a beautiful change of pace that I can get behind, Agreed, something positive for once! […] >across multiple projects, but I actually don’t perceive any of it as >“my code” even where the inception, authorship, and sharing

Re: [License-discuss] exploring the attachment between the author and the code

On Fri, Feb 28, 2020 at 11:16 AM Gil Yehuda via License-discuss < license-discuss@lists.opensource.org> wrote: > >1. When I use open source code in my solution, I still feel that my >solution is mine (even though others wrote some of it). >2. When my code is used by others, I don't fe

Re: [License-discuss] exploring the attachment between the author and the code

This exploration is a beautiful change of pace that I can get behind, so thanks Gil! I would offer a counter-perspective to your code ownership claim. I’ve authored and modified more than a million lines of code over decades across multiple projects, but I actually don’t perceive any of it as

[License-discuss] exploring the attachment between the author and the code

I'm exploring the psychological relationship between the author of a work, and the work. i.e. parsing the phrase "my open source code" and would like your thoughts. Assume I need an algorithm, say the quadratic formula. Option A is promising and is licen