On Wednesday 08 June 2016 01:07 AM, Bastian Blank wrote: > [SN: trimmed Cc list, as this is about what Debian wants] > > Hi Alex > > On Tue, Jun 07, 2016 at 08:06:41PM +0200, Alexander Wirt wrote: >> Its more things like: >> - integration into alioth - aka, how easy is it to integrate the already >> existing identity data (which we want to keep) into the system > > This can be easy (use OAUTH2 against the identity provider) or hard > (convert all data). Also it speaks ldap itself. Does alioth/fusionforge already support becoming an OAUTH2 identity provider? How do other debian services (like nm.debian.org) use alioth login? [1] I found this [2] >> - mapping groups and permissions from alioth to the new system > > Fusionforge also uses a similar group based permission system. > > Okay, there is this (hacked in?) "allow every DD to write" permission > that some groups use, which is only supported by gitlab EE. We'll have to ask gitlab folks if they are willing to provide that in CE. I'm tracking the requirements and possible solutions here [3] [1] https://lists.debian.org/debian-devel-announce/2014/03/msg00008.html [2] https://wiki.debian.org/DebianSingleSignOn#Howto_setup_your_web-app_with_DACS [3] https://wiki.debian.org/Shukra
Attachment:
signature.asc
Description: OpenPGP digital signature