[CentOS-devel] [scl.org] CentOS SCLo SIG sync-up meeting on #centos-devel (2015-11-25)

Wed Dec 2 12:33:27 UTC 2015
Fabian Arrotin <arrfab at centos.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 27/11/15 10:42, Dominic Cleal wrote:
> On 24/11/15 12:15, Honza Horak wrote:
>> * review new-SIG-member process (make approval part more
>> concrete)
> 
> I don't think this was discussed in the end, but how would I become
> a member at the moment?  As per 
> https://www.redhat.com/archives/sclorg/2015-November/msg00021.html
> I'm interested in creating a new SCL under the SIG.
> 
> Initially I'd like to start by creating a wiki page to plan it
> under https://wiki.centos.org/SpecialInterestGroup/SCLo, which I
> don't have permissions to do, and would assume I need to be a
> member before I'd get edit access to that part of the wiki.
> 
> It'll be a little while before I'm interested in building in CBS,
> but I'll also raise bugs for access and to create tags which
> appears to need SIG membership.
> 
> Cheers,
> 

So,

For the koji/CBS access, we'll migrate tomorrow the authentication
backend, so once done (all current accounts being
migrated/tested/validated), we'll announce it publicly, and we'll
change the documentation according to the new setup.

So there is no need to create a bug report actually, but rather wait
some days so that we can have migrated, and then create yourself your
account. Then, once a week, we'll review the people who have asked to
be member of a SIG group, and we'll sync with the SIG Chair so that he
can confirm with a +1 or -1, and then "sponsor" the user in the
according Group (for a +1).

More infos to come (very) soon for that

For wiki access, it's still using its own auth backend, so you have to
create your username (FirstnameLastname as convention) and ask for
permissions to be granted (through a mail to the centos-docs list :
https://lists.centos.org/mailman/listinfo/centos-docs)

Does that answer your question(s) ?

- -- 
Fabian Arrotin
The CentOS Project | http://www.centos.org
gpg key: 56BEC54E | twitter: @arrfab
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iEYEARECAAYFAlZe5RcACgkQnVkHo1a+xU6x9wCfZMF26P7romPSehJRbSmW0STx
zb4An3yGle6mJPXObNzHZkvtrNCrzQ16
=q1au
-----END PGP SIGNATURE-----