lsl_archived
lsl_archived copied to clipboard
sccn
LSL dev/support - Discord or Slack?
@dmedine @mgrivich @tstenner
I'll set one up. Do we have a preference between Discord or Slack?
I vote for Slack because I have to be in there everyday anyway, but I also use Discord occasionally so it's not a big deal to me either way (I actually prefer the Discord interface).
Is Github Teams an option? Otherwise I'd prefer slack for better CI integration
@tstenner , I'm not sure we're on the same page.
I was looking for a solution for us to chat in real-time with each other and in a separate channel with users. Sometimes, as can be evidenced by our long discussions on issue pages, it makes more sense to do real-time chatting to help clarify what a problem is before we start to solve the problem. A lot of that clarification doesn't need to go in the issues tracker.
We don't want to lose the valuable public information that is preserved in the issues trackers so we'll have to be vigilant about requiring ourselves or the users with the problems to create an issue on GitHub containing the correct information.
I've setup a Slack: [email protected] Tristan, I don't have your e-mail so I wasn't able to invite you directly. Try to join then I'll be sure to invite you into the appropriate channel(s).
I've registered, but can't join (or request permission to join). Could you invite [email protected]?
I will invite you now, but you can also auto-join with this link. We only need to keep the #developers channel private, but the #users or #general channels can be public.
Tristan and I have been using Slack a little for chatting and so far I've helped one user. It'd be great if some of the other devs could join, especially to join in the discussion about what would be the best ways to deploy LSL. @dmedine @mgrivich
