I'm ok to create the channel and then be used by the people that can / have time. We can have make the paths an some of them will be used and other not...
Thanks El lun., 9 dic. 2019 a las 6:45, Alex Harui (<[email protected]>) escribió: > I don't see any harm in creating the channel. If it never gets used, no > big deal AFAICT. Unless someone can think of why we need to be careful, > I'd say it is in the category of "might help, won't hurt" so JFDI. > > -Alex > > On 12/8/19, 4:04 PM, "Andrew Wetmore" <[email protected]> wrote: > > As @Harbs says, if we had a channel, it would only be available to > people > with an Apache email address, so it can't be a support channel or a > way of > easing new folks into the project. If we used it, it would be for > exploring > ideas, hammering out misunderstandings, testing positioning, co-writing > slogans and other such stuff. > > On Sun, Dec 8, 2019 at 5:54 PM Harbs <[email protected]> wrote: > > > Anyone with an apache.org < > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache.org%2F&data=02%7C01%7Caharui%40adobe.com%7Caffef5ad990842dafcaa08d77c3b5da4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637114466763027979&sdata=P1kwRCZ%2FIq4fsYpHff5BOgR%2BK7wnjcPSD7dQdNfPxlw%3D&reserved=0> > email address can join the > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fthe-asf.slack.com%2F&data=02%7C01%7Caharui%40adobe.com%7Caffef5ad990842dafcaa08d77c3b5da4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637114466763027979&sdata=ZttOmUqrMLD9%2BRgoYyOVwMNlenjZAMrV67vvWf20PtU%3D&reserved=0 > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fthe-asf.slack.com%2F&data=02%7C01%7Caharui%40adobe.com%7Caffef5ad990842dafcaa08d77c3b5da4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637114466763027979&sdata=ZttOmUqrMLD9%2BRgoYyOVwMNlenjZAMrV67vvWf20PtU%3D&reserved=0> > Slack group. > > > > I’m not sure about non-committers. It’s definitely not the place to > > discuss things that belong on the list and I don’t think it’s a good > place > > for additional support channels. > > > > It might be useful for real-time collaboration on getting things > done. For > > that, we should add a royale channel. > > > > I can go either way on that. I already use Slack for other things, > so it’s > > not a big deal for me to add another channel. > > > > Harbs > > > > > On Dec 8, 2019, at 10: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 > > >> > > >> > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcottage14.blogspot.com%2F&data=02%7C01%7Caharui%40adobe.com%7Caffef5ad990842dafcaa08d77c3b5da4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637114466763027979&sdata=cd95m9qwKbAzjGEj8jiz2jPJyxbagifIJvatmNbxNLE%3D&reserved=0 > > >> > > > > > > > > > -- > > > Carlos Rovira > > > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Caffef5ad990842dafcaa08d77c3b5da4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637114466763027979&sdata=jLrU%2B53lVmQfkkkl%2FI0DCMDynkjMKInQd2khRlrgLpE%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%7Caffef5ad990842dafcaa08d77c3b5da4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637114466763027979&sdata=cd95m9qwKbAzjGEj8jiz2jPJyxbagifIJvatmNbxNLE%3D&reserved=0 > > > -- Carlos Rovira http://about.me/carlosrovira
