I'm keen on a Slack channel. But I don't personally consider it as a great idea for offering support unless we can make sure we get new participants to linger and start offering support to others (grow the community). Otherwise I think that if people ask for support in a real-time channel, they generally expect a real-time response - they are hoping to avoid the effort and potential delay of a SO entry. And I'm not sure we can meet those expectations with our current resources. The SO approach seems more manageable to me. If we could 'grow the community' for peer support via SO, and then start inviting active people from SO to participate in realtime support via something like Slack alongside us, then I think it might be a more prudent approach to make it 'work' as a support channel.
Why I am keen on Slack is more in terms of collaboration possibilities. And I don't view our separation in terms of time zones to be a hindrance here. A tool like this just makes certain types of collaboration and communication possible that are impractical or very inefficient via list, which I also agree it should not undermine. Maybe we can have some sort of informal guide for this, to make sure that key decisions are always 'list-first' and the realtime tool is primarily used for actual collaboration on doc content, features or improvements (perhaps with a need to to have a summary thread on list for certain types of topics, so everyone has at least a 'helicopter view' of anything major) my two cents.... Greg On Mon, Dec 9, 2019 at 10:07 AM Piotr Zarzycki <[email protected]> wrote: > Hi Carlos, > > Give this thread more time so more active PMCs express their thoughts > about slack channel before you make noise about that trough social media. > > Thanks, > Piotr > > On Sun, Dec 8, 2019, 9:22 PM Carlos Rovira <[email protected]> > wrote: > > > Hi Andrew, > > > > if you open a Slack channel in The-ASF Slack try to call it "Apache > Royale" > > or the way it should be to make it more official. > > Then post here so we can add to it, and finally I can post it on website > > and Social media so people know about it. > > We just need to let people clear that is a help channel and maybe > relevant > > people on the community will be not there (disclaimer) > > and that every thing that should be discussed to make it happen in the > > project need to be posted in @dev list > > > > Thanks > > > > > > El dom., 8 dic. 2019 a las 13:51, Andrew Wetmore (<[email protected]>) > > escribió: > > > > > Hi, Alex: > > > > > > I should clarify that I am "Slack-curious" in relation to Royale. I > > needed > > > to discuss some things with an ASF staffer and he said that he did not > > see > > > me on the ASF Slack workspace, and asked how come. To that point, I had > > not > > > known there WAS such a workspace. That made me curious about whether it > > was > > > a resource Royale might consider using in some situations. > > > > > > There are several Royale email threads where the conversations would > have > > > been shorter, clearer, and possibly more productive if we had carried > > them > > > out in real-time, rather than firing increasingly-exasperated email > > > messages back and forth; but I don't think anyone can tell IN ADVANCE > > which > > > question is going to generate a wrangle by email that might be avoided > > in a > > > near-live discussion. > > > > > > I find it easier to search a Slack thread for a keyword than to do the > > same > > > thing across all the Royale-related emails in which it might have > > appeared, > > > and I know I have mislaid valuable Royale-related information by not > > > extracting it from the email thread when I saw it, rather than > presuming > > I > > > could find it again. This may be mainly due to my own failure to curate > > the > > > information that I personally need, and others may not experience this > > > problem. > > > > > > Slack channels within the workspace are free, so I may set one up for > > > Royale to have it ready against the time when it might be useful. If I > > do, > > > I will mention its name (in an email haha) so others on dev will know > it > > is > > > there. > > > > > > Andrew > > > > > > On Sun, Dec 8, 2019 at 4:02 AM Alex Harui <[email protected]> > > > wrote: > > > > > > > I agree that Stack Overflow solves a different problem that Slack > does > > > for > > > > other projects. > > > > > > > > Andrew, if you are still interested in Slack, can you think of a > couple > > > of > > > > Royale conversations from any of our mailing lists/forums/whatever > > that > > > > you think would have worked better on Slack? I suppose that some > > editing > > > > of the documentation/website would be better done on IRC since it > isn't > > > > super important to most of the subscribers to dev@, but you can > > > certainly > > > > ask the few other people you are working with to choose a chat-app on > > an > > > > ad-hoc basis for that one discussion if it isn't going to result in > > some > > > > decision or if the decision will be proposed on dev@ after the chat > > > wraps > > > > up. > > > > > > > > IIRC, the projects I've heard that are using Slack at the ASF have a > > set > > > > of paid committers that work at the same time on interrelated stuff. > > > > Certain teams within Adobe use Slack but I don't since I don't > > > collaborate > > > > with other Adobe engineers. For the most part, I don't need to be > > > plugged > > > > into any team effort on Royale most of the time. I'm not sure there > > are > > > > many committers who work on framework code every day. > > > > > > > > My 2 cents, > > > > -Alex > > > > > > > > > > > Andrew Wetmore > > > > > > http://cottage14.blogspot.com/ > > > > > > > > > -- > > Carlos Rovira > > http://about.me/carlosrovira > > >
