I agree it should be part of the release documentation (though not the "release notes" page, I assume you meant release docs). It's something that the configurer of the system needs to understand,
Chris On Mon, 25 Jun 2012 17:35:15 +0200 Tobias Wunden <[email protected]> wrote: > Hi, > > I love the fact that all of you seem to have strong feelings for long > pages :-) However, the main question is *where* to put that page, not > whether it's long or not... We do have cookbooks, but this feels more > like a structured piece of documentation, similar to the REST > endpoints, so a fixed place close to the workflow configuration docs > would be great. > > Tobias > > On 25.06.2012, at 17:27, Christopher Brooks <[email protected]> > wrote: > > > I like one page with all of the ootb handlers on it. > > > > I'm a big fan of big pages, which makes navigation and searching > > easier imo. But I'll leave organization up to you. > > > > Great to see docs start on operation handlers though. > > > > Chris > > > >> Hi, > >> > >> Lukas just wrote a new operation handler that will do nothing else > >> but tagging and setting of flavors. Like this, it will be possible > >> to pick up elements like the dublin core catalogs that have been > >> added to the mediapackage at the beginning of the workflow and tag > >> them, so they can be picked up by operations later on. > >> > >> The big question now is where documentation for this operation > >> should go. We should start documentation the ootb workflow > >> operations with description, parameters and some usage samples, > >> and most probably we should allow for one page per handler, with > >> an index page. > >> > >> I was thinking that this should be part of the release notes, but I > >> have to admit I am rather confused as to where things need to go, > >> so I am happy to get pointers or even have someone start a > >> structure for operation handler documentation. > >> > >> Thanks, > >> Tobias > >> _______________________________________________ > >> 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] > > _______________________________________________ > > _______________________________________________ > 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] _______________________________________________
