Re: [paho-dev] IBM .Net MQTT Client - to contribute or not?

["Nicholas O'Leary" <nick.oleary@xxxxxxxxx>]

Hi,

my gut feeling is to not contribute this code. If we were starting from scratch, then there may be a reason to contribute the code as a starting point. Given we have M2Mqtt on its way, I think contributing a completely different .NET code base would be confusing in the long term. Regardless of how we structure it, users will browse the repository and inevitably pick up the wrong thing. 

I'd rather we didn't fill the repository with orphaned code on the off-chance it one day proves useful... which in this case I would doubt.

Nick

On 10 October 2014 10:37, Ian Craggs <icraggs@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

Hello everyone,

I have in my possession the code for a .Net MQTT client written by several people in IBM. I was going to contribute it to Paho before
Benjamin asked Paolo about M2Mqtt.

I much prefer to have M2Mqtt in Paho, because Paolo is an enthusiastic and committed maintainer of M2Mqtt, and there is no one like that for the IBM code.

So this is a simple question: should I put the IBM code into Paho simply as a collection which can be learned or stolen from, or
not contribute it at all, as that could lead to confusion?  (If contributed, it could go into the permanent incubator sub-project which I've asked to be set up).

I asked Paolo, and he left it up to me. :-)   Any other opinions please?

--
Ian Craggs
icraggs@xxxxxxxxxx                 IBM United Kingdom
Paho Project Lead; Committer on Mosquitto

_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/paho-dev