> Well, in that case it would probably end up either > somewhere in BluePrints program on Sun's site, or > somewhere on BigAdmin. But as far as I know, only Sun > employed engineers are allowed to write this kind of > documentation for the Sun BluePrints program.
In the past, we've published Sun BluePrints which were written by people who do not work at Sun. However, the Sun BluePrints program was, er, changed last year, and the former infrastructure for peer review, editing, tech writing, and marketing is basically gone. We continue to produce some articles, but each is a labor of love. I would recommend BigAdmin or similar channels which have a streamlined process better suited for ad-hoc works, and of course getting the good ones into the regular docs is always a good thing[*] Perhaps there is an opportunity for something on the opensolaris.org site? [*] these docs tend to tell how-to. The Sun BluePrints pubs were intended to tell why, in the context of best practices. Also, Sun BluePrints pubs could have a develop-to-publish time on the order of a few months versus the traditionally long cycle time for manuals. -- richard This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list [email protected]
