Extend the "Why can't I open up an issue" section in the readme

README.md

@@ -2,14 +2,18 @@
 
 I love the [Sublime Text](http://www.sublimetext.com) editor. [I have](https://github.com/quarnster/SublimeClang) [created](https://github.com/quarnster/SublimeJava) [several](https://github.com/quarnster/CompleteSharp) [plugins](https://github.com/quarnster/SublimeGDB) [to make](https://github.com/quarnster/ADBView) it even better. One thing that scares me though is that it is not open sourced and the [pace of nightly releases](http://www.sublimetext.com/nightly) have recently been anything but nightly, even now that version 3 is out in Beta.
 
-There was a period of about 6 months after the Sublime Text 2 “stable“ version was released where pretty much nothing at all was communicated to the users about what to expect in the future, nor was there much support offered in the forums. People including myself were wondering if the product was dead and I personally wondered what would happen to all the bugs, crashes and annoyances that still existed in ST2. This lack of communication is a dealbreaker to me and I decided that I will not spend any more money on that product because of it.
+There was a period of about 6 months after the Sublime Text 2 "stable" version was released where pretty much nothing at all was communicated to the users about what to expect in the future, nor was there much support offered in the forums. People including myself were wondering if the product was dead and I personally wondered what would happen to all the bugs, crashes and annoyances that still existed in ST2. This lack of communication is a dealbreaker to me and I decided that I will not spend any more money on that product because of it.
 
 As none of the other text editors I've tried come close to the love I had for Sublime Text, I decided I had to create my own.
 
 The frontend(s) are not ready to replace your favourite editor, but the backend itself I believe isn't too far away.
 
 ![Screenshot taken Oct 23 2013](http://i.imgur.com/VIpmjau.png)
 
+### Why create a clone?
+
+Because I like the architecture of the extensibilities in the original editor.
+
 # Goals
 
 - ☑ 100% Open source
@@ -26,9 +30,23 @@ The frontend(s) are not ready to replace your favourite editor, but the backend
 - ☐ Terminal UI (*Maybe* I’ll work on a simple non-terminal UI at some point)
 - ☐ Cross platform (It appears to be compiling and running on OSX and Linux last I tried, but needs further validation.)
 
-# Why can’t I open up an issue?
+# Why can't I open up an issue?
+
+Because I'm just a single person and I don't want to offer up my spare time doing support or dealing with feature requests that I don't care about myself. If you want a feature implemented or a bug fixed, fork it and implement it yourself and submit a pull request when you're happy with the implementation.
+
+### Isn't that exactly what you were complaining about earlier?
+
+Sadly I have to add this section as people keep asking, and the answer is "not at all". If you really are wondering, perhaps that's a sign you need to educate yourself regarding the concepts of [Free Software](http://www.gnu.org/philosophy/free-sw.html) and [Open Source](http://opensource.org/).
+
+I cannot fix issues in the original software due to it's closed nature and I'm thus dependant on the author of it acknowledging the existence of the issue and then have a dialogue with him until it is solved. When the author does not respond at all, this model breaks down and there is nothing at all I can do.
+
+In contrast, as this project is 100% Open Source no one depends on me to fix anything and everyone can change exactly every single line of code that makes it up without my personal involvement.
+
+### Will you please open up the issues list? It'll make cooperation easier.
+
+Well, why don't you fork it and open up the list in your fork? Why isn't any excuse you can think of to not do that valid for me also?
 
-Because I’m just a single person and I don’t want to offer up my spare time doing support or dealing with feature requests that I don’t care about myself. If you want a feature implemented or a bug fixed, fork it and implement it yourself and submit a pull request when you’re happy with the implementation.
+Just because I kicked this off doesn't mean I'd like to be the spider in the web managing it. I have after all not written [much code](https://github.com/quarnster/lime/graphs/code-frequency) for it since April 2013. If you'd like to ask if anyone else is working on something before you dig in, feel free to summon me via @quarnster, or you could just grab my email address from a commit via ```git log --author=quarnster -1```.
 
 # Build instructions