On 20/08/14 11:51, Richard Weinberger wrote: > > But if there is an issue with almost no reaction from developers > within 14 months > I begin to wonder WTF is going on. > A simple "We're working on it..." would not harm.
Fair enough, and I can fully grasp this. But I'll give you a glimpse of the bigger perspective. There are now 3-5 active _community_ developers, and only one of them really plays with Windows. And almost none of them are paid to do OpenVPN. Then you have the users, and there are insanely many of them, Many of those finds bugs or issues and some of them actually do report them. Unfortunately the list of bugs just seems to increase, some with really important issues to fix. So what really happens is that when some of the community developers have some time to hack on OpenVPN, the attention is mostly given to the areas where they have issues too, or have promised to fix things. And if all that is done (which is quite seldom), we tend to look at the areas of the code base which we know best. However, if patches which fixes things arrives on the ML, then they do get reviewed at some point, especially if there are good descriptions of the patches and good test descriptions. When this happens, patches are accepted much quicker. If there's just a patch without much additional comments, the patch might linger for a long time unless some of the developers knows the code paths quite well. What I'm trying to say is that we need more people who understands coding to submit good patches with fixes, so that others can help review or test them easily. Then you'll get a quicker turn-around on these reports. And that is why we tend to be touchy when people complain too loud. But if you want to gain respect and get gratitude from the developers, sending patches is the very best cure. -- kind regards, David Sommerseth
signature.asc
Description: OpenPGP digital signature
