+1 on that. Either one page per handler or a wikipedia-style page with an index at the beginning and one section per handler.
Regards Rubén 2012/6/25 Tobias Wunden <[email protected]> > 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] > _______________________________________________ >
_______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
