Re: [mosquitto-dev] [paho-dev] Java MQTT broker

[Ian Craggs <icraggs@xxxxxxxxxxxxxxxxxxxxxxx>]

I would like to look at "broader compatibility between the features and configuration of the Java broker with the C broker" regardless of whether Moquette is in its own project or in Mosquitto :-)  Personally I don't think this is a defining reason for Moquette to be in its own project.

From my point of view the major factors are:

1) + a separate project allows the Moquette name to be visible
2) - a separate project entails a significant amount of extra work, both in project creation and (possibly less so) in day-to-day running.
3) - we (I?!) might have to work harder to monitor the status of both projects
4) + a separate project does have the advantage of keeping C and Java implementations apart nicely, and maybe more clearly encouraging specific communities and contributions

Although Paho is one project for the MQTT clients, having separate projects for MQTT servers makes as much sense as having one, because in general there are more features and code required for MQTT servers, so they are that much bigger than a client library.

That's a personal view.

Ian

On 27/01/14 17:00, Andy Piper wrote:

Hi Andrea, and thanks for jumping in, Mike!

This is really exciting and we would be delighted to work with you on bringing moquette to Eclipse!

You are completely free to choose which path to take - contribute moquette as its own project and retain your project name etc, or join the mosquitto project as a Java broker.

My own suggestion would be that joining the mosquitto project would leave us with an "MQTT clients" project (Paho) and an "MQTT brokers" project (Mosquitto), and that would be a nice way of organising things. However, as Roger and Ian discussed, you would probably then want to look at broader compatibility between the features and configuration of the Java broker with the C broker - that would not be a bad thing, but it might add to your code backlog!

Either way, please let us know your feelings and we will see how best to proceed.

Welcome again! great times for the MQTT community!

Andy

On Mon, Jan 27, 2014 at 4:27 PM, Mike Milinkovich <mike.milinkovich@xxxxxxxxxxx> wrote:

On 27/01/2014 10:51 AM, Andrea Selva wrote:

Hi Ian and list,
so seems that we all agree on the spirit and motivations. It's the
right time to move Moquette MQTT under the Eclipse Foundation? There
is an application path to make external projects be incubated into the
foundation?
I am very honored to be able to provide a valuable open source project
to an open community.

Andrea,

That's wonderful! Welcome to the Eclipse community!

Yes, there is a whole process[1] of bringing existing open source projects to the Eclipse Foundation.

One question that immediately comes to mind is whether you wish to keep "Moquette" as a separately identifiable name, or whether you wish to have this become the Java implementation of Mosquitto. Which path you desire will have implications for the project structure, trademarks, etc. So please discuss with everyone here which approach is preferred so that the EMO (the "Eclipse Management Organization") can help achieve the desired result.

[1] http://wiki.eclipse.org/Development_Resources/HOWTO/Starting_A_New_Project

--
Mike Milinkovich
mike.milinkovich@xxxxxxxxxxx
+1.613.220.3223

_______________________________________________
mosquitto-dev mailing list
mosquitto-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mosquitto-dev

--

Andy Piper | Kingston upon Thames, London (UK)
blog: http://andypiper.co.uk   |   skype: andypiperuk
twitter: @andypiper  |  images: http://www.flickr.com/photos/andypiper

_______________________________________________
mosquitto-dev mailing list
mosquitto-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mosquitto-dev