You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nifi.apache.org by Bryan Bende <bb...@gmail.com> on 2017/02/10 16:40:33 UTC
[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 decision and
establish consensus.
The scope of this project is to define APIs for interacting with
resources that one or more NiFi instances may be interested in, such
as a flow registry for versioned flows, an extension registry for
extensions, and possibly other configuration resources in the future.
In addition, this project will provide reference implementations of
these registries, with the goal of allowing the community to build a
diverse set of implementations, such as a Git provider for versioned
flows, or a bintray provider for an extension registry.
I am a +1 and looking forward to the future work in this area.
The vote will be open for 72 hours and be a majority rule vote.
[ ] +1 Establish Registry, a subproject of Apache NiFi
[ ] 0 Do not care
[ ] -1 Do not establish Registry, a subproject of Apache NiFi
Thanks,
Bryan
[1] http://mail-archives.apache.org/mod_mbox/nifi-dev/201702.mbox/%3CCALo_M19euo2LLy0PVWmE70FzeLhQRcCtX6TC%3DqoiBVfn4zFQMA%40mail.gmail.com%3E
Re: [VOTE] Establish Registry, a sub-project of Apache NiFi
Posted by Joe Skora <js...@gmail.com>.
@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 <jo...@icloud.com> wrote:
> +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 simplicity of the build
> and install.
>
> On Feb 13, 2017, 6:04 AM -0600, Tony Kurc <tr...@gmail.com>, wrote:
> > +1 (binding)
> >
> > On Feb 12, 2017 10:17 PM, "Jeff" <jt...@gmail.com> wrote:
> >
> > > +1 (non-binding)
> > >
> > > On Fri, Feb 10, 2017 at 10:43 PM Brandon DeVries <br...@jhu.edu> wrote:
> > >
> > > > +1 binding
> > > > On Fri, Feb 10, 2017 at 6:36 PM Andre <an...@fucs.org> wrote:
> > > >
> > > > > +1 binding
> > > > >
> > > > > On Sat, Feb 11, 2017 at 3:40 AM, Bryan Bende <bb...@gmail.com>
> 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 decision
> and
> > > > > > establish consensus.
> > > > > >
> > > > > > The scope of this project is to define APIs for interacting with
> > > > > > resources that one or more NiFi instances may be interested in,
> such
> > > > > > as a flow registry for versioned flows, an extension registry for
> > > > > > extensions, and possibly other configuration resources in the
> future.
> > > > > > In addition, this project will provide reference implementations
> of
> > > > > > these registries, with the goal of allowing the community to
> build a
> > > > > > diverse set of implementations, such as a Git provider for
> versioned
> > > > > > flows, or a bintray provider for an extension registry.
> > > > > >
> > > > > > I am a +1 and looking forward to the future work in this area.
> > > > > >
> > > > > > The vote will be open for 72 hours and be a majority rule vote.
> > > > > >
> > > > > > [ ] +1 Establish Registry, a subproject of Apache NiFi
> > > > > > [ ] 0 Do not care
> > > > > > [ ] -1 Do not establish Registry, a subproject of Apache NiFi
> > > > > >
> > > > > > Thanks,
> > > > > >
> > > > > > Bryan
> > > > > >
> > > > > > [1]
> > > > > http://mail-archives.apache.org/mod_mbox/nifi-dev/201702.
> mbox/%3CCALo_
> > > > > > M19euo2LLy0PVWmE70FzeLhQRcCtX6TC%3DqoiBVfn4zFQMA%40mail.
> gmail.com%3E
> > > > > >
> > > > >
> > > >
> > >
>
Re: [VOTE] Establish Registry, a sub-project of Apache NiFi
Posted by iCloud <jo...@icloud.com>.
+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 simplicity of the build and install.
On Feb 13, 2017, 6:04 AM -0600, Tony Kurc <tr...@gmail.com>, wrote:
> +1 (binding)
>
> On Feb 12, 2017 10:17 PM, "Jeff" <jt...@gmail.com> wrote:
>
> > +1 (non-binding)
> >
> > On Fri, Feb 10, 2017 at 10:43 PM Brandon DeVries <br...@jhu.edu> wrote:
> >
> > > +1 binding
> > > On Fri, Feb 10, 2017 at 6:36 PM Andre <an...@fucs.org> wrote:
> > >
> > > > +1 binding
> > > >
> > > > On Sat, Feb 11, 2017 at 3:40 AM, Bryan Bende <bb...@gmail.com> 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 decision and
> > > > > establish consensus.
> > > > >
> > > > > The scope of this project is to define APIs for interacting with
> > > > > resources that one or more NiFi instances may be interested in, such
> > > > > as a flow registry for versioned flows, an extension registry for
> > > > > extensions, and possibly other configuration resources in the future.
> > > > > In addition, this project will provide reference implementations of
> > > > > these registries, with the goal of allowing the community to build a
> > > > > diverse set of implementations, such as a Git provider for versioned
> > > > > flows, or a bintray provider for an extension registry.
> > > > >
> > > > > I am a +1 and looking forward to the future work in this area.
> > > > >
> > > > > The vote will be open for 72 hours and be a majority rule vote.
> > > > >
> > > > > [ ] +1 Establish Registry, a subproject of Apache NiFi
> > > > > [ ] 0 Do not care
> > > > > [ ] -1 Do not establish Registry, a subproject of Apache NiFi
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Bryan
> > > > >
> > > > > [1]
> > > > http://mail-archives.apache.org/mod_mbox/nifi-dev/201702.mbox/%3CCALo_
> > > > > M19euo2LLy0PVWmE70FzeLhQRcCtX6TC%3DqoiBVfn4zFQMA%40mail.gmail.com%3E
> > > > >
> > > >
> > >
> >
Re: [VOTE] Establish Registry, a sub-project of Apache NiFi
Posted by Tony Kurc <tr...@gmail.com>.
+1 (binding)
On Feb 12, 2017 10:17 PM, "Jeff" <jt...@gmail.com> wrote:
> +1 (non-binding)
>
> On Fri, Feb 10, 2017 at 10:43 PM Brandon DeVries <br...@jhu.edu> wrote:
>
> > +1 binding
> > On Fri, Feb 10, 2017 at 6:36 PM Andre <an...@fucs.org> wrote:
> >
> > > +1 binding
> > >
> > > On Sat, Feb 11, 2017 at 3:40 AM, Bryan Bende <bb...@gmail.com> 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 decision and
> > > > establish consensus.
> > > >
> > > > The scope of this project is to define APIs for interacting with
> > > > resources that one or more NiFi instances may be interested in, such
> > > > as a flow registry for versioned flows, an extension registry for
> > > > extensions, and possibly other configuration resources in the future.
> > > > In addition, this project will provide reference implementations of
> > > > these registries, with the goal of allowing the community to build a
> > > > diverse set of implementations, such as a Git provider for versioned
> > > > flows, or a bintray provider for an extension registry.
> > > >
> > > > I am a +1 and looking forward to the future work in this area.
> > > >
> > > > The vote will be open for 72 hours and be a majority rule vote.
> > > >
> > > > [ ] +1 Establish Registry, a subproject of Apache NiFi
> > > > [ ] 0 Do not care
> > > > [ ] -1 Do not establish Registry, a subproject of Apache NiFi
> > > >
> > > > Thanks,
> > > >
> > > > Bryan
> > > >
> > > > [1]
> > > http://mail-archives.apache.org/mod_mbox/nifi-dev/201702.mbox/%3CCALo_
> > > > M19euo2LLy0PVWmE70FzeLhQRcCtX6TC%3DqoiBVfn4zFQMA%40mail.gmail.com%3E
> > > >
> > >
> >
>
Re: [VOTE] Establish Registry, a sub-project of Apache NiFi
Posted by Jeff <jt...@gmail.com>.
+1 (non-binding)
On Fri, Feb 10, 2017 at 10:43 PM Brandon DeVries <br...@jhu.edu> wrote:
> +1 binding
> On Fri, Feb 10, 2017 at 6:36 PM Andre <an...@fucs.org> wrote:
>
> > +1 binding
> >
> > On Sat, Feb 11, 2017 at 3:40 AM, Bryan Bende <bb...@gmail.com> 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 decision and
> > > establish consensus.
> > >
> > > The scope of this project is to define APIs for interacting with
> > > resources that one or more NiFi instances may be interested in, such
> > > as a flow registry for versioned flows, an extension registry for
> > > extensions, and possibly other configuration resources in the future.
> > > In addition, this project will provide reference implementations of
> > > these registries, with the goal of allowing the community to build a
> > > diverse set of implementations, such as a Git provider for versioned
> > > flows, or a bintray provider for an extension registry.
> > >
> > > I am a +1 and looking forward to the future work in this area.
> > >
> > > The vote will be open for 72 hours and be a majority rule vote.
> > >
> > > [ ] +1 Establish Registry, a subproject of Apache NiFi
> > > [ ] 0 Do not care
> > > [ ] -1 Do not establish Registry, a subproject of Apache NiFi
> > >
> > > Thanks,
> > >
> > > Bryan
> > >
> > > [1]
> > http://mail-archives.apache.org/mod_mbox/nifi-dev/201702.mbox/%3CCALo_
> > > M19euo2LLy0PVWmE70FzeLhQRcCtX6TC%3DqoiBVfn4zFQMA%40mail.gmail.com%3E
> > >
> >
>
Re: [VOTE] Establish Registry, a sub-project of Apache NiFi
Posted by Brandon DeVries <br...@jhu.edu>.
+1 binding
On Fri, Feb 10, 2017 at 6:36 PM Andre <an...@fucs.org> wrote:
> +1 binding
>
> On Sat, Feb 11, 2017 at 3:40 AM, Bryan Bende <bb...@gmail.com> 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 decision and
> > establish consensus.
> >
> > The scope of this project is to define APIs for interacting with
> > resources that one or more NiFi instances may be interested in, such
> > as a flow registry for versioned flows, an extension registry for
> > extensions, and possibly other configuration resources in the future.
> > In addition, this project will provide reference implementations of
> > these registries, with the goal of allowing the community to build a
> > diverse set of implementations, such as a Git provider for versioned
> > flows, or a bintray provider for an extension registry.
> >
> > I am a +1 and looking forward to the future work in this area.
> >
> > The vote will be open for 72 hours and be a majority rule vote.
> >
> > [ ] +1 Establish Registry, a subproject of Apache NiFi
> > [ ] 0 Do not care
> > [ ] -1 Do not establish Registry, a subproject of Apache NiFi
> >
> > Thanks,
> >
> > Bryan
> >
> > [1]
> http://mail-archives.apache.org/mod_mbox/nifi-dev/201702.mbox/%3CCALo_
> > M19euo2LLy0PVWmE70FzeLhQRcCtX6TC%3DqoiBVfn4zFQMA%40mail.gmail.com%3E
> >
>
Re: [VOTE] Establish Registry, a sub-project of Apache NiFi
Posted by Andre <an...@fucs.org>.
+1 binding
On Sat, Feb 11, 2017 at 3:40 AM, Bryan Bende <bb...@gmail.com> 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 decision and
> establish consensus.
>
> The scope of this project is to define APIs for interacting with
> resources that one or more NiFi instances may be interested in, such
> as a flow registry for versioned flows, an extension registry for
> extensions, and possibly other configuration resources in the future.
> In addition, this project will provide reference implementations of
> these registries, with the goal of allowing the community to build a
> diverse set of implementations, such as a Git provider for versioned
> flows, or a bintray provider for an extension registry.
>
> I am a +1 and looking forward to the future work in this area.
>
> The vote will be open for 72 hours and be a majority rule vote.
>
> [ ] +1 Establish Registry, a subproject of Apache NiFi
> [ ] 0 Do not care
> [ ] -1 Do not establish Registry, a subproject of Apache NiFi
>
> Thanks,
>
> Bryan
>
> [1] http://mail-archives.apache.org/mod_mbox/nifi-dev/201702.mbox/%3CCALo_
> M19euo2LLy0PVWmE70FzeLhQRcCtX6TC%3DqoiBVfn4zFQMA%40mail.gmail.com%3E
>
Re: [VOTE] Establish Registry, a sub-project of Apache NiFi
Posted by Matt Gilman <ma...@gmail.com>.
+1 binding
On Fri, Feb 10, 2017 at 11:47 AM, Marc <ph...@apache.org> 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 <bb...@gmail.com> 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 decision and
> > establish consensus.
> >
> > The scope of this project is to define APIs for interacting with
> > resources that one or more NiFi instances may be interested in, such
> > as a flow registry for versioned flows, an extension registry for
> > extensions, and possibly other configuration resources in the future.
> > In addition, this project will provide reference implementations of
> > these registries, with the goal of allowing the community to build a
> > diverse set of implementations, such as a Git provider for versioned
> > flows, or a bintray provider for an extension registry.
> >
> > I am a +1 and looking forward to the future work in this area.
> >
> > The vote will be open for 72 hours and be a majority rule vote.
> >
> > [ ] +1 Establish Registry, a subproject of Apache NiFi
> > [ ] 0 Do not care
> > [ ] -1 Do not establish Registry, a subproject of Apache NiFi
> >
> > Thanks,
> >
> > Bryan
> >
> > [1] http://mail-archives.apache.org/mod_mbox/nifi-dev/201702.mbo
> > x/%3CCALo_M19euo2LLy0PVWmE70FzeLhQRcCtX6TC%3DqoiBVfn4zFQMA%4
> > 0mail.gmail.com%3E
> >
>
Re: [VOTE] Establish Registry, a sub-project of Apache NiFi
Posted by Marc <ph...@apache.org>.
+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 <bb...@gmail.com> 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 decision and
> establish consensus.
>
> The scope of this project is to define APIs for interacting with
> resources that one or more NiFi instances may be interested in, such
> as a flow registry for versioned flows, an extension registry for
> extensions, and possibly other configuration resources in the future.
> In addition, this project will provide reference implementations of
> these registries, with the goal of allowing the community to build a
> diverse set of implementations, such as a Git provider for versioned
> flows, or a bintray provider for an extension registry.
>
> I am a +1 and looking forward to the future work in this area.
>
> The vote will be open for 72 hours and be a majority rule vote.
>
> [ ] +1 Establish Registry, a subproject of Apache NiFi
> [ ] 0 Do not care
> [ ] -1 Do not establish Registry, a subproject of Apache NiFi
>
> Thanks,
>
> Bryan
>
> [1] http://mail-archives.apache.org/mod_mbox/nifi-dev/201702.mbo
> x/%3CCALo_M19euo2LLy0PVWmE70FzeLhQRcCtX6TC%3DqoiBVfn4zFQMA%4
> 0mail.gmail.com%3E
>
Re: [VOTE] Establish Registry, a sub-project of Apache NiFi
Posted by Andrew Psaltis <ps...@gmail.com>.
+1 non-binding This will be an awesome addition. Looking forward to
helping out.
On Fri, Feb 10, 2017 at 17:26 Uwe@Moosheimer.com <Uw...@moosheimer.com> wrote:
> +1 (non-binding)
>
> Uwe
>
> > Am 10.02.2017 um 22:18 schrieb Koji Kawamura <ij...@apache.org>:
> >
> > +1 (non-binding)
> >
> > On Feb 11, 2017 5:37 AM, "Jennifer Barnabee" <
> jennifer.barnabee@gmail.com>
> > wrote:
> >
> > +1 binding
> >
> > Sent from my iPhone
> >
> >> On Feb 10, 2017, at 2:55 PM, Joe Skora <js...@gmail.com> wrote:
> >>
> >> +1 binding
> >>
> >> On Fri, Feb 10, 2017 at 2:09 PM, Peter Wicks (pwicks) <
> pwicks@micron.com>
> >> wrote:
> >>
> >>> +1 (non-binding)
> >>>
> >>> -----Original Message-----
> >>> From: Bryan Bende [mailto:bbende@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 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 with
> >>> resources that one or more NiFi instances may be interested in, such
> >>> as a flow registry for versioned flows, an extension registry for
> >>> extensions, and possibly other configuration resources in the future.
> >>> In addition, this project will provide reference implementations of
> >>> these registries, with the goal of allowing the community to build a
> >>> diverse set of implementations, such as a Git provider for versioned
> >>> flows, or a bintray provider for an extension registry.
> >>>
> >>> I am a +1 and looking forward to the future work in this area.
> >>>
> >>> The vote will be open for 72 hours and be a majority rule vote.
> >>>
> >>> [ ] +1 Establish Registry, a subproject of Apache NiFi
> >>> [ ] 0 Do not care
> >>> [ ] -1 Do not establish Registry, a subproject of Apache NiFi
> >>>
> >>> Thanks,
> >>>
> >>> Bryan
> >>>
> >>> [1] http://mail-archives.apache.org/mod_mbox/nifi-dev/201702.
> > mbox/%3CCALo_
> >>> M19euo2LLy0PVWmE70FzeLhQRcCtX6TC%3DqoiBVfn4zFQMA%40mail.gmail.com%3E
> >>>
>
--
Thanks,
Andrew
Subscribe to my book: Streaming Data <http://manning.com/psaltis>
<https://www.linkedin.com/pub/andrew-psaltis/1/17b/306>
twiiter: @itmdata <http://twitter.com/intent/user?screen_name=itmdata>
Re: [VOTE] Establish Registry, a sub-project of Apache NiFi
Posted by "Uwe@Moosheimer.com" <Uw...@Moosheimer.com>.
+1 (non-binding)
Uwe
> Am 10.02.2017 um 22:18 schrieb Koji Kawamura <ij...@apache.org>:
>
> +1 (non-binding)
>
> On Feb 11, 2017 5:37 AM, "Jennifer Barnabee" <je...@gmail.com>
> wrote:
>
> +1 binding
>
> Sent from my iPhone
>
>> On Feb 10, 2017, at 2:55 PM, Joe Skora <js...@gmail.com> wrote:
>>
>> +1 binding
>>
>> On Fri, Feb 10, 2017 at 2:09 PM, Peter Wicks (pwicks) <pw...@micron.com>
>> wrote:
>>
>>> +1 (non-binding)
>>>
>>> -----Original Message-----
>>> From: Bryan Bende [mailto:bbende@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 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 with
>>> resources that one or more NiFi instances may be interested in, such
>>> as a flow registry for versioned flows, an extension registry for
>>> extensions, and possibly other configuration resources in the future.
>>> In addition, this project will provide reference implementations of
>>> these registries, with the goal of allowing the community to build a
>>> diverse set of implementations, such as a Git provider for versioned
>>> flows, or a bintray provider for an extension registry.
>>>
>>> I am a +1 and looking forward to the future work in this area.
>>>
>>> The vote will be open for 72 hours and be a majority rule vote.
>>>
>>> [ ] +1 Establish Registry, a subproject of Apache NiFi
>>> [ ] 0 Do not care
>>> [ ] -1 Do not establish Registry, a subproject of Apache NiFi
>>>
>>> Thanks,
>>>
>>> Bryan
>>>
>>> [1] http://mail-archives.apache.org/mod_mbox/nifi-dev/201702.
> mbox/%3CCALo_
>>> M19euo2LLy0PVWmE70FzeLhQRcCtX6TC%3DqoiBVfn4zFQMA%40mail.gmail.com%3E
>>>
Re: [VOTE] Establish Registry, a sub-project of Apache NiFi
Posted by Koji Kawamura <ij...@apache.org>.
+1 (non-binding)
On Feb 11, 2017 5:37 AM, "Jennifer Barnabee" <je...@gmail.com>
wrote:
+1 binding
Sent from my iPhone
> On Feb 10, 2017, at 2:55 PM, Joe Skora <js...@gmail.com> wrote:
>
> +1 binding
>
> On Fri, Feb 10, 2017 at 2:09 PM, Peter Wicks (pwicks) <pw...@micron.com>
> wrote:
>
>> +1 (non-binding)
>>
>> -----Original Message-----
>> From: Bryan Bende [mailto:bbende@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 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 with
>> resources that one or more NiFi instances may be interested in, such
>> as a flow registry for versioned flows, an extension registry for
>> extensions, and possibly other configuration resources in the future.
>> In addition, this project will provide reference implementations of
>> these registries, with the goal of allowing the community to build a
>> diverse set of implementations, such as a Git provider for versioned
>> flows, or a bintray provider for an extension registry.
>>
>> I am a +1 and looking forward to the future work in this area.
>>
>> The vote will be open for 72 hours and be a majority rule vote.
>>
>> [ ] +1 Establish Registry, a subproject of Apache NiFi
>> [ ] 0 Do not care
>> [ ] -1 Do not establish Registry, a subproject of Apache NiFi
>>
>> Thanks,
>>
>> Bryan
>>
>> [1] http://mail-archives.apache.org/mod_mbox/nifi-dev/201702.
mbox/%3CCALo_
>> M19euo2LLy0PVWmE70FzeLhQRcCtX6TC%3DqoiBVfn4zFQMA%40mail.gmail.com%3E
>>
Re: [VOTE] Establish Registry, a sub-project of Apache NiFi
Posted by Jennifer Barnabee <je...@gmail.com>.
+1 binding
Sent from my iPhone
> On Feb 10, 2017, at 2:55 PM, Joe Skora <js...@gmail.com> wrote:
>
> +1 binding
>
> On Fri, Feb 10, 2017 at 2:09 PM, Peter Wicks (pwicks) <pw...@micron.com>
> wrote:
>
>> +1 (non-binding)
>>
>> -----Original Message-----
>> From: Bryan Bende [mailto:bbende@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 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 with
>> resources that one or more NiFi instances may be interested in, such
>> as a flow registry for versioned flows, an extension registry for
>> extensions, and possibly other configuration resources in the future.
>> In addition, this project will provide reference implementations of
>> these registries, with the goal of allowing the community to build a
>> diverse set of implementations, such as a Git provider for versioned
>> flows, or a bintray provider for an extension registry.
>>
>> I am a +1 and looking forward to the future work in this area.
>>
>> The vote will be open for 72 hours and be a majority rule vote.
>>
>> [ ] +1 Establish Registry, a subproject of Apache NiFi
>> [ ] 0 Do not care
>> [ ] -1 Do not establish Registry, a subproject of Apache NiFi
>>
>> Thanks,
>>
>> Bryan
>>
>> [1] http://mail-archives.apache.org/mod_mbox/nifi-dev/201702.mbox/%3CCALo_
>> M19euo2LLy0PVWmE70FzeLhQRcCtX6TC%3DqoiBVfn4zFQMA%40mail.gmail.com%3E
>>
Re: [VOTE] Establish Registry, a sub-project of Apache NiFi
Posted by Joe Skora <js...@gmail.com>.
+1 binding
On Fri, Feb 10, 2017 at 2:09 PM, Peter Wicks (pwicks) <pw...@micron.com>
wrote:
> +1 (non-binding)
>
> -----Original Message-----
> From: Bryan Bende [mailto:bbende@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 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 with
> resources that one or more NiFi instances may be interested in, such
> as a flow registry for versioned flows, an extension registry for
> extensions, and possibly other configuration resources in the future.
> In addition, this project will provide reference implementations of
> these registries, with the goal of allowing the community to build a
> diverse set of implementations, such as a Git provider for versioned
> flows, or a bintray provider for an extension registry.
>
> I am a +1 and looking forward to the future work in this area.
>
> The vote will be open for 72 hours and be a majority rule vote.
>
> [ ] +1 Establish Registry, a subproject of Apache NiFi
> [ ] 0 Do not care
> [ ] -1 Do not establish Registry, a subproject of Apache NiFi
>
> Thanks,
>
> Bryan
>
> [1] http://mail-archives.apache.org/mod_mbox/nifi-dev/201702.mbox/%3CCALo_
> M19euo2LLy0PVWmE70FzeLhQRcCtX6TC%3DqoiBVfn4zFQMA%40mail.gmail.com%3E
>
RE: [VOTE] Establish Registry, a sub-project of Apache NiFi
Posted by "Peter Wicks (pwicks)" <pw...@micron.com>.
+1 (non-binding)
-----Original Message-----
From: Bryan Bende [mailto:bbende@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 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 with
resources that one or more NiFi instances may be interested in, such
as a flow registry for versioned flows, an extension registry for
extensions, and possibly other configuration resources in the future.
In addition, this project will provide reference implementations of
these registries, with the goal of allowing the community to build a
diverse set of implementations, such as a Git provider for versioned
flows, or a bintray provider for an extension registry.
I am a +1 and looking forward to the future work in this area.
The vote will be open for 72 hours and be a majority rule vote.
[ ] +1 Establish Registry, a subproject of Apache NiFi
[ ] 0 Do not care
[ ] -1 Do not establish Registry, a subproject of Apache NiFi
Thanks,
Bryan
[1] http://mail-archives.apache.org/mod_mbox/nifi-dev/201702.mbox/%3CCALo_M19euo2LLy0PVWmE70FzeLhQRcCtX6TC%3DqoiBVfn4zFQMA%40mail.gmail.com%3E
Re: [VOTE] Establish Registry, a sub-project of Apache NiFi
Posted by Yolanda Davis <yo...@gmail.com>.
+1 (non-binding)
On Fri, Feb 10, 2017 at 11:40 AM, Bryan Bende <bb...@gmail.com> 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 decision and
> establish consensus.
>
> The scope of this project is to define APIs for interacting with
> resources that one or more NiFi instances may be interested in, such
> as a flow registry for versioned flows, an extension registry for
> extensions, and possibly other configuration resources in the future.
> In addition, this project will provide reference implementations of
> these registries, with the goal of allowing the community to build a
> diverse set of implementations, such as a Git provider for versioned
> flows, or a bintray provider for an extension registry.
>
> I am a +1 and looking forward to the future work in this area.
>
> The vote will be open for 72 hours and be a majority rule vote.
>
> [ ] +1 Establish Registry, a subproject of Apache NiFi
> [ ] 0 Do not care
> [ ] -1 Do not establish Registry, a subproject of Apache NiFi
>
> Thanks,
>
> Bryan
>
> [1] http://mail-archives.apache.org/mod_mbox/nifi-dev/201702.mbox/%3CCALo_
> M19euo2LLy0PVWmE70FzeLhQRcCtX6TC%3DqoiBVfn4zFQMA%40mail.gmail.com%3E
>
--
--
yolanda.m.davis@gmail.com
@YolandaMDavis
Re: [VOTE] Establish Registry, a sub-project of Apache NiFi
Posted by Joe Gresock <jg...@gmail.com>.
+1 (non-binding)
On Fri, Feb 10, 2017 at 6:26 PM, Michael Moser <mo...@gmail.com> 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 <jp...@apache.org>
> 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 be referred to.
> >
> > With that cleared up, I am a +1.
> >
> > Joe
> >
> > On Fri, Feb 10, 2017 at 1:01 PM, Pierre Villard <
> > pierre.villard.fr@gmail.com
> > > wrote:
> >
> > > +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 <jo...@gmail.com>:
> > >
> > > > 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 NiFi Registry works out quite well to explain both
> > > > what it is an to be consistent with the marks. See here for an
> > > > example of this guidance from ASF naming/marks guidance [1].
> > > >
> > > > I view this vote as actually being about the community decision to
> > > > create this subproject with the stated goals and in that perspective
> I
> > > > am a strong +1. I'm open to alternative names though I do think
> > > > "Apache NiFi Registry" is nice and descriptive.
> > > >
> > > > [1] https://www.apache.org/dev/project-names.html
> > > >
> > > > Thanks
> > > > Joe
> > > >
> > > > On Fri, Feb 10, 2017 at 12:32 PM, Bryan Bende <bb...@gmail.com>
> > wrote:
> > > > > 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 there was a case where it would be referred to as
> > > > > only "Apache Registry", but if sub-project names are trademarked on
> > > > > their own then I do agree we would likely have to call it "NiFi
> > > > > Registry".
> > > > >
> > > > >
> > > > > On Fri, Feb 10, 2017 at 12:21 PM, Joe Percivall <
> > jpercivall@apache.org
> > > >
> > > > wrote:
> > > > >> 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 initial discussion had.
> > > > >>
> > > > >>
> > > > >> Joe
> > > > >>
> > > > >> On Fri, Feb 10, 2017 at 12:19 PM, Michael Moser <
> moser.mw@gmail.com
> > >
> > > > wrote:
> > > > >>
> > > > >>> 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 <
> > > > >>> ozhurakousky@hortonworks.com> wrote:
> > > > >>>
> > > > >>> > +1 Here as well. We desperately need it.
> > > > >>> >
> > > > >>> > > On Feb 10, 2017, at 12:11 PM, Jeremy Dyer <jd...@gmail.com>
> > > > 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 <
> > > > mattyb149@apache.org>
> > > > >>> > wrote:
> > > > >>> > >
> > > > >>> > >> +1 binding
> > > > >>> > >>
> > > > >>> > >> On Fri, Feb 10, 2017 at 11:40 AM, Bryan Bende <
> > bbende@gmail.com
> > > >
> > > > >>> 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
> > decision
> > > > and
> > > > >>> > >>> establish consensus.
> > > > >>> > >>>
> > > > >>> > >>> The scope of this project is to define APIs for interacting
> > > with
> > > > >>> > >>> resources that one or more NiFi instances may be interested
> > in,
> > > > such
> > > > >>> > >>> as a flow registry for versioned flows, an extension
> registry
> > > for
> > > > >>> > >>> extensions, and possibly other configuration resources in
> the
> > > > future.
> > > > >>> > >>> In addition, this project will provide reference
> > > implementations
> > > > of
> > > > >>> > >>> these registries, with the goal of allowing the community
> to
> > > > build a
> > > > >>> > >>> diverse set of implementations, such as a Git provider for
> > > > versioned
> > > > >>> > >>> flows, or a bintray provider for an extension registry.
> > > > >>> > >>>
> > > > >>> > >>> I am a +1 and looking forward to the future work in this
> > area.
> > > > >>> > >>>
> > > > >>> > >>> The vote will be open for 72 hours and be a majority rule
> > vote.
> > > > >>> > >>>
> > > > >>> > >>> [ ] +1 Establish Registry, a subproject of Apache NiFi
> > > > >>> > >>> [ ] 0 Do not care
> > > > >>> > >>> [ ] -1 Do not establish Registry, a subproject of Apache
> > NiFi
> > > > >>> > >>>
> > > > >>> > >>> Thanks,
> > > > >>> > >>>
> > > > >>> > >>> Bryan
> > > > >>> > >>>
> > > > >>> > >>> [1] http://mail-archives.apache.
> org/mod_mbox/nifi-dev/201702
> > .
> > > > >>> > >> mbox/%3CCALo_M19euo2LLy0PVWmE70FzeLhQRcCtX6
> > > > TC%3DqoiBVfn4zFQMA%40mail.
> > > > >>> > >> gmail.com%3E
> > > > >>> > >>
> > > > >>> >
> > > > >>> >
> > > > >>>
> > > > >>
> > > > >>
> > > > >>
> > > > >> --
> > > > >> *Joe Percivall*
> > > > >> linkedin.com/in/Percivall
> > > > >> e: jpercivall@apache.com
> > > >
> > >
> >
> >
> >
> > --
> > *Joe Percivall*
> > linkedin.com/in/Percivall
> > e: jpercivall@apache.com
> >
>
--
I know what it is to be in need, and I know what it is to have plenty. I
have learned the secret of being content in any and every situation,
whether well fed or hungry, whether living in plenty or in want. I can do
all this through him who gives me strength. *-Philippians 4:12-13*
Re: [VOTE] Establish Registry, a sub-project of Apache NiFi
Posted by Michael Moser <mo...@gmail.com>.
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 <jp...@apache.org>
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 be referred to.
>
> With that cleared up, I am a +1.
>
> Joe
>
> On Fri, Feb 10, 2017 at 1:01 PM, Pierre Villard <
> pierre.villard.fr@gmail.com
> > wrote:
>
> > +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 <jo...@gmail.com>:
> >
> > > 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 NiFi Registry works out quite well to explain both
> > > what it is an to be consistent with the marks. See here for an
> > > example of this guidance from ASF naming/marks guidance [1].
> > >
> > > I view this vote as actually being about the community decision to
> > > create this subproject with the stated goals and in that perspective I
> > > am a strong +1. I'm open to alternative names though I do think
> > > "Apache NiFi Registry" is nice and descriptive.
> > >
> > > [1] https://www.apache.org/dev/project-names.html
> > >
> > > Thanks
> > > Joe
> > >
> > > On Fri, Feb 10, 2017 at 12:32 PM, Bryan Bende <bb...@gmail.com>
> wrote:
> > > > 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 there was a case where it would be referred to as
> > > > only "Apache Registry", but if sub-project names are trademarked on
> > > > their own then I do agree we would likely have to call it "NiFi
> > > > Registry".
> > > >
> > > >
> > > > On Fri, Feb 10, 2017 at 12:21 PM, Joe Percivall <
> jpercivall@apache.org
> > >
> > > wrote:
> > > >> 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 initial discussion had.
> > > >>
> > > >>
> > > >> Joe
> > > >>
> > > >> On Fri, Feb 10, 2017 at 12:19 PM, Michael Moser <moser.mw@gmail.com
> >
> > > wrote:
> > > >>
> > > >>> 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 <
> > > >>> ozhurakousky@hortonworks.com> wrote:
> > > >>>
> > > >>> > +1 Here as well. We desperately need it.
> > > >>> >
> > > >>> > > On Feb 10, 2017, at 12:11 PM, Jeremy Dyer <jd...@gmail.com>
> > > 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 <
> > > mattyb149@apache.org>
> > > >>> > wrote:
> > > >>> > >
> > > >>> > >> +1 binding
> > > >>> > >>
> > > >>> > >> On Fri, Feb 10, 2017 at 11:40 AM, Bryan Bende <
> bbende@gmail.com
> > >
> > > >>> 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
> decision
> > > and
> > > >>> > >>> establish consensus.
> > > >>> > >>>
> > > >>> > >>> The scope of this project is to define APIs for interacting
> > with
> > > >>> > >>> resources that one or more NiFi instances may be interested
> in,
> > > such
> > > >>> > >>> as a flow registry for versioned flows, an extension registry
> > for
> > > >>> > >>> extensions, and possibly other configuration resources in the
> > > future.
> > > >>> > >>> In addition, this project will provide reference
> > implementations
> > > of
> > > >>> > >>> these registries, with the goal of allowing the community to
> > > build a
> > > >>> > >>> diverse set of implementations, such as a Git provider for
> > > versioned
> > > >>> > >>> flows, or a bintray provider for an extension registry.
> > > >>> > >>>
> > > >>> > >>> I am a +1 and looking forward to the future work in this
> area.
> > > >>> > >>>
> > > >>> > >>> The vote will be open for 72 hours and be a majority rule
> vote.
> > > >>> > >>>
> > > >>> > >>> [ ] +1 Establish Registry, a subproject of Apache NiFi
> > > >>> > >>> [ ] 0 Do not care
> > > >>> > >>> [ ] -1 Do not establish Registry, a subproject of Apache
> NiFi
> > > >>> > >>>
> > > >>> > >>> Thanks,
> > > >>> > >>>
> > > >>> > >>> Bryan
> > > >>> > >>>
> > > >>> > >>> [1] http://mail-archives.apache.org/mod_mbox/nifi-dev/201702
> .
> > > >>> > >> mbox/%3CCALo_M19euo2LLy0PVWmE70FzeLhQRcCtX6
> > > TC%3DqoiBVfn4zFQMA%40mail.
> > > >>> > >> gmail.com%3E
> > > >>> > >>
> > > >>> >
> > > >>> >
> > > >>>
> > > >>
> > > >>
> > > >>
> > > >> --
> > > >> *Joe Percivall*
> > > >> linkedin.com/in/Percivall
> > > >> e: jpercivall@apache.com
> > >
> >
>
>
>
> --
> *Joe Percivall*
> linkedin.com/in/Percivall
> e: jpercivall@apache.com
>
Re: [VOTE] Establish Registry, a sub-project of Apache NiFi
Posted by Joe Percivall <jp...@apache.org>.
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 <pierre.villard.fr@gmail.com
> wrote:
> +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 <jo...@gmail.com>:
>
> > 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 NiFi Registry works out quite well to explain both
> > what it is an to be consistent with the marks. See here for an
> > example of this guidance from ASF naming/marks guidance [1].
> >
> > I view this vote as actually being about the community decision to
> > create this subproject with the stated goals and in that perspective I
> > am a strong +1. I'm open to alternative names though I do think
> > "Apache NiFi Registry" is nice and descriptive.
> >
> > [1] https://www.apache.org/dev/project-names.html
> >
> > Thanks
> > Joe
> >
> > On Fri, Feb 10, 2017 at 12:32 PM, Bryan Bende <bb...@gmail.com> wrote:
> > > 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 there was a case where it would be referred to as
> > > only "Apache Registry", but if sub-project names are trademarked on
> > > their own then I do agree we would likely have to call it "NiFi
> > > Registry".
> > >
> > >
> > > On Fri, Feb 10, 2017 at 12:21 PM, Joe Percivall <jpercivall@apache.org
> >
> > wrote:
> > >> 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 initial discussion had.
> > >>
> > >>
> > >> Joe
> > >>
> > >> On Fri, Feb 10, 2017 at 12:19 PM, Michael Moser <mo...@gmail.com>
> > wrote:
> > >>
> > >>> 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 <
> > >>> ozhurakousky@hortonworks.com> wrote:
> > >>>
> > >>> > +1 Here as well. We desperately need it.
> > >>> >
> > >>> > > On Feb 10, 2017, at 12:11 PM, Jeremy Dyer <jd...@gmail.com>
> > 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 <
> > mattyb149@apache.org>
> > >>> > wrote:
> > >>> > >
> > >>> > >> +1 binding
> > >>> > >>
> > >>> > >> On Fri, Feb 10, 2017 at 11:40 AM, Bryan Bende <bbende@gmail.com
> >
> > >>> 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 decision
> > and
> > >>> > >>> establish consensus.
> > >>> > >>>
> > >>> > >>> The scope of this project is to define APIs for interacting
> with
> > >>> > >>> resources that one or more NiFi instances may be interested in,
> > such
> > >>> > >>> as a flow registry for versioned flows, an extension registry
> for
> > >>> > >>> extensions, and possibly other configuration resources in the
> > future.
> > >>> > >>> In addition, this project will provide reference
> implementations
> > of
> > >>> > >>> these registries, with the goal of allowing the community to
> > build a
> > >>> > >>> diverse set of implementations, such as a Git provider for
> > versioned
> > >>> > >>> flows, or a bintray provider for an extension registry.
> > >>> > >>>
> > >>> > >>> I am a +1 and looking forward to the future work in this area.
> > >>> > >>>
> > >>> > >>> The vote will be open for 72 hours and be a majority rule vote.
> > >>> > >>>
> > >>> > >>> [ ] +1 Establish Registry, a subproject of Apache NiFi
> > >>> > >>> [ ] 0 Do not care
> > >>> > >>> [ ] -1 Do not establish Registry, a subproject of Apache NiFi
> > >>> > >>>
> > >>> > >>> Thanks,
> > >>> > >>>
> > >>> > >>> Bryan
> > >>> > >>>
> > >>> > >>> [1] http://mail-archives.apache.org/mod_mbox/nifi-dev/201702.
> > >>> > >> mbox/%3CCALo_M19euo2LLy0PVWmE70FzeLhQRcCtX6
> > TC%3DqoiBVfn4zFQMA%40mail.
> > >>> > >> gmail.com%3E
> > >>> > >>
> > >>> >
> > >>> >
> > >>>
> > >>
> > >>
> > >>
> > >> --
> > >> *Joe Percivall*
> > >> linkedin.com/in/Percivall
> > >> e: jpercivall@apache.com
> >
>
--
*Joe Percivall*
linkedin.com/in/Percivall
e: jpercivall@apache.com
Re: [VOTE] Establish Registry, a sub-project of Apache NiFi
Posted by Pierre Villard <pi...@gmail.com>.
+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 <jo...@gmail.com>:
> 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 NiFi Registry works out quite well to explain both
> what it is an to be consistent with the marks. See here for an
> example of this guidance from ASF naming/marks guidance [1].
>
> I view this vote as actually being about the community decision to
> create this subproject with the stated goals and in that perspective I
> am a strong +1. I'm open to alternative names though I do think
> "Apache NiFi Registry" is nice and descriptive.
>
> [1] https://www.apache.org/dev/project-names.html
>
> Thanks
> Joe
>
> On Fri, Feb 10, 2017 at 12:32 PM, Bryan Bende <bb...@gmail.com> wrote:
> > 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 there was a case where it would be referred to as
> > only "Apache Registry", but if sub-project names are trademarked on
> > their own then I do agree we would likely have to call it "NiFi
> > Registry".
> >
> >
> > On Fri, Feb 10, 2017 at 12:21 PM, Joe Percivall <jp...@apache.org>
> wrote:
> >> 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 initial discussion had.
> >>
> >>
> >> Joe
> >>
> >> On Fri, Feb 10, 2017 at 12:19 PM, Michael Moser <mo...@gmail.com>
> wrote:
> >>
> >>> 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 <
> >>> ozhurakousky@hortonworks.com> wrote:
> >>>
> >>> > +1 Here as well. We desperately need it.
> >>> >
> >>> > > On Feb 10, 2017, at 12:11 PM, Jeremy Dyer <jd...@gmail.com>
> 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 <
> mattyb149@apache.org>
> >>> > wrote:
> >>> > >
> >>> > >> +1 binding
> >>> > >>
> >>> > >> On Fri, Feb 10, 2017 at 11:40 AM, Bryan Bende <bb...@gmail.com>
> >>> 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 decision
> and
> >>> > >>> establish consensus.
> >>> > >>>
> >>> > >>> The scope of this project is to define APIs for interacting with
> >>> > >>> resources that one or more NiFi instances may be interested in,
> such
> >>> > >>> as a flow registry for versioned flows, an extension registry for
> >>> > >>> extensions, and possibly other configuration resources in the
> future.
> >>> > >>> In addition, this project will provide reference implementations
> of
> >>> > >>> these registries, with the goal of allowing the community to
> build a
> >>> > >>> diverse set of implementations, such as a Git provider for
> versioned
> >>> > >>> flows, or a bintray provider for an extension registry.
> >>> > >>>
> >>> > >>> I am a +1 and looking forward to the future work in this area.
> >>> > >>>
> >>> > >>> The vote will be open for 72 hours and be a majority rule vote.
> >>> > >>>
> >>> > >>> [ ] +1 Establish Registry, a subproject of Apache NiFi
> >>> > >>> [ ] 0 Do not care
> >>> > >>> [ ] -1 Do not establish Registry, a subproject of Apache NiFi
> >>> > >>>
> >>> > >>> Thanks,
> >>> > >>>
> >>> > >>> Bryan
> >>> > >>>
> >>> > >>> [1] http://mail-archives.apache.org/mod_mbox/nifi-dev/201702.
> >>> > >> mbox/%3CCALo_M19euo2LLy0PVWmE70FzeLhQRcCtX6
> TC%3DqoiBVfn4zFQMA%40mail.
> >>> > >> gmail.com%3E
> >>> > >>
> >>> >
> >>> >
> >>>
> >>
> >>
> >>
> >> --
> >> *Joe Percivall*
> >> linkedin.com/in/Percivall
> >> e: jpercivall@apache.com
>
Re: [VOTE] Establish Registry, a sub-project of Apache NiFi
Posted by Joe Witt <jo...@gmail.com>.
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 NiFi Registry works out quite well to explain both
what it is an to be consistent with the marks. See here for an
example of this guidance from ASF naming/marks guidance [1].
I view this vote as actually being about the community decision to
create this subproject with the stated goals and in that perspective I
am a strong +1. I'm open to alternative names though I do think
"Apache NiFi Registry" is nice and descriptive.
[1] https://www.apache.org/dev/project-names.html
Thanks
Joe
On Fri, Feb 10, 2017 at 12:32 PM, Bryan Bende <bb...@gmail.com> wrote:
> 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 there was a case where it would be referred to as
> only "Apache Registry", but if sub-project names are trademarked on
> their own then I do agree we would likely have to call it "NiFi
> Registry".
>
>
> On Fri, Feb 10, 2017 at 12:21 PM, Joe Percivall <jp...@apache.org> wrote:
>> 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 initial discussion had.
>>
>>
>> Joe
>>
>> On Fri, Feb 10, 2017 at 12:19 PM, Michael Moser <mo...@gmail.com> wrote:
>>
>>> 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 <
>>> ozhurakousky@hortonworks.com> wrote:
>>>
>>> > +1 Here as well. We desperately need it.
>>> >
>>> > > On Feb 10, 2017, at 12:11 PM, Jeremy Dyer <jd...@gmail.com> 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 <ma...@apache.org>
>>> > wrote:
>>> > >
>>> > >> +1 binding
>>> > >>
>>> > >> On Fri, Feb 10, 2017 at 11:40 AM, Bryan Bende <bb...@gmail.com>
>>> 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 decision and
>>> > >>> establish consensus.
>>> > >>>
>>> > >>> The scope of this project is to define APIs for interacting with
>>> > >>> resources that one or more NiFi instances may be interested in, such
>>> > >>> as a flow registry for versioned flows, an extension registry for
>>> > >>> extensions, and possibly other configuration resources in the future.
>>> > >>> In addition, this project will provide reference implementations of
>>> > >>> these registries, with the goal of allowing the community to build a
>>> > >>> diverse set of implementations, such as a Git provider for versioned
>>> > >>> flows, or a bintray provider for an extension registry.
>>> > >>>
>>> > >>> I am a +1 and looking forward to the future work in this area.
>>> > >>>
>>> > >>> The vote will be open for 72 hours and be a majority rule vote.
>>> > >>>
>>> > >>> [ ] +1 Establish Registry, a subproject of Apache NiFi
>>> > >>> [ ] 0 Do not care
>>> > >>> [ ] -1 Do not establish Registry, a subproject of Apache NiFi
>>> > >>>
>>> > >>> Thanks,
>>> > >>>
>>> > >>> Bryan
>>> > >>>
>>> > >>> [1] http://mail-archives.apache.org/mod_mbox/nifi-dev/201702.
>>> > >> mbox/%3CCALo_M19euo2LLy0PVWmE70FzeLhQRcCtX6TC%3DqoiBVfn4zFQMA%40mail.
>>> > >> gmail.com%3E
>>> > >>
>>> >
>>> >
>>>
>>
>>
>>
>> --
>> *Joe Percivall*
>> linkedin.com/in/Percivall
>> e: jpercivall@apache.com
Re: [VOTE] Establish Registry, a sub-project of Apache NiFi
Posted by Bryan Bende <bb...@gmail.com>.
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 there was a case where it would be referred to as
only "Apache Registry", but if sub-project names are trademarked on
their own then I do agree we would likely have to call it "NiFi
Registry".
On Fri, Feb 10, 2017 at 12:21 PM, Joe Percivall <jp...@apache.org> wrote:
> 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 initial discussion had.
>
>
> Joe
>
> On Fri, Feb 10, 2017 at 12:19 PM, Michael Moser <mo...@gmail.com> wrote:
>
>> 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 <
>> ozhurakousky@hortonworks.com> wrote:
>>
>> > +1 Here as well. We desperately need it.
>> >
>> > > On Feb 10, 2017, at 12:11 PM, Jeremy Dyer <jd...@gmail.com> 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 <ma...@apache.org>
>> > wrote:
>> > >
>> > >> +1 binding
>> > >>
>> > >> On Fri, Feb 10, 2017 at 11:40 AM, Bryan Bende <bb...@gmail.com>
>> 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 decision and
>> > >>> establish consensus.
>> > >>>
>> > >>> The scope of this project is to define APIs for interacting with
>> > >>> resources that one or more NiFi instances may be interested in, such
>> > >>> as a flow registry for versioned flows, an extension registry for
>> > >>> extensions, and possibly other configuration resources in the future.
>> > >>> In addition, this project will provide reference implementations of
>> > >>> these registries, with the goal of allowing the community to build a
>> > >>> diverse set of implementations, such as a Git provider for versioned
>> > >>> flows, or a bintray provider for an extension registry.
>> > >>>
>> > >>> I am a +1 and looking forward to the future work in this area.
>> > >>>
>> > >>> The vote will be open for 72 hours and be a majority rule vote.
>> > >>>
>> > >>> [ ] +1 Establish Registry, a subproject of Apache NiFi
>> > >>> [ ] 0 Do not care
>> > >>> [ ] -1 Do not establish Registry, a subproject of Apache NiFi
>> > >>>
>> > >>> Thanks,
>> > >>>
>> > >>> Bryan
>> > >>>
>> > >>> [1] http://mail-archives.apache.org/mod_mbox/nifi-dev/201702.
>> > >> mbox/%3CCALo_M19euo2LLy0PVWmE70FzeLhQRcCtX6TC%3DqoiBVfn4zFQMA%40mail.
>> > >> gmail.com%3E
>> > >>
>> >
>> >
>>
>
>
>
> --
> *Joe Percivall*
> linkedin.com/in/Percivall
> e: jpercivall@apache.com
Re: [VOTE] Establish Registry, a sub-project of Apache NiFi
Posted by Joe Percivall <jp...@apache.org>.
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 initial discussion had.
Joe
On Fri, Feb 10, 2017 at 12:19 PM, Michael Moser <mo...@gmail.com> wrote:
> 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 <
> ozhurakousky@hortonworks.com> wrote:
>
> > +1 Here as well. We desperately need it.
> >
> > > On Feb 10, 2017, at 12:11 PM, Jeremy Dyer <jd...@gmail.com> 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 <ma...@apache.org>
> > wrote:
> > >
> > >> +1 binding
> > >>
> > >> On Fri, Feb 10, 2017 at 11:40 AM, Bryan Bende <bb...@gmail.com>
> 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 decision and
> > >>> establish consensus.
> > >>>
> > >>> The scope of this project is to define APIs for interacting with
> > >>> resources that one or more NiFi instances may be interested in, such
> > >>> as a flow registry for versioned flows, an extension registry for
> > >>> extensions, and possibly other configuration resources in the future.
> > >>> In addition, this project will provide reference implementations of
> > >>> these registries, with the goal of allowing the community to build a
> > >>> diverse set of implementations, such as a Git provider for versioned
> > >>> flows, or a bintray provider for an extension registry.
> > >>>
> > >>> I am a +1 and looking forward to the future work in this area.
> > >>>
> > >>> The vote will be open for 72 hours and be a majority rule vote.
> > >>>
> > >>> [ ] +1 Establish Registry, a subproject of Apache NiFi
> > >>> [ ] 0 Do not care
> > >>> [ ] -1 Do not establish Registry, a subproject of Apache NiFi
> > >>>
> > >>> Thanks,
> > >>>
> > >>> Bryan
> > >>>
> > >>> [1] http://mail-archives.apache.org/mod_mbox/nifi-dev/201702.
> > >> mbox/%3CCALo_M19euo2LLy0PVWmE70FzeLhQRcCtX6TC%3DqoiBVfn4zFQMA%40mail.
> > >> gmail.com%3E
> > >>
> >
> >
>
--
*Joe Percivall*
linkedin.com/in/Percivall
e: jpercivall@apache.com
Re: [VOTE] Establish Registry, a sub-project of Apache NiFi
Posted by Michael Moser <mo...@gmail.com>.
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 <
ozhurakousky@hortonworks.com> wrote:
> +1 Here as well. We desperately need it.
>
> > On Feb 10, 2017, at 12:11 PM, Jeremy Dyer <jd...@gmail.com> 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 <ma...@apache.org>
> wrote:
> >
> >> +1 binding
> >>
> >> On Fri, Feb 10, 2017 at 11:40 AM, Bryan Bende <bb...@gmail.com> 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 decision and
> >>> establish consensus.
> >>>
> >>> The scope of this project is to define APIs for interacting with
> >>> resources that one or more NiFi instances may be interested in, such
> >>> as a flow registry for versioned flows, an extension registry for
> >>> extensions, and possibly other configuration resources in the future.
> >>> In addition, this project will provide reference implementations of
> >>> these registries, with the goal of allowing the community to build a
> >>> diverse set of implementations, such as a Git provider for versioned
> >>> flows, or a bintray provider for an extension registry.
> >>>
> >>> I am a +1 and looking forward to the future work in this area.
> >>>
> >>> The vote will be open for 72 hours and be a majority rule vote.
> >>>
> >>> [ ] +1 Establish Registry, a subproject of Apache NiFi
> >>> [ ] 0 Do not care
> >>> [ ] -1 Do not establish Registry, a subproject of Apache NiFi
> >>>
> >>> Thanks,
> >>>
> >>> Bryan
> >>>
> >>> [1] http://mail-archives.apache.org/mod_mbox/nifi-dev/201702.
> >> mbox/%3CCALo_M19euo2LLy0PVWmE70FzeLhQRcCtX6TC%3DqoiBVfn4zFQMA%40mail.
> >> gmail.com%3E
> >>
>
>
Re: [VOTE] Establish Registry, a sub-project of Apache NiFi
Posted by Oleg Zhurakousky <oz...@hortonworks.com>.
+1 Here as well. We desperately need it.
> On Feb 10, 2017, at 12:11 PM, Jeremy Dyer <jd...@gmail.com> 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 <ma...@apache.org> wrote:
>
>> +1 binding
>>
>> On Fri, Feb 10, 2017 at 11:40 AM, Bryan Bende <bb...@gmail.com> 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 decision and
>>> establish consensus.
>>>
>>> The scope of this project is to define APIs for interacting with
>>> resources that one or more NiFi instances may be interested in, such
>>> as a flow registry for versioned flows, an extension registry for
>>> extensions, and possibly other configuration resources in the future.
>>> In addition, this project will provide reference implementations of
>>> these registries, with the goal of allowing the community to build a
>>> diverse set of implementations, such as a Git provider for versioned
>>> flows, or a bintray provider for an extension registry.
>>>
>>> I am a +1 and looking forward to the future work in this area.
>>>
>>> The vote will be open for 72 hours and be a majority rule vote.
>>>
>>> [ ] +1 Establish Registry, a subproject of Apache NiFi
>>> [ ] 0 Do not care
>>> [ ] -1 Do not establish Registry, a subproject of Apache NiFi
>>>
>>> Thanks,
>>>
>>> Bryan
>>>
>>> [1] http://mail-archives.apache.org/mod_mbox/nifi-dev/201702.
>> mbox/%3CCALo_M19euo2LLy0PVWmE70FzeLhQRcCtX6TC%3DqoiBVfn4zFQMA%40mail.
>> gmail.com%3E
>>
Re: [VOTE] Establish Registry, a sub-project of Apache NiFi
Posted by Jeremy Dyer <jd...@gmail.com>.
+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 <ma...@apache.org> wrote:
> +1 binding
>
> On Fri, Feb 10, 2017 at 11:40 AM, Bryan Bende <bb...@gmail.com> 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 decision and
> > establish consensus.
> >
> > The scope of this project is to define APIs for interacting with
> > resources that one or more NiFi instances may be interested in, such
> > as a flow registry for versioned flows, an extension registry for
> > extensions, and possibly other configuration resources in the future.
> > In addition, this project will provide reference implementations of
> > these registries, with the goal of allowing the community to build a
> > diverse set of implementations, such as a Git provider for versioned
> > flows, or a bintray provider for an extension registry.
> >
> > I am a +1 and looking forward to the future work in this area.
> >
> > The vote will be open for 72 hours and be a majority rule vote.
> >
> > [ ] +1 Establish Registry, a subproject of Apache NiFi
> > [ ] 0 Do not care
> > [ ] -1 Do not establish Registry, a subproject of Apache NiFi
> >
> > Thanks,
> >
> > Bryan
> >
> > [1] http://mail-archives.apache.org/mod_mbox/nifi-dev/201702.
> mbox/%3CCALo_M19euo2LLy0PVWmE70FzeLhQRcCtX6TC%3DqoiBVfn4zFQMA%40mail.
> gmail.com%3E
>
Re: [VOTE] Establish Registry, a sub-project of Apache NiFi
Posted by Matt Burgess <ma...@apache.org>.
+1 binding
On Fri, Feb 10, 2017 at 11:40 AM, Bryan Bende <bb...@gmail.com> 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 decision and
> establish consensus.
>
> The scope of this project is to define APIs for interacting with
> resources that one or more NiFi instances may be interested in, such
> as a flow registry for versioned flows, an extension registry for
> extensions, and possibly other configuration resources in the future.
> In addition, this project will provide reference implementations of
> these registries, with the goal of allowing the community to build a
> diverse set of implementations, such as a Git provider for versioned
> flows, or a bintray provider for an extension registry.
>
> I am a +1 and looking forward to the future work in this area.
>
> The vote will be open for 72 hours and be a majority rule vote.
>
> [ ] +1 Establish Registry, a subproject of Apache NiFi
> [ ] 0 Do not care
> [ ] -1 Do not establish Registry, a subproject of Apache NiFi
>
> Thanks,
>
> Bryan
>
> [1] http://mail-archives.apache.org/mod_mbox/nifi-dev/201702.mbox/%3CCALo_M19euo2LLy0PVWmE70FzeLhQRcCtX6TC%3DqoiBVfn4zFQMA%40mail.gmail.com%3E