Slack, Discord, other

[joshbruce]

Marked version: 0.3.17

Proposal type: other (communication and collaboration)

What pain point are you perceiving?

See comment from @intcreator for context.

If you want a faster, more general team communication platform, you can start a Discord server. If you're not familiar with Discord, it's kind of like Slack except there are unlimited text messages for free (instead of 10k) and unlimited team voice calls.

What solution are you suggesting?

I tend toward Slack. Not being too concerned about archived things. There are 7 practitioners in 8fold right now, and have never really needed the history or archives. I think for more static referential things, they should end up on GitHub somehow either as an Issue or PR.

These platforms we be more for rapid communication across all the contributors (anyone willing to register to the group in this case).

[UziTech]

Why not use github discussions

• They are free
• No need to sign up for something else
• They integrate with GitHub pretty well
• No need to have another set of notifications

[joshbruce]

@UziTech: Are they limited to the committers?

I didn't have a chance to look into them in depth. Thinking of instances where contributors, who aren't part of the committers (@Feder1co5oave now, @intcreator, and @davisjam, for example) and just want to ask a quick question (that doesn't necessarily need to go through the overhead of creating a GitHub issue).

[intcreator]

Maybe we can try out GitHub discussions to see what features they offer?

[UziTech]

@joshbruce Ya I think it would be limited to markedjs members

[joshbruce]

@UziTech: Thanks for the confirmation. Other question is, do we think we have the ability to keep up??

From a product perspective, I think it could go a long way to helping us hear more from users who are interested enough to at least sign up for the group. (That's been a serious pain point for me...how do I increase stakeholder reach out and feedback.)

Maybe something we could start, but not really advertise and go from there. For rationally selfish reasons I would go for Slack - my day job is there, 8fold is there, the design system groups I'm part of, and Vapor...it's nice having one app.

We could even do GitHub integrations. Maybe let some of us unsubscribe from email notifications - this was a pain point expressed by Feder1co5oave and confirmed by others re the updates I was making last week.

Also, hooked him up with the email rules I use to keep my sanity.

---

On the notification front, I don't know what email client you have, but here are my rules for dealing with all things GitHub (it has saved my skin! - and sanity) - subscriptions across the board actually (this is Mail for macOS):

1. I don't have email notifications turned on - I go to it when I want to, not when it gets all up in my face. See Randy Pausch on Time Management. "Notifications are interruptions" [and I got stuff to do]. 😉
2. Here's the rule (if all of the following are true):

• If "from" contains "@github.com" (all the GitHub emails)
• If "subject" contains "[account]/[repo]" (all the ones from that repo)
• If "Message content" does NOT contain "@joshbruce" (not explicitly for me, woohoo!)
• Then "Move message" to mailbox: "[repo specific mailbox]"

3. I have a day where I do most of my planning and whatnot per week, as part of that, I go through and catch up on all the conversations I might have missed that I may or may not want to comment on. See The Seven Habits of Highly Effective People (specifically "sharpening the saw" - but it's a good read - at least I thought so), Getting Things Done, and The Pomodoro Technique (I have the PDF for when this was still being market tested before it became a commercial product, if you would like).