One of the things I've talked about previously is writing a much involved "Best Practices" deployment guide for Cobbler. I think Cobbler's far enough now that it would be a good time to do this, as the core of things should not be changing so significantly that it will not rapidly become out of date.
The focus would be on large scale and complex deployments, and would roll up and incorporate all the content on the Wiki with various things I hear from users about how they manage their deployments. This is very much going to be a "book" in terms of length. How short or long I'm not sure, but it will exceed the manpage and Wiki in scope. I'm going to start working on that soon, so I am wondering if there is anything specific you folks would like to see covered or included? As with Cobbler, this is intended to be collaboratively developed, so the document sources will be kept in git. My main concern at this point is if the deployment guide would become out of sync with the Wiki and/or manpage, so I'm tempted to just write the deployment guide on the Wiki. However this is less than ideal for printing reasons. Alternatively, we can look to hosting all documentation in DocBook, though this makes the Wiki less Wiki like. Publican seems to be a popular option for document publishing. (https://fedorahosted.org/publican/wiki/UsersGuide). It has the disadvantage of being XML, though I think this still may be a bit better for getting contributions than something like LaTEX. --Michael _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
