On 28 May 2016, at 10:38, aditi hilbert wrote:
I think John D. Ament raised some good points.
* Nothing in our binaries say Mynewt - do we need to by Apache rules?
* Our repos already include mynewt - so we should be fine there.
* the package "apache-newt" lacks a NOTICE/LICENSE file
* our license includes references to code that doesn't match our
notice - not sure which ones?
We don’t need it to say Mynewt by apache rules, John was pointing out
that it was confusing to him.
apache-newt does have a NOTICE/LICENSE file now, that is why Chris
repackaged the release. for some reason, only the newt directory of
apache-mynewt-newt was included in the source tarball of newt.
LICENSE/NOTICE issues can be resolved in a subsequent release IMO. We
have kept all the license info out of NOTICE, which I actually believe
is appropriate: I don’t believe we’re required by BSD license to put
that in a notice file (LICENSE should suffice.)
i’d be interested in what others (especially newcomers) would have
found helpful in the release tarballs in terms of documentation. i feel
like we have a fairly good set of docs on mynewt.apache.org, but that
often people want to see the docs next to the source code— and not
have to wonder what’s on a website. but i’d take others thoughts
here: i usually just go ahead and try and break things, and then search
for docs after they don’t work.
cheers,
sterling
