<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>steveklabnik</author><text>I do this on all my personal projects now. It&apos;s pretty amazing. I&apos;ve actually gained several long-term contributors by doing this.&lt;p&gt;I&apos;ve gotten emails from people that said, in effect, &quot;Thanks! I feel like part of the team, that you trust me with the code. Before, I was just going to fix that one bug, now, I&apos;m excited to poke around the codebase and see how I can help.&quot;&lt;p&gt;Really, this is a variant of a theme that we see around here all the time: autonomy, mastery, and purpose. The upside is that you empower people to take mastery over the code they use, you provide them with the autonomy a commit bit has to offer, and you give them a sense of purpose: you&apos;re now helping everyone else out, too.</text><parent_chain></parent_chain></comment><story><title>The Pull Request Hack</title><url>http://felixge.de/2013/03/11/the-pull-request-hack.html</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>wuest</author><text>This is a clever bit of social engineering which really taps into the mentality, not to mention the rhetoric, of open source hackers.  I like it!</text><parent_chain></parent_chain></comment><story><title>The Pull Request Hack</title><url>http://felixge.de/2013/03/11/the-pull-request-hack.html</url></story>