﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>James Newton-King commented on Send me a patch for that</title><description>This guy has no concept of opportunity cost.

My time is important and the time I do spend on OSS is spent on the features that help the most people. If I tell someone that I don't have time to implement the feature they want it is because I don't think it is important as another feature that helps more people.</description><link>http://ayende.com/154305/send-me-a-patch-for-that#comment2</link><guid>http://ayende.com/154305/send-me-a-patch-for-that#comment2</guid><pubDate>Fri, 10 Feb 2012 12:27:26 GMT</pubDate></item><item><title>Hadi Hariri commented on Send me a patch for that</title><description>And I would agree that if someone wants to contribute to your codebase then those are the minimum in terms of stumbling blocks one has to overcome. 

Offering the user to submit patches when a feature request (or even a minor bug) doesn't fit in with the current plans, is acceptable and one of the benefits of OSS. You offer them a choice. 

However, if we try and generalize this and apply it strictly to feature, bug, critical or not, and they way in which we approach users, that's what I think is wrong and is counter-productive to the adoption of our project among other things. 
</description><link>http://ayende.com/154305/send-me-a-patch-for-that#comment1</link><guid>http://ayende.com/154305/send-me-a-patch-for-that#comment1</guid><pubDate>Tue, 07 Feb 2012 06:50:56 GMT</pubDate></item></channel></rss>