Comment 73 for bug 346095

> Most of us are angry because it is flagged as "Wishlist" and not "Bug".

Well, it's not a bug - plain and simple. There is no code in the program for moving the notification, so how can there be a bug that doesn't inherent preferences? That's like saying "When I installed Amarok, it didn't import my Rhythmbox library." Besides, this whole bug or wish-list thing is just a word to help categorize items. There have been wish-list items fixed before bug items and vice-versa. It all depends on who wants to program what at what time. The unfortunate underlying concept here is that this is Mark S.'s baby and we have to convince him. :/ Besides all that, isn't there a more proper place to talk about this? Maybe one where actual developers will directly hear your opinions?

From http://www.ubuntu.com/community/ReportProblem:
"Feature and policy discussions should be discussed on the ubuntu-devel mailing list"
To help you out even more, you can sign up here:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel

> "It's a bug and we will fix it as soon as possible".

That is laughably un-true - as soon as possible. I wish it were true though! =)

> Not to mention that you force code that's no-where NEAR complete down the
> pipes to people who expect a release to have pretty proven code.

Seems pretty complete to me. Most problems that people are having stems from changing their icon set/theme or using a "weird" monitor layout - all of which have/are being fixed. The only problem I personally have with it is when my Mobile Broadband connection connects, I get about 6 messages in ~/.cache/notify-osd.log in a 0 second span, causing the bubble to "flash" for a bit before settling down, and I'm sure it will be fixed in one way or another - who knows, maybe it's NetworkManager's fault.

> I will not "wait" for developers to finish, that's what the dev-cycle of
> this release was for. They should have offered this replacement as
> experimental and an optional install if they wanted a "break" from
> criticism.

I did not intend to say or imply we wait for them to finish, I merely meant to recommend that you allow them time to work out the kinks. Even firefox has several on-going problems that have been put to the way-side for one reason or another - should firefox still be an experimental, optional install? These so-called "issues" are more common than you all want to believe.

> Also, your argument that programs overuse libnotify is mind boggling...
> The programs that use libnotify wouldn't use libnotify if their users didn't
> want it to use libnotify. Just like your argument for this new feature...
> The users who don't like this new notification system can use another one.

It wasn't an argument that the programs overuse libnotify. I was referring, mainly, to the pidgin "problems" people have. Those users feel that pidgin is overusing the bubbles (sign on/off, etc). That is not notify-osd's problem, and pidgin has a facility to deal with it. If users feel other programs have a similar 'over-use' then they should recommend the program adjusts it's features, just like pidgin has a facility for. Again, it's not notify-osd's fault.

> I'd just like to point out though... that the users of ubuntu will no longer
> use ubuntu if they no longer like ubuntu.

Agreed. We choose to compute in an open environment - open to feelings, open to change, open to leave. However, if something as silly as notifications cause them to leave... Then, I doubt they will find happiness anywhere, but I wish them luck.

In closing, I sincerely hope this discussion will be moved to the proper place for this kind of talk, as I feel it's these bug-reports-turned-to-forum-threads that hurt Ubuntu more than anything - and I will be taking my own advice, since I do, in fact, believe there should be a facility to customize the notification bubbles.