Dear Ian Craggs
Sorry for late reply, and thank you very much for your answer
and the details regards the Intellectual Property Policy at
Eclipse.
We read this document carefully and it seems that there is no
major issue regarding the process.
In case of acceptance, the source code could be maintained by
Pierre Goudet and myself Yuchiro Shibata.
The source have been fully developed at Ruby Development, with the
inclusion of source from the ruby-mqtt gems for the packet
serialiazer.
We are currently re-evaluating the contribution of Nicholas for
his help, and we hope that he would allow us to use this source
code in our gem.
Except in the packet serializer, there no external source, or
dependencies that should raise license issues.
Also as deep source code reviews would be need, could you give us
more details about who will be in charge of the reviews and where
the reviews would be done?
Thank you again for your interest in the creation of a ruby paho
version,
Best regards,
Yuichiro Shibata
On 2017/02/09 18:27, Ian Craggs wrote:
Yuichiro Shibata, (and Nick Humfrey),
we are very interested in having an MQTT client library in Ruby
as part of the Eclipse Paho project, of course. In fact, we had
a discussion with Nick a couple of years back about having Nick
contribute his, but at the time we weren't using Github as the
code repository, and this was a significant hurdle for Nick.
The process for contributions at Eclipse is quite strict,
because the intent is to make the software safe for all
consumers, whether private or commercial, free from any
copyright or patent issues (see
http://www.eclipse.org/community/eclipse_newsletter/2014/july/article4.php
for an introduction).
Assuming the contribution process is successful, we would also
prefer to have someone join Paho as the committer responsible
for the Ruby client, as everyone has their plate full already.
Ian
On 02/08/2017 12:39 PM, Ian Skerrett
wrote:
Yuichiro Shibata
Thank you for the quick reply and the
willingness to address these issues quickly. I believe the
Eclipse Paho project leaders are the best to respond on what
will be the next steps for submitting a pull request. Ian
Craggs and James can you guys help here?
Ian
Dear
all,
Thank you for your answers and comments. We would
try to fix the issues that you noticed as fast as
possible.
We are also thinking about the license, as the paho
library is distributed under the Eclipse License and
our gem is currently distributed under the very
permissive MIT License. Is there any issue if we
change the MIT License to the Eclipse License in our
gem?
Thank you
again for the packet serializer, as we talk in a
previous conversation, it seems to be really efficient
and we estimate that there were no need to make big
changes on it. Also, we would be glad to credit you in
the packet modules. Could you tell us what format would
please you?
For example,
what about including the following header in the packet
serializer files?
### original
file from the ruby-mqtt gem
### located at https://github.com/njh/ruby-mqtt/blob/master/lib/mqtt/packet.rb
###
### The MIT License (MIT)
### Copyright (c) 2009-2013
Nicholas J Humfrey
### Permission is hereby
granted, free of charge, to any person obtaining a copy of
this software and associated documentation files (the
"Software"), to deal in the Software without
### restriction, including
without limitation the rights to use, copy, modify, merge,
publish, distribute, sublicense, and/or sell copies of the
Software, and to permit persons to whom the
### Software is furnished to do
so, subject to the following conditions:
### The above copyright notice
and this permission notice shall be included in all copies
or substantial portions of the Software
###
### THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF
ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
THE
### WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE AND NON INFRINGEMENT. IN NO EVENT SHALL
THE AUTHORS
### OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES
OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT
OR
### OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH
THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
For
lowering the dependencies of the new gem, we chose to just
use the source regarding the serialization of packets in
your gem instead of including the whole gem. We understand
that you would like us to contribute to your project.
However, as the implementation choice of our client seems
to differ from yours, so we decided to make separate
client.
We
apology for the misuse of the paho library name, we might
have been too much enthusiastic in the development. In
order to solve the issues that you pointed, could you
teach us the process to match the Eclipse paho project
expectations? We are aware that other fixing might be need
and we would be glad to make them for improving the
library.
Thank you for
answer. Indeed, one of the goal of that project is to be
included in the Eclipse Paho Project and we will do our
best for this. Could you tell us on where the pull request
should be opened for the ruby version of Eclipse paho?
Regarding the committer, Pierre Goudet
would be happy to provide any kind of support for the gem.
Best regards,
Yuichiro Shibata
On 2017/02/08
10:09, Ian Skerrett wrote:
I
am sure there is good intentions by the Ruby
Development, Inc. to have the Ruby client as part of
Eclipse Paho project.
However,
I would like to reiterate Nick’s point about the Paho
project name. Paho is a trademark of the Eclipse
Foundation and can only be used by the Eclipse Paho
project or by permission of the Eclipse Foundation.
I
certainly hope Ruby Development, Inc will respect the
Paho trademark. One obvious solution will be this code
is accepted by the Eclipse Paho project. To have this
happen, would it make sense for a pull request to be
opened for Eclipse Paho? I would also assume a new
committer would come with this code?
If
the code is not accepted, I would hope and expect the
Ruby Development, Inc. would respect the Eclipse Paho
trademark and change the name of the package. I would
also hope Nicholas’s request for correct attribution is
fulfilled.
Thank
you
Ian
Skerrett
Eclipse
Foundation
From: paho-dev-bounces@xxxxxxxxxxx
[mailto:paho-dev-bounces@xxxxxxxxxxx]
On Behalf Of Nick O'Leary
Sent: Monday, February 6, 2017 8:16 AM
To: General development discussions for paho
project <paho-dev@xxxxxxxxxxx>
Cc: mqtt@xxxxxxxxxxx; p-goudet@xxxxxxxxxxx
Subject: Re: [paho-dev] Paho MQTT Client for Ruby
Also,
please note that as it isn't an Eclipse Paho project,
using the paho name is misrepresenting itself to users.
That
isn't the best starting point to the conversation as
to whether the Paho project wants to adopt your
client.
On 6
February 2017 at 11:08, Nicholas Humfrey <njh@xxxxxxxxxx> wrote:
Dear
Yuichiro,
Congratulations on creating a very complete library
- as a big fan of ruby, it is good to see ruby has
first-class MQTT functionality. However I am
slightly disappointed that you created a new
library, rather than collaborating with me on
enhancing the existing ruby mqtt gem. But this seems
to be the way of open source.
Pierre did contact me before starting this work and
I suggested that it might be better to have a
dependency on the packet parser/serialising in the
mqtt gem, rather than copying/pasting it, so that it
would benefit from any upstream fixes.
I notice you credit me:
"Special thanks to Nicholas Humfrey for providing a
great help with the packet serializer/deserializer."
But given that it is nearly completely a copy/paste,
this slightly undervalues my contribution.
The, otherwise very liberal, MIT license states:
"The above copyright notice and this permission
notice shall be included in
all copies or substantial portions of the Software."
Please can you make sure that you include this
notice on the sections of code written by me.
Nicholas Humfrey
On 2017-02-06 03:46, 柴田有一郎
wrote:
Dear
all
My name is Yuichiro Shibata.
I am a project manager at Ruby Development, Inc.
In our company's project we needed to a Ruby
library implementing a
MQTT client.
A first version of the client is currently ready
for usage.
https://github.com/RubyDevInc/paho.mqtt.ruby
https://rubygems.org/gems/paho-mqtt
Regarding the features that the client should own,
we have been inspired by the design of the
multi-language paho library.
Among those features, the ruby client supports:
- MQTT v3.1
- MQTT v3.1.1
- Last Will Treatment
- Encryption through SSL/TLS
- Some persistence on messages
- Automatic reconnection
- Offline buffering
- Non-bloking and blocking API
As we noticed that the paho library do not have a
ruby version,
we suggest to you the one that we developed.
We tried to make a fairly complete API but any
comment or fixing is welcomed.
Your sincerely,
Yuichiro Shibata
_______________________________________________
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
_______________________________________________
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
--
※本社が移転いたしました。
※メールアドレスが変わりました。
┏◇───────────────────
┌─╂ 柴田 有一郎(Shibata Yuichiro)
■━┛
│ 株式会社Ruby開発
│ 〒103-0001
│ 東京都中央区日本橋小伝馬町2-4 三報ビル9F
│ 電話(直通) :03-3527-3962
│ 携帯電話 :080-3551-3960
│ 電話(代表) :03-3527-3960
│ FAX :03-3527-3961
│ E-mail :y-shibata@xxxxxxxxxxx
□─────────────────────
_______________________________________________
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
--
Ian Craggs
icraggs@xxxxxxxxxx IBM United Kingdom
Eclipse Paho Project Lead; Committer on Eclipse Mosquitto;
Tech Lead in IBM Watson IoT Platform
_______________________________________________
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
--
※本社が移転いたしました。
※メールアドレスが変わりました。
┏◇───────────────────
┌─╂ 柴田 有一郎(Shibata Yuichiro)
■━┛
│ 株式会社Ruby開発
│ 〒103-0001
│ 東京都中央区日本橋小伝馬町2-4 三報ビル9F
│ 電話(直通) :03-3527-3962
│ 携帯電話 :080-3551-3960
│ 電話(代表) :03-3527-3960
│ FAX :03-3527-3961
│ E-mail :y-shibata@xxxxxxxxxxx
□─────────────────────
|