"feedback from the community on the matter - that's what Launchpad is
for, right?"

Someone can correct me if I'm wrong, but I don't thing that's right;
that's what the community forums are for. Launchpad Bugs is for
reporting technical problems, FTBFS, regressions, incompatibilities,
wishlist items, etc., and to do so in a way a developer or maintainer
can act upon.

My opinion is that the folks who are hard at work coding what will
hopefully become improvements to the desktop experience should also take
into account the effect of incremental changes. For example, until the
project is fully implemented it would be a good idea to document how to
revert to previous behavior. Also, I don't think new code should be
introduced without posting somewhere how to configure it. The old panel
applets were configurable in gconf. With the new code, perhaps the
design decisions are hard-coded; I have no idea how to customize it. I
would prefer greater "openness" in the sense of publicly available
documentation and increased configuration options, even if they are
hidden away in dconf or dot files or something like that.

Indeed, it would be preferable for the battery status applet to show
both the time remaining and the % charge/discharge, but I don't mind if
I have to click once to see it. That to me is a regression. With no
config option, I do consider it a regression, an inconvenience and
wishlist item for the new software to include.

-- 
please include status messages/tooltips
https://bugs.launchpad.net/bugs/527458
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to