Well, yes and no.
I’ve just become one of the authors for the newly-created Apache OpenOffice.org blog.
As I write this, the blog’s main page is blank. I didn’t intend to have it be that way any longer.
Today’s lesson: Never ever do initial creation, pondering, and linking of a blog post using a browser. At some point, I will do some fat-fingered fumble that causes the in-progress post window to close and be lost forever.
I will now collect myself, pour another cup of coffee, and check to see what is going at Apache OpenOffice.org email lists (not necessarily in that order).
Cooled down, I’ll maybe take another shot at creating off-line text that I can paste into the browser-based blog editing window without mishap. The Apache Software Foundation blogs are housed by Apache Roller. I have no idea whether there is a way to use Windows Live Writer to author for it. Absent that, I suspect plain old text editing (via jEdit in my case) will be sufficient. That seems to be a common foundation for the various ways of producing content for Apache projects. It has something to do with document-management of everything via Apache Subversion and oversight by viewing change-commit logs. This is a serious dog-food operation, and I haven’t quite got the taste for it yet. (And folks think Microsoft NIH is excessive!). I’ve concluded that tool-crafters, and I’m one, are a dangerous breed.
So, When Will Orcmid Get the Lesson?
Now, I already know to author wiki articles this way. But it seems that this lesson is one that I will need to relearn every time I think I have a new way of intruding myself into cyberspace. (Don’t ask about Google+, that is just too confusing.)
Fortunately, I was gifted with this lesson in my first attempt and I didn’t lose too many of my beautifully-crafted paragraphs. (Sob.)
PS: I don’t propose to blog about the soap-opera around OpenOffice.org ending up in the incubator at the Apache Software Foundation. You can get a taste for that in the related articles, below. I intend for that to be the final mention I will make of that.

As part of the acquisition of 
I use the Web Services password, but that doesn't do it. Using an actual account User ID doesn't work either. Hmm, it says name. Do you think they really mean the name field.
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_a.png?x-id=69870785-fc25-46e4-9311-8ef83640849e)
What I did was remove any ##-comments at the ends of non-comment lines. Those are not recognized as comments. I also shrank the white space between the name of the configuration settings and their parameter values.![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_a.png?x-id=bc171231-5ce8-40f4-81b9-4763277a55dc)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_a.png?x-id=f6e1f5dd-28b6-45b1-b4c8-dbe7bf22d284)
There was other evidence in the broken links to images and other provisions:
My prayer was that I would not actually have to replicate the Movable Type installation or do any kind of directory-linking magic. I trusted that there was some setting that I could find for using the same Movable Type installation from all of the blogs in sites anchored on nfoCentrale.
Once I uploaded the changed mt-config.cgi to the nfoCentrale Movable Type installation, and then republished Spanner Wingnut, everything, including trackbacks, worked ![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_a.png?x-id=d9417e9b-ee4e-4347-8a72-bc4db869ab5b)

![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_a.png?x-id=e57fc2a2-640c-43f8-9c98-ef7aeba5cd16)
