Re: [DISCUSS] Rework NMS.AMQP

2018-02-15 Thread Duane Pauls
Thanks for the feedback Tim. We're relatively new to the community so it's very much appreciated. We had planned to setup the 2017 project files to automatically pull in the NMS and AmqpNetLite packages via NuGet. So there shouldn't be a need for those planning to build this project to build

Re: [DISCUSS] Rework NMS.AMQP

2018-02-15 Thread Timothy Bish
On 02/15/2018 11:57 AM, Duane Pauls wrote: In particular, I think we are wondering whether it would be considered feasible to work towards an initial release with the VS2017 project and solution files. This would require those who want to build it to either use VS2017 to build, or to use the

Re: [DISCUSS] Rework NMS.AMQP

2018-02-15 Thread Duane Pauls
In particular, I think we are wondering whether it would be considered feasible to work towards an initial release with the VS2017 project and solution files. This would require those who want to build it to either use VS2017 to build, or to use the dotnet sdk tool, as is described in the

Re: [DISCUSS] Rework NMS.AMQP

2018-02-14 Thread cmorgan
Hi everyone, Tim's post about not having a platform to run Visual Studio 2017 recently sparked a discussion between Duane, Ragnar and I about adding project and solution files for older versions of visual studio to the NMS AMQP Provider and were looking for guidance. Currently, the project only

Re: [DISCUSS] Rework NMS.AMQP

2018-02-01 Thread Timothy Bish
On 02/01/2018 03:08 PM, cmorgan wrote: I have updated the README.md file in the fork, see https://github.com/cjwmorgan-sol-sys/nms-amqp, for the project to show the features supported by the amqp provider. Let me know if there are any questions. I have also been working on adding SSL/TLS

Re: [DISCUSS] Rework NMS.AMQP

2018-02-01 Thread cmorgan
I have updated the README.md file in the fork, see https://github.com/cjwmorgan-sol-sys/nms-amqp, for the project to show the features supported by the amqp provider. Let me know if there are any questions. I have also been working on adding SSL/TLS configuration with client certificate

Re: [DISCUSS] Rework NMS.AMQP

2018-01-19 Thread Timothy Bish
On 01/19/2018 05:23 PM, cmorgan wrote: I have created Jira issue AMQNET-575, https://issues.apache.org/jira/browse/AMQNET-575, with a few sub tasks. I plan to add more when/if needed. Duane and are working on documenting features of the API NMS will be implemented. The current repo is not

Re: [DISCUSS] Rework NMS.AMQP

2018-01-19 Thread cmorgan
I have created Jira issue AMQNET-575, https://issues.apache.org/jira/browse/AMQNET-575, with a few sub tasks. I plan to add more when/if needed. Duane and are working on documenting features of the API NMS will be implemented. The current repo is not feature complete although it is close to

Re: [DISCUSS] Rework NMS.AMQP

2018-01-18 Thread Timothy Bish
On 01/17/2018 03:50 PM, cmorgan wrote: Hi Everyone, Happy New Year. I have a progress update about the NMS AMQP API Rework. The work done in the fork, https://github.com/cjwmorgan-sol-sys/nms-amqp, is close to being finished. Duane and I have also signed the ICLA. I will follow what Tim

Re: [DISCUSS] Rework NMS.AMQP

2018-01-17 Thread cmorgan
Hi Everyone, Happy New Year. I have a progress update about the NMS AMQP API Rework. The work done in the fork, https://github.com/cjwmorgan-sol-sys/nms-amqp, is close to being finished. Duane and I have also signed the ICLA. I will follow what Tim suggested by creating an NMS JIRA under the

Re: [DISCUSS] Rework NMS.AMQP

2017-03-15 Thread Timothy Bish
On 03/15/2017 11:31 AM, cmorgan wrote: Thanks Tim, I will transition my development work to the Apache repo. The project is currently unstable so, once it has become (at least more) stable I will begin the transition. Would a pull request through the github mirror be sufficient? Once you've

Re: [DISCUSS] Rework NMS.AMQP

2017-03-15 Thread cmorgan
Thanks Tim, I will transition my development work to the Apache repo. The project is currently unstable so, once it has become (at least more) stable I will begin the transition. Would a pull request through the github mirror be sufficient? tabish...@gmail.com wrote > I created a branch for

Re: [DISCUSS] Rework NMS.AMQP

2017-03-13 Thread Timothy Bish
I created a branch for the previous work and named it deprecated-impl (for want of a better name) and pushed it upstream. Should be clear now to start on any new development of this client as folks see fit. On 02/14/2017 02:32 PM, Duane Pauls wrote: Hello, I'm relatively new to the ActiveMQ

Re: [DISCUSS] Rework NMS.AMQP

2017-03-13 Thread Timothy Bish
Just to close the loop here, the AMQP NMS client repo is now migrated to Git and mirrored on Github here: https://github.com/apache/activemq-nms-amqp We should probably create a branch of the old client work before pushing any rework PRs in, I'll take care of that a bit later today. On

Re: [DISCUSS] Rework NMS.AMQP

2017-02-28 Thread Clebert Suconic
that's probably a question for Legal. I would think you need both... I am not a lawyer.. but usually employees will have a contract with the company you were hired from. So if you are doing this during your day job you probably need a corporate agreement to release any of the company's IP as an

Re: [DISCUSS] Rework NMS.AMQP

2017-02-28 Thread Duane Pauls
On Tue, Feb 21, 2017 at 5:30 PM, Clebert Suconic wrote: > > I think u still need to fill a contributors agreement Does anyone know if there is a practical difference between the individual CLA and the corporate CLA? Or do they both accomplish the same goal equally?

Re: [DISCUSS] Rework NMS.AMQP

2017-02-21 Thread Clebert Suconic
I think u still need to fill a contributors agreement PR is a good way to start. But since your PRs will be likely substantial I would recommend the agreement filled from the guys involved. Someone with more legal background can probably help with additional information. On Tue, Feb 21, 2017

Re: [DISCUSS] Rework NMS.AMQP

2017-02-21 Thread Duane Pauls
In parallel with getting this proposal ready, we went ahead and created a github repo to get started: https://github.com/SolaceLabs/nms-amqp It's basically empty, but work has just kicked off in a fork: https://github.com/cjwmorgan-sol-sys/nms-amqp/ As this proposal would indicate, our intent is

Re: [DISCUSS] Rework NMS.AMQP

2017-02-20 Thread Chuck Rolke
- Original Message - > From: "Robbie Gemmell" <robbie.gemm...@gmail.com> > To: dev@activemq.apache.org > Sent: Thursday, February 16, 2017 10:18:22 AM > Subject: Re: [DISCUSS] Rework NMS.AMQP > > On 14 February 2017 at 19:32, Duane Pauls <du

Re: [DISCUSS] Rework NMS.AMQP

2017-02-18 Thread John D. Ament
On Sat, Feb 18, 2017 at 9:30 AM Jim Gomes wrote: > I would prefer if this can also be built on Linux, and not just be a > Windows only solution. Having Visual Studio do a NuGet dependency seems > like it will require Visual Studio and only work on Windows. > > Does NuGet work

Re: [DISCUSS] Rework NMS.AMQP

2017-02-18 Thread John D. Ament
On Sat, Feb 18, 2017 at 9:10 AM Duane Pauls wrote: > On Feb 17, 2017 10:26 PM, "John D. Ament" wrote: > > > I'm just wondering, AMQPNETLITE is published on nuget. Does NMS need to > import the source code from it, or can you rely on the nuget

Re: [DISCUSS] Rework NMS.AMQP

2017-02-18 Thread Jim Gomes
I would prefer if this can also be built on Linux, and not just be a Windows only solution. Having Visual Studio do a NuGet dependency seems like it will require Visual Studio and only work on Windows. Does NuGet work without Visual Studio? On Sat, Feb 18, 2017, 6:10 AM Duane Pauls

Re: [DISCUSS] Rework NMS.AMQP

2017-02-18 Thread Duane Pauls
On Feb 17, 2017 10:26 PM, "John D. Ament" wrote: I'm just wondering, AMQPNETLITE is published on nuget. Does NMS need to import the source code from it, or can you rely on the nuget dependency? Right, Chris could confirm, but I think he is going to be creating an MS

Re: [DISCUSS] Rework NMS.AMQP

2017-02-17 Thread Clebert Suconic
On Fri, Feb 17, 2017 at 11:42 PM Clebert Suconic wrote: > I believe it will be just like the blog I posted. It's really not required > to redistribute. > For reference https://blogs.apache.org/activemq/entry/using-net-libraries-with-activemq > > > On Fri, Feb

Re: [DISCUSS] Rework NMS.AMQP

2017-02-17 Thread Clebert Suconic
I believe it will be just like the blog I posted. It's really not required to redistribute. On Fri, Feb 17, 2017 at 10:26 PM John D. Ament wrote: > Hey, > > So I saw the legal question, but only briefly looked at this thread (have > never had to deal with messaging with

Re: [DISCUSS] Rework NMS.AMQP

2017-02-17 Thread John D. Ament
Hey, So I saw the legal question, but only briefly looked at this thread (have never had to deal with messaging with .NET apps yet..) I'm just wondering, AMQPNETLITE is published on nuget. Does NMS need to import the source code from it, or can you rely on the nuget dependency? John On Fri,

Re: [DISCUSS] Rework NMS.AMQP

2017-02-17 Thread cmorgan
Hello, I'll be working with Duane on the API rework. clebertsuconic wrote > This is actually the list you should follow up with the question: > > http://www.apache.org/foundation/mailinglists.html#foundation-legal > > > but I think just the JIRA should be enough. > > > Other guys here will

Re: [DISCUSS] Rework NMS.AMQP

2017-02-16 Thread Robbie Gemmell
On 14 February 2017 at 19:32, Duane Pauls wrote: > Hello, > > I'm relatively new to the ActiveMQ community, but I've been watching this > list for the last little while and would like to propose some rework to the > NMS.AMQP API. > > I'm interested in any feedback you folks

Re: [DISCUSS] Rework NMS.AMQP

2017-02-15 Thread Timothy Bish
On 02/15/2017 06:26 PM, Jim Gomes wrote: Yes, I would object. It's not a simple thing as there are many downstream dependencies on the Subversion repository. Although, anyone is free to use Git as their own front-end to a Subversion repository if they prefer working with Git toolset. I'm not

Re: [DISCUSS] Rework NMS.AMQP

2017-02-15 Thread Timothy Bish
On 02/15/2017 06:19 PM, Clebert Suconic wrote: would anyone object if I open a request on Infra to convert it to git? This would require a separate discussion thread to gain consensus on the conversion. While I'd wholeheartedly agree that they should move to git as they are the only

Re: [DISCUSS] Rework NMS.AMQP

2017-02-15 Thread Jim Gomes
Yes, I would object. It's not a simple thing as there are many downstream dependencies on the Subversion repository. Although, anyone is free to use Git as their own front-end to a Subversion repository if they prefer working with Git toolset. Normally, a CLA (Contributor License Agreement) is

Re: [DISCUSS] Rework NMS.AMQP

2017-02-15 Thread Clebert Suconic
would anyone object if I open a request on Infra to convert it to git? Also: since Duane will start as a contributor, and it is expected to send a considerable amount of contributions, should him sign up the contributors agreement? On Wed, Feb 15, 2017 at 12:48 PM, Clebert Suconic

Re: [DISCUSS] Rework NMS.AMQP

2017-02-15 Thread Clebert Suconic
This is actually the list you should follow up with the question: http://www.apache.org/foundation/mailinglists.html#foundation-legal but I think just the JIRA should be enough. Other guys here will have more experience on that.. they may provide more information, but that's what I would do..

Re: [DISCUSS] Rework NMS.AMQP

2017-02-15 Thread Clebert Suconic
of course I mistyped git as github on my previous message. apache git projects are mirrored on github, but the main repo is always the apache one. Just as a reference to make sure my typo won't confuse you. On Wed, Feb 15, 2017 at 12:44 PM, Clebert Suconic wrote: >

Re: [DISCUSS] Rework NMS.AMQP

2017-02-15 Thread Clebert Suconic
how I would do regarding legal: i would create a JIRA on https://issues.apache.org/jira/browse/LEGAL And I would follow up with a [DISCUSS] thread on the dev list, referencing the JIRA. Pointing out the dependency you will include, the license and the source of the project. I don't foresee

Re: [DISCUSS] Rework NMS.AMQP

2017-02-15 Thread Duane Pauls
Thanks for the feedback. On Tue, Feb 14, 2017 at 5:45 PM, Clebert Suconic wrote: > On Tue, Feb 14, 2017 at 5:03 PM Jim Gomes wrote: > > As you point out, the licensing seems to be compatible, but maybe a quick > > review from Apache legal might be

Re: [DISCUSS] Rework NMS.AMQP

2017-02-14 Thread Clebert Suconic
On Tue, Feb 14, 2017 at 5:03 PM Jim Gomes wrote: > Hi Duane, > > Thank you very much for this proposal. I think it sounds great. The > current NMS.AMQP is just a wrapper around another library. If we could > have a full native implementation of the NMS API using AMQP, that

Re: [DISCUSS] Rework NMS.AMQP

2017-02-14 Thread Jim Gomes
Hi Duane, Thank you very much for this proposal. I think it sounds great. The current NMS.AMQP is just a wrapper around another library. If we could have a full native implementation of the NMS API using AMQP, that would be much better. As you point out, the licensing seems to be compatible,

Re: [DISCUSS] Rework NMS.AMQP

2017-02-14 Thread Clebert Suconic
wow.. IMHO it sounds an awesome idea... you could also include ActiveMQ Artemis to the list of brokers. I have been doing some work around AMQP on Artemis, and I also wrote a blog on how to use the AMQP lite: https://blogs.apache.org/activemq/entry/using-net-libraries-with-activemq Using the

[DISCUSS] Rework NMS.AMQP

2017-02-14 Thread Duane Pauls
Hello, I'm relatively new to the ActiveMQ community, but I've been watching this list for the last little while and would like to propose some rework to the NMS.AMQP API. I'm interested in any feedback you folks may have. Thanks in advance! NMS.AMQP REWORK PROPOSAL Abstract A pure .NET