Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Services v2 roadmap suggestion -Clarify incident response participation requirement #25

Open
lliming opened this issue Apr 7, 2023 · 0 comments
Labels
services ACCESS-integrated Services Integration Roadmap

Comments

@lliming
Copy link
Contributor

lliming commented Apr 7, 2023

The task "Incident Response and Coordination v1" says

Resource Providers and ACCESS Tracks must follow incident response and coordination procedures as defined in ACCESS’s Incident Response Policy. Representatives from each RP and Track must be identified to participate in the ACCESS Incident Response Trust Group (AIRTG).

So, does this mean operators of ACCESS-integrated services who are NOT also RPs or ACCESS Tracks don’t have anything to do for this task? (I’m thinking from the perspective of Globus or ORCID, for example.) Or, do we want operators of other ACCESS-integrated services to follow the incident response and coordination procedures, too?

@lliming lliming changed the title Services v2 roadmap suggestion - Services v2 roadmap suggestion -Clarify incident response participation requirement Apr 7, 2023
@lliming lliming added the services ACCESS-integrated Services Integration Roadmap label Apr 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
services ACCESS-integrated Services Integration Roadmap
Projects
None yet
Development

No branches or pull requests

1 participant