Re: Podling Nuttx Report Reminder - April 2020

[Flavio Junqueira]

Any update on the report? I don't see it on the April 2020 wiki page.

Thanks,
-Flavio

> On 26 Mar 2020, at 00:20, jmcl...@apache.org wrote:
> 
> Dear podling,
> 
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
> 
> The board meeting is scheduled for Wed, 15 April 2020, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, April 01).
> 
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
> 
> Candidate names should not be made public before people are actually
> elected, so please do not include the names of potential committers or
> PPMC members in your report.
> 
> Thanks,
> 
> The Apache Incubator PMC
> 
> Submitting your Report
> 
> --
> 
> Your report should contain the following:
> 
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
>the project or necessarily of its field
> *   A list of the three most important issues to address in the move
>towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
>aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
> *   How does the podling rate their own maturity.
> 
> This should be appended to the Incubator Wiki page at:
> 
> https://cwiki.apache.org/confluence/display/INCUBATOR/April2020
> 
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
> 
> Note: The format of the report has changed to use markdown.
> 
> Mentors
> ---
> 
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
> 
> Incubator PMC

Re: Incubator site link broken

[Flavio Junqueira]

It is back.

-Flavio

> On 30 Jan 2020, at 14:28, Flavio Junqueira  wrote:
> 
> There was indeed an issue with the xml, I'm looking into fixing it. Thanks 
> for pointing it out, Pelle.
> 
> -Flavio
> 
> 
>> On 30 Jan 2020, at 14:18, Flavio Junqueira  wrote:
>> 
>> I have made the most of the latest changes to the project xml:
>> 
>> 
>> r1873362 | fpj | 2020-01-30 14:15:54 +0100 (Thu, 30 Jan 2020) | 1 line
>> 
>> Removed one tracker as suggested.
>> 
>> r1873271 | wave | 2020-01-28 21:03:53 +0100 (Tue, 28 Jan 2020) | 1 line
>> 
>> There can be only one tracker
>> 
>> r1873156 | fpj | 2020-01-25 16:32:02 +0100 (Sat, 25 Jan 2020) | 1 line
>> 
>> Updates NuttX status page.
>> 
>> r1873143 | fpj | 2020-01-25 13:07:03 +0100 (Sat, 25 Jan 2020) | 1 line
>> 
>> Updates NuttX status page.
>> 
>> r1871817 | fpj | 2019-12-19 11:13:15 +0100 (Thu, 19 Dec 2019) | 1 line
>> 
>> Adds gitbox repo link to nuttx status page.
>> 
>> r1871700 | fpj | 2019-12-17 16:13:10 +0100 (Tue, 17 Dec 2019) | 1 line
>> 
>> Updates mentor-related section in NuttX status page.
>> 
>> r1871671 | fpj | 2019-12-16 18:37:39 +0100 (Mon, 16 Dec 2019) | 1 line
>> 
>> Updates to NuttX status.
>> 
>> r1871599 | fpj | 2019-12-15 19:19:12 +0100 (Sun, 15 Dec 2019) | 1 line
>> 
>> Add status page for Nuttx.
>> 
>> 
>> But there was one from "wave" (I don't know who wave is), which doesn't look 
>> it broke anything. I have made a suggested change and will keep 
>> investigating.
>> 
>> -Flavio 
>> 
>>> On 30 Jan 2020, at 10:24, Philippe Coval  
>>> wrote:
>>> 
>>> Hi.
>>> 
>>> Well,
>>> It used to work (google indexed it already)
>>> 
>>> I also noticed that there are some broken links on this page too:
>>> http://nuttx.apache.org/community/
>>> 
>>> like:
>>> https://www.mail-archive.com/dev@nuttx.incubator.apache.org/
>>> 
>>> Should be:
>>> https://www.mail-archive.com/dev@nuttx.apache.org/
>>> 
>>> maybe it would be wise to look at 404 errors in logs or crawl pages...
>>> 
>>> My .02 EUR
>>> 
>>> 
>>> 
>>> 
>>> On Thu, Jan 30, 2020 at 8:12 AM Pelle Windestam <
>>> pelle.windes...@tagmaster.com> wrote:
>>> 
>>>> Hi,
>>>> 
>>>> The link to NuttX at https://incubator.apache.org/projects/ seems to be
>>>> broken, I just get a 404 error. Has it been moved?
>>>> 
>>>> //Pelle
>>>> 
>>>> 
>>>> 
>>> 
>>> -- 
>>> -- 
>>> gpg:0x467094BC
>>> xmpp:philippe.coval@gmail.com
>>> https://elinux.org/User:RzR
>> 
> 

Re: Incubator site link broken

[Flavio Junqueira]

There was indeed an issue with the xml, I'm looking into fixing it. Thanks for 
pointing it out, Pelle.

-Flavio


> On 30 Jan 2020, at 14:18, Flavio Junqueira  wrote:
> 
> I have made the most of the latest changes to the project xml:
> 
> 
> r1873362 | fpj | 2020-01-30 14:15:54 +0100 (Thu, 30 Jan 2020) | 1 line
> 
> Removed one tracker as suggested.
> 
> r1873271 | wave | 2020-01-28 21:03:53 +0100 (Tue, 28 Jan 2020) | 1 line
> 
> There can be only one tracker
> 
> r1873156 | fpj | 2020-01-25 16:32:02 +0100 (Sat, 25 Jan 2020) | 1 line
> 
> Updates NuttX status page.
> 
> r1873143 | fpj | 2020-01-25 13:07:03 +0100 (Sat, 25 Jan 2020) | 1 line
> 
> Updates NuttX status page.
> 
> r1871817 | fpj | 2019-12-19 11:13:15 +0100 (Thu, 19 Dec 2019) | 1 line
> 
> Adds gitbox repo link to nuttx status page.
> 
> r1871700 | fpj | 2019-12-17 16:13:10 +0100 (Tue, 17 Dec 2019) | 1 line
> 
> Updates mentor-related section in NuttX status page.
> 
> r1871671 | fpj | 2019-12-16 18:37:39 +0100 (Mon, 16 Dec 2019) | 1 line
> 
> Updates to NuttX status.
> 
> r1871599 | fpj | 2019-12-15 19:19:12 +0100 (Sun, 15 Dec 2019) | 1 line
> 
> Add status page for Nuttx.
> 
> 
> But there was one from "wave" (I don't know who wave is), which doesn't look 
> it broke anything. I have made a suggested change and will keep investigating.
> 
> -Flavio 
> 
>> On 30 Jan 2020, at 10:24, Philippe Coval  
>> wrote:
>> 
>> Hi.
>> 
>> Well,
>> It used to work (google indexed it already)
>> 
>> I also noticed that there are some broken links on this page too:
>> http://nuttx.apache.org/community/
>> 
>> like:
>> https://www.mail-archive.com/dev@nuttx.incubator.apache.org/
>> 
>> Should be:
>> https://www.mail-archive.com/dev@nuttx.apache.org/
>> 
>> maybe it would be wise to look at 404 errors in logs or crawl pages...
>> 
>> My .02 EUR
>> 
>> 
>> 
>> 
>> On Thu, Jan 30, 2020 at 8:12 AM Pelle Windestam <
>> pelle.windes...@tagmaster.com> wrote:
>> 
>>> Hi,
>>> 
>>> The link to NuttX at https://incubator.apache.org/projects/ seems to be
>>> broken, I just get a 404 error. Has it been moved?
>>> 
>>> //Pelle
>>> 
>>> 
>>> 
>> 
>> -- 
>> -- 
>> gpg:0x467094BC
>> xmpp:philippe.coval@gmail.com
>> https://elinux.org/User:RzR
> 

Re: Incubator site link broken

[Flavio Junqueira]

I have made the most of the latest changes to the project xml:


r1873362 | fpj | 2020-01-30 14:15:54 +0100 (Thu, 30 Jan 2020) | 1 line

Removed one tracker as suggested.

r1873271 | wave | 2020-01-28 21:03:53 +0100 (Tue, 28 Jan 2020) | 1 line

There can be only one tracker

r1873156 | fpj | 2020-01-25 16:32:02 +0100 (Sat, 25 Jan 2020) | 1 line

Updates NuttX status page.

r1873143 | fpj | 2020-01-25 13:07:03 +0100 (Sat, 25 Jan 2020) | 1 line

Updates NuttX status page.

r1871817 | fpj | 2019-12-19 11:13:15 +0100 (Thu, 19 Dec 2019) | 1 line

Adds gitbox repo link to nuttx status page.

r1871700 | fpj | 2019-12-17 16:13:10 +0100 (Tue, 17 Dec 2019) | 1 line

Updates mentor-related section in NuttX status page.

r1871671 | fpj | 2019-12-16 18:37:39 +0100 (Mon, 16 Dec 2019) | 1 line

Updates to NuttX status.

r1871599 | fpj | 2019-12-15 19:19:12 +0100 (Sun, 15 Dec 2019) | 1 line

Add status page for Nuttx.


But there was one from "wave" (I don't know who wave is), which doesn't look it 
broke anything. I have made a suggested change and will keep investigating.

-Flavio 

> On 30 Jan 2020, at 10:24, Philippe Coval  wrote:
> 
> Hi.
> 
> Well,
> It used to work (google indexed it already)
> 
> I also noticed that there are some broken links on this page too:
> http://nuttx.apache.org/community/
> 
> like:
> https://www.mail-archive.com/dev@nuttx.incubator.apache.org/
> 
> Should be:
> https://www.mail-archive.com/dev@nuttx.apache.org/
> 
> maybe it would be wise to look at 404 errors in logs or crawl pages...
> 
> My .02 EUR
> 
> 
> 
> 
> On Thu, Jan 30, 2020 at 8:12 AM Pelle Windestam <
> pelle.windes...@tagmaster.com> wrote:
> 
>> Hi,
>> 
>> The link to NuttX at https://incubator.apache.org/projects/ seems to be
>> broken, I just get a 404 error. Has it been moved?
>> 
>> //Pelle
>> 
>> 
>> 
> 
> -- 
> -- 
> gpg:0x467094BC
> xmpp:philippe.coval@gmail.com
> https://elinux.org/User:RzR

[DISCUSS] Security list

[Flavio Junqueira]

This is Flavio, I'm one of the project mentors, and I'd like to start a 
discussion thread about creating a security list. Let me start with some 
background.

The ASF has a security team that provides guidance to projects on security 
matters and coordinates the handling of security vulnerabilities, e.g., 
handling CVE requests. The security team has a general secur...@apache.org 
address to receive reports and to communicate with projects. See this page for 
more information.

https://www.apache.org/security/ 

Some projects opt for having their own security team and consequently their own 
security list. Project security teams evaluate vulnerability reports submitted 
about the project and interact with both reporters and the Apache Security 
Team. 

If we create such a list for this project, then it would be listed here:

https://www.apache.org/security/projects.html 


And vulnerability reports would be sent to that list for evaluation. Without a 
project security list, any vulnerability report will be sent to the general 
secur...@apache.org list, which will then be forwarded to the private@nuttx 
list. 

In the case the team decides to have its own security team, the team includes 
project PMC members, and it could also include committers if the project 
chooses to. At this point of the project, there is no difference between the 
set of committers and PPMC, but it might make a difference later on.

The two points I suggest we discuss and eventually move to vote depending on 
the feedback are:

1- Should this project have a security team and create a 
secur...@nuttx.apache.org list for this project?
2- Should the security list include only project PMC members or also interested 
committers?

Thanks,
-Flavio

Re: Workflow and Release strategy Proposal (Was RE: Project Emails)

[Flavio Junqueira]

Greg,

Why would you want to shut down your slack space? Some projects use a slack 
space and even the ASF has one: the-asf.slack.com

-Flavio

> On 14 Dec 2019, at 00:46, Gregory Nutt  wrote:
> 
> 
>>> I suggest that we really need to get all discussions, participation,
>>> and contributions "under one roof" so to speak, at
>>> dev@nuttx.apache.org. I think the Slack, the Google Group, the
>>> LinkedIn Group, and any other forums that fragment participants,
>>> should wind up soon. Whenever we reply to a message there, we should
>>> remind people that those forums are deprecated and that they should
>>> join dev@nuttx.apache.org.
>>> 
>> I think at least the LinkedIn group is not in this category of
>> removing users from the mailing list, quite the opposite. The LinkedIn
>> group goal is to advertise and show projects and products using NuttX.
>> Many people discovered NuttX thanks our announcements there. There is
>> not a discussion group in the Linkedin, but only a showcase for NuttX.
> 
> The LinkedIn group really is a different creature.  It has thousands of 
> subscribers and close to no participation.  Alan is essentially the only 
> poster there.
> 
> I am willing to shut down the Slack right now, at this moment. Every time I 
> proposed doing that, people balk because there might be something of 
> importance there.  There might be, but it would be in a closed channel or a 
> person-to-person conversation.  I think it should go now, but I need support 
> and concurrence to take that step.
> 
> Just speak the words and it is gone.
> 

Re: Contributions (PR or patches)

[Flavio Junqueira]

Patches through the email list are acceptable [1]. It is harder to track issues 
and implement an effective workflow (e.g., running QA builds, code reviews) for 
contributions via the list, but from a legal standpoint, it is acceptable.

-Flavio

[1] https://www.apache.org/foundation/how-it-works/legal.html 


> On 19 Dec 2019, at 09:15, Alin Jerpelea  wrote:
> 
> I agree that we should use both.
> 
> Personally I like github PR since we can do code review and automated
> testing on PR
> With some manual work we can also handle patches as long as they apply
> clean and someone will spend the time to test them manually.
> 
> Regards
> Alin
> 
> 
> On Mon, Dec 16, 2019 at 12:56 PM David Sidrane  wrote:
> 
>>> So, how will we keep track of approvals? I assume that GitHub has a built
>> in mechanism for this purpose?
>> 
>> Nathan,
>> 
>> Yes it if built for this and from my perspective working on a 93 person
>> team, with 67 repositories. It is highly efficient, collaborative, and
>> effective.
>> 
>> For example:
>> Ignoring the excellent process integration to create a proper work flow
>> that keeps master clean and building with full CI integration.
>> 
>> Have a look Suggested changes:
>> Suppose you’re collaborating on a repository with an active pull request.
>> A reviewer can look at that pull request, and if they see room for
>> improvement, suggest a change to the code by leaving a comment. The author
>> can then accept the suggestion with a single click.
>> 
>> DRAFT PR. You want input on a design. Create a draft PR, get all the input
>> and value add the community has to offer. That will not be merged before it
>> is ready.
>> 
>> Here is the value I see in this from past experiences: I have had multiple
>> ways to solve a problem and wanted to get the collective expert's feed
>> back. I Put up a PR for discussion marking it a Work In Progress [WIP] and
>> the next thing I know, my WIP was merged.
>> 
>> From my perspective patches, unless applied to a branch do not offer a
>> collaborative resolution method- nor do they provide a way to educate the
>> community, without an undo effort to decode the delta for the contributed
>> patch to what was applied (speaking of the past process).
>> 
>> Let's get some requirements defined, our goals laid out and then discuss
>> the pros and cons of the options for workflow and the tools that exits the
>> make the whole of the PPMC productive. I am reflecting on statements like,
>> "Volunteers with full time jobs" and "Simple for users." We owe it to
>> ourselves and the community to make this efficient and effective.
>> 
>> David
>> 
>> On 2019/12/16 03:35:01, Xiang Xiao  wrote:
>>> Yes, GitHub has the standard workflow, we just need insert our special
>>> requirement(style, build and test) into it:
>>> 
>> https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/github-flow
>>> Here is one example mynewt:
>>> https://github.com/apache/mynewt-core/pull/2126
>>> 
>>> Thanks
>>> Xiang
>>> On Mon, Dec 16, 2019 at 10:56 AM Nathan Hartman
>>>  wrote:
 
 On Sun, Dec 15, 2019 at 9:12 PM Gregory Nutt 
>> wrote:
 
> Sorry to keep running on...
> 
> Another thing is that we do not want dictate to uses of release what
> configuration management tools they must use.  In our open source
> culture, GIT is pervasive, but remember that many corporations prefer
> commercial SCM systems.
 
 
 Case in point: My $company uses a really awesome SCM: Apache
>> Subversion :-)
 
 So the process is something along these lines:
 
 (Please fill in any gaps...)
 
 Will we receive a patch, which I'm assuming will come to dev@ in the
>> form
 of email attachments, then a NuttX committer looks at it, sees if it
>> looks
 reasonable, then converts that into a GitHub PR.
 
 Which begs the question: how do we keep track of emailed patches being
 processed? Perhaps as simple as a committer replying to the email to
>> say
 that it's being processed?
 
 Once at GitHub then automated tests run (including nxstyle), then ...
>> ???
 
 In certain parts of the system, I think we should have reasonably low
 barriers to getting contributions in. Drivers for adding, say, SPI
>> support
 to some chip shouldn't require too much scrutiny provided they meet the
 coding standard...
 
 But:
 
 In some critical parts, including the build system and OS internals
>> like
 the scheduler, we need a process whereby several pairs of eyes will
>> look at
 the PR and agree that it should be merged. For example, say, we need N
>> +1s
 and zero -1s for any changes that affect those parts... (the value of N
 will need discussion but that is a subject for another day).
 
 So, how will we keep track of approvals? I assume that GitHub has a
>> built
 in mechanism for this purpose?

Re: nuttx.events

[Flavio Junqueira]

Hi Greg,

It is ok to discuss separately the organization of events, they don't need to 
happen on the project mailing lists. If the event is open to the community with 
an open call for abstracts, then you might want to announce it on the user/dev 
lists. Some communities do not like it, though. If there is a company backing 
such an event, people could complain that it is not a neutral event and as such 
should not be advertised on the Apache lists.

As a sample point, I have never organized events using the Apache lists or any 
other channels, but we have announced project meetups to let people sign up to 
attend and present.

-Flavio

> On 18 Dec 2019, at 20:06, Gregory Nutt  wrote:
> 
> This is a question for Justin or any other mentor.
> 
> There are a couple of associated web sites that are dedicated for NuttX event 
> planning:  nuttx2019.org and https://nuttx.events/. nuttx2019.org now just 
> re-directs to nuttx.events.  They event planners used to use a private 
> channel in the NuttX Slack for communication.  However, the NuttX project can 
> no longer host private conversations in the NuttX Slack;
> 
> nuttx.events is managed by Dave Marples..  It is fairly open but they need to 
> have some private discussions related to events, event planning, sponsor 
> relationships, etc.  For example, planning is (or at least was) underway for 
> the NuttX2020 event in Tokyo in May.  I am not sure what they are doing now.. 
> I hope I didn't undermine them too badly.
> 
> So the question is, after having booted event planning out into the cold, is 
> there some way to bring it back into the fold.  There must be other projects 
> that host events and must have similar planning needs.  Do you know what the 
> standard practice is for such things?  I imagine that an independent group 
> like nuttx.events is necessary, but is there any way to coordinate. Slack 
> private channels worked very well for this.  I don't know what the 
> replacement could be and would be open to suggestions.
> 
> Greg
> 
> 

Mentors -> Access to Incubator SVN?

[Flavio Junqueira]

I wanted to confirm that all mentors have access to the incubator SVN. Justin 
McLean clearly does. Could Junping Du and Mohammad Asif Siddiqui confirm that 
they have Incubator SVN access?

Thanks,
-Flavio

Re: Add some instructions or make the link available on Nuttx home page

[Flavio Junqueira]

Hello,

I have fixed a few things and pushed the changes. They need to propagate to the 
site.

-Flavio

> On 16 Dec 2019, at 17:06, Abdelatif Guettouche 
>  wrote:
> 
> Hi Flavio,
> 
> The dev mailing list seems not updated:
> d...@project.incubator.apache.org instead of
> d...@nuttx.incubator.apache.org
> 
> On Mon, Dec 16, 2019 at 3:05 PM Flavio Junqueira  wrote:
>> 
>> Hi Jincheng,
>> 
>> The status page is now live and being populated:
>> 
>> http://incubator.apache.org/projects/nuttx.html
>> 
>> I'm not sure where the broken link in the main apache.org page is.
>> 
>> -Flavio
>> 
>>> On 16 Dec 2019, at 08:07, jincheng sun  wrote:
>>> 
>>> I found there is a link of NuttX is not work in home page of 
>>> `apache.org`[1].
>>> So, I create a JIRA for this issue [2]. But I found is not the issue for `
>>> apache.org` but something worng in NuttX home page [3]. I do not know how
>>> to deal with this kind of problems, so, report the problems in this
>>> maillist.
>>> 
>>> Best,
>>> Jincheng
>>> 
>>> [1] http://apache.org/
>>> [2] https://issues.apache.org/jira/browse/INFRA-19576
>>> [3] http://incubator.apache.org/projects/nuttx.html
>> 

Re: Add some instructions or make the link available on Nuttx home page

[Flavio Junqueira]

Hi Jincheng,

The status page is now live and being populated:

http://incubator.apache.org/projects/nuttx.html

I'm not sure where the broken link in the main apache.org page is.

-Flavio

> On 16 Dec 2019, at 08:07, jincheng sun  wrote:
> 
> I found there is a link of NuttX is not work in home page of `apache.org`[1].
> So, I create a JIRA for this issue [2]. But I found is not the issue for `
> apache.org` but something worng in NuttX home page [3]. I do not know how
> to deal with this kind of problems, so, report the problems in this
> maillist.
> 
> Best,
> Jincheng
> 
> [1] http://apache.org/
> [2] https://issues.apache.org/jira/browse/INFRA-19576
> [3] http://incubator.apache.org/projects/nuttx.html

Re: File headers [was Re: ICLA needed?]

[Flavio Junqueira]

The BSD license (except for the BSD 4-clause) is friendly towards the ALv2 one:

https://www.apache.org/legal/resolved.html#category-b 


I suppose that the worst case is that we keep that contributed code under the 
BSD license, and make necessary references, like in NOTICE?

-Flavio

> On 15 Dec 2019, at 22:18, Gregory Nutt  wrote:
> 
> 
>>> So, could we just remove the original BSD header
>>> from Samsung modified files and just keep their Apache license into
>>> those file?
>> I don’t recommend we do that as they may of made changes or the files may of 
>> changed since they copied them. They probably also used teh 3rd party header 
>> not the ASF one.
> 
> No Samsung files could be brought in until they are made to conform to the 
> NuttX coding standard (Yes, Samsung changed the coding standard too).  If 
> they are reconverted to the NuttX standard, it should be pretty easy to see 
> any differences.
> 
> I think we are talking about a doomsday scenario here.  We need to get 
> creative only if there is a snag.  Let's assume that there will be no snag 
> (but also be prepared with Plan B).
> 
> Greg
> 
> 

Re: Podling status page

[Flavio Junqueira]

Ok, the status page is live now, I'll continue populating it.

-Flavio

> On 15 Dec 2019, at 21:38, Justin Mclean  wrote:
> 
> Hi,
> 
>> And committed a new nuttx.xml file under trunk/content/projects, but then I 
>> was checking the svn log, and I saw a commit from you adding a nuttx.yml 
>> file under trunk/content/podlings. Is the documentation stale and we are 
>> supposed to track the status in the file you added? Could you please clarify?
> 
> Currently you need both files, the yml one is not well documented.
> 
> Thanks,
> Justin

Re: Project Emails

[Flavio Junqueira]

Hi Greg,

On the email lists, the mentor's guide suggest that we create dev@, commits@, 
and private@, also recommending that we add user@ later if needed:

https://incubator.apache.org/guides/mentor.html#request_mailing_lists 


We are following the guidelines, but there is some flexibility to it.

-Flavio

> On 12 Dec 2019, at 19:36, Gregory Nutt  wrote:
> 
> [Moved to the dev list.  Was Re: Access to private email archive ].
>> People should send patches to dev@.
> 
> Other projects have additional emails, often user[s] and issues, often many 
> more:  https://mail-archives.apache.org/mod_mbox/
> 
> I am personally used to having a one-email-for-everything, but it looks like 
> additional emails could be used if the PPMC decides to do that.
> 
> We are actually starting with a sub-project.  We probably should discuss that.
> 
> A NuttX release consists of two tarballs nuttx/ and apps/. nuttx/ is the 
> operating system proper; apps/ is a collection of applications that may or 
> maynot be used with the operating system proper.  These applications 
> including some key things and I think most people want to incorporate some 
> subset of applications into their project.
> 
> But since the applications are NOT part of the operating system they do need 
> to remain separate.  I would argue against trying to merge application code 
> into the operating system.  So I think we have to consider these two separate 
> releases.  We historically release them together as a matched pair so that 
> the use can be user that they interoperate properly.
> 
> Back to emails... separating application-related discussions from core OS 
> discussions might be something worth considering.  Some projects also have 
> separate commits mail lists for commits to the two repositories. For example, 
> the lucene project has commits, c-commits, java-commits, pylucene-commits, 
> and solr-commits.  I assume that thes are all sub-projects.
> 
> Greg
> 
> 
> 

Re: Apache NuttX website

[Flavio Junqueira]

Hi Nathan,

As part of this thread, I wanted to make sure you have come across this page:

https://incubator.apache.org/guides/sites.html 


-Flavio

> On 11 Dec 2019, at 16:22, Nathan Hartman  wrote:
> 
> Currently there is nothing at http://nuttx.apache.org (not that I
> expected to find anything there at this early stage in the game).
> 
> Until there is an actual site, can we throw up some kind of "coming
> soon" with the Apache and NuttX logos, a blurb about the podling just
> starting up, and a call for volunteers? (Volunteers wanted for ALL
> areas, including to build the new site.)
> 
> How should the Apache NuttX website be hosted?
> 
> I guess our choices are: hosting from the ASF's Subversion repository;
> hosting from a CMS of some type... are there other possibilities?
> 
> What steps will those participating in the project take to edit the
> site?
> 
> Cheers,
> Nathan

Re: State of Bitbucket Repsitories

[Flavio Junqueira]

I don't think you need to get rid of the earlier incarnation of the project. As 
per the ASF legal documentation, we need to make sure that the copyright 
holders sign either CLAs or software grants:

https://www.apache.org/foundation/how-it-works/legal.html 


This incubator document also talks about the initial code import:

https://incubator.apache.org/guides/transitioning_asf.html 


Finally, as an example, we still have the zookeeper code in sourceforge from 
before Apache, and I don't that's wrong:

https://sourceforge.net/p/zookeeper/code/ 


-Flavio

> On 10 Dec 2019, at 16:50, Gregory Nutt  wrote:
> 
> 
>> I think we need to ask our mentors what is the generally accepted
>> thing to do with the project's earlier incarnation.
> 
> 100% agreed.  We need guidance.
> 
> 

Re: State of Bitbucket Repsitories

[Flavio Junqueira]

I can see this INFRA issue for NuttX:

https://issues.apache.org/jira/browse/INFRA-19542 


But that does not talk about creating a gitbox repo.

Justin, do we need to create a new INFRA ticket?

-Flavio

> On 10 Dec 2019, at 15:25, Gregory Nutt  wrote:
> 
> I am continuing to accept changes to the (deprecated) NuttX repositories on 
> Bitbucket.org.  Can someone please inform me when INFRA is ready to 
> instantiate the Apache Github repositories?  I will then make the the 
> Bitbucket repositories read-only and prohibit forks and PRs.  Let's try to 
> make that transition as "knife-edge" as possible.
> 
> Greg
> 
>