incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Kim <>
Subject License and notice files
Date Mon, 19 Mar 2012 22:02:48 GMT
Hey everyone,

So to cut a proper release we need to include a license and notice file
that contains the various licenses and required third party notices that
our project uses [1]. Another requirement of these license and notice files
is that they be placed in the top level directory of our release [2]. I was
thinking that when we generate our release using the coho tool, it'll look
into each platform repo for these notice/license files, combine them into a
master notice/license file, and place that in the top level directory of
the release. So it'll look something like:



For coho to combine these license/notice files there's going to be some
overlap to worry about. For example, each license/notice file starts out
with the same legal jargon as well the possibility of using the same code
with the same license between platforms. Which means it'd be nice if we
could have some delimiters in the license/notice files to make string
compares easier.

Perhaps another way we could go is to have the top level notice and license
file stating that there are lower level notice and license files and to
look for them if a user is so inclined. It'd be easier since it's less
work, but I'm not certain if that's okay. If a mentor could be so kind to
comment on that, that'd be great.

In any case, a quick review of the repos show that ios, android, and bb
have the notice and license files whereas the other repos either just have
a license file or none. So I think it'll fall upon the platform maintainers
to keep these up to date as well making sure they are complete.

Timothy Kim

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message