All,
This vote has ended with:
10 binding +1s
13 non-binding +1s
0 <= 0
The vote to establish Registry as a sub-project of the Apache NiFi TLP
has passed.
Thank you all for your participation in this important vote. I will
submit the necessary information to infra to get the ball rolling
@joey, if I understand correctly, this will be an external and optional
resource and so will have it's own separate project and build that's not
necessary for most users getting started with NiFi.
On Mon, Feb 13, 2017 at 9:25 AM, iCloud wrote:
> +1 (non-binding)
>
> But
+1 (non-binding)
But want to add that we now have the (small) burden of making sure the
developer docs, etc. are crystal clear on how all the sub-projects and repos
fit together. More sub-projects and repos means harder for new people to get
started and understand. Let’s not lose the
+1 (binding)
On Feb 12, 2017 10:17 PM, "Jeff" wrote:
> +1 (non-binding)
>
> On Fri, Feb 10, 2017 at 10:43 PM Brandon DeVries wrote:
>
> > +1 binding
> > On Fri, Feb 10, 2017 at 6:36 PM Andre wrote:
> >
> > > +1 binding
> > >
> > > On Sat,
+1 (non-binding)
On Fri, Feb 10, 2017 at 10:43 PM Brandon DeVries wrote:
> +1 binding
> On Fri, Feb 10, 2017 at 6:36 PM Andre wrote:
>
> > +1 binding
> >
> > On Sat, Feb 11, 2017 at 3:40 AM, Bryan Bende wrote:
> >
> > > All,
> > >
> > >
+1 binding
On Fri, Feb 10, 2017 at 6:36 PM Andre wrote:
> +1 binding
>
> On Sat, Feb 11, 2017 at 3:40 AM, Bryan Bende wrote:
>
> > All,
> >
> > Following a solid discussion for the past few days [1] regarding the
> > establishment of Registry as a
+1 binding
On Sat, Feb 11, 2017 at 3:40 AM, Bryan Bende wrote:
> All,
>
> Following a solid discussion for the past few days [1] regarding the
> establishment of Registry as a sub-project of Apache NiFi, I'd like to
> call a formal vote to record this important community
oe Skora <jsk...@gmail.com> wrote:
> >>
> >> +1 binding
> >>
> >> On Fri, Feb 10, 2017 at 2:09 PM, Peter Wicks (pwicks) <
> pwi...@micron.com>
> >> wrote:
> >>
> >>> +1 (non-binding)
> >>>
> >>>
;> -Original Message-
>>> From: Bryan Bende [mailto:bbe...@gmail.com]
>>> Sent: Friday, February 10, 2017 9:41 AM
>>> To: dev@nifi.apache.org
>>> Subject: [VOTE] Establish Registry, a sub-project of Apache NiFi
>>>
>>> All,
>>&g
ter Wicks (pwicks) <pwi...@micron.com>
> wrote:
>
>> +1 (non-binding)
>>
>> -Original Message-
>> From: Bryan Bende [mailto:bbe...@gmail.com]
>> Sent: Friday, February 10, 2017 9:41 AM
>> To: dev@nifi.apache.org
>> Subject: [VOTE] Est
ginal Message-
>> From: Bryan Bende [mailto:bbe...@gmail.com]
>> Sent: Friday, February 10, 2017 9:41 AM
>> To: dev@nifi.apache.org
>> Subject: [VOTE] Establish Registry, a sub-project of Apache NiFi
>>
>> All,
>>
>> Following a solid discussion f
: [VOTE] Establish Registry, a sub-project of Apache NiFi
>
> All,
>
> Following a solid discussion for the past few days [1] regarding the
> establishment of Registry as a sub-project of Apache NiFi, I'd like to
> call a formal vote to record this important community deci
+1 (non-binding)
-Original Message-
From: Bryan Bende [mailto:bbe...@gmail.com]
Sent: Friday, February 10, 2017 9:41 AM
To: dev@nifi.apache.org
Subject: [VOTE] Establish Registry, a sub-project of Apache NiFi
All,
Following a solid discussion for the past few days [1] regarding
+1 (non-binding)
On Fri, Feb 10, 2017 at 11:40 AM, Bryan Bende wrote:
> All,
>
> Following a solid discussion for the past few days [1] regarding the
> establishment of Registry as a sub-project of Apache NiFi, I'd like to
> call a formal vote to record this important
+1 (non-binding)
On Fri, Feb 10, 2017 at 6:26 PM, Michael Moser wrote:
> It definitely sounds like careful consideration was given to the name.
>
> +1 (non-binding)
>
>
> On Fri, Feb 10, 2017 at 1:03 PM, Joe Percivall
> wrote:
>
> > Thanks for the
It definitely sounds like careful consideration was given to the name.
+1 (non-binding)
On Fri, Feb 10, 2017 at 1:03 PM, Joe Percivall
wrote:
> Thanks for the clarification Joe and Bryan, and we appear to be on the same
> page that "Apache NiFi Registry" is how it would
Thanks for the clarification Joe and Bryan, and we appear to be on the same
page that "Apache NiFi Registry" is how it would be referred to.
With that cleared up, I am a +1.
Joe
On Fri, Feb 10, 2017 at 1:01 PM, Pierre Villard wrote:
> +1 as well, that will be a
+1 as well, that will be a very important piece of the ecosystem and
looking forward its development!
2017-02-10 18:47 GMT+01:00 Joe Witt :
> The name 'registry' is insufficient but we're not creating 'Apache
> Registry'. We're creating a subproject of 'Apache NiFi' which is
The name 'registry' is insufficient but we're not creating 'Apache
Registry'. We're creating a subproject of 'Apache NiFi' which is a
TLP of the ASF. This subproject, just like 'MiNiFi' would properly be
referred to as 'Registry: a subproject of Apache NiFi' or 'Apache NiFi
Registry'. Apache
Well using MiNiFi as an example...
Website - "MiNiFi - A subproject of Apache NiFi"
Git - "nifi-minifi.git"
JIRA - "Apache NiFi MiNiFi"
For Registry I was thinking...
Website - "Registry - A subproject of Apache NiFi"
Git - "nifi-registry.git"
JIRA "Apache NiFi Registry"
So I didn't think
I 100% agree with Mike and was actually in the process of writing a very
similar response. Just having "Registry" as the name will mean the
trademark will be "Apache Registry" and I don't think that conveys the
specificity of the sub-project. I'd much prefer something like NiFi
Registry like the
I am in favor of the concept but the name made me pause. I did a Google
search of "apache registry" and found an existing Perl module called
Apache::Registry. Should I be worried about potential naming confusion?
-- Mike
On Fri, Feb 10, 2017 at 12:16 PM, Oleg Zhurakousky <
+1 non-binding. I like the separation and I see a lot of need for this in
the community.
On Fri, Feb 10, 2017 at 12:03 PM, Matt Burgess wrote:
> +1 binding
>
> On Fri, Feb 10, 2017 at 11:40 AM, Bryan Bende wrote:
> > All,
> >
> > Following a solid
+1 Here as well. We desperately need it.
> On Feb 10, 2017, at 12:11 PM, Jeremy Dyer wrote:
>
> +1 non-binding. I like the separation and I see a lot of need for this in
> the community.
>
> On Fri, Feb 10, 2017 at 12:03 PM, Matt Burgess wrote:
>
>>
+1 binding
On Fri, Feb 10, 2017 at 11:40 AM, Bryan Bende wrote:
> All,
>
> Following a solid discussion for the past few days [1] regarding the
> establishment of Registry as a sub-project of Apache NiFi, I'd like to
> call a formal vote to record this important community
+1 binding
On Fri, Feb 10, 2017 at 11:47 AM, Marc wrote:
> +1 non-binding -- but I think creating a sub project creates a demarcation
> point that separates responsibilities in a way that makes sense.
>
> On Fri, Feb 10, 2017 at 11:40 AM, Bryan Bende
+1 non-binding -- but I think creating a sub project creates a demarcation
point that separates responsibilities in a way that makes sense.
On Fri, Feb 10, 2017 at 11:40 AM, Bryan Bende wrote:
> All,
>
> Following a solid discussion for the past few days [1] regarding the
>
All,
Following a solid discussion for the past few days [1] regarding the
establishment of Registry as a sub-project of Apache NiFi, I'd like to
call a formal vote to record this important community decision and
establish consensus.
The scope of this project is to define APIs for interacting
28 matches
Mail list logo