Auto-launching of applications
(=?iso-8859-1?q?=60=60-=5F-=B4=B4?=) -- BUGabundo
ubuntu at bugabundo.net
Thu Feb 26 02:18:01 UTC 2009
Olá Mark e a todos.
On Wednesday 25 February 2009 09:40:04 Mark Shuttleworth wrote:
> 4. opening a system modal window in the foreground (obviously, this is only for total emergencies)
Even in the case of emergency, can these *popups* not take control of keyboard (and may I even dare to say the mouse, if it already above the window) ?
I'm not wishing for something like Mozilla's count down, of course (those who like that, can now throw me rocks), but some method that requires user *action* over the popup, and not accidental click.
> and apologise that the initial landing wasn't smooth -
> in particular for our core dev team and beta / development release
> users, who of course are a key part of the community. Since these
> changes had been discussed at UDS, we didn't expect such a big surprise,
> but we should have announced the changes here when they landed and
> provided a forum for this discussion.
I've started a thread a few weeks back, on both -devel and -devel-discuss, called:
[RFC] Improve communication with testing users about master key changes in development branches
that didnt get much traction, and in the light of your words I would like to resurrect.
The "beta / development release users" need a clear source of information of thing that are going to change, what changed, how it changed, and is this upstream or (x/k)ubuntu only.
There was the discussion that some devs are leaving the devel-discuss list, but I see many users on #ubuntu+1 that arent on -devel ml, and it seems that most of the "hot topics" are announced/flamed here (and I guess the rest on IRC weekly meeting).
James has been doing a great job with his technical news bulletins, and the meetings resume are also great. But the problem remains: the information there is scarce and most of the times post-applied. Again, I would like to state that I dont want to impose even more workload with providing updates (I know most of you hate _paperwork_ as much as I do), but we need to have a better way to communicate this changes, in a away that doesnt create noise for TeamDevs, but actually makes the broad testing community to get it.
_Now the hard part_, I have no idea what that way is. A new [announce]ML? a wiki? a feed on fridge? I'm open to suggestions, but one thing is clear: it needs to be short, concise, multi formated (feed,email,etc), *pre*-changes (so that healthy discussion can come from it, even if it means that some users/devs will flag it until eventually they learn the extra value of future changes), and finally appealing to the testers so that they actually want to have it.
> So, thanks to Bruce Cowan for raising the thread.
bruce89 wink ;)
--
Hi, I'm BUGabundo, and I am Ubuntu (whyubuntu.com)
(``-_-´´) http://LinuxNoDEI.BUGabundo.net
Linux user #443786 GPG key 1024D/A1784EBB
ps. My emails tend to sound authority and aggressive. I'm sorry in advance. I'll try to be more assertive as time goes by...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <https://lists.ubuntu.com/archives/ubuntu-devel-discuss/attachments/20090226/93bab70d/attachment.sig>
More information about the Ubuntu-devel-discuss
mailing list