We've had a lot of mailing list traffic lately. Already, halfway
through the month of November, there are far more than all the
messages from October. This is a great problem, but I'm getting some
feedback that indicates we're going to lose some ML members if we
don't find a way to decrease traffic.

This is a critical time for the development of the NuPIC software, and
much of the discussion has been about software engineering and
technical decisions about how NuPIC should evolve. These conversations
will only grow as NuPIC grows.

Other major topics include CLA theory and NuPIC usage.

I propose creating a new mailing list, called "nupic-dev", which sends
emails with the subject prefix "[nupic-dev]" (just like this one does
currently). Also, we change the email subject prefix for *this* list
to "[nupic-users]". So we'll have two lists:

"[nupic-dev]": nupic-...@lists.numenta.org
Topics:
- NuPIC development
- algorithm implementation
- software engineering processes and strategies
- future of the NuPIC project

"[nupic-users]": nupic@lists.numenta.org
Topics:
- HTM / CLA theory
- NuPIC usage (installation, use-cases, projects)

Hopefully, we'll keep all our current subscribers on [nupic-users],
and those interested in the development of NuPIC will also subscribe
to [nupic-dev], where we'll continue having discussions involving the
development of the NuPIC software.

As open source projects grow, they usually have a few mailing lists
associated with them, including xxx-dev, xxx-users, xxx-ann
(annoucements), and sometimes more. At some point in the future, there
may even be a point to break out a [nupic-theory] list up from
[nupic-users].

Anyone opposed? I'm going to let this topic ride for a few days to let
people have a chance to comment before taking any action. This is your
chance to weigh in.

---------
Matt Taylor
OS Community Flag-Bearer
Numenta

_______________________________________________
nupic mailing list
nupic@lists.numenta.org
http://lists.numenta.org/mailman/listinfo/nupic_lists.numenta.org

Reply via email to