David's reasoning makes sense given where
the project is. I also suggest one list for now. We can adjust later if
it becomes a problem, (e.g. with indicators in subject line).
.................Scott
From:
David M Williams/Raleigh/IBM@IBMUS
To:
General development
discussions for paho project <paho-dev@xxxxxxxxxxx>
Date:
03/09/2012 02:45 PM
Subject:
Re: [paho-dev]
Paho: MQTT C client code available
Sent by:
paho-dev-bounces@xxxxxxxxxxx
My advise ... stick with one list until or if it just gets too busy and
cluttered with vastly separate topics and a very different group of people.
Hopefully titles will be specific enough that people would know which to
skip/skim read and which interested them in detail. Having one list per
project is easier for Eclipse webmasters to administer, easier for users
to
find, improves things like searching for a topic months later, prevents
a
"general" topic of interest to all accidentally get started (or
"transform"
into general topic) on the wrong list, etc. ... and who knows ... there
might be some C and Java/OSGi overlap? :)
From:
Raymond Auge <raymond.auge@xxxxxxxxxxx>
To:
General development discussions for paho project
<paho-dev@xxxxxxxxxxx>,
Date:
03/09/2012 02:18 PM
Subject:
Re: [paho-dev] Paho: MQTT C client code available
Sent by:
paho-dev-bounces@xxxxxxxxxxx
Patiently awaiting the java code as I'm about as skill in C as I am in
neuroscience.
:)
Regarding discussions on language specifics, will it all be conducted under
this one list?
For example I'd like to eventually discuss the java client details of OSGi
support. Such a topic is likely of no interest to developers
of other
languages. Will that matter? Does anyone care?
Sincerely,
- Ray
On Fri, Mar 9, 2012 at 1:18 PM, Andy Piper <andypiperuk@xxxxxxxxx>
wrote:
Great stuff. Now, if only we had a make target that would let me
build it
on OS Xâ :-)