[GSoC] Automated Usage Stats Collection

Mark Doliner mark at kingant.net
Sun Apr 1 22:41:08 EDT 2012

On Sat, Mar 31, 2012 at 11:45 PM, Rishi Agarwal <rishiag.iitd at gmail.com> wrote:
> 1. Regarding restrictions, I have following examples in my mind:
> (a) No direct access to user's and his contacts' mail ids. If at all, a
> plugin requires to collect these stats (let's say a plugin which collects
> the level of participation in a group chat), actual ids will be substituted
> with dummy markers.
> (b) Limited access to chat conversations and keyboard. Actual chat
> conversations can't be logged and only keyboard commands (like Alt +F4) can
> be logged. This is basically to facilitate debugging while not compromising
> on privacy.

Hmm, those are certainly respectable goals.  I should note that
currently there are no restrictions on what plugins can do.  They can
access basically all of the user's information, and they can make TCP
connections and transmit this data anywhere.  Adding restrictions on
what can be logged probably would reduce the chance that some
sensitive will be logged... but it's not a 100% guarantee.

> The crash reports that I am targeting are mainly from the plugins' crashes.
> Also, why I thought grouping of crash reports and filing under the same
> ticket will be required is because multiple user's will have same sort of
> crashes in a single plugin. Grouping will make it easy for the developer to
> prioritize the issues which need to be fixed.

Oh, yeah, I'm definitely in favor of grouping.  I guess I'm just not
convinced that opening tickets in our existing ticket tracker is a
good idea.

More information about the Devel mailing list