4 ms·

How does it compare to a forum, such as a discourse instance?

• j4yav 5y ago
  A forum has a topic thread that can be nice for having a discussion, but we pair that discussion thread with an artifact (a documented decision or other outcome) that everyone collaborates on during the discussion. It's relatively bare-bones when it comes to that artifact for now, but once we find more users we want to work with them to make a series of custom artifact types that really support that collaborate, async way of working.
  • derekzhouzhen 5y ago
    I see. So you want to go deeper into the workflow, to become something like a issue tracker or a ticketing system?
    • j4yav 5y ago
      Something like that, you could say a ticketing system for decisions and that wouldn’t be too far off. Tickets are good for work items, and we are trying to build something like that but for larger discussion topics that have a decision at the end. We use it to build the product itself, and we use GitHub issues to track features we are going to build, AsyncGo for discussions we need to have, and don’t use Slack at all.. just Google Chat for rare quick pings. We have a few discussion threads going in AsyncGo at a time, and it’s nicer than chat because you have a persistent context, a clear due date, and can engage with the topic when you want to focus on it instead of as they happen in Slack.