Hello Pierre,
thank you for your persistence through the process of
contributing the Ruby client to Eclipse Paho. This was one of
those complicated processes due to the number of contributors
involved. I, and others I know of, think this is worthwhile to
end up with components that consumers can use, safe in the
knowledge that the license terms are being adhered to, and for
commercial use.
Also, welcome Pierre as the first new committer for the Ruby
client! If there are any other people you would like to join you
as committers to support the Ruby client, then let us know, and we
can consider starting an election.
As a committer, you should get familiar with the Eclipse Project
Handbook -
http://www.eclipse.org/projects/handbook/
There is a lot of information - but we are here to help you.
Sections which are especially useful right now I think are:
Elections -
http://www.eclipse.org/projects/handbook/#elections (if another
committer should be brought on board)
Intellectual Property -
http://www.eclipse.org/projects/handbook/#ip (handling
contributions)
Releases - http://www.eclipse.org/projects/handbook/#release
Paho is a graduated project, so some of the processes (such as
IP) are slightly different from one still in incubation.
We've just had a release review for our (very soon) upcoming MQTT
V5 (https://projects.eclipse.org/projects/iot.paho) release,
1.4.0, so it's too late for the Ruby client to be included within
that. I plan to pencil in a release later in the year (could be
1.4.1 or 1.5) to include more MQTT V5 work and that would be a
good time for the first official release of the Ruby client within
Paho.
In the meantime, other components have made unofficial releases
before an official one, so I think that making the gems available
is fine. Do you have a planned version number?
All committers can update the website, it's a git repo at
ssh://git.eclipse.org/gitroot/www.eclipse.org/paho.git. If you
have any questions, or need help, please ask. We have had ideas
for improving the website, but haven't had time to implement them
yet, so don't feel like anything is set in stone (except the
headers/footers where we have Eclipse guidelines to follow).
FYI, I'm intending to restart regular Paho (video) calls in two
weeks time, so it will be easier for us all to have regular
communications.
Ian
On 02/07/2018 03:01, Pierre Goudet
wrote:
Could you tell me if there are any additional review or test
that should be done before making the ruby gems available
from the official webpage?
Best regards,
Pierre Goudet
_______________________________________________
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 & Mosquitto Committer