[Chandler-dev] Supporting an auto-update feature for the Desktop

[Sheila Mooney]

Grant,

Thanks for looking into this and providing the estimate. This will of  
course need to be prioritized along with everything else in the 1.0  
queue. I knew it had been under discussion before but I didn't  
remember it went that far back :-). I suspect that we had always  
thought of it from the perspective of an end-user feature and not for  
gathering metrics. Yes, we would need an opt-out for people, I meant  
to mention that in my original post.

Cheers,
Sheila

On Mar 27, 2008, at 5:00 PM, Grant Baillie wrote:

> On 27 Mar, 2008, at 15:23, Sheila Mooney wrote:
>> We would have to monitor the update check somehow. Of course, I  
>> have no idea what is easy/hard technically. The theory is that if  
>> your application is checking for updates, it means you are running  
>> Chandler. We currently monitor synchs per day on the hub and equate  
>> that to "activity".
>
> It's not too hard to do, even though what you want seems to have  
> been under discussion since 2004:
>
> <https://bugzilla.osafoundation.org/show_bug.cgi?id=603>
>
> Of course, such a thing could only start happening in 0.7.6, and  
> also people should probably have some kind of opt-out (for privacy  
> reasons).
>
> Now that I have some idea of the workings of the build system and  
> various web servers, I think that it wouldn't take more than a  
> couple of days to get something basic working (a periodic or manual  
> check, followed by showing a simple dialog if something new is  
> available).
>
> I also have a couple of related (but somewhat different) proposals  
> in my queue for 1.0:
>
> <https://bugzilla.osafoundation.org/show_bug.cgi?id=11448>
> <https://bugzilla.osafoundation.org/show_bug.cgi?id=11737>
>
> It might be a good time to review these and figure out exactly what  
> we'd like to do for 1.0 :).
>
> --Grant
>
>> On Mar 27, 2008, at 3:04 PM, Grant Baillie wrote:
>>
>>> On 27 Mar, 2008, at 14:59, Sheila Mooney wrote:
>>>> Not sure if this makes things easier but we could also simply pop  
>>>> up
>>>> a dialog letting people know there is an update available and they
>>>> could install manually. It would accomplish the same goals as far  
>>>> as
>>>> finding out who is running Chandler.
>>>
>>> Hi, Sheila
>>>
>>> How would that help you distinguish regular users from people who
>>> download, but don't use regularly?
>>>
>>> --Grant
>>>
>>> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>>>
>>> Open Source Applications Foundation "chandler-dev" mailing list
>>> http://lists.osafoundation.org/mailman/listinfo/chandler-dev
>>
>> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>>
>> Open Source Applications Foundation "chandler-dev" mailing list
>> http://lists.osafoundation.org/mailman/listinfo/chandler-dev
>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "chandler-dev" mailing list
> http://lists.osafoundation.org/mailman/listinfo/chandler-dev