<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Team Blogging and Multi-Author Blog Etiquette</title>
	<atom:link href="http://forthardknox.com/2008/05/15/team-blogging-and-multi-author-blog-etiquette/feed/" rel="self" type="application/rss+xml" />
	<link>http://forthardknox.com/2008/05/15/team-blogging-and-multi-author-blog-etiquette/</link>
	<description>Politically-Conservative Web 2.0 Activists</description>
	<pubDate>Thu, 28 Aug 2008 23:21:48 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Stephen</title>
		<link>http://forthardknox.com/2008/05/15/team-blogging-and-multi-author-blog-etiquette/#comment-7113</link>
		<dc:creator>Stephen</dc:creator>
		<pubDate>Tue, 03 Jun 2008 16:16:03 +0000</pubDate>
		<guid isPermaLink="false">http://forthardknox.com/2008/05/15/team-blogging-and-multi-author-blog-etiquette/#comment-7113</guid>
		<description>&lt;strong&gt;Stephen...&lt;/strong&gt;

Some weblog software programs, such as Wordpress, Movable Type and Community Server, support automatic pingbacks where all the links...</description>
		<content:encoded><![CDATA[<p><strong>Stephen&#8230;</strong></p>
<p>Some weblog software programs, such as Wordpress, Movable Type and Community Server, support automatic pingbacks where all the links&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jenn Sierra</title>
		<link>http://forthardknox.com/2008/05/15/team-blogging-and-multi-author-blog-etiquette/#comment-6596</link>
		<dc:creator>Jenn Sierra</dc:creator>
		<pubDate>Mon, 19 May 2008 00:14:43 +0000</pubDate>
		<guid isPermaLink="false">http://forthardknox.com/2008/05/15/team-blogging-and-multi-author-blog-etiquette/#comment-6596</guid>
		<description>Thanks for the feedback, everyone.  I think on FHK, we'll leave the "default" alone, which is that comments made on FHK will remain on FHK.  It's good to know, however, that we do have the option to redirect them.  There may be a time when an author specifically would like to have all of the comments on a given topic in one place, such as for research purposes, and we'll gladly oblige.

Also, for now, I've added a link to this post to FHK's "about" page.  I'll be re-writing that, soon, and plan to incorporate more of it at that time.   Thanks, again, Barb, for the great info.

Jenn</description>
		<content:encoded><![CDATA[<p>Thanks for the feedback, everyone.  I think on FHK, we&#8217;ll leave the &#8220;default&#8221; alone, which is that comments made on FHK will remain on FHK.  It&#8217;s good to know, however, that we do have the option to redirect them.  There may be a time when an author specifically would like to have all of the comments on a given topic in one place, such as for research purposes, and we&#8217;ll gladly oblige.</p>
<p>Also, for now, I&#8217;ve added a link to this post to FHK&#8217;s &#8220;about&#8221; page.  I&#8217;ll be re-writing that, soon, and plan to incorporate more of it at that time.   Thanks, again, Barb, for the great info.</p>
<p>Jenn</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Faultline USA</title>
		<link>http://forthardknox.com/2008/05/15/team-blogging-and-multi-author-blog-etiquette/#comment-6579</link>
		<dc:creator>Faultline USA</dc:creator>
		<pubDate>Sun, 18 May 2008 12:23:16 +0000</pubDate>
		<guid isPermaLink="false">http://forthardknox.com/2008/05/15/team-blogging-and-multi-author-blog-etiquette/#comment-6579</guid>
		<description>Sorry but I've been gone for the last few days so couldn't respond. 

Regarding comments: No I wasn’t asking for any changes. Personally I don’t think it’s a good idea to close or redirect the comments for a couple of reasons. (1) It isn’t good for the team blog. (2) If I’m reading an article on the team blog I don’t want to have to leave the page and comment on yet another page. I want to leave the comment exactly where I read the article.
 
If I’m cross-posting an article to another blog the only way I will know if there are comments left is: (1) to periodically go back to that blog and check, or (2) be the first to leave a comment on that article so that I will receive an e-mail notification. 

Thanks Jenn. Yes please add the article to the ”About” information. Thanks.</description>
		<content:encoded><![CDATA[<p>Sorry but I&#8217;ve been gone for the last few days so couldn&#8217;t respond. </p>
<p>Regarding comments: No I wasn’t asking for any changes. Personally I don’t think it’s a good idea to close or redirect the comments for a couple of reasons. (1) It isn’t good for the team blog. (2) If I’m reading an article on the team blog I don’t want to have to leave the page and comment on yet another page. I want to leave the comment exactly where I read the article.</p>
<p>If I’m cross-posting an article to another blog the only way I will know if there are comments left is: (1) to periodically go back to that blog and check, or (2) be the first to leave a comment on that article so that I will receive an e-mail notification. </p>
<p>Thanks Jenn. Yes please add the article to the ”About” information. Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ron</title>
		<link>http://forthardknox.com/2008/05/15/team-blogging-and-multi-author-blog-etiquette/#comment-6524</link>
		<dc:creator>Ron</dc:creator>
		<pubDate>Fri, 16 May 2008 15:21:57 +0000</pubDate>
		<guid isPermaLink="false">http://forthardknox.com/2008/05/15/team-blogging-and-multi-author-blog-etiquette/#comment-6524</guid>
		<description>I don't think redirecting comments would be a good idea.  If you manage to get comments, the commenter is going to look for additional comments in the same place.  If his/her comments are somewhere else, that makes it more difficult.

Cross posting has its advantages and disadvantages.  I think that if the author wants the comments on his/her blog, he/she can copy them over so readers there can see them.  But comments should remain on the blog where the commenter made them.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think redirecting comments would be a good idea.  If you manage to get comments, the commenter is going to look for additional comments in the same place.  If his/her comments are somewhere else, that makes it more difficult.</p>
<p>Cross posting has its advantages and disadvantages.  I think that if the author wants the comments on his/her blog, he/she can copy them over so readers there can see them.  But comments should remain on the blog where the commenter made them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jenn Sierra</title>
		<link>http://forthardknox.com/2008/05/15/team-blogging-and-multi-author-blog-etiquette/#comment-6521</link>
		<dc:creator>Jenn Sierra</dc:creator>
		<pubDate>Fri, 16 May 2008 14:31:39 +0000</pubDate>
		<guid isPermaLink="false">http://forthardknox.com/2008/05/15/team-blogging-and-multi-author-blog-etiquette/#comment-6521</guid>
		<description>Ron, we were addressing this paragraph of the post:  

&lt;blockquote&gt;What to do about comments? I’ve noticed that it has become common practice for some contributors to redirect comments from the team blog to the blogger’s blog. That makes it far easier for the contributor to respond to comments, but I’m not sure it does much for the team blog. This is a decision that should be left up to the owner or editor of the team blog.&lt;/blockquote&gt;

I suppose the way we would do this would be to close the comments on the cross-posted article, and add a link to the bottom of the post back to the original post for comments...?  That is, if we decide we want to do it that way.  I don't think Barb was necessarily calling for a change - she was just mentioning that there are options to be considered...right Barb?</description>
		<content:encoded><![CDATA[<p>Ron, we were addressing this paragraph of the post:  </p>
<blockquote><p>What to do about comments? I’ve noticed that it has become common practice for some contributors to redirect comments from the team blog to the blogger’s blog. That makes it far easier for the contributor to respond to comments, but I’m not sure it does much for the team blog. This is a decision that should be left up to the owner or editor of the team blog.</p></blockquote>
<p>I suppose the way we would do this would be to close the comments on the cross-posted article, and add a link to the bottom of the post back to the original post for comments&#8230;?  That is, if we decide we want to do it that way.  I don&#8217;t think Barb was necessarily calling for a change - she was just mentioning that there are options to be considered&#8230;right Barb?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ron</title>
		<link>http://forthardknox.com/2008/05/15/team-blogging-and-multi-author-blog-etiquette/#comment-6519</link>
		<dc:creator>Ron</dc:creator>
		<pubDate>Fri, 16 May 2008 13:04:00 +0000</pubDate>
		<guid isPermaLink="false">http://forthardknox.com/2008/05/15/team-blogging-and-multi-author-blog-etiquette/#comment-6519</guid>
		<description>Hmm, where do you want to forward comments to?  I'm not sure I understand what you want to do.</description>
		<content:encoded><![CDATA[<p>Hmm, where do you want to forward comments to?  I&#8217;m not sure I understand what you want to do.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jenn Sierra</title>
		<link>http://forthardknox.com/2008/05/15/team-blogging-and-multi-author-blog-etiquette/#comment-6502</link>
		<dc:creator>Jenn Sierra</dc:creator>
		<pubDate>Fri, 16 May 2008 04:10:37 +0000</pubDate>
		<guid isPermaLink="false">http://forthardknox.com/2008/05/15/team-blogging-and-multi-author-blog-etiquette/#comment-6502</guid>
		<description>Thanks for the nice comments, everyone.  Buffoon, and Faultline, as our newest collaborators, you all have been wonderful additions to our team. (And no, I would not know where to begin in keeping up with all of the new innovations - there are literally new technologies every day, it seems.)

Barb, this is a very good article, and very useful.  If you don't mind, I'm going to add it to our "about" information in the next few days.

As for the comments...it has seemed to me that it is good to keep them in the blogging community, but I'm open to trying something new on that...if someone can figure out the technology for forwarding comments to another blog (Ron? Esteemed IT Guy?)</description>
		<content:encoded><![CDATA[<p>Thanks for the nice comments, everyone.  Buffoon, and Faultline, as our newest collaborators, you all have been wonderful additions to our team. (And no, I would not know where to begin in keeping up with all of the new innovations - there are literally new technologies every day, it seems.)</p>
<p>Barb, this is a very good article, and very useful.  If you don&#8217;t mind, I&#8217;m going to add it to our &#8220;about&#8221; information in the next few days.</p>
<p>As for the comments&#8230;it has seemed to me that it is good to keep them in the blogging community, but I&#8217;m open to trying something new on that&#8230;if someone can figure out the technology for forwarding comments to another blog (Ron? Esteemed IT Guy?)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Faultline USA</title>
		<link>http://forthardknox.com/2008/05/15/team-blogging-and-multi-author-blog-etiquette/#comment-6500</link>
		<dc:creator>Faultline USA</dc:creator>
		<pubDate>Fri, 16 May 2008 03:41:05 +0000</pubDate>
		<guid isPermaLink="false">http://forthardknox.com/2008/05/15/team-blogging-and-multi-author-blog-etiquette/#comment-6500</guid>
		<description>Jenn has been great and very helpful to me too. I think we are all in a sense "new bloggers" as quickly as the blogging world is changing. It's impossible for one person, with the exception of Jenn, to keep up with all the new innovations!</description>
		<content:encoded><![CDATA[<p>Jenn has been great and very helpful to me too. I think we are all in a sense &#8220;new bloggers&#8221; as quickly as the blogging world is changing. It&#8217;s impossible for one person, with the exception of Jenn, to keep up with all the new innovations!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ron</title>
		<link>http://forthardknox.com/2008/05/15/team-blogging-and-multi-author-blog-etiquette/#comment-6498</link>
		<dc:creator>Ron</dc:creator>
		<pubDate>Fri, 16 May 2008 01:27:39 +0000</pubDate>
		<guid isPermaLink="false">http://forthardknox.com/2008/05/15/team-blogging-and-multi-author-blog-etiquette/#comment-6498</guid>
		<description>I gotta agree with you about Jenn.  I've worked with her for quite a while now and I have to say it has been a pleasure.  I trust her judgment and I agree with her direction.  I'm glad I'm a part of this blog!</description>
		<content:encoded><![CDATA[<p>I gotta agree with you about Jenn.  I&#8217;ve worked with her for quite a while now and I have to say it has been a pleasure.  I trust her judgment and I agree with her direction.  I&#8217;m glad I&#8217;m a part of this blog!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Buffoon</title>
		<link>http://forthardknox.com/2008/05/15/team-blogging-and-multi-author-blog-etiquette/#comment-6496</link>
		<dc:creator>Buffoon</dc:creator>
		<pubDate>Fri, 16 May 2008 01:09:42 +0000</pubDate>
		<guid isPermaLink="false">http://forthardknox.com/2008/05/15/team-blogging-and-multi-author-blog-etiquette/#comment-6496</guid>
		<description>Being a newb and not very smart I assume I haven't done anything wrong...  Jenn has been far and above the most helpful and guiding light I've had the pleasure of knowing.

Not really knowing the ins and outs I trust other bloggers to grab anything of mine they like, with a link back of course...</description>
		<content:encoded><![CDATA[<p>Being a newb and not very smart I assume I haven&#8217;t done anything wrong&#8230;  Jenn has been far and above the most helpful and guiding light I&#8217;ve had the pleasure of knowing.</p>
<p>Not really knowing the ins and outs I trust other bloggers to grab anything of mine they like, with a link back of course&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
