Re: IP Clearance

2020-10-09 Thread Nathan Hartman
On Thu, Oct 8, 2020 at 11:22 PM Matias N.  wrote:

>
> > We need all of the above:
> >
> > 1. Integrate license clearing with ongoing work like we are already doing
> > for nxstyle, *AND*
>
> I've created the following issue to remind ourselves of this:
>
> https://github.com/apache/incubator-nuttx/issues/1954
>
>
> >
> > 2. Ongoing calls for non-coders to participate (license clearing,
> > documentation, artwork, marketing), *AND*
>
> Definitely.
>
> > 3. Seek funding and/or corporate support to pay for professional license
> > clearing
>
> Maybe the fourth point would be to distribute the load to committers? I
> think that in the end
> we should collectively realize of the importance of this task in order to
> guarantee this project
> stays afloat. If point (3) is to be pursued and you agree that (4) should
> be a fallback then (3)
> should have some kind of deadline, otherwise we will be waiting for too
> long until it is too late.
>

We should not wait. All must proceed simultaneously.

All points need to start simultaneously and continue forever or until all
files are cleared. We don't wait to do point 1 or 4. We don't stop doing
points 2 or 3.

I am okay with adding a modified point 4: At each release, there is a
blocker to clear 20 random files per committer. So every release, we will
clear approximately 300 files, with that number increasing as we add
committers. After 5 releases (while adding committers), we will clear ~1500
to ~2000 files. That doesn't sound impressive because we have ~90,000
files, but we also have point 1: every file touched gets cleared like
nxstyle. Approximately ~7500 files were modified since we joined the
Incubator (almost 1 year), so we will clear approximately ~8000 files per
year from point 1, + ~2000 files cleared from point 4 = ~10,000 files per
year.

Yes, that will take 9 years but it means that the project will always make
progress toward license clearing because it will be an ongoing activity, so
it will not be a blocker to graduation.

Also we do points 2 and 3 and we don't give up. We continually seek
volunteers and corporate support. If the 5 biggest companies that use NuttX
in their products would split the cost of a professional license clearing,
the entire 90,000 files will be cleared in a month. That's good for those
companies because (1) it helps ensure the longevity and health of this
project which they depend on, and (2) it frees up the engineers to improve
NuttX instead of clearing licenses.

We should reduce the number of files. We should announce that broken
boards, architectures, and drivers that have not received maintenance in a
long time and have no one working to fix/maintain them will be removed
after the next two releases, especially if they also have license problems.
Of course this is more work to identify the broken ones and publish a list,
to give ample advance notice before removing code. But this is a code job,
so it's not as boring for engineers and will have the added benefit of
making the codebase smaller and more maintainable.

Nathan


Re: [DISCUSS] NuttX 10.0.0 Release schedule

2020-10-09 Thread Brennan Ashton
I'm a little behind where I wanted to be but I have collected a bunch of
the boards that we support and am going to work through what I can test
with them this weekend.

I did notice a fair number of patches for bug fixes this week that we may
want to be applying to this release including the spresense and esp, but
there may have been others as well. It would be nice if those could be
backported as needed prior to cutting the RC.

--Brennan

On Sat, Oct 3, 2020, 9:52 PM Brennan Ashton 
wrote:

> The releases/10.0 branches have been created off of master for both
> apps and the OS.
>
> I will work on populating the release note board tomorrow and starting
> to compile them.
> If any fixes need to be made for the 10.0.0 release they should be
> made against master
> and then a new PR made against the release branch with BACKPORT in the
> title so it
> is easier to identify.
>
> Also this issue was called out as being a blocker:
> https://github.com/apache/incubator-nuttx/issues/1804
>
> --Brennan
>
> On Tue, Sep 22, 2020 at 10:13 PM Brennan Ashton
>  wrote:
> >
> > Hey all, we have talked in loose terms about this release, but I think
> > it is time we committed, it has been probably too long since our last
> > release.
> >
> > Here is what I would propose for a release schedule:
> >
> >   09/28/20 -- Master Stability Window (keep the merging of risky PRs
> > to a minimum this week)
> >   10/03/20 -- Create the 10.0 release branch
> >   10/04/20 - 10/12/20 -- Stabilize / test / release notes
> >  Additionally in this window we need to make a couple CI tweeks to
> > handle the new docs off of the release branch (I expect this won't be
> > much work, but will be easier with the branch in place)
> >   10/12/20 -- Tag RC0 and call for PPMC / Community Vote
> >   10/15/20 (or when we have the votes) Call for IPMC Vote  or create a
> > new RC if needed to address issues
> >   10/23/20 (Pending votes and RC0 issues) --  Release RC0
> >   10/24/20 -- Update site and announce (we have to wait for download
> > mirrors to sync).
> >
> > I know that is almost a month, but that is usually about how long it
> > takes for the whole process, but realistically there is only a week or
> > so where we are aiming to slow down and stabilize the master branch.
> > The rest of it is testing, documenting, voting, and waiting time.
> >
> > I can be the release manager again for this one. But it would be great
> > if someone else jumps in for the release after and I will try to
> > document things a bit more to make the process easier.  We will need
> > to have more than one release manage to graduate, there are other
> > projects that have run into this.
> >
> > --Brennan
>