# data[].attributes.body
However we prioritise, how do these with it with what other orgs are prioritising. Risk of the the policies we put effort into developing being superseded by parent org.

# data[].attributes.headline
Develop an "IRIS for dummies" explanation of what IRIS is, does and how it's structured

# data[].attributes.subject
Develop an "IRIS for dummies" explanation of what IRIS is, does and how it's structured

# data[].attributes.body
4B: highest priority - IRIS needs to be a long running activity to enable projects to plan in using it with at least a 5yr look ahead. It takes time and effort to deploy to IRIS, hence knowing it exists longer term is vital. (I'm assuming sustainable in the economic context here, not necessarily in the 'green' context)

4D: IRIS needs to be relevant - supporting innovation in the research sense and wider (economic) will ensure that it continues to be relevant and funded

4E: IRIS will evolve, hopefully taking on a wider UKRI level role, hence its governance will need to adapt to reflect that larger role.

4A and 4C are 'normal' work

# data[].attributes.body
all the listed priorities are appropriate

# data[].attributes.body
If IRIS evolves to fill the 'UK academic science cloud' role - how do the IRIS Governance policies align with those of the key resource providers (e.g. DiRAC).

Also - when IRIS becomes the major platform for end user projects in meeting their computational resource demands (processing and disk), then how are potential service level agreements between IRIS and the end user project managed? Should their be formal IRIS representation on the end user projects?

# data[].attributes.body
aligning the mission aims and governance between IRIS, the resource providers, and the end user projects. also the situation with IRIS integration in wider European initiatives (e.g. EGI, EOSC, etc).

# data[].attributes.headline
More action than planning needed for things like security

# data[].attributes.subject
More action than planning needed for things like security

# data[].attributes.headline
Not clear how IRIS mission relates to governance and vice versa

# data[].attributes.subject
Not clear how IRIS mission relates to governance and vice versa

# data[].attributes.body
4A - desperately needed (to inform areas like ops etc.)

4D - formalisation around this needed to avoid wasting resources

4C - so the security people can sleep at night

4B - whatever orgs IRIS interacts with, they'll supersede it on this topic

4E - CI is good, but what does supporting flexibility mean

# data[].attributes.headline
4a: IRIS needs to be able to explain itself to the UK scientific computing community in easy terms.

# data[].attributes.subject
4a: IRIS needs to be able to explain itself to the UK scientific computing community in easy terms.

# data[].attributes.body
Difficult for both potential and existing users (i.e. projects) to know what IRIS does/ is. Potentially exacerbated as different projects interact with IRIS in different way.

# data[].attributes.headline
IRIS needs to make itself part of STFC (or UKRI) strategy

# data[].attributes.subject
IRIS needs to make itself part of STFC (or UKRI) strategy

# data[].attributes.body
Risk that IRIS solves STFC's problems for immediately satisfying computing requirements but isn't a priority in long-term planning.

# data[].attributes.body
Lots of things on policy, but what's the structure? Should this be reviewed for now and looking into the future.

# data[].attributes.body
How these are retired, managed, some way of measuring sustainability etc

# data[].attributes.body
4E: Governance is ever evolving, needs to be always improved and developed - it's a feedback loop.

4D: Innovation is key to IRIS processes, and continues to be important here.

4A: is an "easy win", and does underpin the development of newer resources, and establishes the "status quo"

4C: Central security policy and risk management is more of an operational process rather than governance.

4B: What can IRIS management actually influence/enforce, aside from suggested guidance? Financial motivation?

# data[].attributes.headline
Provide mechanism for new people to contribute to IRIS governance/ operations/ promotion

# data[].attributes.subject
Provide mechanism for new people to contribute to IRIS governance/ operations/ promotion

# data[].attributes.body
Potentially lots of enthusiasm and energy in the wider community for IRIS, which we should try to exploit/ enable.

# data[].attributes.body
Need effort to make it all happen

# data[].attributes.body
(mapped to priorities)

# data[].attributes.body
Potential that every IRIS project has a different relationship with IRIS, which makes it difficult for IRIS to achieve economies of scale and to enable cross-cutting initiatives and, more generally, a roadmap that's relevant to all partners.

# data[].attributes.body
Do not be afraid the stop initiatives/ activities that aren't delivering for IRIS.