[Pidgin] #4986: automatic chat input field resizing should be optional, regression from 2.3
Pidgin
trac at pidgin.im
Wed Apr 23 23:00:24 EDT 2008
#4986: automatic chat input field resizing should be optional, regression from 2.3
---------------------------+------------------------------------------------
Reporter: swbrown | Owner:
Type: enhancement | Status: closed
Priority: minor | Milestone:
Component: pidgin (gtk) | Version: 2.4.0
Resolution: wontfix | Keywords: chat input resize
Pending: 0 |
---------------------------+------------------------------------------------
Comment (by rekkanoryo):
Replying to [comment:272 DanLivingston]:
> I teach "Collaboration in an Open Source World" at a local college. I
have been searching for, and in this ticket have found, a perfect example
where communication between open source developers and users fails at
multiple, fundamental levels.
[[BR]]
You are making a fundamental mistake here in assuming that communication
has failed. The fact that we aren't willing to undo our UI changes is not
a sign of communications failure. We have listened to the whining, the
complaining, the threats, and the few well-presented and logical arguments
we've received. We are working to improve the changed UI; reverting this
is a step ''backwards'' in the development process that we're not willing
to take.
[[BR]]
> What happens when those same newfound powers are taken away? What
happens when the developers impose their personal dogmas upon the project?
Even for as small an issue as chat window resizing, a minority (or
majority) of users will emphatically express dissent.
[[BR]]
As I noted in another ticket related to the automatic resizing, we had
similar numbers of complaints about our changes to the buddy list and
status UIs in the transition from 1.5.0 to 2.0.0. The complaints died
down after several weeks. The loss of protocol icons as status indicators
is a dead issue and has been for many months now. The change to a status
selector that is a first-class citizen in the buddy list window also
caused some friction that died down after a short time. The same will
happen with the input area resizing given time.
[[BR]]
> ''<snip of long, rambling text only tangentially related to the
following>'' [[BR]]
> The fact is that typing letters into an IM window is THE most critical
task of an IM program. Users have varying needs, needs which can not be
addressed by your limited attempts to come up with "one solution for
everything" that incorporates "shiny new logic" that demonstrates how
smart you are. You are ignoring the fan base with a dedication to your
convictions that is alarmingly evident to even the most unobservant of
followers, and as such, you are demonstrating that you no longer deserve
to be in the position of servicing the needs of your user base.
[[BR]]
None of us develop Pidgin as a function of our job. Pidgin is a hobby for
us. We don't claim to represent a community--we claim to make an IM
client that meets '''our own needs''' and ''hopefully'' meets others'
needs as well. We aren't forcing anyone to use our software, nor are we
profiting from our users. As you noted, we have the autonomy to make our
own decisions. We are the people putting forth the development effort,
and therefore we have a right to decide what goes into our software.
Quite simply, it doesn't matter if we have one user or six billion users
outside the developer community. We have long understood that we can
never please all our users with our single user interface--it's simply not
possible. Because of that, we do not aim to please all our users, but
instead to please ourselves and hope that we have pleased like-minded
users. We encourage users whose needs are not met by our software to find
other software that does meet their needs.
[[BR]]
> For the sake of everyone involved, I hope you find your path back to the
light.
[[BR]]
We never strayed from our path. The Path to Enlightenment is unique for
each individual.
--
Ticket URL: <http://developer.pidgin.im/ticket/4986#comment:275>
Pidgin <http://pidgin.im>
Pidgin
More information about the Tracker
mailing list