I'm going to wade in with another sideways take on this thread. Summary: ask other developers and/or make constructive suggestions. Don't flame developers... no-one wins if it goes that way.
Laurens M. Fridael <[EMAIL PROTECTED]> wrote: > You've already indicated that you have no inclination to address this issue. > There's no need to defend that position. People keep attacking on this issue as if it is a battle, so it shouldn't be a surprise that some people will defend the progress made so far. If advocates of this fix were a little less confrontational, it would probably be corrected sooner. > Everyone understands that it's free software and the time and effort that > went into it. Still, many people do find this problem annoying because > it's a limitation that greatly affects usage. Yes, it's a bug. Help in finding the best way to fix it has been requested. Some developers have said that it doesn't bother them, so they probably won't fix it. Again, that's really a request for more help fixing it. > Dismissing their "demands" as "bitching" makes you come off as unwilling > to listen to user requests, which is not the best way to promote your > software. I clearly filtered that out. Try to do so too. They work hard and sometimes get bad-tempered. It doesn't excuse it, but flaming them on-list for it won't help. You have to remember: not all of the developers depend on plucker being promoted and popular. Some of them are doing this for fun and non-constructive criticism about something they can't or won't fix makes it less fun for them. Annoy them enough and we'll have fewer developers. The two best ways to respond are either constructive criticism, or asking other developers to help. Or become a developer too. I guess that's three. Just as well I'm not teaching maths. Oh wait, I do. Ooops. ;-) MJR _______________________________________________ plucker-list mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-list
