nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Chaffelson <chaffel...@gmail.com>
Subject Re: Collaboration for Azure features
Date Sat, 18 Apr 2020 09:01:31 GMT
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, <bbende@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 <kswanson@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 <joe.witt@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
> > > > >
> > > >
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message