•  
     
    story #8419 have permissions per tags/branches
Summary
git admin
have permissions per tags/branches
Empty
  • Introduce new UI to manage branches and tags (cf. epic "mockups")
    • Warning: this is designed for a few elements (~10 branches/tags) not to handle 100 or 1000 permissions
    • Warning: the UI component to use (selectbox, multi, etc) are not yet defined
  • Store permissions in DB
  • Serialize permissions in Gitolite
  • At activation, the permissions defined in "RW" and "RW+" selectbox are used as default values, for instance "Write" for Developers and "Rewind" for Integrators would become
Branches
--------

Pattern |   Write    |       Rewind     |
--------|------------|------------------|
   *    | Developers |   Integrators    |
   
Tags
----

Pattern |   Write    |       Rewind     |
--------|------------|------------------|
   *    | Developers |   Integrators    |
  • At desactivation (ie if git admin no longer want to use per tag/branch permissions), the admin cannot save the configuration if she doesn't select at lease one group for "Write" and "Rewind" selectbox (can be Nobody)

Then check everything is properly used in:

  • repository update
  • repository creation (use of project template)
  • fork
  • grokmirror
Empty
Yannis ROSSETTO (rossettoy)
Status
Empty
Done
Development
  • [ ] Does it involves User Interface? 
  • [ ] Are there any mockups?
  • [ ] Are permissions checked?
  • [ ] Does it need Javascript development?
  • [ ] Does it need a forge upgrade bucket?
  • [ ] Does it need to execute things in system events?
  • [ ] Does it impact project creation (templates)?
  • [ ] Is it exploratory?
Empty
Details
#8419
Manuel Vacelet (vaceletm)
2016-06-24 17:32
2015-09-16 10:52
8545

References

Follow-ups