rework permission article #204

Closed
opened 4 months ago by fnetX · 4 comments
fnetX commented 4 months ago
Collaborator

I think the article about (repo / org / team) permissions is outdated as of Gitea 1.16. Someone should check that it's still correct, or update it accordingly.

I think the article about (repo / org / team) permissions is outdated as of Gitea 1.16. Someone should check that it's still correct, or update it accordingly.
fnetX added the
Kind: Documentation
Priority: High
labels 4 months ago
fnetX added the due date 2022-03-09 4 months ago
fnetX modified the due date to 2022-03-17 from 2022-03-09 4 months ago
Collaborator

@fnetX The problem with the current page is that team permissions were updated to allow each "unit"(issues, code, wiki etc.) to have a different permission level. A certain team could have only write permissions to issues but have no access to other the units.

As for repo colloborates the page is still up-to-date, so it would only need to include a new section? for these unit permissions, as they are quite configurable and can really differ from the default permissions.

@fnetX The problem with the current page is that team permissions were updated to allow each "unit"(issues, code, wiki etc.) to have a different permission level. A certain team could have only write permissions to issues but have no access to other the units. As for repo colloborates the page is still up-to-date, so it would only need to include _a new section?_ for these unit permissions, as they are quite configurable and can really differ from the default permissions.
Poster
Collaborator

Yeah, I know. TBH, when I opened this issue, I expected that more stuff was changed upstream, but when writing the blog post I noticed it's not so much that needs changing. Still, I hope someone else finds the time to write about this. But recently, we haven't received much from the community, especially for the docs 🤷

Yeah, I know. TBH, when I opened this issue, I expected that more stuff was changed upstream, but when writing the blog post I noticed it's not so much that needs changing. Still, I hope someone else finds the time to write about this. But recently, we haven't received much from the community, especially for the docs 🤷
Collaborator

Still, I hope someone else finds the time to write about this. But recently, we haven't received much from the community, especially for the docs 🤷

I will have a 👀 , codeberg is hosting my personal projects and my horrible code. The least I can do 😄

> Still, I hope someone else finds the time to write about this. But recently, we haven't received much from the community, especially for the docs 🤷 I will have a 👀 , codeberg is hosting my personal projects and my horrible code. The least I can do 😄
Poster
Collaborator

Thank you. Anyway, you are already contributing to Gitea, which is probably worth more than hosting a few MB of content 😉

Thank you. Anyway, you are already contributing to Gitea, which is probably worth more than hosting a few MB of content 😉
fnetX referenced this issue from a commit 4 months ago
fnetX closed this issue 4 months ago
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date

2022-03-17

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.