I'm still unclear who is the one who has to move the docs out of the
wiki and into drupal.  My concern is that this is just another task for
the already overburdened release manager to take on.  Right now the
docs can just be copied between spaces, and quickly updated.  No need
to learn new tools, setup new infrastructure (accounts/etc.) or go
through a tedious process (copying content).

Can a proponent of this proposal please put me at ease?

Where do docs for previous releases lie in this proposal?

Chris

On Tue, 14 Feb 2012 11:28:31 +0100
Ruediger Rolf <[email protected]> wrote:

> I guess the main problem with the two wikis was that they more or
> less look identically, so it was hard to find out in which wiki-space
> I am. So I am +1 for moving the release docs to drupal to make clear
> that they are different from the wiki that reflects work in progress.
> 
> What the current proposal misses is taht we discussed to enable a 
> comment feature on the release (and maybe even on the trunk docs) to 
> allow users to give feedback to the docs or share their workarounds
> etc. Here's an example from the jquery docs [1].
> 
> Rüdiger
> 
> [1] http://api.jquery.com/hide/
> 
> Am 14.02.2012 00:56, schrieb Greg Logan:
> > Yes, along with (hopefully) the accidental links which send users
> > from the stable release docs into the trunk docs.  In effect the
> > release docs are a snapshot of the trunk docs just before the
> > release, with a layer of QA applied to ensure that they are
> > accurate and up to date.
> >
> > G
> >
> > Michelle Ziegmann<[email protected]>  wrote:
> >
> >> I think Chris was asking if we are getting ridding of the
> >> Documentation space within our wiki
> >> (http://opencast.jira.com/wiki/display/MHDOC/Matterhorn+Documentation).
> >> This would go away, yes?
> >>
> >> Michelle
> >>
> >> On 2/13/12 3:23 PM, Jaime Gago wrote:
> >>> Chris,
> >>> My understanding during the Unconference session was *not* to get
> >>> rid of the wiki. What I understood about the proposal is to have
> >>> a static official version of the documentation that matches the
> >>> actual Matterhorn release that would be approved similar to the
> >>> way the release is (i.e. QA). The wiki wouldn't be gone as it
> >>> would be the needed canvas where to update the docs for the
> >>> upcoming releases and also a space to add new page for say dev
> >>> recipes.
> >>>
> >>> One way to look at technical documentation writing is to compare
> >>> it to code writing, with branches, release candidates and
> >>> official releases, basically versioning, the official release doc
> >>> being that static document that is pushed to the official
> >>> channels (i.e. outside of the wiki) at the same time as the
> >>> official released code.
> >>>
> >>> J.
> >>>
> >>> On Feb 13, 2012, at 2:40 PM, Michelle Ziegmann wrote:
> >>>
> >>>>> Are we talking about abandoning the wiki completely for docs?
> >>>>> (I don't particularly like this idea)
> >>>> I think that's the idea, yes. I'd love to hear your thoughts
> >>>> about this, Chris. It's an idea that came up during the Opencast
> >>>> conference.
> >>> _______________________________________________
> >>> 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]
> >> _______________________________________________
> > _______________________________________________
> > Matterhorn mailing list
> > [email protected]
> > http://lists.opencastproject.org/mailman/listinfo/matterhorn
> >
> >
> > To unsubscribe please email
> > [email protected]
> > _______________________________________________
> 
> 



-- 
Christopher Brooks, BSc, MSc
ARIES Laboratory, University of Saskatchewan

Web: http://www.cs.usask.ca/~cab938
Phone: 1.306.966.1442
Mail: Advanced Research in Intelligent Educational Systems Laboratory
     Department of Computer Science
     University of Saskatchewan
     176 Thorvaldson Building
     110 Science Place
     Saskatoon, SK
     S7N 5C9
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn


To unsubscribe please email
[email protected]
_______________________________________________

Reply via email to