Is it better to develop inside or outside KDE?
As core developer Waldo Bastian explains in a copyrighted mail: Being part of KDE means that you have to work together with others. Such cooperation brings along advantages but it also brings along responsibilities. Some of those advantages are: your code ends up on all distro’s, people might fix your bugs, you get free translations and documentation, you get tons of bugreports. On the other side there are disadvantages and responsibilities: you will have to communicate with other developers about your work, other people might make changes to your code, you will have to respect release freezes, you get tons of bugreports and people actually expect that you fix them as well (what are they smoking?), people expect you to maintain your code. You can’t chose for the advantages and ignore the responsibilities that come with it, it’s a complete package, it’s both or nothing. In general it should be the author of a piece of software that chooses to put his application in SVN. We usualy don’t
