[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



Reply via email to