[Board] Web Officer

[Garrett Kajmowicz]

After the last meeting I've done a little thinking about the points raised.

The main concern was over potential conflict between the web officer and 
ConChair vision.

Above all else, the ConChair shuold have two options to address issue:
1)  Bring the issue to the board for a final decision.  This is the preferred 
resolution mechanism.

2)  Obtain separate hosting elsewhere out of the budget (to be avoided as it 
costs us more and would duplicate effort).

It is the role of the web officer to provide web site facilities which meet 
the requirements of the board as well as the ConChair.  The express purpose 
of PenguiCon is to put on one or more annual conventions.  If we aren't 
working toward that end, we need to revisit our purpose for existing.

The first thing to ask is:  What requirements does the board itself have?  I'd 
like to propose:
-     Section where we can put corporate documents (bylaws, minutes, budgets, 
tax returns, etc.)
-     Information on board members (yes, it's pure vanity)

The question which does need to be answered is wether we want to be able to 
archive the site for each year for posterity or not.  If not, no work is 
required.  If yes, then all of the web technologies selected *must* be able 
to get us a static version of the page which will live for eternity.  
Something which requires a PHP, Python, Plone, (or worse, livejournal) site 
will be nearly impossible to deal with.  Fortunately, some web technologies 
like WordPress (written in PHP) are readily set up to be "Web Whacked" so 
that we can generate final static HTML once the convention is over.  This 
decision will fundamentally shape the technologies available to the ConChair.  
Technologoes which the ConChair would like to use may not meet these 
requirements and be disallowed.

Thoughts?

-     Garrett