You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nifi.apache.org by Pierre Villard <pi...@gmail.com> on 2020/05/01 14:51:54 UTC
Re: Collaboration for Azure features
It's fine for me. I can look at creating the channel early next week if
there is no objection.
Pierre
Le mer. 29 avr. 2020 à 17:15, Muazma Zahid <mu...@gmail.com> a écrit :
> Do we have a consensus here? I am fine with a generic one #dev_cloud. Also
> as part of the channel description, we can add a note to not cross-post.
> Also, generic slack guidelines can be published for effective
> collaboration.
> Thanks,
> Muazma
>
> On Sat, Apr 18, 2020 at 2:57 AM Daniel Chaffelson <ch...@gmail.com>
> wrote:
>
> > I would check how search functionality works in two cases; do you get
> > results from channels you are not a member of, do you get results from
> > archived channels.
> > If both are true, then having side channels doesn't prevent the most
> common
> > way of finding specific information, though it would be good to ensure
> that
> > general chat remains in generally channels to encourage community
> cohesion.
> >
> > On Fri, 17 Apr 2020, 19:06 Bryan Bende, <bb...@gmail.com> wrote:
> >
> > > Personally I have always wished there was just a single channel with
> > > threaded convos, rather than needing to monitor many channels and see
> the
> > > same question cross posted multiple times, but since we are well past
> > that
> > > point, I am not really opposed. The only issue I could see is where to
> > draw
> > > the line, we could easily create channels for many areas development
> and
> > > have it get out of hand.
> > >
> > > On Fri, Apr 17, 2020 at 1:54 PM Pierre Villard <
> > > pierre.villard.fr@gmail.com>
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > On my side, I think this is a good idea if that helps having groups
> of
> > > > collaboration focusing on specific areas for NiFi.
> > > >
> > > > If having too much channels in our Slack is a concern, I guess a
> > > #dev_cloud
> > > > channel could be an intermediate solution (assuming we expect to see
> > > > #dev_aws and #dev_gcp now or in the future). We could then
> re-evaluate
> > > > based on how much people are interacting there.
> > > >
> > > > Pierre
> > > >
> > > > Le ven. 17 avr. 2020 à 18:28, Ken Swanson <ks...@1904labs.com> a
> > > écrit
> > > > :
> > > >
> > > > > Is there a place to vote on channel proliferation in Slack? I might
> > > have
> > > > > missed that.
> > > > >
> > > > > -Ken
> > > > >
> > > > > On Fri, Apr 17, 2020 at 11:03 AM Joe Witt <jo...@gmail.com>
> > wrote:
> > > > >
> > > > > > Muazma,
> > > > > >
> > > > > > My initial reaction was strongly against this as it creates even
> > more
> > > > > > channels and our slack in my view already has too many.
> > > > > >
> > > > > > However, we definitely do want groups of extensions to be well
> > > > > > managed/groomed by contributors and users alike. So in that
> regard
> > > > this
> > > > > is
> > > > > > a good focus area. We want to get extension bundles into their
> own
> > > > > project
> > > > > > structure and out of the main nifi build. So this is probably a
> > > > helpful
> > > > > > step in that direction.
> > > > > >
> > > > > > I'm fine with it.
> > > > > >
> > > > > > I'd let folks comment and see if there is consensus. Dont think
> we
> > > > need
> > > > > a
> > > > > > vote or anything. Our channel proliferation on slack hasnt had
> any
> > > > votes
> > > > > > either.
> > > > > >
> > > > > > Thanks
> > > > > > Joe
> > > > > >
> > > > > >
> > > > > > On Fri, Apr 17, 2020 at 11:20 AM Muazma Zahid <mu...@gmail.com>
> > > > wrote:
> > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > I wanted to float an idea for creating a dedicated #dev_azure
> > > channel
> > > > > in
> > > > > > > the NiFi Slack where people could chime in and collaborate on
> new
> > > > > > features.
> > > > > > > Let me know if this is something that can be done in the
> > community
> > > as
> > > > > we
> > > > > > > are adding many new features and we can get feedback and
> > > collaborate
> > > > > with
> > > > > > > others interested.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Muazma
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: Collaboration for Azure features
Posted by Muazma Zahid <mu...@gmail.com>.
Thanks Pierre, looking forward to collaborating on Azure cloud features.
Thanks,
Muazma
On Tue, May 12, 2020 at 11:51 AM Pierre Villard <pi...@gmail.com>
wrote:
> Hi all,
>
> I created the channel #dev-cloud in our Slack workspace.
>
> Thanks,
> Pierre
>
> Le ven. 1 mai 2020 à 16:51, Pierre Villard <pi...@gmail.com> a
> écrit :
>
> > It's fine for me. I can look at creating the channel early next week if
> > there is no objection.
> >
> > Pierre
> >
> > Le mer. 29 avr. 2020 à 17:15, Muazma Zahid <mu...@gmail.com> a écrit :
> >
> >> Do we have a consensus here? I am fine with a generic one #dev_cloud.
> Also
> >> as part of the channel description, we can add a note to not cross-post.
> >> Also, generic slack guidelines can be published for effective
> >> collaboration.
> >> Thanks,
> >> Muazma
> >>
> >> On Sat, Apr 18, 2020 at 2:57 AM Daniel Chaffelson <chaffelson@gmail.com
> >
> >> wrote:
> >>
> >> > I would check how search functionality works in two cases; do you get
> >> > results from channels you are not a member of, do you get results from
> >> > archived channels.
> >> > If both are true, then having side channels doesn't prevent the most
> >> common
> >> > way of finding specific information, though it would be good to ensure
> >> that
> >> > general chat remains in generally channels to encourage community
> >> cohesion.
> >> >
> >> > On Fri, 17 Apr 2020, 19:06 Bryan Bende, <bb...@gmail.com> wrote:
> >> >
> >> > > Personally I have always wished there was just a single channel with
> >> > > threaded convos, rather than needing to monitor many channels and
> see
> >> the
> >> > > same question cross posted multiple times, but since we are well
> past
> >> > that
> >> > > point, I am not really opposed. The only issue I could see is where
> to
> >> > draw
> >> > > the line, we could easily create channels for many areas development
> >> and
> >> > > have it get out of hand.
> >> > >
> >> > > On Fri, Apr 17, 2020 at 1:54 PM Pierre Villard <
> >> > > pierre.villard.fr@gmail.com>
> >> > > wrote:
> >> > >
> >> > > > Hi,
> >> > > >
> >> > > > On my side, I think this is a good idea if that helps having
> groups
> >> of
> >> > > > collaboration focusing on specific areas for NiFi.
> >> > > >
> >> > > > If having too much channels in our Slack is a concern, I guess a
> >> > > #dev_cloud
> >> > > > channel could be an intermediate solution (assuming we expect to
> see
> >> > > > #dev_aws and #dev_gcp now or in the future). We could then
> >> re-evaluate
> >> > > > based on how much people are interacting there.
> >> > > >
> >> > > > Pierre
> >> > > >
> >> > > > Le ven. 17 avr. 2020 à 18:28, Ken Swanson <ks...@1904labs.com>
> a
> >> > > écrit
> >> > > > :
> >> > > >
> >> > > > > Is there a place to vote on channel proliferation in Slack? I
> >> might
> >> > > have
> >> > > > > missed that.
> >> > > > >
> >> > > > > -Ken
> >> > > > >
> >> > > > > On Fri, Apr 17, 2020 at 11:03 AM Joe Witt <jo...@gmail.com>
> >> > wrote:
> >> > > > >
> >> > > > > > Muazma,
> >> > > > > >
> >> > > > > > My initial reaction was strongly against this as it creates
> even
> >> > more
> >> > > > > > channels and our slack in my view already has too many.
> >> > > > > >
> >> > > > > > However, we definitely do want groups of extensions to be well
> >> > > > > > managed/groomed by contributors and users alike. So in that
> >> regard
> >> > > > this
> >> > > > > is
> >> > > > > > a good focus area. We want to get extension bundles into
> their
> >> own
> >> > > > > project
> >> > > > > > structure and out of the main nifi build. So this is
> probably a
> >> > > > helpful
> >> > > > > > step in that direction.
> >> > > > > >
> >> > > > > > I'm fine with it.
> >> > > > > >
> >> > > > > > I'd let folks comment and see if there is consensus. Dont
> >> think we
> >> > > > need
> >> > > > > a
> >> > > > > > vote or anything. Our channel proliferation on slack hasnt
> had
> >> any
> >> > > > votes
> >> > > > > > either.
> >> > > > > >
> >> > > > > > Thanks
> >> > > > > > Joe
> >> > > > > >
> >> > > > > >
> >> > > > > > On Fri, Apr 17, 2020 at 11:20 AM Muazma Zahid <
> muazma@gmail.com
> >> >
> >> > > > wrote:
> >> > > > > >
> >> > > > > > > Hi,
> >> > > > > > >
> >> > > > > > > I wanted to float an idea for creating a dedicated
> #dev_azure
> >> > > channel
> >> > > > > in
> >> > > > > > > the NiFi Slack where people could chime in and collaborate
> on
> >> new
> >> > > > > > features.
> >> > > > > > > Let me know if this is something that can be done in the
> >> > community
> >> > > as
> >> > > > > we
> >> > > > > > > are adding many new features and we can get feedback and
> >> > > collaborate
> >> > > > > with
> >> > > > > > > others interested.
> >> > > > > > >
> >> > > > > > > Thanks,
> >> > > > > > > Muazma
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> >
>
Re: Collaboration for Azure features
Posted by Pierre Villard <pi...@gmail.com>.
Hi all,
I created the channel #dev-cloud in our Slack workspace.
Thanks,
Pierre
Le ven. 1 mai 2020 à 16:51, Pierre Villard <pi...@gmail.com> a
écrit :
> It's fine for me. I can look at creating the channel early next week if
> there is no objection.
>
> Pierre
>
> Le mer. 29 avr. 2020 à 17:15, Muazma Zahid <mu...@gmail.com> a écrit :
>
>> Do we have a consensus here? I am fine with a generic one #dev_cloud. Also
>> as part of the channel description, we can add a note to not cross-post.
>> Also, generic slack guidelines can be published for effective
>> collaboration.
>> Thanks,
>> Muazma
>>
>> On Sat, Apr 18, 2020 at 2:57 AM Daniel Chaffelson <ch...@gmail.com>
>> wrote:
>>
>> > I would check how search functionality works in two cases; do you get
>> > results from channels you are not a member of, do you get results from
>> > archived channels.
>> > If both are true, then having side channels doesn't prevent the most
>> common
>> > way of finding specific information, though it would be good to ensure
>> that
>> > general chat remains in generally channels to encourage community
>> cohesion.
>> >
>> > On Fri, 17 Apr 2020, 19:06 Bryan Bende, <bb...@gmail.com> wrote:
>> >
>> > > Personally I have always wished there was just a single channel with
>> > > threaded convos, rather than needing to monitor many channels and see
>> the
>> > > same question cross posted multiple times, but since we are well past
>> > that
>> > > point, I am not really opposed. The only issue I could see is where to
>> > draw
>> > > the line, we could easily create channels for many areas development
>> and
>> > > have it get out of hand.
>> > >
>> > > On Fri, Apr 17, 2020 at 1:54 PM Pierre Villard <
>> > > pierre.villard.fr@gmail.com>
>> > > wrote:
>> > >
>> > > > Hi,
>> > > >
>> > > > On my side, I think this is a good idea if that helps having groups
>> of
>> > > > collaboration focusing on specific areas for NiFi.
>> > > >
>> > > > If having too much channels in our Slack is a concern, I guess a
>> > > #dev_cloud
>> > > > channel could be an intermediate solution (assuming we expect to see
>> > > > #dev_aws and #dev_gcp now or in the future). We could then
>> re-evaluate
>> > > > based on how much people are interacting there.
>> > > >
>> > > > Pierre
>> > > >
>> > > > Le ven. 17 avr. 2020 à 18:28, Ken Swanson <ks...@1904labs.com> a
>> > > écrit
>> > > > :
>> > > >
>> > > > > Is there a place to vote on channel proliferation in Slack? I
>> might
>> > > have
>> > > > > missed that.
>> > > > >
>> > > > > -Ken
>> > > > >
>> > > > > On Fri, Apr 17, 2020 at 11:03 AM Joe Witt <jo...@gmail.com>
>> > wrote:
>> > > > >
>> > > > > > Muazma,
>> > > > > >
>> > > > > > My initial reaction was strongly against this as it creates even
>> > more
>> > > > > > channels and our slack in my view already has too many.
>> > > > > >
>> > > > > > However, we definitely do want groups of extensions to be well
>> > > > > > managed/groomed by contributors and users alike. So in that
>> regard
>> > > > this
>> > > > > is
>> > > > > > a good focus area. We want to get extension bundles into their
>> own
>> > > > > project
>> > > > > > structure and out of the main nifi build. So this is probably a
>> > > > helpful
>> > > > > > step in that direction.
>> > > > > >
>> > > > > > I'm fine with it.
>> > > > > >
>> > > > > > I'd let folks comment and see if there is consensus. Dont
>> think we
>> > > > need
>> > > > > a
>> > > > > > vote or anything. Our channel proliferation on slack hasnt had
>> any
>> > > > votes
>> > > > > > either.
>> > > > > >
>> > > > > > Thanks
>> > > > > > Joe
>> > > > > >
>> > > > > >
>> > > > > > On Fri, Apr 17, 2020 at 11:20 AM Muazma Zahid <muazma@gmail.com
>> >
>> > > > wrote:
>> > > > > >
>> > > > > > > Hi,
>> > > > > > >
>> > > > > > > I wanted to float an idea for creating a dedicated #dev_azure
>> > > channel
>> > > > > in
>> > > > > > > the NiFi Slack where people could chime in and collaborate on
>> new
>> > > > > > features.
>> > > > > > > Let me know if this is something that can be done in the
>> > community
>> > > as
>> > > > > we
>> > > > > > > are adding many new features and we can get feedback and
>> > > collaborate
>> > > > > with
>> > > > > > > others interested.
>> > > > > > >
>> > > > > > > Thanks,
>> > > > > > > Muazma
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>>
>