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 sure that is technically enough of a reason to not move the
repos to git as the ActiveMQ project is an independent entity from those
downstream users.
Normally, a CLA (Contributor License Agreement) is determined at the time
of the contribution. It's usually only required for very large
contributions of original code. Since this may be an amalgamation of
third-party projects, it's unclear yet as to whether a CLA would be
required in this case.
On Wed, Feb 15, 2017 at 3:20 PM Clebert Suconic <clebert.suco...@gmail.com>
wrote:
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
<clebert.suco...@gmail.com> 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 have more experience on that.. they may provide
more information, but that's what I would do.. open the LEGAL JIRA.
On Wed, Feb 15, 2017 at 12:44 PM, Clebert Suconic
<clebert.suco...@gmail.com> wrote:
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 any issues.. but it would be nice to have you on board
with that discussion.
I really think we should convert the NMS as a github project. I have
seen more interest on projects around github these days. (TBH I don't
even remember how to use SVN, git by itself is another + on building
community).
On Wed, Feb 15, 2017 at 10:05 AM, Duane Pauls <duane.pa...@gmail.com>
wrote:
Thanks for the feedback.
On Tue, Feb 14, 2017 at 5:45 PM, Clebert Suconic <
clebert.suco...@gmail.com>
wrote:
On Tue, Feb 14, 2017 at 5:03 PM Jim Gomes <jgo...@apache.org> wrote:
As you point out, the licensing seems to be compatible, but maybe a
quick
review from Apache legal might be a good idea since the intent is to
re-integrate it into the NMS codebase as an official project.
Would you be able to explain how I'd do this (or refer me to some
instructions)?
The NMS code is in Subversion, and not in Git. Here is the
repository
URL:
https://svn.apache.org/repos/asf/activemq/activemq-dotnet/
Apache.NMS.AMQP/trunk
.
It does not need to be ported to Git in order to create a new AMQP
provider
implementation.
It would make it easier to contribute thought. PRs is a perfect way to
start with contributions.
From my point of view we wouldn't strictly require a conversion to git.
But I agree PR's would simplify reviews and contributions.
you could also include ActiveMQ Artemis to the list of brokers.
I agree it makes sense to add Artemis to the list of brokers.
Do you have an idea on how much effort it would take... do you
have
any ideas for the initial implementation already?
One of my colleagues, Chris Morgan has spent more time than I have at
this
stage scoping the effort. We think this will likely take a few months.
Cheers,
Duane
--
Clebert Suconic
--
Clebert Suconic
--
Clebert Suconic
--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/
