Dissemination
We want to have a policy of openness, we'd like the whole migration process to be transparent with the ability for an arb to find out what were doing at any given time.
Websites
There will be 2 main disseminaton routes:
- OUCS public website - open public access no restrictions
Weblearn wiki - publicly readable, authenticated write access
OUCS Public Website
We will place executive summaries of all progress under: http://www.oucs.ox.ac.uk/ltg/
Weblearn wiki
This will be opened up for public read access. Writing will only be possible for people with usernames; we control these usernames. It is also possible for us to enforce extra access control on a page by page basis for material that is sensitive. We should be sparing with this sort of access control though.
News Feeds
The following dedicated newsfeeds are available
- oucs/weblearn-news
- oucs/weblearn-update
Also, our instance of JIRA should generate RSS feeds.
We could also use:
- oucs/its3-news
- oucs/ltg-websitenews
- oucs/news
- oucs/services
Maillists
The following dedicated mail lists are available
sakai-discuss@maillist.ox.ac.uk - currently unpopulated 18/07/2007. To be used for discussing Sakai!
wl-manage-announce@maillist.ox.ac.uk - list for announcement of Weblearn issues
wl-discuss@maillist.ox.ac.uk - weblearn managers discssion list. To be honest not a great deal of discssion happens here!
We could also use:
tetraelf-all@jiscmail.ac.uk - currently unpopulated 18/07/2007
Issue Tracker
In keeping with the policy of openness, we want a publicly readable issues tracker. (This has been a issue we have not been able to resolve with Weblearn; the OUCS hosted RT service is OK as far as it goes but it is only available for OUCS staff members.)
After a fair amount of research we have decided that we wish to use Jira as our issue tracker: http://www.atlassian.com/software/jira/ . This suits our needs and is cheap but the big drawback is that the Helpdesk will not be obliged to support its use. (However, the Helpdesk wouldn't talk to staff or students about RT either as it is not visible outside of OUCS!)
Jira is generally accepted to be one of the best issue trackers around and integrates well with Eclipse and Mylyn. We intend to make Jira one of the central cornerstyones of our development process: "if it ain't in Jira it won't get done" would be our motto. We will be linking each Jira entry to the code modifications that it defines (or equivalent). There is a separate page all about our use of Jira.
Code Repository
We will use SYSDEV's SVN instance: https://svn.oucs.ox.ac.uk/projects/vle/sakai/ This is available for the general public to browse (if they so desire).