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.
On Mar 27, 2008, at 11:24 AM, Mimi Yin wrote:
Something else we could do is subscribe to a "Chandler Help"
collection out of the box. You can always unsubscribe. But if you
don't, you'll periodically ping the server even if you're not
sharing for your own purposes.
It would also provide us with a way to demonstrate sharing
functionality and send announcements to users.
Mimi
On Mar 26, 2008, at 8:54 PM, Sheila Mooney wrote:
So, it's my understanding that we have discussed this before but I
wanted to throw it out on the list again.
As part of the metrics project I am working on, I am looking at
ways to better track the users we have. We currently capture
metrics around people synching to the hub but this doesn't really
tell us anything about the users who aren't sharing - I think they
are out there. I was thinking that an auto-update feature would
enable us to get better metrics on people who are using the desktop
regularly. As an end-user feature, auto-update is probably a nice-
to-have but for collecting data it might be very useful.
I was interested in some kind of discussion around the cost and
complications of implementing this and what creative ideas might be
floating around. Grant, I am cc'ing you in particular to help kick
off the discussion.
Cheers,
Sheila
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
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
