On 02/06/2017 22:20, James Bognar wrote: > Thanks! > > I haven't found a metadata editor that works yet, so I'll just add a > LICENSE.txt file to the directory. Hopefully that's enough.
That is more than is necessary. It might even cause confusion at some point in the future. I would recommend against doing that. The concern is that folks have a tendency to attempt to reverse engineer ASF policy from what they see other projects do which leads them to assume all sorts of things are required when they are not. That in turn can consume effort that could have been better spent on other things. Any file in the project's source tree is ALv2 licensed unless explicitly called out otherwise in the LICENSE file at the root of the source tree. Where we can add a header to a file we do, but if we can't (easily), then we don't and that is fine. Mark > > On Fri, Jun 2, 2017 at 4:48 PM, Josh Elser <els...@apache.org> wrote: > >> On 6/2/17 1:15 PM, James Bognar wrote: >> >>> I just added several png files to the source tree of our podling. I >>> created them myself. Are there any best-practices on how to mark these as >>> Apache licensed? >>> >>> >> I'm not sure of a good way to track this. I'm not sure if png supports >> arbitrary metadata which could be edited. Some ways I've seen used >> elsewhere to try to better propagate license/ownership: >> >> * Comments on the issue-tracker issue that introduced them citing >> origin/source (typically for images that are copied, not created) >> * Entry in LICENSE/NOTICE (shouldn't be done unnecessarily, of course) >> * A README in the same directory with relevant info >> >> If the images are of the podling's creation, I wouldn't be particularly >> worried. The copyright notice on your source-release and LICENSE are >> sufficient to inform downstream consumers. >> >> Probably not the answer you're looking for, but hope it helps :) >> >> - Josh >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >> > > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
