opening up and expanding.

Bohuslav Kabrda bkabrda at redhat.com
Tue Jul 2 08:39:20 UTC 2013


----- Original Message -----
> On Tue, 18 Jun 2013 00:48:51 -0400
> seth vidal <skvidal at fedoraproject.org> wrote:
> 
> > Sgallagh suggested opening up the current functionality of coprs to
> > proven packagers - to discover more bugs and to help us figure out
> > what else is needed.
> > 
> > I'd like to suggest two things:
> > 
> > 1. open up what we have to provenpackagers as sgallagh suggested
> > 
> > 2. setting up a second 'dev' instance so we can test there before
> > rolling over into the more public instance. - Also it will help us
> > verify the setup process.
> > 
> > I can easily setup a be and fe dev instances in the private openstack
> > cloud we have setup. It would also let us refresh those instances and
> > be sure we're still functional.
> > 
> 
> I've been talking with patrick uiterwijk about the openid teams
> extension for python. Once that is in place we will be able to specify
> group memberships for users who can log in and use the copr instance(s)
> we have setup.
> 
> -sv

How exactly will this work? The information will be available in the extra info that OpenID can ask for when authenticating?

-- 
Regards,
Bohuslav "Slavek" Kabrda.


More information about the copr-devel mailing list