<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>krschultz</author><text>An open question is how the community should provide feedback. Trello provides a decent example of how to do it well [1], but GitHub feels like a black box. I&amp;#x27;ve been on GitHub since 2008 and I have been paying every month for years, but other than emailing support I have no idea how to vote for a feature request.&lt;p&gt;My personal pet peeve is not being able to mark a public repo as &amp;#x27;deprecated&amp;#x27;. There are a lot of other people with the same frustration [2], but we have no idea how to get that on GitHub&amp;#x27;s roadmap.&lt;p&gt;[1] &lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;help.trello.com&amp;#x2F;article&amp;#x2F;724-submitting-feature-requests-for-trello&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;help.trello.com&amp;#x2F;article&amp;#x2F;724-submitting-feature-reques...&lt;/a&gt;
[2] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;isaacs&amp;#x2F;github&amp;#x2F;issues&amp;#x2F;144&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;isaacs&amp;#x2F;github&amp;#x2F;issues&amp;#x2F;144&lt;/a&gt;</text><parent_chain><item><author>jonobacon</author><text>Hi Adam, Addy, Andreas, Ariya, Forbes, James, Henry, John-David, Juriy , Ken, Nicholas, Pascal, Sam, Sindre,&lt;p&gt;My name is Jono and I started as Director of Community back in November at GitHub. Obviously I am pretty new at GitHub, but I thought I would weigh in.&lt;p&gt;Firstly, thanks for your feedback. I think it is essential that GitHub always has a good sense of not just what works well for our users, but also where the pain points are. Constructive criticism is an important of doing great work. I appreciate how specific and detailed you were in your feedback. Getting a good sense of specific problems provides a more fruitful beginning to a conversation than &amp;quot;it suxx0rs&amp;quot;, so I appreciate that.&lt;p&gt;I am still figuring out how GitHub fits together as an organization but I am happy to take a look into these issues and ensure they are considered in how future work is planned. We have a growing product team at GitHub that I know is passionate about solving the major pain points that rub up against our users. Obviously I can&amp;#x27;t make any firm commitments as I am not on the product team, but I can ensure the right eyeballs are on this. I also want to explore with my colleagues how we can be a little clearer about future feature and development plans to see if we can reduce some ambiguity.&lt;p&gt;As I say, I am pretty new, so I am still getting the lay of the land, but feel free to reach out to me personally if you have any further questions or concerns about this or any other issue. I am at jono@github.com.</text></item></parent_chain></comment><story><title>Dear GitHub</title><url>https://github.com/dear-github/dear-github</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>jhchen</author><text>Promises about the future about Github’s roadmap is understandably difficult to make, besides by a very small number of people at the top. I don’t think this is the expectation. But visibility into past failure to address these concerns and the current status is long overdue. I assume when these maintainers reached out in private channels, they were equally detailed, and have waited years.&lt;p&gt;At present, I’m not sure how this response is different from the &amp;quot;empty response&amp;quot; that motivated the publication of this document in the first place, except that this response is also public. Comments like &amp;quot;happy to take a look into these issues&amp;quot;, &amp;quot;considered in how future work is planned&amp;quot; and &amp;quot;ensure the right eyeballs are on this&amp;quot; uses a lot of words to say nothing. If the community department is not the right place, maybe it’s time to walk over to where the the product group sits and ask. They probably read Hacker New too.&lt;p&gt;I’ll also highlight a possible theory: the right people at Github have already looked at these requests and decided that is not what Github Issues is for. Perhaps Issues is prioritized for the masses, not the small minority of very popular projects (but not resourceful enough that they have staff). Each of these feature requests do add friction (if only in complexity) and the majority of projects that do not need and should not utilize them. Hopefully someone at Github will quash this theory but it is consistent with events so far.</text><parent_chain><item><author>jonobacon</author><text>Hi Adam, Addy, Andreas, Ariya, Forbes, James, Henry, John-David, Juriy , Ken, Nicholas, Pascal, Sam, Sindre,&lt;p&gt;My name is Jono and I started as Director of Community back in November at GitHub. Obviously I am pretty new at GitHub, but I thought I would weigh in.&lt;p&gt;Firstly, thanks for your feedback. I think it is essential that GitHub always has a good sense of not just what works well for our users, but also where the pain points are. Constructive criticism is an important of doing great work. I appreciate how specific and detailed you were in your feedback. Getting a good sense of specific problems provides a more fruitful beginning to a conversation than &amp;quot;it suxx0rs&amp;quot;, so I appreciate that.&lt;p&gt;I am still figuring out how GitHub fits together as an organization but I am happy to take a look into these issues and ensure they are considered in how future work is planned. We have a growing product team at GitHub that I know is passionate about solving the major pain points that rub up against our users. Obviously I can&amp;#x27;t make any firm commitments as I am not on the product team, but I can ensure the right eyeballs are on this. I also want to explore with my colleagues how we can be a little clearer about future feature and development plans to see if we can reduce some ambiguity.&lt;p&gt;As I say, I am pretty new, so I am still getting the lay of the land, but feel free to reach out to me personally if you have any further questions or concerns about this or any other issue. I am at jono@github.com.</text></item></parent_chain></comment><story><title>Dear GitHub</title><url>https://github.com/dear-github/dear-github</url></story>