You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apologies for raising this issue here, but I couldn't find a suitable repo to make this request.
I think it would be nice to enable organization-level discussions (docs). This would help GitHub users discuss Framework laptops in a general location, which might not be related to a single repository. For example usage, the GitHub organization accomplishes this by making a repository called "community" the main discussions location.
This request is partially resolved by the existing community.frame.work site, but org-level GitHub discussions can:
Allow users with existing GitHub accounts to discuss with each other
Allow for a space that, while not specific to an individual Framework repository, is specific to GitHub users who are interested in Framework
The text was updated successfully, but these errors were encountered:
I definitely understand the ask, but as a small team we are very constrained on bandwidth to monitor and moderate multiple communities. Even with our Community Forum and Discord, we are stretched thin. We'd like to keep general discussions centralized to the Community Forum.
Anyway, I was hoping to have that central location so that I could ask if you'd be willing to set your organization up for GitHub Sponsorships. I really love your product and mission, and was hoping to provide just a little bit of extra support 🙂
Apologies for raising this issue here, but I couldn't find a suitable repo to make this request.
I think it would be nice to enable organization-level discussions (docs). This would help GitHub users discuss Framework laptops in a general location, which might not be related to a single repository. For example usage, the GitHub organization accomplishes this by making a repository called "community" the main discussions location.
This request is partially resolved by the existing community.frame.work site, but org-level GitHub discussions can:
The text was updated successfully, but these errors were encountered: