...
- Check to make sure you have an ICLA on file with Jasig. Check the Completed Contributor Agreements page to make sure your name is listed.
- Contact the project lead or project management committee for the project you need access to. Provide them with the username you use to log in to Jira.
- All users with commit access to any project have access to the sandbox. For sandbox-only access please contact the Incubation Group and request to be added to the
incu-sandbox-developersgroup.
- All users with commit access to any project have access to the sandbox. For sandbox-only access please contact the Incubation Group and request to be added to the
- The project lead then follows the instructions on the How to Manage Groups page to grant access.
...
Jasig uses a single source for users and groups. User's with commit access use the same username and password that the use for Jira and Confluence. If you have multiple Jasig accounts and are unsure which one to use look in the groups listed at the bottom of this page and see if any of your accounts are listed.
Authorization
The following paths have specific authorization restrictions. While anyone with commit access can commit to the root path users should not created new root directories without prior approval of the Jasig Infrastructure Group.
Path | Read Access | Write Access |
|---|---|---|
/ | public | cas-clients-devs |
/cas-clients | public | cas-clients-devs |
/cas-extensions | public | cas-extension-devs |
/cas3 | public | cas-server-devs |
/cas4 | public | cas-server4-devs |
/channels | public | upc-portlet-developers |
/gaps | public | upc-developers |
/jasig-parent | public | jch-service-administrators |
/jch-service-administrators | jch-service-administrators | jch-service-administrators |
/openregistry | public | openregistry-devs |
/person-directory | public | upc-developers |
/portlets | public | upc-portlet-developers |
/resource-server | public | upc-developers |
/sandbox | public | cas-clients-devs |
/uPortal | public | upc-developers |
...