You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@otava.apache.org by "smccarthy788 (via GitHub)" <gi...@apache.org> on 2025/03/17 13:34:23 UTC
[I] Remove license header from config files and potentially other snippets [otava]
smccarthy788 opened a new issue, #38:
URL: https://github.com/apache/otava/issues/38
From the dev list:
> config files can typically be considered not creative work and therefore not copyrightable. TheASF Source Header and Copyright Notice Policy seems to recognize this in https://www.apache.org/legal/src-headers.html#faq-exceptions
This applies to the `otava.yaml` config, but debatably applies to other code snippets under `examples/`.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@otava.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Remove license header from config files and potentially other snippets [otava]
Posted by Henrik Ingo <he...@nyrkio.com>.
On Tue, Mar 18, 2025 at 1:51 AM dave2wave (via GitHub) <gi...@apache.org>
wrote:
>
> dave2wave commented on issue #38:
> URL: https://github.com/apache/otava/issues/38#issuecomment-2731213072
>
> > Since we expect users to copy paste short snippets into their own
> code, and that own code isn't necessarily licensed in an Apache compatible
> way, nor do we want to burden users with such consideration, it follows
> that the code snippets cannot be Apache licensed either, and therefore we
> would like to think they're also not copyrightable.
>
> Not quite true. The Apache License 2.0 is entirely compatible with
> users copying code and using it within a differently licensed work. That's
> due to the permissive nature of the license. Also, the license is a license
> to copy.
>
Hmm.. I tried to be careful when I wrote that... I mean things like
paragraph 4, where someone copying a few lines of example code would need
to then also distribute a copy of the apache license, list of trademarks,
etc... That seems to defeat the purpose of providing examples, if it
becomes impractical to use the examples at all.
From a practical point of view, we want the otava software to be ASL
licensed. When a user downloads and executes otava, they become recipients
of the ASL. However, if our docs have a few lines of code showing how
someone might use Otava from some other system, we don't want that other
system to be considered a derivative work of Otava. (Unless of course it
incorporates Otava itself.)
henrik
henrik
Re: [I] Remove license header from config files and potentially other snippets [otava]
Posted by Henrik Ingo <he...@nyrkio.com>.
On Tue, Mar 18, 2025 at 3:28 PM dave2wave (via GitHub) <gi...@apache.org>
wrote:
>
> dave2wave commented on issue #38:
> URL: https://github.com/apache/otava/issues/38#issuecomment-2733227901
>
> I don't think that's true. If you wish clarification then please ask
> legal-discuss@apache.org
It's not obvious wich email and who you are repllying to, but I'm going to
assume it's me.
Yeah so before asking for the formal opinion, I would first go and review
for example code snippets, t o determine what we actually have and wether
they even reasonably could be the kind of file/snippet that this discussion
is meaningful. And now that I looked around, I don't see that we even have
such code examples.
The examples/ directory actually contain config files, one for each
different data backend. I presume it is well established that a short
config file isn't a creative work, since each option is constrained by a
limited set of allowed options that a user can even choose, and then that
set is further constrained by constraints of reality.
So this is something we could indeed ask legal-discuss, if there isn't
consensus that the otava.yaml files could be without a license header.
I should also say this isn't high priority for me, merely wanted to
complete a discussion that branched off Sean's PR.
henrik
Re: [I] Remove license header from config files and potentially other snippets [otava]
Posted by "henrikingo (via GitHub)" <gi...@apache.org>.
henrikingo closed issue #38: Remove license header from config files and potentially other snippets
URL: https://github.com/apache/otava/issues/38
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@otava.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Remove license header from config files and potentially other snippets [otava]
Posted by "henrikingo (via GitHub)" <gi...@apache.org>.
henrikingo commented on issue #38:
URL: https://github.com/apache/otava/issues/38#issuecomment-6494929399
Since this ticket came from something I said in another review, I'll just close it. Time has passed, everything working fine.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@otava.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Remove license header from config files and potentially other snippets [otava]
Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave commented on issue #38:
URL: https://github.com/apache/otava/issues/38#issuecomment-2731213072
> Since we expect users to copy paste short snippets into their own code, and that own code isn't necessarily licensed in an Apache compatible way, nor do we want to burden users with such consideration, it follows that the code snippets cannot be Apache licensed either, and therefore we would like to think they're also not copyrightable.
Not quite true. The Apache License 2.0 is entirely compatible with users copying code and using it within a differently licensed work. That's due to the permissive nature of the license. Also, the license is a license to copy.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@otava.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Remove license header from config files and potentially other snippets [otava]
Posted by "henrikingo (via GitHub)" <gi...@apache.org>.
henrikingo commented on issue #38:
URL: https://github.com/apache/otava/issues/38#issuecomment-2731184049
Examples is a good catch. Since we expect users to copy paste short snippets into their own code, and that own code isn't necessarily licensed in an Apache compatible way, nor do we want to burden users with such consideration, it follows that the code snippets cannot be Apache licensed either, and therefore we would like to think they're also not copyrightable.
In config files I'd want to include also the toml file for the project. Basically any file that a user would edit directly when merely building and running otava.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@otava.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Remove license header from config files and potentially other snippets [otava]
Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave commented on issue #38:
URL: https://github.com/apache/otava/issues/38#issuecomment-2733227901
I don't think that's true. If you wish clarification then please ask legal-discuss@apache.org
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@otava.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org