<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>madeofpalk</author><text>I agree - I think the maintainers of the project could have handled this better by responding to it immediately. But that wouldn&amp;#x27;t have resolved the wasted effort of the whole PR.&lt;p&gt;&amp;gt; &lt;i&gt;Just accept the grief and venting, people deserve it. It’s toxic positivity.&lt;/i&gt;&lt;p&gt;Absolutely not. No one is entitled to vent at a project, and no maintainer deserves to have that directed to them.</text><parent_chain><item><author>klabb3</author><text>Look at the timestamps. It’s months of complete silence, which is not a great sign from a saas. It was clear that the feature was popular.&lt;p&gt;Another thing that annoys me to no end is locking threads because it’s “heated”. Just accept the grief and venting, people deserve it. It’s toxic positivity.</text></item><item><author>madeofpalk</author><text>One lesson from this is to not contribute a &amp;#x27;major feature&amp;#x27; to an open source project without a signal that it would actually be accepted. Even if the feature doesn&amp;#x27;t conflict with enterprise&amp;#x2F;monetisation, the feature could just be against the goals of ideals of the maintainers, of whom the project is up to.&lt;p&gt;Open source is not a mandate that the maintainers must accept every contribution. The author should consider why they don&amp;#x27;t want to maintain a fork, and whether that&amp;#x27;s the same reason why this PR was rejected in favor of an enterprise feature.</text></item></parent_chain></comment><story><title>When &apos;open core&apos; projects reject contributions for competing with the EE</title><url>https://github.com/hoppscotch/hoppscotch/pull/3266</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>soamv</author><text>&amp;gt; Just accept the grief and venting&lt;p&gt;Maintainers do not owe you this, in addition to maintaining the software that you can use for free. You&amp;#x27;re entitled to be upset, and they&amp;#x27;re just as entitled to say &amp;quot;please go somewhere else to vent, we&amp;#x27;re busy&amp;quot;.</text><parent_chain><item><author>klabb3</author><text>Look at the timestamps. It’s months of complete silence, which is not a great sign from a saas. It was clear that the feature was popular.&lt;p&gt;Another thing that annoys me to no end is locking threads because it’s “heated”. Just accept the grief and venting, people deserve it. It’s toxic positivity.</text></item><item><author>madeofpalk</author><text>One lesson from this is to not contribute a &amp;#x27;major feature&amp;#x27; to an open source project without a signal that it would actually be accepted. Even if the feature doesn&amp;#x27;t conflict with enterprise&amp;#x2F;monetisation, the feature could just be against the goals of ideals of the maintainers, of whom the project is up to.&lt;p&gt;Open source is not a mandate that the maintainers must accept every contribution. The author should consider why they don&amp;#x27;t want to maintain a fork, and whether that&amp;#x27;s the same reason why this PR was rejected in favor of an enterprise feature.</text></item></parent_chain></comment><story><title>When &apos;open core&apos; projects reject contributions for competing with the EE</title><url>https://github.com/hoppscotch/hoppscotch/pull/3266</url></story>