...
Policies
Lots of questions / concerns around policies (e.g. who’s eligible for an account? When can we restrict somebody? When can we reset a password? Etc. etc).
Policies will need to be approves by EC, suggestion is to have a ACCESS Policy sub-committee to reduce the bottlenecking. Also, consent agendas will be used at the EC level.
In this start-up phase, it may be necessary to adopt an existing XSEDE policy as a provisional ACCESS policy, that is subject to a more detailed review and approval.
Acceptable Use Policy is an important high-priority policy for ACCESS. XSEDE AUP is here.
Code of Conduct is another important policy.
XSEDE Event Code of Conduct (to be linked)
XSEDE-to-ACCESS Policy review/creation/transfer
XSEDE to provide a list of policies in functional areas
ACCESS tracks to provide list of policies needed
Is there a repository of existing XSEDE policies?
There is a set of policies on the XSEDE Staff Wiki, however, it is likely incomplete. Requests for existing policies should be included during XSEDE-to-ACCESS transfer activities/discussions.
Will they automatically be adopted? No, EC approval needed
Who will compile / maintain a list / repo of them?
Who decided which track is responsible for which ones?
Terminology Task Force (TTF)
How will this be carried on through ACCESS? The ACCESS program has not decided to continue the TTF effort. This needs to be discussed at the EC level.
...