GNOME Accounts - Introducing Automation

--===============7223623793351325756==
Content-Type: multipart/alternative; boundary="0000000000001ceae805e8c80a76"

--0000000000001ceae805e8c80a76
Content-Type: text/plain; charset="UTF-8"

Hello,

As we discussed during GUADEC and as many of you know, processing new and
existing GNOME account changes has been a manual action for many years now.
With the introduction of OCP, GitLab CI/CD, IPA and SSO, we wanted to
enable GNOME contributors and developers to fulfil their needs in total
autonomy and freedom without requiring interventions from our side when it
came to provision resources or build/test GNOME software.

With that in mind we're happy to announce new and existing GNOME account
changes are now processed via automation.

How it works
---

When visiting [1] you will be shown an issue template composed of some
documentation on top and a json dictionary. The only field that requires an
update is the json dictionary, the following format should be used:

action can be any of:

1. new_account
2. git_access
3. master_access
4. update_email

While the module key should be the name of any GNOME module as found within
[2], the module key should only be specified with the new_account,
git_access, master_access actions.

The title of the issue should be: "Account request".

Other key takes when selecting the new_account action:

1. Your name, surname and username will be computed out of your full name
as found in your GitLab profile
2. The registered email on your account will be the one of your GitLab
profile

Other key takes when selecting the update_email action:

1. The email that will be synchronized with IPA is the primary one you have
registered on your GitLab account, please make sure that one is up-to-date

What automation will take care of:

1. Generate your account information and allow the Accounts team to verify
compliance, also add necessary labels
2. Mail individual existing GNOME module maintainers and have them
acknowledge your new or existing GNOME account request
3. Once all the verifications have happened, automation will create your
account or update it with additional permissions
4. Close the issue and turn the confidential flag to on once the full
process has completed

Please let us know any feedback you may have, for any bug report please use
[3].

Once an initial phase of testing has happened, the idea we have is
introducing the same automation within the GNOME Foundation Membership
Committee as well during the coming months.

Thanks!

[1]
https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/new?issuable_template=account-request
[2] https://gitlab.gnome.org/GNOME
[3] https://gitlab.gnome.org/Infrastructure/Infrastructure/issues


-- 
Cheers,
Andrea

Principal Systems Engineer at Red Hat,
GNOME Infrastructure Team Coordinator,
Former GNOME Foundation Board of Directors Secretary,
GNOME Foundation Membership & Elections Committee Chairman

Homepage: https://www.dragonsreach.it

--0000000000001ceae805e8c80a76
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello,<div><br></div><div>As we discussed during GUADEC an=
d as many of you know, processing new and existing GNOME account changes ha=
s been a manual action for many years now. With the introduction of OCP, Gi=
tLab CI/CD, IPA and SSO, we wanted to enable GNOME contributors and develop=
ers to fulfil=C2=A0their needs in total autonomy and freedom without requir=
ing interventions from our side when it came to provision resources or buil=
d/test GNOME software.</div><div><br></div><div>With that in mind we&#39;re=
 happy to announce new and existing GNOME account changes are now processed=
 via automation.</div><div><br></div><div>How it works</div><div>---</div><=
div><br></div><div>When visiting [1] you will be shown an issue template co=
mposed of some documentation on top and a json dictionary. The only field t=
hat requires an update is the json dictionary, the following format should =
be used:=C2=A0</div><div><br></div><div>action can be any of:</div><div><br=
></div><div>1. new_account</div><div>2. git_access</div><div>3. master_acce=
ss</div><div>4. update_email</div><div><br></div><div>While the module key =
should be the name of any GNOME module as found within [2], the module key =
should only be specified with the new_account, git_access, master_access ac=
tions.</div><div><br></div><div>The title of the issue should be: &quot;Acc=
ount request&quot;.</div><div><br></div><div>Other key takes when selecting=
 the new_account action:</div><div><br></div><div>1. Your name, surname and=
 username will be computed out of your full name as found in your GitLab pr=
ofile</div><div>2. The registered email=C2=A0on your account will be the on=
e of your GitLab profile</div><div><br></div><div>Other key takes when sele=
cting the update_email action:</div><div><br></div><div>1. The email that w=
ill be synchronized with IPA is the primary one you have registered on your=
 GitLab account, please make sure that one is up-to-date</div><div><br></di=
v><div>What automation will take care of:</div><div><br></div><div>1. Gener=
ate your account information and allow the Accounts team to verify complian=
ce, also add necessary labels</div><div>2. Mail individual existing GNOME m=
odule maintainers and have them acknowledge your new or existing GNOME acco=
unt request</div><div>3. Once all the verifications have happened, automati=
on will create your account or update it with additional permissions</div><=
div>4. Close the issue and turn the confidential flag to on once the full p=
rocess has completed</div><div><br></div><div>Please let us know any feedba=
ck you may have, for any bug report please use [3].</div><div><br></div><di=
v>Once an initial phase of testing has happened, the idea we have is introd=
ucing the same automation within the GNOME Foundation Membership Committee =
as well during the coming months.</div><div><br></div><div>Thanks!</div><di=
v><br></div><div>[1]=C2=A0<a href=3D"https://gitlab.gnome.org/Infrastructur=
e/Infrastructure/issues/new?issuable_template=3Daccount-request">https://gi=
tlab.gnome.org/Infrastructure/Infrastructure/issues/new?issuable_template=
=3Daccount-request</a></div><div>[2] <a href=3D"https://gitlab.gnome.org/GN=
OME">https://gitlab.gnome.org/GNOME</a></div><div>[3] <a href=3D"https://gi=
tlab.gnome.org/Infrastructure/Infrastructure/issues">https://gitlab.gnome.o=
rg/Infrastructure/Infrastructure/issues</a><br><br clear=3D"all"><div><br><=
/div>-- <br><div dir=3D"ltr" class=3D"gmail_signature" data-smartmail=3D"gm=
ail_signature"><div dir=3D"ltr"><div>Cheers,</div><div>Andrea</div><div><br=
></div><div>Principal Systems Engineer at Red Hat,<br></div><div>GNOME Infr=
astructure Team Coordinator,<br></div><div>Former GNOME Foundation Board of=
 Directors Secretary,</div><div>GNOME Foundation Membership &amp; Elections=
 Committee Chairman</div><div><br></div><div>Homepage: <a href=3D"https://w=
ww.dragonsreach.it" target=3D"_blank">https://www.dragonsreach.it</a></div>=
</div></div></div></div>

--0000000000001ceae805e8c80a76--

--===============7223623793351325756==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
foundation-list mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/foundation-list

--===============7223623793351325756==--