> 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.
Well, if the article's concept is approved for publication, I can easily rewrite it into the more offical document format(1). -- 1 the article actually goes both into "why" and "how". It could (and should) be expanded in both areas. This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
