The best place for AgentOS discussions?

[andyk]

These are the options I can think of for how to manage general discussions by committers, users, or any community member:

1. Use the Discussions feature inside the agentos repo, similar to how we are currently using the Discussions feature to capture discussions surrounding design_docs.
   • advantages: is similar to how we use Discussions in the design_doc repo. Can convert issues to discussions if they fit better there. GitHub integration is nice: Easy to reference by ID in other discussions, issues, etc. (e.g., this is The best place for AgentOS discussions? #106); Seamless integration with the GitHub mobile app and GitHub Notifications (so participants can get updates via emails); Can mark some responses as answers; Can pin important discussions.
   • disadvantages: does not support private discussions. Is scoped to the agentos repo, so not as intuitive to have discussions about other repos (e.g., the design_docs repo or other future ones we add). Have 2 (eventually n?) places where discussions can live, one per repo.
2. Use the Discussions feature within a GitHub team called Dev (teams exist at the AgentOS Github Organization level, above the individual repos) and the associatd team discussion feature. That's what this comment is using.
   • advantages: the org-level scope more closely resembles the generic-ness of a devs or users mailing list. Same Github integration issues as option 1 above (can still reference issues/discussions in a repo via the org_name/repo_name#NUM syntax).
   • disadvantages: List membership is limited to organization members, which cost $4/mo per seat currently. It can be confusing to have to juggle 2 areas where Discussion threads can live (in agentos repo and design_docs repo)
3. The classic way projects handle discussion threads is via email lists. We could create a google group [email protected] (or a list that we manage ourselves at [email protected]), and eventually a users list too.
   • advantages: Email is a well known communication pattern by devs. Mailing lists are a standard for open source projects
   • disadvantages: Doesn't fit into current strategy of using GitHub as our one-stop-shop for project process/tooling. email lists don't thread things as nicely and don't have all of the benefits of GitHub integrations listed on item 1 above (e.g., don't allow nice @mentions, convenient links/refs, etc.)
4. Set up a free Slack org
   • advantages: real-time conversations are nice, good threading, etc.
   • disadvantages: a bit heavyweight, have to pay eventually to see history. No GitHub integrations.

I propose we use option 1 for all public discussions, and option 2 for private discussions amongst committers.

Thoughts?

[andyk]

@nickjalbert @trush any thoughts?