Re: [DISCUSS] Slack Channel Use

2018-11-12 Thread Otto Fowler
What we need is a slackbot where you can: - start a discuss thread, that will get sent to email list - listen to emails ( be on the list ) and post any discuss thread replies not from slack TO slack - add tagged comments to discuss thread the list-slack singularity On November 12, 2018 at

Re: [DISCUSS] Slack Channel Use

2018-11-12 Thread zeo...@gmail.com
Spot on Justin, I totally agree. My only nit is that often it's much easier troubleshooting in Slack as opposed to the mailing lists, so I'm game to allow some troubleshooting in Slack as long as the issue and resolution makes it back to the lists. Given that slack message history is being kept

Re: [DISCUSS] Slack Channel Use

2018-11-12 Thread Casey Stella
Piling on, +1 to what Justin said. On Mon, Nov 12, 2018 at 12:42 PM Michael Miklavcic < michael.miklav...@gmail.com> wrote: > I'm also +1 to Justin's points. > > On Mon, Nov 12, 2018 at 10:38 AM Nick Allen wrote: > > > +1 to all your points Justin. > > > > On Mon, Nov 12, 2018 at 10:08 AM

Re: [DISCUSS] Slack Channel Use

2018-11-12 Thread Michael Miklavcic
I'm also +1 to Justin's points. On Mon, Nov 12, 2018 at 10:38 AM Nick Allen wrote: > +1 to all your points Justin. > > On Mon, Nov 12, 2018 at 10:08 AM Justin Leet > wrote: > > > I wanted to add back onto this thread after putting some more thought > into > > it. > > > > I like Slack for the

Re: [DISCUSS] Slack Channel Use

2018-11-12 Thread Michael Miklavcic
Your suggestion is well received. I think what we're trying to avoid is a big dump of Slack's stream of consciousness. There is an inherent organization and required collection of thoughts that comes with the dev/user list discussions that doesn't occur on Slack. Maybe threads can help that a bit,

Re: [DISCUSS] Slack Channel Use

2018-11-12 Thread Nick Allen
+1 to all your points Justin. On Mon, Nov 12, 2018 at 10:08 AM Justin Leet wrote: > I wanted to add back onto this thread after putting some more thought into > it. > > I like Slack for the type of small developer "what's going on here?" type > discussions. That's the kind of thing I like

Re: [DISCUSS] Slack Channel Use

2018-11-12 Thread Scott C. Cote
I realize that I’m a “new kid” here, but I think you can have your cake and eat it too….. If I can create it, find it, or configure it, perhaps the really best way is to be able to either: 1) dump public slack conversations to the developer thread - arbitrarily 2) dump public slack

Re: [DISCUSS] Slack Channel Use

2018-11-12 Thread Justin Leet
I wanted to add back onto this thread after putting some more thought into it. I like Slack for the type of small developer "what's going on here?" type discussions. That's the kind of thing I like being real-time ("Hey, full dev is acting weird", "What's the basic layout of this stuff?",

Re: [DISCUSS] Slack Channel Use

2018-10-24 Thread Michael Miklavcic
Yeah, I'm also surprised by that comment about the mailing list activity. Our dev/user list discussions are by far more active than they've ever been. Just have a look at the list of DISCUSS threads that have come up in the past few months and it's clear that not only participation has increased,

Re: [DISCUSS] Slack Channel Use

2018-10-24 Thread Casey Stella
quick clarification, I said "a lot of dev discussion happens on github and JIRA". I want to make sure I didn't mean to imply that larger decisions were being made outside of the appropriate place, the dev list. On Wed, Oct 24, 2018 at 10:08 AM Casey Stella wrote: > Not for nothing, but at

Re: [DISCUSS] Slack Channel Use

2018-10-24 Thread Casey Stella
Not for nothing, but at least according to the last board report that I submitted, the user@ traffic is up 100% and the dev list traffic is flat as compared to last quarter. That's not to say that we couldn't stand more discussion on the lists, but a lot of the dev discussion happens on github

Re: [DISCUSS] Slack Channel Use

2018-10-24 Thread Otto Fowler
I wouldn’t be so quick to related the slack discussion with perceived activity on the list. That is more do to the other things that are bigger issues. On October 24, 2018 at 07:15:30, Nick Allen (n...@nickallen.org) wrote: > I have heard recently people thought Metron is sort of dead just

Re: [DISCUSS] Slack Channel Use

2018-10-24 Thread Nick Allen
> I have heard recently people thought Metron is sort of dead just because the mailing list is not so active anymore! That is exactly my concern. On Wed, Oct 24, 2018, 2:49 AM Ali Nazemian wrote: > I kind of expect to have Slack for more dev related discussions rather than > user QA. I guess

Re: [DISCUSS] Slack Channel Use

2018-10-24 Thread Ali Nazemian
I kind of expect to have Slack for more dev related discussions rather than user QA. I guess it is quite common to expect mailing list to be used for the purpose of knowledge sharing to make sure it will be accessible by other users as well. Of course, it is a trade-off that most of the other

Re: [DISCUSS] Slack Channel Use

2018-10-22 Thread Casey Stella
Agreed, the benefit of the mailing list is that it’s searchable by ponymail and the major search engines. On Mon, Oct 22, 2018 at 17:18 Nick Allen wrote: > I don't know that it is the same kind of searchable. Is it being indexed > by the major search engines? I have never used a search engine

Re: [DISCUSS] Slack Channel Use

2018-10-22 Thread Nick Allen
I don't know that it is the same kind of searchable. Is it being indexed by the major search engines? I have never used a search engine and uncovered the answer to my problem in a Slack archive. On Mon, Oct 22, 2018 at 5:05 PM Otto Fowler wrote: > According to Greg Stein, an infra admin on

Re: [DISCUSS] Slack Channel Use

2018-10-22 Thread Otto Fowler
According to Greg Stein, an infra admin on the NiFi slack, the ASF slack that metron is in IS the standard plan, not the free one and is searchable past 10,000 messages. On October 22, 2018 at 15:35:51, Michael Miklavcic ( michael.miklav...@gmail.com) wrote: ...From an archival and broader

Re: [DISCUSS] Slack Channel Use

2018-10-22 Thread Michael Miklavcic
...From an archival and broader reach point of view, I do think there's something to be said about using the mailing list. It's also easier to link to Q/A threads from the mailing list archives and do searches...

Re: [DISCUSS] Slack Channel Use

2018-10-22 Thread Michael Miklavcic
I just want to point out that we currently have 32 members in the Metron Slack channel which I personally think is a great sign. This is good from a community perspective and helps foster interactive sessions where required. >From an archival and broader reach point of view, I do think there's

Re: [DISCUSS] Slack Channel Use

2018-10-22 Thread Justin Leet
If we want to push more discussion to the dev list, my obvious follow up question then is "What are we hoping to get out of Slack/irc/other interactive medium?". What discussion would we even want on there, if we can't have decisions and don't want usage/support? On Mon, Oct 22, 2018 at 12:44 PM

Re: [DISCUSS] Slack Channel Use

2018-10-22 Thread Casey Stella
I am of 2 minds, but I tend to agree. On the one hand, it's definitely the preference that we use the mailing lists for the reasons you stated (and also because not everyone has access to slack generally). On the other hand, I think an interactive medium like Slack has a lot of advantages in

Re: [DISCUSS] Slack Channel Use

2018-10-22 Thread Nick Allen
The help given on the Channel is great. It is just much more scalable on an archived mailing list. Hence the Apache Foundation's preference for mailing lists. On Mon, Oct 22, 2018 at 12:27 PM Otto Fowler wrote: > These questions also occurred on the IRC channel. The difference is that >

Re: [DISCUSS] Slack Channel Use

2018-10-22 Thread Otto Fowler
These questions also occurred on the IRC channel. The difference is that there are more than Jon and I answering now. On October 22, 2018 at 12:18:08, Nick Allen (n...@nickallen.org) wrote: It seems that we are seeing a lot of Metron usage and support questions on the Slack Channel. These are