Re: System Presence Integration Idea
On Wednesday 12 March 2008 17:38:54 Chris Warburton wrote: With the increased momentum towards unified messaging and presence systems (ie. Telepathy and things built on top such as Decibel) I think there needs to be some thought put into the use of presence by the system. That is, if the system can see the user's various presence attributes then it can infer actions to take (locking screen when Away for example), and likewise the user's actions can infer their presence (Away when screen locked). If integrated throughout the stack then this could be a very powerful, and as far as I know unique to Free Software, feature. To me such an idea would take 3 stages to implement: 1) Discussion and brainstorming of possible use cases throughout the system 2) Building the infrastructure needed to enable such cases (Dbus as far as I can tell) 3) Creation/modification of interfaces for users to control them I have written a spec[1] and blueprint[2] for stage 1, the discussion, which I think needs to be had (even if it results in rejection of the idea) and was wondering what people thought. I have also added it to the Ubuntu Brainstorm[3]. Thanks, Chris Warburton 1 https://wiki.ubuntu.com/SystemPresenceIntegrationSpec 2 https://blueprints.launchpad.net/ubuntu/+spec/system-presence-integration 3 http://brainstorm.ubuntu.com/idea/1650/ Great. I've been looking for a way to do this for a long time. I guess this will be a great addition to Hardy+1 ( Intrepid Ibex ). Just a new idea to join: have an option to reduce CPU/screen power to lower limits, saving energy when not in use, or the ability to start management tasks or seti-at-home alike apps. -- BUGabundo :o) (``-_-´´) http://Ubuntu.BUGabundo.net Linux user #443786GPG key 1024D/A1784EBB My new micro-blog @ http://BUGabundo.net 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... signature.asc Description: This is a digitally signed message part. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: System Presence Integration Idea
On Wed, 2008-03-12 at 17:38 +, Chris Warburton wrote: To me such an idea would take 3 stages to implement: 1) Discussion and brainstorming of possible use cases throughout the system 2) Building the infrastructure needed to enable such cases (Dbus as far as I can tell) 3) Creation/modification of interfaces for users to control them I think that this is an interesting topic, and one that we do need to solve for the desktop. I think that one thing that needs to be in your list, 1a perhaps, is looking at the way that people think about their status. For instance, when I'm at work I really don't want my buddies sending me pictures from the party over the weekend. But, e-mail from my boss probably had less importance while I was at those parties. I know that in the spec you mentioned gathering such information from the WiFi hotspot being used, which is interesting. I'm curious if that is enough. Also, how much configurability would someone want? Status on every IM network for every hotspot seems like a crazy matrix. --Ted -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: System Presence Integration Idea
On Thu, 2008-03-13 at 12:07 -0700, Ted Gould wrote: I think that this is an interesting topic, and one that we do need to solve for the desktop. I think that one thing that needs to be in your list, 1a perhaps, is looking at the way that people think about their status. For instance, when I'm at work I really don't want my buddies sending me pictures from the party over the weekend. But, e-mail from my boss probably had less importance while I was at those parties. I know that in the spec you mentioned gathering such information from the WiFi hotspot being used, which is interesting. I'm curious if that is enough. Also, how much configurability would someone want? Status on every IM network for every hotspot seems like a crazy matrix. --Ted Hi thanks for the input. I realise that such a proposal is quite open ended, thus I tried to split it into relatively clear steps to go through to try and prevent both blue sky designing and worrying about issues that end up not appearing in the implementation. I think stage 1, the discussion, should be a quite technical discussion, ie. throw some ideas into the aether and decide which of those is possible. My own train of thought was about having Telepathy running as a central, standard system to use for presence. Presence would cover general key:value type data, ie. Location:Home, Status:Busy, Activity:On The Phone, etc. (those are just examples). There may need to be an agreed upon standard for the naming here, if multiple programs and desktop environments are going to use it. The model for broadcast of these would be, I would think, XMPP's Publish/Subscribe system (I've heard good things about it, but haven't used it personally). For other networks it could perhaps fall back to a generic status message containing the pairs. What I think is the most interesting aspect is using presence locally, ie. having a way to tell your computer what you're up to and configuring it to take some actions based on that. Local presence can be taken straight from Telepathy itself or a local account inside Telepathy, thus legacy network issues aren't too important for this. In terms of UI I think everything should be opt-in, so the Wifi example I gave would have a user explicitly saying this Wifi network means Home and this Wifi network means School and then the machine only acts when those two are detected. A lot of the possibilities this could enable may be annoying to have on by default, so I think options should be opt-in to begin with. These UI issues are the 3rd stage I proposed though, and I imagine will mainly consist of a few widgets added to some already existing preference dialogues. Thanks, Chris -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: System Presence Integration Idea
Chris Warburton wrote: Hi thanks for the input. I realise that such a proposal is quite open ended, thus I tried to split it into relatively clear steps to go through to try and prevent both blue sky designing and worrying about issues that end up not appearing in the implementation. I think stage 1, the discussion, should be a quite technical discussion, ie. throw some ideas into the aether and decide which of those is possible. My own train of thought was about having Telepathy running as a central, standard system to use for presence. Presence would cover general key:value type data, ie. Location:Home, Status:Busy, Activity:On The Phone, etc. (those are just examples). There may need to be an agreed upon standard for the naming here, if multiple programs and desktop environments are going to use it. IMHO what you need is a central daemon that only performs a few actions and communicated via D-BUS. You just have to set a D-BUS protocol so that programs can set/get the state: Telepathy can set it, but also retreive it when starting - this way the daemon can test some system parameters and decide of a certain state automatically depending on the network, on the battery... Maybe gnome-session could be the place to do so. And network settings has a profile management that you could integrate. Just ideas... Cheers -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
System Presence Integration Idea
With the increased momentum towards unified messaging and presence systems (ie. Telepathy and things built on top such as Decibel) I think there needs to be some thought put into the use of presence by the system. That is, if the system can see the user's various presence attributes then it can infer actions to take (locking screen when Away for example), and likewise the user's actions can infer their presence (Away when screen locked). If integrated throughout the stack then this could be a very powerful, and as far as I know unique to Free Software, feature. To me such an idea would take 3 stages to implement: 1) Discussion and brainstorming of possible use cases throughout the system 2) Building the infrastructure needed to enable such cases (Dbus as far as I can tell) 3) Creation/modification of interfaces for users to control them I have written a spec[1] and blueprint[2] for stage 1, the discussion, which I think needs to be had (even if it results in rejection of the idea) and was wondering what people thought. I have also added it to the Ubuntu Brainstorm[3]. Thanks, Chris Warburton 1 https://wiki.ubuntu.com/SystemPresenceIntegrationSpec 2 https://blueprints.launchpad.net/ubuntu/+spec/system-presence-integration 3 http://brainstorm.ubuntu.com/idea/1650/ -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
