Thanks for the info, Robbie. I've signed and submitted the ICLA and have 
created the JIRA issue. I'm assuming that there needs to be explicit approval 
to send the pull request, currently waiting for any comments on the issue 
(QPIDJMS-121).

Thank you.
-Andrew

-----Original Message-----
From: Robbie Gemmell [mailto:[email protected]] 
Sent: Wednesday, October 7, 2015 3:05 AM
To: [email protected]
Subject: Re: Contribution question

On 6 October 2015 at 22:40, Andrew Buckley <[email protected]> wrote:

> Hello,
>
>
>
> I’m a software engineer in Azure IoT over here at Microsoft ( 
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithu
> b.com%2fAzure%2fazure-iot-sdks&data=01%7c01%7candbuc%40microsoft.com%7
> c25afb53989e54f4f5e9708d2cefecd43%7c72f988bf86f141af91ab2d7cd011db47%7
> c1&sdata=wdbXzrxREQIrJESsCtMxxpR5QexHdpEjh0UOFDEioQg%3d). Our team 
> creates open source SDKs (both device and service SDKs) for multiple 
> languages to both enable connectivity between IoT devices and the 
> Azure IoT Hub, as well as manage Azure IoT Hub service instances. We 
> have made some modifications to Qpid JMS to enable some extra AMQP 
> acknowledgement handling. Currently this work lives in a fork and we’re at 
> the point where we would like to publish our Java SDK to maven central so 
> we’d like to inquire about contributing this work back into the Qpid JMS 
> project.
>
>
>
> Thank you,
>
> --
>
> Andrew Buckley
>
> Software Engineer
> Microsoft
> Azure Iot
>
> Office: 109/3133
>
> [email protected]
>
> [image: Twitter] 
> <https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2ftwitter.com%2fMicrosoft&data=01%7c01%7candbuc%40microsoft.com%7c25afb53989e54f4f5e9708d2cefecd43%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=G%2fzNBmCWArk8b9Pi3yi6E0GdkGtCuNCS%2bhfT5G0rmoU%3d>
>     [image: Facebook]
> <https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fwww.facebook.com%2fMicrosoft&data=01%7c01%7candbuc%40microsoft.com%7c25afb53989e54f4f5e9708d2cefecd43%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=b8QW4YAFUxn822kIc%2f2rP9WoC9APmZHPowepyh3ud4w%3d>
>     [image: Linkedin]
> <https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fwww.linkedin.com%2fcompany%2fmicrosoft&data=01%7c01%7candbuc%40microsoft.com%7c25afb53989e54f4f5e9708d2cefecd43%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=W2EYBCYIgr%2bnCSZUkQ6jIJC3RsQPzEp9Fw315ocTI14%3d>
>     [image: Youtube]
> <https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fwww.
> youtube.com%2fuser%2fMicrosoft&data=01%7c01%7candbuc%40microsoft.com%7
> c25afb53989e54f4f5e9708d2cefecd43%7c72f988bf86f141af91ab2d7cd011db47%7
> c1&sdata=FV%2b2Jr6nYst5pnANngby47jjZc8jkf2pSP%2bB6a8p220%3d>
>
> [image: Microsoft Logo]
>
>
>

Hi Andrew,

Discussing on the mailing lists 
(https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fqpid.apache.org%2fdiscussion.html&data=01%7c01%7candbuc%40microsoft.com%7c25afb53989e54f4f5e9708d2cefecd43%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=aYwAzX2v8m%2bsPz4zJOAqUQDEHa5JTmD1yciy%2bZsEBhI%3d)
 or opening a JIRA issues 
(https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissues.apache.org%2fjira%2fbrowse%2fQPIDJMS&data=01%7c01%7candbuc%40microsoft.com%7c25afb53989e54f4f5e9708d2cefecd43%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=N0wO1WoqrnTi%2bpZK6CXvZ0sbuPJ1%2bD35T4SZZCOXHBU%3d
 in this case) is a good start for any proposed contributions, either of which 
will allow elaboration and further discussion of the changes if needed.

Once there is something to contribute it can either be attached in patch form 
on the JIRA, or a Pull Request opened against the GitHub mirror ( 
https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithub.com%2fapache%2fqpid-jms&data=01%7c01%7candbuc%40microsoft.com%7c25afb53989e54f4f5e9708d2cefecd43%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=KISSECIkCjFWNVeqfSGmP%2bTiuurnTSDa7xDcMPOuJXk%3d
 in this case). If doing the latter, including the JIRA key (QPIDJMS-<number>) 
at the start of the PR title will enable many of the PR updates to be relayed 
on the JIRA automatically.
Similarly, include the JIRA key at the start of the commit log messages so they 
can be automatically recorded against the JIRA once merged.

As Steve mentioned, it would be good to get an ICLA on file if you are planning 
to contribute. More details at 
https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fwww.apache.org%2flicenses%2f%23clas&data=01%7c01%7candbuc%40microsoft.com%7c25afb53989e54f4f5e9708d2cefecd43%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=sfjB8ZO6tTfLBgBOLcje5QfYhVNNqz2HP%2bvz1%2fVUQjw%3d
.

Robbie

Reply via email to