<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/9.9.9" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Basecamp + Writeboard</title>
	<link>http://www.panoramio.com/blog/basecamp-writeboard/</link>
	<description>Development of Panoramio, a mash-up of Google Maps and geopositioned photos</description>
	<pubDate>Wed, 23 Jul 2008 21:10:47 +0000</pubDate>
	<generator>http://wordpress.org/?v=9.9.9</generator>

	<item>
		<title>by: Joaquín Cuenca Abela</title>
		<link>http://www.panoramio.com/blog/basecamp-writeboard/#comment-57</link>
		<pubDate>Mon, 31 Oct 2005 12:19:42 +0000</pubDate>
		<guid>http://www.panoramio.com/blog/basecamp-writeboard/#comment-57</guid>
					<description>Hi David,

Your post explains clearly the difference in scope of these two features, fair enough.

There are not a lot of things that go unnoticed on a two person project, so we do not need a place to let anybody know something and thus, as Eduardo said, we were (are) using the messages mainly to store some technical notes, and not as some kind of news frontend of the project.

I'm sure the messages should be helpful on bigger teams.

Thank you for taking the time to explain in detail their purpose.

Cheers,</description>
		<content:encoded><![CDATA[<p>Hi David,</p>
<p>Your post explains clearly the difference in scope of these two features, fair enough.</p>
<p>There are not a lot of things that go unnoticed on a two person project, so we do not need a place to let anybody know something and thus, as Eduardo said, we were (are) using the messages mainly to store some technical notes, and not as some kind of news frontend of the project.</p>
<p>I&#8217;m sure the messages should be helpful on bigger teams.</p>
<p>Thank you for taking the time to explain in detail their purpose.</p>
<p>Cheers,
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Eduardo Manchón</title>
		<link>http://www.panoramio.com/blog/basecamp-writeboard/#comment-39</link>
		<pubDate>Wed, 26 Oct 2005 12:32:04 +0000</pubDate>
		<guid>http://www.panoramio.com/blog/basecamp-writeboard/#comment-39</guid>
					<description>Thanks for your post David. It's nice to hear the reasons directly from the developers of Basecamp. 

Because we were already using "Messages" like stable pieces of text, we expected "Writeboards" to replace them. 

For communicating about the status of the project we just use e-mail. Maybe is worth to keep some of the messages in a weblog style, but I believe most of them are too irrelevant.

My two cents.</description>
		<content:encoded><![CDATA[<p>Thanks for your post David. It&#8217;s nice to hear the reasons directly from the developers of Basecamp. </p>
<p>Because we were already using &#8220;Messages&#8221; like stable pieces of text, we expected &#8220;Writeboards&#8221; to replace them. </p>
<p>For communicating about the status of the project we just use e-mail. Maybe is worth to keep some of the messages in a weblog style, but I believe most of them are too irrelevant.</p>
<p>My two cents.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: David Heinemeier Hansson</title>
		<link>http://www.panoramio.com/blog/basecamp-writeboard/#comment-38</link>
		<pubDate>Wed, 26 Oct 2005 10:08:50 +0000</pubDate>
		<guid>http://www.panoramio.com/blog/basecamp-writeboard/#comment-38</guid>
					<description>Thanks for the kind words. But Writeboards are certainly not able to replace messages. Their purpose is entirely different. Messages provide a low-barrier way to communicate about the status of a project. They're displayed like a weblog, showing multiple entries at once, and available in different categories. And there's significantly less mental overhead involved with creating a new message than a new Writeboard. Oh, and they can have files attached.

Writeboards, on the other hand, is for longer, more stable pieces of text in need of collaboration from multiple parties. The focus is on highlighting differences between versions and to give amble room for pages of content. Very different scope and application than messages.

Thanks for pondering, though.</description>
		<content:encoded><![CDATA[<p>Thanks for the kind words. But Writeboards are certainly not able to replace messages. Their purpose is entirely different. Messages provide a low-barrier way to communicate about the status of a project. They&#8217;re displayed like a weblog, showing multiple entries at once, and available in different categories. And there&#8217;s significantly less mental overhead involved with creating a new message than a new Writeboard. Oh, and they can have files attached.</p>
<p>Writeboards, on the other hand, is for longer, more stable pieces of text in need of collaboration from multiple parties. The focus is on highlighting differences between versions and to give amble room for pages of content. Very different scope and application than messages.</p>
<p>Thanks for pondering, though.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Joaquín Cuenca Abela</title>
		<link>http://www.panoramio.com/blog/basecamp-writeboard/#comment-36</link>
		<pubDate>Tue, 25 Oct 2005 18:39:33 +0000</pubDate>
		<guid>http://www.panoramio.com/blog/basecamp-writeboard/#comment-36</guid>
					<description>Hi Mark,

Killing the messages and keeping just writeboards do not need a "more general" interface.

If the interface of writeboards was more intrusive, I would have some concerns about merging these two kind of messages. But given how well it handles the use-cases of its little brother I think they can safely remove the messages and leave only writeboards.</description>
		<content:encoded><![CDATA[<p>Hi Mark,</p>
<p>Killing the messages and keeping just writeboards do not need a &#8220;more general&#8221; interface.</p>
<p>If the interface of writeboards was more intrusive, I would have some concerns about merging these two kind of messages. But given how well it handles the use-cases of its little brother I think they can safely remove the messages and leave only writeboards.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Mark</title>
		<link>http://www.panoramio.com/blog/basecamp-writeboard/#comment-35</link>
		<pubDate>Tue, 25 Oct 2005 16:15:43 +0000</pubDate>
		<guid>http://www.panoramio.com/blog/basecamp-writeboard/#comment-35</guid>
					<description>I don't mind that they are separate. Sometimes an all-in-one kitchenmatic that toasts your bread and washes your dishes is not best.

Learn how to spell "development".</description>
		<content:encoded><![CDATA[<p>I don&#8217;t mind that they are separate. Sometimes an all-in-one kitchenmatic that toasts your bread and washes your dishes is not best.</p>
<p>Learn how to spell &#8220;development&#8221;.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
