Robert Kaiser wrote:
Paul B. Gallagher wrote:
It's a fine line to walk when lobbying for change -- you have to push
hard enough, but not too hard, give credit, but not too much credit, and
so forth. From what I can tell, you've done a lot of good with the new
version, but every user has his own set of priorities as to which
features matter more or less.
Right. The only way to really change thing in an open source project,
though, is to step up and try to help making progress in the direction
you want. Bitching volunteer developers only helps to stop any progress
that would be happening.
In the case of the form management, it would help if someone would step
up and try to work on writing up something that can bring those features
back that some people apparently liked, without harming the features we
gained by the switch to the new code, e.g. remembering a lot of field
data in places where we didn't do that in 1.x times.
Shouting won't help. Trying to help to get code into place does.
Scratching your own itch by actually working on it is the best way to
get things done in any open source project.
I thought you (some developer?) said it had to be accepted by Firefox because it
would be in the common code. In any case, motivation wanes now that there is an
add-in which is usable if not perfect.
--
Bill Davidsen <[email protected]>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
