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. In the following tables there is a summary on how the several attributes are controlled. 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. 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.).Baseline
Level of control
List of Software/Hardware attributes
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 Rucio Release version 
Normal/Standard EGI CAB Service endpoint(s) Registered on GOCDB: RAL-LCG2 (rucio-server.gridpp.rl.ac.uk (ch.cern.rucio))Normal EGI CAB List of attributes not related to software or hardware
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 Rucio Service operators (individuals) Registered on GOCDB RAL-LCG2 (rucio-server.gridpp.rl.ac.uk (ch.cern.rucio))Provider
Old content
History of changes
on applied the following change: https://rt.egi.eu/rt/Ticket/Display.html?id=15834 (RfC Update EGI Check-in OP)
on 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 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 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 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)