Hi,
On 31 Aug 2017, at 8:19, aditi hilbert wrote:
On Aug 31, 2017, at 8:15 AM, David Brown <[email protected]>
wrote:
BTW, can someone please remove the !@#$ Reply-to header in the apache
mailing lists? It completely breaks messages that are cross posted,
effectively stealing all replies from all other mailing lists, as
well
as from anyone that was CC'd that doesn't happen to be on the Apache
mailing list.
On Wed, Aug 30, 2017 at 10:08:50PM +0200, Andrzej Kaczmarek wrote:
I'm now porting NFFS code to Zephyr and in order to avoid forking
this
code into two separate projects I'd like to propose to move NFFS
code into
its own repository (i.e. mynewt-nffs) and basically make it a bit
more
generic so it can be used by other projects.
I think this is a good idea. We'll need to figure out what project
to
host it under.
Just as MCUboot was pulled out into a separate repository hosted under
runtimeco,
perhaps NFFS could have its own repo there as well? Happy to copy that
over.
In my opinion this should be a sub-project of Apache Mynewt:
apache-mynewt-nffs. The filesystem is a part of our operating system,
unlike a boot loader which is more naturally a joint project. We can
market NFFS as a sub-project, and separately release it within the
Mynewt PMC (from *core.) The project definition defines governance, but
does not restrict multiple different releases.
If we get critical mass on NFFS, we can break it into a sub-project of
Apache Mynewt as the TLP (allowing it to have its own PMC/committers to
vote on release), but that requires going through incubator which seems
heavyweight to me.
Sterling
