On Sat, Mar 7, 2020 at 9:45 PM Brennan Ashton <bash...@brennanashton.com> wrote: > Adam if you look back I have a hosted instance of it running for the > project, no sense in duplicating the work. I'm happy to provide you an > account. The nice thing about using this is that the reports can be shared > publicly and we can use the proper flow of working through the identified > license and copyrights and then marking them as resolved.
Hi all, I'd like to nudge (or pehaps push and shove) Apache NuttX toward making our first release as an Apache podling. Along those lines I'd like to revive this conversation... Where are we in terms of Fossology, Rat, and tracking down copyrights, in the move toward applying Apache 2.0 headers to our source files? I.e., how much has been done, what remains to be done, what specific things do we need help with, and can/should we make a "Call To Action" to our community to put more emphasis on getting this done? On a related note, would it be appropriate to open a "Do Not Merge" PR on GitHub, for the purposes of applying the header to each file as it is cleared, and also as a central location for all interested persons to collaborate on this (admittedly large) task? Or would it be more appropriate to open a PR for each file (or set of a few files) as they are cleared? Perhaps files that are cleared should immediately shift to Apache header, and files that prove to be more problematic should immediately be marked with some code that we can easily `grep' for in their header, so that it will be easier to keep track of what they are, and of who (people and/or companies) we need to reach out to for permission to change the headers? Finally (this is more a question for our mentors), assuming we have a proper DISCLAIMER, is there any reason for this licensing work to be a release blocker for our first Apache release? Thanks, Nathan
