Baseline

As baseline we use the Request for Change (Jira tickets) created any time the suppliers announce a new release of their services. In the tickets it is reported the date when a given change has been implemented and the version. The links in the table point to the Jira project where the tickets are collected by the "component" field.

Level of control

In the following tables there is a summary on how the several attributes are controlled.

List of Software/Hardware attributes

The changes affecting some of the attributes in the table below are not in the CHM scope because they are controlled in a federated way. For us transparency means either that the information is stored and maintained on GOCDB or that we are notified by email about any change.

Service component	Attribute...	...under direct EGI Foundation control	...controlled by suppliers, whose changes need the EGI F. approval	...where EGI F. must have transparency	Procedure / How it is controlled	Type of EGI CHM change	Approving body
Check-in	Release version					Normal/Standard	EGI CAB
	Service endpoint(s)				Registered on GOCDB: GRIDOPS-CheckIn	Normal	EGI CAB

List of attributes not related to software or hardware

The associated attributes in the table below are not software-related and they are controlled by the EGI Federation in other ways (infrastructure procedures, management boards, etc.).

Service component	Attributes...	...under direct EGI F. control	...controlled by suppliers, whose changes need the EGI F. approval	...where EGI F. must have transparency	Procedure / How it is controlled	Approving body
Check-in	Service operators (individuals)				Registered on GOCDB GRIDOPS-CheckIn	Provider
	registration/de-registration of external IDPs (not available via eduGAIN) and external SPs, Community AAI IdPS, Infrastructure Proxy SPs				https://docs.egi.eu/providers/check-in/idp/ https://docs.egi.eu/providers/check-in/sp/	provider
	registration/de-registration of IdPs and SPs already belonging to the federation				https://docs.egi.eu/providers/check-in/idp/ https://docs.egi.eu/providers/check-in/sp/	provider
	adding/removing COmanage VO groups				PROC13 VO Deregistration PROC14 VO Registration Managed within Check-in	Operations

Old content

History of changes

on 09 Jul 2019 applied the following change: https://rt.egi.eu/rt/Ticket/Display.html?id=15834 (RfC Update EGI Check-in OP)

on 03 May 2019 applied the following change: https://rt.egi.eu/rt/Ticket/Display.html?id=15687 (RfC Upgrade EGI Check-in COmanage Registry to version 3.1.1)

on 28 Sep 2017 applied on aai.egi.eu the following change: https://rt.egi.eu/rt/Ticket/Display.html?id=13650 (RfC: New REST API for managing VO membership information through CheckIn)

on 28 Jul 2017 applied on aai.egi.eu the following change: https://rt.egi.eu/rt/Ticket/Display.html?id=13354  (RfC: Allow the use of ssh-public keys to obtain RCauth proxy certs from the EGI Master Portal)

on 10 Jul 2017 applied on aai.egi.eu the following change: https://rt.egi.eu/rt/Ticket/Display.html?id=13179 (Provisioning of VOMS information through SAML and OIDC interfaces) (v. 17.07.1)