svn usage
This page documents the use of the Jasig svn repository for incubation as well as other less formal collaboration. We don't want to burden svn structure unnecessarily. For incubation status the wiki and jira will be the primary source of information including the status of a project or other work. For all other svn artifacts the wiki should have information including status.
When a project is accepted for incubation it becomes eligible for wiki, mailing lists, jira and svn. Outside of incubation Jasig may enable collaboration by granting community members access to these resources as well. There is a shared subversion area called sandbox which can hold artifacts with a variety of statuses.
sandbox will be retained
sandbox - one space for many types of "stuff"
- Sandbox is experimental. There are not necessarily any expectations for future of the work.
- Sandbox can be used to initiate collaborative work on a portlet or other work that sooner or later requests incubation.
- Artifacts can be in sandbox during incubation. There is no need to require work to be moved to a different svn location for incubation.
- Once out of incubation work would definitely need to move to either a new existing non-sandbox svn directory
- Sandbox can contain contributions that are not active but might be useful to others
Information about files in the sandbox svn area should be on the wiki. If there is no status or other information on the wiki then svn files may be removed.
contrib - to be retired (removed after contents transferred to sandbox)
The existence of 2 directories for similar purposes has proved to be confusing. We have decided to consolidate all the files and directories in sandbox and put the burden for documenting status or intention on the wiki.
Other directories
- new repo directories will be created for newly incubating non-portlet projects
- portlets - the svn repo for sponsored portlets under governance of uP steering committee