<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for Bad Nomenclature</title>
	<atom:link href="http://blog.paulbiggar.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.paulbiggar.com</link>
	<description>Compilers, open source, and similar.</description>
	<lastBuildDate>Wed, 13 Jul 2011 21:03:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>Comment on TryChooser by Paul Biggar</title>
		<link>http://blog.paulbiggar.com/archive/trychooser/#comment-273</link>
		<dc:creator>Paul Biggar</dc:creator>
		<pubDate>Wed, 13 Jul 2011 21:03:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.paulbiggar.com/?p=177#comment-273</guid>
		<description>Those are great suggestions. I&#039;m only actively working on things that make my life easier, but I&#039;d happily take code to do these things. I&#039;d be delighted if you&#039;d file these issues on github (and optionally implement them :))!

- [All, None, Some] is a great idea
- Not pushing: volkmar made a pull request for this, which needs a tiny change (being called &quot;pretend&#039; instead of &quot;dry-run&quot;). See https://github.com/pbiggar/trychooser/pull/3
- this is really easy to fix. I might do that if nobody beats me to it. (If you were interested in doing this, it would be a nice easy first step).</description>
		<content:encoded><![CDATA[<p>Those are great suggestions. I&#8217;m only actively working on things that make my life easier, but I&#8217;d happily take code to do these things. I&#8217;d be delighted if you&#8217;d file these issues on github (and optionally implement them :))!</p>
<p>- [All, None, Some] is a great idea<br />
- Not pushing: volkmar made a pull request for this, which needs a tiny change (being called &#8220;pretend&#8217; instead of &#8220;dry-run&#8221;). See <a href="https://github.com/pbiggar/trychooser/pull/3" rel="nofollow">https://github.com/pbiggar/trychooser/pull/3</a><br />
- this is really easy to fix. I might do that if nobody beats me to it. (If you were interested in doing this, it would be a nice easy first step).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on TryChooser by Felipe Gomes</title>
		<link>http://blog.paulbiggar.com/archive/trychooser/#comment-272</link>
		<dc:creator>Felipe Gomes</dc:creator>
		<pubDate>Wed, 13 Jul 2011 20:46:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.paulbiggar.com/?p=177#comment-272</guid>
		<description>That is a great extension. A few suggestions to make it better:
 - I would change the two-step process when you want &quot;some&quot; to something requiring 1 choice. E.g.:
&quot;Unit tests?&quot; [All, None, Some] 
or [Yes, No, Some] if you want to keep y/n

- I&#039;d love an option where it just created the cset but doesn&#039;t actually push.. I want to be able to run hg outgoing and keep the cset around for future uses

- try: -a is deprecated and doesn&#039;t run the full suite anymore.. see this on trybuilder, the correct syntax now for everything is try: -b do -p all -u all -t all
</description>
		<content:encoded><![CDATA[<p>That is a great extension. A few suggestions to make it better:<br />
 - I would change the two-step process when you want &#8220;some&#8221; to something requiring 1 choice. E.g.:<br />
&#8220;Unit tests?&#8221; [All, None, Some]<br />
or [Yes, No, Some] if you want to keep y/n</p>
<p>- I&#8217;d love an option where it just created the cset but doesn&#8217;t actually push.. I want to be able to run hg outgoing and keep the cset around for future uses</p>
<p>- try: -a is deprecated and doesn&#8217;t run the full suite anymore.. see this on trybuilder, the correct syntax now for everything is try: -b do -p all -u all -t all</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on TryChooser by Paul Biggar</title>
		<link>http://blog.paulbiggar.com/archive/trychooser/#comment-271</link>
		<dc:creator>Paul Biggar</dc:creator>
		<pubDate>Mon, 11 Jul 2011 21:15:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.paulbiggar.com/?p=177#comment-271</guid>
		<description>If you don&#039;t have mq enabled, it will just print the trychooser line.

We could make it so that it pushes even if mq is not enabled, with a similar UI. I&#039;d be delighted to incorporate a patch for that :)</description>
		<content:encoded><![CDATA[<p>If you don&#8217;t have mq enabled, it will just print the trychooser line.</p>
<p>We could make it so that it pushes even if mq is not enabled, with a similar UI. I&#8217;d be delighted to incorporate a patch for that :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on TryChooser by Smaug</title>
		<link>http://blog.paulbiggar.com/archive/trychooser/#comment-269</link>
		<dc:creator>Smaug</dc:creator>
		<pubDate>Mon, 11 Jul 2011 19:53:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.paulbiggar.com/?p=177#comment-269</guid>
		<description>Does the extension require using mq?</description>
		<content:encoded><![CDATA[<p>Does the extension require using mq?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on CC-lists and openness by Karl</title>
		<link>http://blog.paulbiggar.com/archive/cc-lists-and-openness/#comment-268</link>
		<dc:creator>Karl</dc:creator>
		<pubDate>Wed, 22 Jun 2011 04:09:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.paulbiggar.com/?p=167#comment-268</guid>
		<description>In W3C reality, it is called the *-archive mailing-list. It is very practical. It helps also with communications on the outside, when you want to keep a Web record with a permanent URI for future references about a mail you just sent. 

you could have indeed thematic archives, or a a general archive mailing-list, I would recommend two at least, one which is &quot;private&quot; and related to the social contract of the group and one which is open to the public when it is about public communications. 
</description>
		<content:encoded><![CDATA[<p>In W3C reality, it is called the *-archive mailing-list. It is very practical. It helps also with communications on the outside, when you want to keep a Web record with a permanent URI for future references about a mail you just sent. </p>
<p>you could have indeed thematic archives, or a a general archive mailing-list, I would recommend two at least, one which is &#8220;private&#8221; and related to the social contract of the group and one which is open to the public when it is about public communications. </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on CC-lists and openness by Steve Fink</title>
		<link>http://blog.paulbiggar.com/archive/cc-lists-and-openness/#comment-267</link>
		<dc:creator>Steve Fink</dc:creator>
		<pubDate>Thu, 16 Jun 2011 18:38:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.paulbiggar.com/?p=167#comment-267</guid>
		<description>pbiggar++

I like it. Well, ok, I like the pbiggar-public incarnation of the idea.

The problem with pbiggar at mozilla.com being public is that you are deciding on the sender&#039;s behalf that the message should be public. Which isn&#039;t nice. At all. Especially for people who haven&#039;t emailed you before and aren&#039;t aware yet.

One concern would be requiring correspondents to keep track of one more email address for you. That&#039;s unnecessary for pbiggar-public at mozilla.com or pbiggar+public at mozilla.com or (I think I prefer this) pbiggar at public.mozilla.com. But a lot of people use other email addresses. I have both sfink at mozilla.com and sphink at gmail.com, for example, and I use both for different segments of my Mozilla-related mail. I also use Thunderbird as a mail filter on my gmail account (it sorta works), so I *could* set it up to work (well, public.gmail.com won&#039;t), but I think this would need a common mechanism to work.

Just handling mozilla.com addresses would be enough for this to be useful, I think. There could be a fallback CC for other addresses.

One missing piece -- if I send to pbiggar-public, which CC list does it go to? Or more to the point, if I send to bz-public or damons-public, where does it go? Is there a mapping of user -&gt; set of CC lists?

It might be useful to also post initial thread subject lines to the relevant IRC channel as well. Or a CC version of the IRC channel.

And we&#039;d have to establish conventions about when it&#039;s ok for a third-party observer to start participating in the conversation -- read-only access to these sorts of conversations is one thing, but if I wouldn&#039;t use it if people felt free to start chipping in and starting flamewars on them.

I&#039;d be ok with a policy where you never interject into someone else&#039;s conversation, but you&#039;re always free to start a new thread quoting anything in that conversation.

(Side note: I used &quot; at &quot; everywhere in this post in place of the at-sign not for spam protection, but because the commenting software is doing something truly horrible and evil where it tries to make special links or something when it sees an at sign. And they&#039;re hard to get rid of. Even if you&#039;re nowhere near, the magic-at handler seems to take control of the enter key. Kill kill die die die.)

 </description>
		<content:encoded><![CDATA[<p>pbiggar++</p>
<p>I like it. Well, ok, I like the pbiggar-public incarnation of the idea.</p>
<p>The problem with pbiggar at mozilla.com being public is that you are deciding on the sender&#8217;s behalf that the message should be public. Which isn&#8217;t nice. At all. Especially for people who haven&#8217;t emailed you before and aren&#8217;t aware yet.</p>
<p>One concern would be requiring correspondents to keep track of one more email address for you. That&#8217;s unnecessary for pbiggar-public at mozilla.com or pbiggar+public at mozilla.com or (I think I prefer this) pbiggar at public.mozilla.com. But a lot of people use other email addresses. I have both sfink at mozilla.com and sphink at gmail.com, for example, and I use both for different segments of my Mozilla-related mail. I also use Thunderbird as a mail filter on my gmail account (it sorta works), so I *could* set it up to work (well, public.gmail.com won&#8217;t), but I think this would need a common mechanism to work.</p>
<p>Just handling mozilla.com addresses would be enough for this to be useful, I think. There could be a fallback CC for other addresses.</p>
<p>One missing piece &#8212; if I send to pbiggar-public, which CC list does it go to? Or more to the point, if I send to bz-public or damons-public, where does it go? Is there a mapping of user -&gt; set of CC lists?</p>
<p>It might be useful to also post initial thread subject lines to the relevant IRC channel as well. Or a CC version of the IRC channel.</p>
<p>And we&#8217;d have to establish conventions about when it&#8217;s ok for a third-party observer to start participating in the conversation &#8212; read-only access to these sorts of conversations is one thing, but if I wouldn&#8217;t use it if people felt free to start chipping in and starting flamewars on them.</p>
<p>I&#8217;d be ok with a policy where you never interject into someone else&#8217;s conversation, but you&#8217;re always free to start a new thread quoting anything in that conversation.</p>
<p>(Side note: I used &#8221; at &#8221; everywhere in this post in place of the at-sign not for spam protection, but because the commenting software is doing something truly horrible and evil where it tries to make special links or something when it sees an at sign. And they&#8217;re hard to get rid of. Even if you&#8217;re nowhere near, the magic-at handler seems to take control of the enter key. Kill kill die die die.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Summary of Contributor Engagement threads on dev-planning by Max Kanat-Alexander</title>
		<link>http://blog.paulbiggar.com/archive/dev-planning-contributor-engagement-summary/#comment-265</link>
		<dc:creator>Max Kanat-Alexander</dc:creator>
		<pubDate>Thu, 07 Apr 2011 02:03:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/pbiggar/?p=21#comment-265</guid>
		<description>Cool! You might also be interested in the community research I did for the Bugzilla Project:

http://www.codesimplicity.com/post/open-source-community-simplified/

-Max</description>
		<content:encoded><![CDATA[<p>Cool! You might also be interested in the community research I did for the Bugzilla Project:</p>
<p><a href="http://www.codesimplicity.com/post/open-source-community-simplified/" rel="nofollow">http://www.codesimplicity.com/post/open-source-community-simplified/</a></p>
<p>-Max</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Summary of Contributor Engagement threads on dev-planning by Mitch</title>
		<link>http://blog.paulbiggar.com/archive/dev-planning-contributor-engagement-summary/#comment-264</link>
		<dc:creator>Mitch</dc:creator>
		<pubDate>Sun, 03 Apr 2011 16:37:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/pbiggar/?p=21#comment-264</guid>
		<description>https://bugzilla.mozilla.org/show_bug.cgi?id=644861</description>
		<content:encoded><![CDATA[<p><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=644861" rel="nofollow">https://bugzilla.mozilla.org/show_bug.cgi?id=644861</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why we shut NewsTilt down by Anonymous</title>
		<link>http://blog.paulbiggar.com/archive/why-we-shut-newstilt-down/#comment-263</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Mon, 27 Sep 2010 01:06:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.paulbiggar.com/?p=66#comment-263</guid>
		<description>You say: &quot;Art/science is a false dichotomy, as is left-/right-brained. To think that journalism can only come from inside to box is ludicrous. People have many skills besides the one in which they are trained, and you certainly believe this or you wouldn&#039;t suggest that journalists, whose primary skill is not innovation, can innovate. Please don&#039;t believe that anyone can think themselves out of this wasteland. It requires not only innovation and the right creative force (for want of a better term), but also rapid iteration, and lots of different companies trying. &quot;

You really have been living under a rock.</description>
		<content:encoded><![CDATA[<p>You say: &#8220;Art/science is a false dichotomy, as is left-/right-brained. To think that journalism can only come from inside to box is ludicrous. People have many skills besides the one in which they are trained, and you certainly believe this or you wouldn&#8217;t suggest that journalists, whose primary skill is not innovation, can innovate. Please don&#8217;t believe that anyone can think themselves out of this wasteland. It requires not only innovation and the right creative force (for want of a better term), but also rapid iteration, and lots of different companies trying. &#8221;</p>
<p>You really have been living under a rock.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why we shut NewsTilt down by Anonymous</title>
		<link>http://blog.paulbiggar.com/archive/why-we-shut-newstilt-down/#comment-262</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Mon, 27 Sep 2010 00:59:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.paulbiggar.com/?p=66#comment-262</guid>
		<description>I did apologize, on the mailing list that the we and the journalists used to communicate. Nathan also did that when he announced that we shut down. This piece wasn&#039;t about apology, it was about the lessons to be gotten from it.

Paying writers would have changed the dynamic of our relationship. We weren&#039;t buying content, and we weren&#039;t hiring journalists. We were providing a service to them, and aiming to take a cut of their profits online as our income.

We didn&#039;t just invent this idea. We spoke to dozens of journalists, and the product was based entirely on what they told us. We spoke to some people at Knight (not in an official capacity); I don&#039;t want to put words in their mouths, but they obviously didn&#039;t tell us we were doing the wrong thing or we would have changed what we were doing.

Our intent was plain. We wanted to make a successful company making a successful product. We could only have done that through making successful journalists. Our funders we mentioned in this piece several times: YCombinator. I&#039;m sure they&#039;d be delighted to invest in real journalists, and the application process is open for a few more days I believe. YCombinator&#039;s motto is &#039;make something people want&#039;, and that&#039;s what we were doing.

I&#039;m afraid your final paragraph simply makes no sense. Art/science is a false dichotomy, as is left-/right-brained. To think that journalism can only come from inside to box is ludicrous. People have many skills besides the one in which they are trained, and you certainly believe this or you wouldn&#039;t suggest that journalists, whose primary skill is not innovation, can innovate. Please don&#039;t believe that anyone can think themselves out of this wasteland. It requires not only innovation and the right creative force (for want of a better term), but also rapid iteration, and lots of different companies trying. </description>
		<content:encoded><![CDATA[<p>I did apologize, on the mailing list that the we and the journalists used to communicate. Nathan also did that when he announced that we shut down. This piece wasn&#8217;t about apology, it was about the lessons to be gotten from it.</p>
<p>Paying writers would have changed the dynamic of our relationship. We weren&#8217;t buying content, and we weren&#8217;t hiring journalists. We were providing a service to them, and aiming to take a cut of their profits online as our income.</p>
<p>We didn&#8217;t just invent this idea. We spoke to dozens of journalists, and the product was based entirely on what they told us. We spoke to some people at Knight (not in an official capacity); I don&#8217;t want to put words in their mouths, but they obviously didn&#8217;t tell us we were doing the wrong thing or we would have changed what we were doing.</p>
<p>Our intent was plain. We wanted to make a successful company making a successful product. We could only have done that through making successful journalists. Our funders we mentioned in this piece several times: YCombinator. I&#8217;m sure they&#8217;d be delighted to invest in real journalists, and the application process is open for a few more days I believe. YCombinator&#8217;s motto is &#8216;make something people want&#8217;, and that&#8217;s what we were doing.</p>
<p>I&#8217;m afraid your final paragraph simply makes no sense. Art/science is a false dichotomy, as is left-/right-brained. To think that journalism can only come from inside to box is ludicrous. People have many skills besides the one in which they are trained, and you certainly believe this or you wouldn&#8217;t suggest that journalists, whose primary skill is not innovation, can innovate. Please don&#8217;t believe that anyone can think themselves out of this wasteland. It requires not only innovation and the right creative force (for want of a better term), but also rapid iteration, and lots of different companies trying.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced
Database Caching using disk: basic
Object Caching 315/315 objects using disk: basic

Served from: blog.paulbiggar.com @ 2012-02-06 05:03:51 -->
