Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 157056 - executive blogs never updated
Summary: executive blogs never updated
Alias: None
Product: Red Hat Web Site
Classification: Red Hat
Component: Other
Version: current
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Greg DeKoenigsberg
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2005-05-06 14:55 UTC by Need Real Name
Modified: 2007-04-18 17:25 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-05-08 01:26:20 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Need Real Name 2005-05-06 14:55:44 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050416 Epiphany/1.6.1

Description of problem:
Blogs are wonderful things - frequently updated, they give an insight into the company you have a business relationship with, or have an interest in.

The front page of the Red Hat website is frequently updated (and very good too).

It's been four months since the last Red Hat execs blog update. What happened?

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Additional info:

Comment 1 Luke Meyer 2005-05-06 19:30:40 UTC
full points for amusing me with a bugzilla on this.  i've wondered the same
thing myself.  i'd assign it to szulik but i don't think he has a bugzilla
account.  maybe gdk can give it a shove in the right direction.

Comment 2 Need Real Name 2005-05-06 19:34:08 UTC
Glad to hear you liked it :)

Comment 3 Greg DeKoenigsberg 2005-05-08 01:26:20 UTC

All right, for reasons that must surely be obvious, I'm closing this NOTABUG.

However, this will provide perfect fodder to our executives, so thanks for 
filing it.  :)

Note You need to log in before you can comment on or make changes to this bug.