Group/Org functionality #488

Open
opened 2 weeks ago by dyfet · 0 comments
dyfet commented 2 weeks ago

An org is often the container of a group of closely related individual projects. We really should have more functionality to better represent that unifying role. Currently, we only have the ability to have common labels, and common webhooks.

Some examples might include:

Org wiki for common shared content. For example, this would be the perfect place to publish and maintain org common policies and practices.

Org view of total issue counts, merge requests, and other statistics. This kind of functionality already exist "per user".

Org consolidated "global" view and access to all merge requests and issues from the individual projects. This actually is something found in gitlab.

I am sure in this theme other ideas could be generated. Presumably they should then be seperated into individual proposals and tickets. This is more an overal design and discussion ticket, and likely specific individual ideas should then be taken to gitea upstream.

An org is often the container of a group of closely related individual projects. We really should have more functionality to better represent that unifying role. Currently, we only have the ability to have common labels, and common webhooks. Some examples might include: Org wiki for common shared content. For example, this would be the perfect place to publish and maintain org common policies and practices. Org view of total issue counts, merge requests, and other statistics. This kind of functionality already exist "per user". Org consolidated "global" view and access to all merge requests and issues from the individual projects. This actually is something found in gitlab. I am sure in this theme other ideas could be generated. Presumably they should then be seperated into individual proposals and tickets. This is more an overal design and discussion ticket, and likely specific individual ideas should then be taken to gitea upstream. <!-- NOTE: If your issue is a security concern, please send an email to contact@codeberg.org (and if related to Gitea also to security@gitea.io) instead of opening a public issue. Thank you. Welcome to the Codeberg Community Tracker. This is the right place for bug reports, feature requests and feedback. It's the central place where we track progress and discuss, so please open issues here unless you are sure it's directly related to a specific Codeberg product and only some contributors there need to join the discussion. Easy rule: If you are unsure, report it here. When reporting bugs or asking for features in the software itself, please understand that Codeberg is a fork of Gitea. Please always check upstream (→ see FAQ) if your there is already an open issue. If not, you'd really help us if you could directly get in touch with the maintainers and open an issue here if you think a wider audience should know about that (e. g. when discussing hotfixes, backports or when discussing whether some feature should become part of Gitea or a Codeberg "add-on"). If you don't have a GitHub account, please mention this and we'll gladly forward your report to the Gitea maintainers. Thank you for reporting your findings and giving feedback on Codeberg. ## Some FAQ: ### What does upstream mean? Upstream refers to Gitea, the software Codeberg is built upon. If we ask you if you can report upstream, please visit https://github.com/go-gitea/gitea/issues and check for the bug there and report elsewise. It's usually good if the person interested in a feature or bugfix opens the request to react to questions and join the discussion. We would usually just fire the report, but won't find the time to properly react to that ... **If you do not have a GitHub account**, just tell us and we'll happily forward the report for you. ### I just noticed a typo in the sign_up / sing_up route when regis... No, this is not a typo, but intentional. It was a quick fix to avoid spammers targetting our instance and it actually worked out quite well to rename the route from sign_up to sing_up (few people notice, nice to see you have sharp eyes) ... we might have to take more effective countermeasures in the future, but for now we're actually quite good with that one ... ### How can I help? If you want to help improving Codeberg as a community home for software development, we'll gladly welcome your contribution. Check out the docs about improving Codeberg https://docs.codeberg.org/improving-codeberg/ and have a look at the open issues, especially those that are looking for contribution https://codeberg.org/Codeberg/Community/issues?state=open&labels=105 - some of them don't even require much coding knowledge. We are also happy if you forward bug reports to Gitea if the original author hasn't done that yet or hasn't got a GitHub account. -->
fnetX added the
enhancement
label 1 week ago
fnetX added the
gitea-related
label 1 week ago
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.