Reminder: blog discussion at board meeting

[Anne Gentle]

While I couldn't make it to the board meeting, here are some general blog 
guidelines I would suggest based on my experience so far with blogging at 
BMC.

BMC has pointed me to the IBM guidelines 
(http://www-128.ibm.com/developerworks/blogs/dw_blog_comments.jspa?blog=351&entry=81328). 
The basic idea is to behave as if you were at a professional conference, 
wear your name badge, keep your identity, but make sure that bloggers are 
aware they must state things so that they are speaking on their own behalf, 
not on behalf of the STC. I would definitely suggest we avoid political or 
controversial subject matter. Stick to technical communication and related 
professional topics. I would suggest just 5 to 6 bloggers with post 
priveleges to begin with in order to keep editing to a minimum. I would also 
suggest that we try to post at least once a week. Save your content to 
ensure a steady stream of posts. Fresh content at intervals is more 
important in some ways than lots of posts in bursts of activity.

Here's how I would adapt IBM's guidelines for use on our STC Austin blog.
  1.. Know and follow business conduct guidelines.
  2.. Blogs, wikis and other forms of online discourse are individual 
interactions, not corporate communications. You are personally responsible 
for your posts. Be mindful that what you write will be public for a long 
time -- protect your privacy.
  3.. Identify yourself -- name and, when relevant, role with STC -- when 
you blog about STC or STC-related matters. Write in the first person. You 
must make it clear that you are speaking for yourself and not on behalf of 
STC.
  4.. If you publish a blog or post to a blog and it has something to do 
with work you do for the STC or subjects associated with STC, use a 
disclaimer such as this: "The postings on this site are my own and don't 
necessarily represent STC's positions, strategies or opinions."
  5.. Respect copyright, fair use and financial disclosure laws.
  6.. Don't cite or reference your employer or clients without their 
approval.
  7.. Respect your audience. Don't use ethnic slurs, personal insults, 
obscenity, etc., and show proper consideration for others' privacy and for 
topics that may be considered objectionable or inflammatory -- such as 
politics and religion.
  8.. Find out who else is blogging on the topic, and cite them.
  9.. Don't pick fights, be the first to correct your own mistakes, and 
don't alter previous posts without indicating that you have done so.
  10.. Try to add value. Provide worthwhile information and perspective.
I hope this helps.

Anne

----- Original Message ----- 
From: <jhgough at austin.rr.com>
To: "STC Austin Administrative Discussion List" 
<stc-austin-admin at lists.stc.org>
Sent: Tuesday, January 17, 2006 2:40 PM
Subject: [stc-austin-admin] Reminder: blog discussion at board meeting


> All,
>
> We currently have 16 articles posted on the newsBlog (my word).
>
> 1. Value of a Membership Fee Can Offer Return On Investment
> 2. Joann Hackos to speak...
> 3. STC Austin Meeting - Single Sourcing
> 4. Jan 2006 Networking Lunch...
> 5. How We Communicate...
> 6. Bloggers and TechWriters Converge
> 7. Jan 2005: Successful People
> 8. 2005-2006 Chapter Officers
> 9. Dec 2005: Board Meeting Minutes
> 10. Dec 20: From the Region 5 Director
> 11. Professional Development: Why We Don't Get No Respect
> 12. Networking Lunches
> 13. Events 2005-2006
> 14. 2005 Holiday Party at Andy's
> 15. Dec 13: From the Region 5 Director
> 16. Welcome to New Blog
>
> It will help in the discussion of the blog if you are familiar with
> the content. It took me about 15 minutes to scan the content and
> assess a couple of questions that we should discuss around guidelines
> for publishing. I hope you are already familiar with the content, but
> if not please take a peek before the meeting.
>
> Thanks,
> John
>
> ---
> You are currently subscribed to stc-austin-admin as: 
> annegentle at austin.rr.com
> To unsubscribe send a blank email to 
> leave-stc-austin-admin-229951I at lists.stc.org