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.

The history of the releases is available here: https://github.com/grycap/im/blob/master/changelog

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. 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
	Major release version				IM Github repository	Normal/Standard	EGI CAB
	Minor release version				IM Github repository	Standard	provider
	Service endpoint(s)				Registered on GOCDB: UPV-GRyCAP (appsgrycap.i3m.upv.es (es.upv.grycap.im))	Normal	EGI CAB
	Major changes in hosting platform causing downtimes				Internal manual procedure	Normal	EGI CAB
	Regular update and maintenance of hosting platform				Internal manual procedure	Normal	provider

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	Attribute...	...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
	Service operators (individuals)				Registered on GOCDB: UPV-GRyCAP (appsgrycap.i3m.upv.es (es.upv.grycap.im))	providers
	TOSCA templates				Controlled in GRyCAP/tosca GitHub repo.	provider