On Nov 17, 4:25 pm, jinghua zhang <jinghuaz...@gmail.com
> Hi jjb,
> Sorry for the late reply.
> Yes, you are very welcome to post your work on Test Pilot forum (this one),
> or even in our blog or website, which we will open to public submission in a
> couple of months. If you prefer to start on your personal blog, we can also
> help you to spread the word around through our Test Pilot channels.
I guess I don't know the correct terms. The question I have is: once I
have code that stores firebug usage data I need to send it somewhere
to be aggregated and analyzed. Can you help with that part of the
> For your ideas, I think the metrics and questions you proposed are
> definitely interesting to dig into. We can also provide help to review these
> metrics together with Firebug team when you are close to execute. From items
> you listed in the email, it seems a lot of work. It would be great if you
> can do one small successful case first, then we can work on a bigger one
> later. :)
Yes, sure that make sense. But really collecting the data is the easy
> I am not sure if you need to do any preparations before you instrument
> Firebug, e.g. data policy. If you think there is something that Test Pilot
> Data policy can help you, we can talk about it.
Well I had been hoping to reuse that bit as well, there is a lot of
good stuff in the Test Pilot Data Policy, but also some problems from
my point of view.
The biggest problem is the user experience. (Eclipse has a UI feedback
tool with similar problems). The policy requires lots of opt-in, which
means the user is faced with multiple long dialogs. I'm sure it makes
sense for Firefox, but for Firebug I want to go with a much simpler
model: "it's a community feature". That is, we have an open source
tool that uploads anonymized data on your use of that tool. You can
opt-out by uninstalling the tool at any time, but otherwise your right
to the tool cares a responsibility to contribute. So the user
experience is a one time decision: "Do I trust the Firebug
developers?" If you do, we include your data on the use of the tool.
If you don't, then you don't want to install the tool anyway.
A smaller problem is the last bit about the control of the raw data.
We obviously don't fit the categories allowed to access it, but also I
would want the raw data to be available to anyone in the Firebug
community. There could be restrictions on use of the data to be
consistent with the privacy goals.
What can we do here? Can I crib from your Data Policy, create our own,
and post it for comments?
> Let me know if you have more questions or any other things i can help you
> On Tue, Nov 17, 2009 at 10:39 AM, johnjbarton
> > mozilla-labs-test...@googlegroups.com
> > .