I’m ok with LICENSE and NOTICE. I haven’t reviewed README/RELEASE_NOTES since they are still being worked on. I don’t know how to review CONTRIBUTORS, but I would imagine some of our new testers need to go in it.
-Alex On 12/19/14, 1:04 PM, "Erik de Bruin" <e...@ixsoftware.nl> wrote: >So, the nice quiet on this thread means everyone is OK with the >current state of the legal docs? > >EdB > > > >On Thu, Dec 11, 2014 at 9:03 AM, Alex Harui <aha...@adobe.com> wrote: >> >> >> On 12/10/14, 11:25 PM, "Erik de Bruin" <e...@ixsoftware.nl> wrote: >> >>>Alex, did BlazeDS integration fully land, as far as the docs are >>>concerned? >> >> It seems to be working for me. It could use more testing. It would be >> great if someone took the nightly and tried to follow the README to >>build >> the source package. >> >> Should we mention that we removed the need to download the one BlazeDS >>jar >> in the RELEASE_NOTES? >> >> I think I found a error in LICENSE. I think the MPL shouldn’t be in >> LICENSE. I could not find any MPL files in the source package (and >>there >> shouldn’t be because it is category B and only binaries can be MPL). >>So, >> I am about to pull that out unless someone can explain why it should >>still >> be in there. I kept thinking it had to do with OSMF, but OSMF isn’t in >> the source package either, and there is a sentence at the beginning >>saying >> it applies to most of the directories. In looking at Git/SVN history, my >> current thinking is that we added it for 4.8 when we had some >> to-be-donated Adobe source in the package, but now I think everything >>has >> been donated. >> >> Meanwhile, I’m working on putting the OFL license acceptance into the >> install scripts, but I have to stop for now. >> >> -Alex >> > > > >-- >Ix Multimedia Software > >Jan Luykenstraat 27 >3521 VB Utrecht > >T. 06-51952295 >I. www.ixsoftware.nl
