July 2011 Archives

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.

Enhanced by Zemanta

I just learned via Twitter that an update is coming to Windows Live Essentials 2011.  That impacts me the most with Windows Live Photo Gallery and Windows Live Writer

I’m not sure that I am going to like it.  I won’t know unless I try.  What will it fix?  What will it break.  Can I roll back if it doesn’t work for me. Ah, yes, the real question: CAN I ROLL BACK IF IT DOESN’T WORK FOR ME?

Enhanced by Zemanta

Coming soon: orcmid @ Apache

As a newly-minted Initial Committer on the Apache OpenOffice.org Incubator Podling, there is a *nix account and hosted web pages beckoning to me.  Not there yet?  Well, I am about repairing that.

It is natural for me to want to use my existing deployment model for the new site.

Not So Fast, Sparky

There are two important differences. 

First, the new site serves up as a folder of http://people.apache.org/ so I don’t know how much site substructure there is under the public_html/ directory of the ~orcmid account (and I am not that certain of the URL, for that matter).

Secondly, I have to deploy from my new desktop system, Astraendo.  That is because my developer access to ~orcmid and ~orcmid/public_html/ are via Secure Shell (SSH).  I will use PuTTY and its companion SFTP utility to deploy to the account and from there to the Internet.  This works better if I deploy from a working folder on Astraendo rather than on the (to be migrated someday soon) development server that my other sites are deployed from.

Baby Steps

The first step is to produce a single default page and have it visible over the web.  I will do that this way:

  1. Setup http://compagno/orcmidApache.  This is a new sub-web on my local development server.  It is where I will make my pages using FrontPage or other web-authoring tools.
  2. Create Visual SourceSafe project $/orcmidApache and have it bound to the compagno/orcmidApache development sub-web as its source control system.  I can then make a couple of starter pages and also create an images subfolder.
  3. Create Visual SourceSafe project $/apacheOrcmid/web.  This is a mirror (by sharing) of content in $/orcmidApache.  This is where a current set of authored pages are found for publishing. 
  4. Create computer folder C:\publicca\ApacheOrcmid\web.  This is where a current version of the web content is staged.   It is the assigned working folder (on Astraendo) for $/apacheOrcmid/web.  It is refreshed by Get Latest Version from $/apacheOrcmid/web only when I want to refresh the public site.  Staging here is decoupled from subsequent development until another Get Latest Version is pulled over.
  5. Newer pages are published by SFTP transfer from C:\publicca\ApacheOrcmid\web to the ~orcmid/public_html folder at people.apache.org

This chain seems lengthy only the first time.  After that, everything just flows.  This structure also allows for backup from the site to the development source-control system, although I don’t expect to have need for that.

Enhanced by Zemanta

About this Archive

This page is an archive of entries from July 2011 listed from newest to oldest.

March 2011 is the previous archive.

November 2012 is the next archive.

Find recent content on the main index or look in the archives to find all content.


OpenID accepted here Learn more about OpenID
Powered by Movable Type 4.34-en