The following template is used to track membership applications to give the GeGC a clear overview of the steps that have been followed before proposing a new member.
Candidate Name | Federation X |
---|---|
OTRS Ticket Number | TT#XXXXXXX |
Steps | Requirements | Actions | Owner | Notes |
Step 1: Initial application | Candidate NRO sends application in to help@eduroam.org. |
| ||
Step 2: eligibility check - NRO | Assure that due diligence has been done and that the candidate is an appropriate NRO. |
| As eduroam only allows one roaming operator per region, a clear process is needed to determine which organisation will be accepted. This process is currently unclear regarding who makes this decision / recommendation. All eligibility discussions should be via the helpdesk to ensure we have evidence of the process taken | |
Step 3: Technical check / pilot phase | Ensure that the candidate has the technical capacity to operate in the region / territory and that there is capacity to grow the service. |
| What are the criteria that says that an NRO has “passed” the pilot phase? What other technical checks? | |
Step 4: Signing of Compliance Statement | Ensure that policy requirements are met |
| Where do we want to store compliance statements? Should this be in monitor? | |
Step 5: GeGC approval | Ensure that the community accepts the member and the process followed |
| Not restrict it to GeGC meetings. Approval could be done via email? | |
Step 6: formal notification of acceptance | Prepare candidate to be production ready |
|