Garrett Rooney wrote:
> On 11/22/05, Thompson, Graeme (AELE)
> <Graeme.Thompson@smiths-aerospace.com> wrote:
>>
>> What would you suggest would be the best way to get this issue fixed?
>>
>> A working path has existed for months, but it has not been
>> incorporated into the main trunk. It shouldn't be a massive effort
>> to get this done.
>
> Convincing the developers that the feature is worth having. This
> means that it's useful, and that the patch is good, and that it
> doesn't make the code or UI overly complex and unmaintainable.
>
> Note that these are exactly the same steps that every single change to
> Subversion has to go through, this is no different. If nobody is
> willing to shepherd the change through until it can be committed, then
> it simply won't be, that's how open source works.
So, other than pestering the dev list (which would be bad), or getting
added to the dev team (which isn't something everyone can do), what
should people do? If you look back through this thread, you'll see my
analysis of the votes in the Subversion Issue Tracker, and the comments
that voting doesn't really seem to affect the dev team's decisions. How
else can we go about "convincing the developers that the feature is
worth having...useful...good", etc.?
I frankly don't know.
Voting for Issues makes the most sense, but if the dev team is unwilling
to pay attention to the desires of the community as explicitly expressed
by that voting, what is the community supposed to do?
-David
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 22 20:33:20 2005