Why don't we have a permanent OSS license?
1–6 of 6 posts
Re: Why don't we have a permanent OSS license?
#2Re: Why don't we have a permanent OSS license?
#3A little piece I wrote. I might add more to it later, but I'd love any feedback. I feel like I might be missing something.
2. Companies publishing OSS don’t usually suffer enough skepticism for them to be willing to give up control over their trademark.
3. In some jurisdictions, copyright isn’t transferrable, and only licensing is allowed [0]. The original creator always retains the copyright. You seem to be talking more about the branding/trademark, however, which is a different thing.
[0] https://en.wikipedia.org/wiki/Copyright_transfer_agreement
Re: Why don't we have a permanent OSS license?
#4A little piece I wrote. I might add more to it later, but I'd love any feedback. I feel like I might be missing something.
1. This effectively already exists in the form of organizations like the Apache Software Foundation. 2. Companies publishing OSS don’t usually suffer enough skepticism for them to be willing to give up control over their trademark. 3. In some jurisdictions, copyright isn’t transferrable, and only licensing is allowed [0]. The original creator always retains the copyright. You seem to be talking more about the brandin…
Re: Why don't we have a permanent OSS license?
#5I'm not sure why the post dismisses this.
Re: Why don't we have a permanent OSS license?
#6Earlier quoted context omitted.
1. This effectively already exists in the form of organizations like the Apache Software Foundation. 2. Companies publishing OSS don’t usually suffer enough skepticism for them to be willing to give up control over their trademark. 3. In some jurisdictions, copyright isn’t transferrable, and only licensing is allowed [0]. The original creator always retains the copyright. You seem to be talking more about the brandin…
this is helpful feedback, thank you. Could you elaborate on 1 though?