Xiang introduced me to Peter from Xiaomi, and he is going to help gather
some overview data so we can see how many files and authors we're going to
be dealing with in different areas of the code. We'll be updating the wiki
page here:

https://cwiki.apache.org/confluence/display/NUTTX/License+Clearing

We'll report back when we have some more information.

-adam

On Tue, Jul 28, 2020 at 5:38 PM Adam Feuer <a...@starcat.io> wrote:

> A focused effort to do the IP clearing sounds good. If we can get funding
> to do it quicker, that would be great too. It's a good idea.
>
> I did the stats that are on the wiki page for the 9.0 release. I'll see if
> I can run this process on the rest of the project and post the numbers to
> the wiki. I'll update this thread when I have some results. I'll also see
> if I can make PR with the scripts Brennan and I were using so that the
> tools can be in the main repo and anyone can use them.
>
> -adam
>
> On Sun, Jul 26, 2020 at 8:39 PM 张铎(Duo Zhang) <palomino...@gmail.com>
> wrote:
>
>> OK, there is a sub page, about the status of a module at March
>>
>> https://cwiki.apache.org/confluence/display/NUTTX/Analysis+March+2020
>>
>> Let's try to do this on the whole project to get some numbers?
>>
>> Thanks.
>>
>> 张铎(Duo Zhang) <palomino...@gmail.com> 于2020年7月27日周一 上午11:32写道:
>>
>> > IMO we should at least have some numbers about the current status first,
>> > i.e, how many files can be cleared directly, how many can not, etc.
>> >
>> > With the numbers in hand, then we can decide whether it is possible for
>> us
>> > to finish the work, and how to finish the work. Even if we want to reach
>> > out for help from a 3rd party, we still need these numbers so we can
>> decide
>> > how much money we should pay...
>> >
>> > What I can see on the wiki page
>> >
>> > https://cwiki.apache.org/confluence/display/NUTTX/License+Clearing
>> >
>> >  is just a rough plan, there are no numbers about the current status
>> yet.
>> >
>> > Thanks.
>> >
>> > Gregory Nutt <spudan...@gmail.com> 于2020年7月27日周一 上午10:43写道:
>> >
>> >> We have talked a little about IP clearance on the NuttX podling project
>> >> but I am not sure if anyone really appreciates the magnitude of this
>> >> effort:  There is 13 years of commits, possibly 50,000 total commits,
>> >> many hundreds of contributors, 1000's of files, 1.5 million lines of
>> >> code, and transitions through 3 different configuration management
>> >> systems.  There is no contact information for the majority of the
>> >> contributors and there is no reason to believe that all contributors
>> >> will be cooperative.
>> >>
>> >> I think that anyone who believes that this can be done properly with
>> the
>> >> part time, now-and-then effort of a couple of people is sorely
>> >> mistaken.  I think it will require a fully dedicated, team with some
>> >> specialized expertise and a substantial amount of time to do.
>> >>
>> >> The only way that I can conceive of this happening is if we were to
>> >> contract a 3rd party software CM/QA/IV&V house to to do the job.  That
>> >> would, of course require a serious investment of money.  I am wondering
>> >> if we could motivate some corporate sponsors to fund such an effort.  I
>> >> appreciate that that is a long shot but we should consider it.  In the
>> >> past, Xiaomi, for example, as committed to supporting the licensing/IP
>> >> clearance effort.  But I don't think that anyone really appreciated the
>> >> effort required at that time.
>> >>
>> >> We do have to make this happen and I don't blame anyone on the PPMC for
>> >> not wanting to take this on.  It would cost you the next year of your
>> >> life .. full time.  I wouldn't make that commitment and I would not
>> >> expect any other individual to do so either.
>> >>
>> >> We some need a plan.  With no plan, the project will not graduate.
>> Even
>> >> with a plan in hand, I would not expect graduation to be possible
>> within
>> >> the next year or more.
>> >>
>> >> Greg
>> >>
>> >>
>> >>
>>
>
>
> --
> Adam Feuer <a...@starcat.io>
>


-- 
Adam Feuer <a...@starcat.io>

Reply via email to