Team discussions in gitea?

[Kreyren]

GitHub has a built-in way to allow discussion in between the team members:

Proposing similar integration in Gitea as it allows for a much better coordination in between the team members.

Expected usecase

Proposed primary point of contact for members of The Free Software Foundation Europe - Czechia on https://git.dotya.ml instance tracked at https://git.dotya.ml/fsfe-czechia/fsfe-czechia/issues/1

[Kreyren]

BUG BOUNTY - 10 USD

Submitted bounty: https://www.bountysource.com/issues/96361720-team-discussions-in-gitea

Allowed license: Current gitea's license submitted with commit message Backed-by: Jacob Hrbek <kreyren@fsfe.org>

Bounty submitted as a private citizen.

Qualification for the bounty

Implemented method for team members in Gitea UI to publish a discussion in the team with option for other team members to post comments to that discussion with option to make the discussion visible only to the team members submitted and merged to Gitea https://github.com/go-gitea/gitea.

First merge that implements this grabs the bounty.

---

UPDATE(11/02/2021-EU): Bounty expired, new bounties will be submitted in #14644 for TODO list items.

[buhtz]

I am not sure but I think the "Discussion" feature of GitHub you refering to, is not restricted to teams and organisations. Each repository can have a Discussion section, like in this example
https://github.com/Codeberg-AsGithubAlternative-buhtz/spielwiese/discussions

[Kreyren]

@Codeberg-AsGithubAlternative-buhtz I wanted per-team discussion for complicated projects which have teams dedicated to specific task e.g. Legal team, Quality Assurance Team, etc.. for them to be able to coordinate

For the record i don't want it to be like GitHub as i believe that there is a room for improvement and i've abandoned the merge request as my integration would require rewritting of too much code so i decided to work on my solution in rust instead.

[trymeouteh]

Would like to see this since it will reduce questions being asked under issues since discussions sections will be a place to ask questions.

[qwerty287]

@trymeouteh this issue doesn't address a Github discussions like feature, but a feature to have a discussion possibility inside of teams of orgs (for internal discussions). For GH discussions there isn't a feature request right now, so you can open one

[vhscom]

When I hear the term discussion I think real-time communication. Considering Gitea is joining the Fediverse perhaps there's an opportunity to combine what's good about federated discussions (as on Matrix) with what GitHub created which appears to be more of a Discourse clone.

[HammyHavoc]

Just chiming in to say that I love Gitea, been running it a few years now, and adding interactive email notifications like GitHub has been such an amazing improvement to how we communicate between ourselves.

However, the main downside is that means there's a lot more communication that happens, and at present, it ends up filed away in Issues, and that makes sifting through Issues of ongoing discussion a complete pain in the arse. Would be amazing if/when Discussions happens if we could move Issues to Discussions, and likewise, move Discussions to Issues if a problem emerges in the conversation. Being able to merge existing Discussions into existing Issues would also be brilliant!

[xamidi]

GitHub Discussions essentially provides an option for each repository and organization to have an integrated forum.
Labels and categories can be customized, e.g. one could make it a pure Q&A platform, supplementary documentation, or whatever. For example, Intel limited this forum to polls and design discussions.

By default:

It is a really valuable feature that is still missing from Gitea.

Just imagine this repo would use a forum where stuff can be

1. categorized,
2. voted for, and
3. not pollute issues with requests.

While GitHub Discussions were misunderstood here, the actual thing was apparently requested in #17858.

However, it is still possible to use GitHub Discussions also for the here requested feature, by using locked threads, as long as it is acceptable that everyone has read-access.