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 On 12/7/19, 5:36 AM, "Andrew Wetmore" <[email protected]> wrote: I see Stack Overflow as a marketing opportunity for us and an entry point for people with questions, not really as a conversation tool for the Royale project itself. I think anything of substance that emerges from a Stack Overflow conversation needs to migrate into the project, either as a bug report or as part of the documentation. a On Sat, Dec 7, 2019 at 9:13 AM Piotr Zarzycki <[email protected]> wrote: > Stack Overflow. > > On Sat, Dec 7, 2019, 11:21 AM Andrew Wetmore <[email protected]> wrote: > > > What is "SOF"? > > > > On Sat, Dec 7, 2019 at 4:03 AM Piotr Zarzycki <[email protected] > > > > wrote: > > > > > Hi All > > > > > > I'm -1 to use any other tool than mailing list with this project. It > > > increases only traffic for everyone. Another tool which needs to be > > > maintained and we definitely have much more bigger fish to fry. > > > > > > We have SOF already as an addition to mailing list and in my opinion > it's > > > really enough. > > > > > > Thanks, > > > Piotr > > > > > > On Sat, Dec 7, 2019, 8:38 AM Carlos Rovira <[email protected]> > > > wrote: > > > > > > > Hi Andrew,, > > > > > > > > I'm happy with mailing list but the only point is when people outside > > the > > > > Apache eco-system want to interact with us. They use to post on > social > > > > media networks, or direct emails and so on, and then we need to > derive > > > > here, what could be something they want or not. > > > > > > > > It would be great to use some tool that will be more easily > accessible > > by > > > > all people or that most of new comers would have directly. But don't > > know > > > > what could be. > > > > > > > > Real time chats does not seems to me something to drive discussion > for > > > the > > > > same reason Alex mentioned. We are all in different time zones and > some > > > > times responses delay 10-12 hours. > > > > > > > > Regarding Slack tool in concrete, my main concern is that my > experience > > > is > > > > really bad with it since most of the times I don't get push > > notifications > > > > on my iPhone. While other tools like Telegram works always, Slack > > don't, > > > > and that means sometimes I don't notice a conversation for days. With > > > that > > > > in mind is a surprise for me that Slack get so popular, or maybe I > have > > > > something wrong with it in my devices... > > > > > > > > Anyway, If we want to use Slack, I think it's ok since as many > channels > > > we > > > > have the better. Just warn people that maybe not all of us will be > > there. > > > > Or not always available. And key discussions should come to the list. > > > > Helping there could be in some cases more easy to do. > > > > > > > > Thanks! > > > > > > > > > > > > > > > > > > > > > > > > > > > > El vie., 6 dic. 2019 a las 21:23, Alex Harui > (<[email protected] > > > >) > > > > escribió: > > > > > > > > > > > > > > > > > > > On 12/6/19, 12:00 PM, "Andrew Wetmore" <[email protected]> > wrote: > > > > > > > > > > I recently had some dealings with ASF staff on the ASF Slack > > > > workspace > > > > > ( > > > > > the-asf.slack.com). Some projects seem to maintain channels > > there > > > > for > > > > > coordinating work, but not Royale. Would we gain anything by > > > creating > > > > > and > > > > > using such a channel as opposed to running all discussions > > through > > > > > email > > > > > threads? Or would this just add one more thing to worry about? > > > > > > > > > > I've seen lots of concern about Slack on the board list. One key > > > > > principle of Apache projects is that committers should be able to > > > follow > > > > > the project by only being subscribed to dev@. You shouldn't have > to > > > be > > > > > subscribed elsewhere, not even users@ and especially private@. > Some > > > > > projects have gotten in trouble for using Slack and other IRC too > > much. > > > > It > > > > > isn't that every discussion has to be on dev@, really, only > refined > > > > > proposals leading to decisions need to be on dev@, but then those > > who > > > > > aren't involved in the early discussions feel left out, or the > early > > > > > discussion gets voided by input from those not on the channel or > not > > on > > > > > during the interactive discussion. > > > > > > > > > > That said, the ASF is probably going to be forced to reconsider > that > > > rule > > > > > as chat-based development discussions are the norm in some > countries > > > like > > > > > China. > > > > > > > > > > I'm not opposed to a Slack channel for Royale, but I will try to > not > > > use > > > > > it mainly to make sure there is enough traffic on dev@. Also, the > > > vast > > > > > majority of active committers are not in the US where I am, so I > > won't > > > be > > > > > around to interact most often. But if it helps you and others > > roughly > > > in > > > > > your time zone get work done, go for it. > > > > > > > > > > -Alex > > > > > > > > > > > > > > > > > > > > > > > -- > > > > Carlos Rovira > > > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cf95028a7f30e47a4abf008d77b1a736d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637113225880909875&sdata=yPM5msP%2BRTrhvsrSls%2BEl7KsLg02ghzNjbC6RpmjC98%3D&reserved=0 > > > > > > > > > > > > > -- > > Andrew Wetmore > > > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcottage14.blogspot.com%2F&data=02%7C01%7Caharui%40adobe.com%7Cf95028a7f30e47a4abf008d77b1a736d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637113225880909875&sdata=9VtfS96gOlF5na%2FHugCNLoF6JsYIah3fGNYI1KMDc0A%3D&reserved=0 > > > -- Andrew Wetmore https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcottage14.blogspot.com%2F&data=02%7C01%7Caharui%40adobe.com%7Cf95028a7f30e47a4abf008d77b1a736d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637113225880909875&sdata=9VtfS96gOlF5na%2FHugCNLoF6JsYIah3fGNYI1KMDc0A%3D&reserved=0
