Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Privacy Settings [Overview] [Discusion] #8517

Open
6543 opened this issue Oct 15, 2019 · 1 comment
Open

Privacy Settings [Overview] [Discusion] #8517

6543 opened this issue Oct 15, 2019 · 1 comment
Labels
type/enhancement An improvement of existing functionality type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@6543
Copy link
Member

6543 commented Oct 15, 2019

Thiss issue colect Privayc related Issues to get the big Picture ...

The main concept wich came in mind to me is a user-setting-page wich the user can decide wich scope as acces to his data and wich data ...

this sould be also in scope of GDRP compliance

Scopes: [Public] [Local Users] [Following Users] [Private]

Afected data:

  • User Provile: E-Mail, Folowing, Stared Repos, Watched Repos, Webiste, Location, Last Login, Created
  • Heatmap
  • aktivetys: comment on issue, push/pull, create repo ...

few things are hard and pointles to hide ... but the api can be restricted so if somebody realy like to get the info he has to get it by hand

@6543 6543 changed the title Privacy Settings [Overview] Privacy Settings [Overview] [Discusion] Oct 15, 2019
@guillep2k
Copy link
Member

I think it depends whether a particular Gitea instance is governed by an authority that is also the authority for all the repositories it contains, or Gitea needs to address some degree of privacy for the individual users. I mean, Github has 100% control over my repos, but it's kind of a shadow entity and I "have control" over them repos. In my job, all the repositories are my company's, whether privately created by an employee or for a company project, etc.

What I mean is: many settings we're developing depend on the almighty admin to set them in app.ini, but in reality users might have different opinions about them and may want to control their values independently.

@lunny lunny added type/enhancement An improvement of existing functionality type/proposal The new feature has not been accepted yet but needs to be discussed first. labels Oct 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/enhancement An improvement of existing functionality type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

No branches or pull requests

3 participants