Re: Lost Repository History

2020-01-18 Thread Abdelatif Guettouche
> If i look at the statistics, it says I have 19 thousand commits. That should > be 36 thousand Probably Github is not assigning older commits to you. For instance the first one: https://github.com/apache/incubator-nuttx/commit/b08a86171f237f948fad94fa4906374ad3f413bc It's your username, but it

Re: Lost Repository History

2020-01-18 Thread Gregory Nutt
The GitHub mirror repo shows 36,000 commits. A "git log —reverse" shows the first commit as "Sat Feb 17 23:21:28 2007”. AFACS no history has been lost. Yes, now I see the same thing with "git log --reverse", but I was not seeing a few days ago.  I was seeing a date in 2013.

Re: Lost Repository History

2020-01-18 Thread Gregory Nutt
If i look at the statistics, it says I have 19 thousand commits. That should be 36 thousand Probably Github is not assigning older commits to you. For instance the first one: https://github.com/apache/incubator-nuttx/commit/b08a86171f237f948fad94fa4906374ad3f413bc It's your username, but it

Lost Repository History

2020-01-18 Thread spudaneco
It appears we have lost the first 6 year of history in the NuttX repository.  The oldest commit looks like it is from 2013.  The oldest should be from february 2007.If i look at the statistics, it says I have 19 thousand commits.  That should be 36 thousand,Is the repository permanently broken?

Re: Lost Repository History

2020-01-18 Thread Justin Mclean
Hi, > That should be 36 thousand,Is the repository permanently broken? The GitHub mirror repo shows 36,000 commits. A "git log —reverse" shows the first commit as "Sat Feb 17 23:21:28 2007”. AFACS no history has been lost. Thanks, Justin

Re: Lost Repository History

2020-01-18 Thread Abdelatif Guettouche
In Bitbucket we can see that we have all the history: https://bitbucket.org/nuttx/nuttx-old/commits/?page=1436 Locally (from a github clone) I can do git log --oneline | tail and I see the same last 10 commits as in bitbucket. On Sat, Jan 18, 2020 at 11:51 AM spudaneco wrote: > > It appears we

Re: Lost Repository History

2020-01-18 Thread Abdelatif Guettouche
> > 2013 must be the year that I switched from SVN to GIT? > Apparently, yes: https://bitbucket.org/nuttx/nuttx-old/commits/ca08f96482926d35b52101a863c4b6cfebdfca35 We can see here https://bitbucket.org/nuttx/nuttx-old/commits/?page=989 that every commit before ca08f96

Re: SocketCAN License

2020-01-18 Thread Gregory Nutt
So assuming all the code is dual licensed GPL/BSD and not a mixture of licenses then we’re fine to use it. We would need to note its license in our LICENSE file. Great!  So I am proposing to assist the parties that are interested in the development by creating a SocketCAN branch and

Re: Towards making your first Apache release

2020-01-18 Thread Brennan Ashton
Justin, Is there some docs to guide us in making this licencing transition? I would be happy to start the processing of adding spdx headers based on what is in the code if that would help, but I don't know how to transition files to Apache 2 under this project. I also know that while most of the

Re: [DISCUSS] Remove Windows Native support?

2020-01-18 Thread David S. Alessio
> On Jan 18, 2020, at 3:48 PM, Gregory Nutt wrote: > > >> This is not to say that this is a 100% stable development platform. There >> are still a few dangling, loose ends that I am aware and most likely more >> that I am not aware of. ... So basic functionality is there, but any real

Re: Towards making your first Apache release

2020-01-18 Thread Justin Mclean
Hi, It would be great if some people start working on these issues otherwise it will hold up making a release. I raised a couple of Github issues for the most urgent ones e.g having a LICENSE, NOTICE and DISCLAIMER and putting ASF headers on files. Thanks, Justin

Re: Towards making your first Apache release

2020-01-18 Thread Justin Mclean
Hi, > Is there some docs to guide us in making this licencing transition? I would > be happy to start the processing of adding spdx headers based on what is in > the code if that would help, but I don't know how to transition files to > Apache 2 under this project. It’s easy enough: - Add ASF

Re: Towards making your first Apache release

2020-01-18 Thread Brennan Ashton
On Sat, Jan 18, 2020, 7:11 PM Justin Mclean wrote: > Hi, > > > Is there some docs to guide us in making this licencing transition? I > would > > be happy to start the processing of adding spdx headers based on what is > in > > the code if that would help, but I don't know how to transition files

Re: Towards making your first Apache release

2020-01-18 Thread Gregory Nutt
In general, BSD licensed files with "Copyright (C) 20XX Gregory Nutt” would have the ASF header on them, but we may need to double check that they are not a 3rd party file that’s just had some changes to it or been reformatted. That is kind of offensive.  I would never do something like

License Analysis with Fossology

2020-01-18 Thread Brennan Ashton
To let us get started digging into properly analyzing the code in both the incubator-nuttx and incubator-nuttx-apps repos I spun up a Fossology server and uploaded both git repositories and used the automated monk scanner. You are welcome to see it for yourself at:

Re: Towards making your first Apache release

2020-01-18 Thread Justin Mclean
Hi, > That is kind of offensive. I would never do something like that. I have > never intentionally violated a license. I always give credit when credit is > due. You're misunderstanding me, I’m describing the conditions under which we can change the headers to ALv2. In some cases you have

Re: License Analysis with Fossology

2020-01-18 Thread Justin Mclean
Hi, Thanks for that. One minor issue exist with the HPND license. I’ve raised a legal JIRA for that. [1] this would not hold up a release. Justin 1. https://issues.apache.org/jira/browse/LEGAL-506

Re: License Analysis with Fossology

2020-01-18 Thread Justin Mclean
Hi, For the four clause BSD file, there files are OK, because of [1] incubator-nuttx/libs/libc/stdlib/lib_bsearch.c incubator-nuttx/libs/libc/stdlib/lib_qsort.c incubator-nuttx/libs/libc/stdio/lib_libdtoa.c incubator-nuttx/libs/libc/stdio/legacy_dtoa.c Basically that clause can be removed. Wee

Re: Towards making your first Apache release

2020-01-18 Thread Justin Mclean
Hi, > So for the OS BSD headers we would need to keep them on the file as well as > include it in the NOTICE file? No you would generally not add to NOTICE, only some things are added to NOTICE. See [1] > What happens when someone modifies one of these old files once the project > makes the

Re: Towards making your first Apache release

2020-01-18 Thread Justin Mclean
Hi, In general, BSD licensed files with "Copyright (C) 20XX Gregory Nutt” would have the ASF header on them, but we may need to double check that they are not a 3rd party file that’s just had some changes to it or been reformatted. Thanks, Justin

Re: License Analysis with Fossology

2020-01-18 Thread Justin Mclean
Hi, From memory when I took a quick look at this I think I found about 160 different pieces of 3rd parties codes. A little car may need to be taken as some files have double license headers. Thanks, Justin