This idea came up when Chris was developing the release docs for an earlier release, and found that changes were being made that were incorrect. There is also the issue of official release documents being mixed in a wiki with documents that are either in draft mode or deprecated. So the idea emerged to move the official release docs to a separate space, with fewer people having access to edit, and some separation between developer docs. Sakai (and probably some other projects I don't recall) does this (see https://confluence.sakaiproject.org/display/DOC/Documentation).

Moving them to the website accomplishes the same purpose, though, so I'm fine with this proposal. But others will need to be involved in editing and developing the docs. I can help with setup, but whoever "owns" the release docs for any given version will need to be able to do the bulk of work in the copy, paste, edit and upkeep of these docs.

Just a caution that I don't believe this move would resolve the accidental and random links problem - all of the links need to be QA'd and corrected whether these docs are in the wiki or website.

And unfortunately it also doesn't resolve the laborious copy and paste process involved in creating a new set of release docs. If it were me that had to individually copy and paste all of those pages that are included in each set of release docs (I count 29 pages per release!), I would strongly consider restructuring the release document template to be contained all in one page, similar to how Sakai does it (see https://confluence.sakaiproject.org/display/DOC/Sakai+CLE+2.8+release+notes).

Michelle

On 2/13/12 9:04 AM, Tobias Wunden wrote:
Greg,

this sounds like a great idea! Out of interest, does anybody remember the 
reasoning behind the original creation of the two separate wikis?

Tobias

On 13.02.2012, at 17:54, Greg Logan<[email protected]>  wrote:

We discussed this at Oxford but it should probably also be brought up on
list.  I #propose moving our release docs (the contents of the MHDOC
wiki) onto the main Opencast website.  This would remove the confusion
of having two wikis and the accidental and random links between them.
Creating release docs would then be a matter of trimming the trunk docs
and copying them (process tbd) into the main page.

Thoughts, comments?  This would take effect for the 1.3 release.

G

_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn


To unsubscribe please email
[email protected]
_______________________________________________
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn


To unsubscribe please email
[email protected]
_______________________________________________

--
Michelle Ziegmann
Electronic Communications Specialist
Educational Technology Services
University of California Berkeley

_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn


To unsubscribe please email
[email protected]
_______________________________________________

Reply via email to