I spend most of my OpenLogic attention right now on Wazi, whether it be working with writers like Grant Smith and Dru Lavigne or our terrific internal team on what they might contribute, developing my own contributions, or researching what we might want to cover. Mornings before work I spend reading poetry. Lately Zbigniew Herbert, a Polish poet (I find Alissa Valles translation gorgeous, though it's controversial.) who performs virtuoso syntactic moves with practically no punctuation. Writes complex lists and compound sentences with no commas, for instance. I'm thinking about this phenomena — the way in which what's not there creates and informs, shapes and enhances what is  — called by poets and visual artists managing whitespace. And it occurs to me that Wazi, as a project, might be understood at least in part by what it's not, by what we don't want it to be or become, by what we've chosen to leave out.

To claim that Wazi isn't ultimately a lead generation and promotional tool for OpenLogic would be disingenuous. And that's the main thing we're leaving out: any pretense of being something other than what we are. However, it's also true that we're striving to leave out covert sales pitches, and marketing speak and wishful-thinking feature lists and anything, anything that remotely resembles padding. That leaves lots of room for Wazi to become a place to find substantive articles based on user experience with open source, about participating in the open source industry and making open source work in business.

Toward this end, in October, our researchers and legal team added an article on open source licensing, and a handy comparison tool of the most common open source licenses. Our engineers contributed tips and tutorials on a range of topics including working with Firefox and installing Apache on AIX. Rod Cope reported the results of some experimentation with open source reporting tools.

By the end of November, we'll have published an article that considers the numerous elements of what's being called 'governance' these days — scanning and open source policies and the like. We'll go in-depth laying out what a company might need to do to get a handle on the open source it uses, organize and manage their efforts and keep them organized going forward, while simultaneously meeting license obligations. Additionally, OpenLogic engineers will give you some tips on working with JBoss and Rails in both a development and production environment.

In December, we'll publish an article on getting started using open source for a Web application development project in an enterprise setting, and a comparison of all the available open source email servers. Both of these articles will include information on proprietary alternatives and pricing. January is still shaping up, but we know we'll add some information on stacks like servers and databases that play well together and expand our information on governance.

All this content is available at http://olex.openlogic.com/wazi free of charge; and most is available under a Creative Commons license, so free to use. If you like it (if you, like Mr. Cogito, believe a bird is a bird, and you adore tautologies and explanations), all we ask is that you talk about it. Subscribe to our RSS feed, Digg us, tell your friends. And, of course, if you really like it, if you like it enough to use the tools you're exposed to, keep in mind that OpenLogic keeps Wazi's lights on by selling support for open source (and much more) on hundreds of open source projects.

On a closing note, we're looking for writers and artists. If you'd like to work with us, or there's something particular you'd like to see, be impetuous and send us an email at wazi-at-openlogic.com.