Flagging commands would be an ideal solution but given the number of commands that are being used, it might be a bit of a pain to go through all of them and flag the private ones.
On May 23, 5:09 am, "mitcho (Michael 芳貴 Erlewine)" <[email protected]> wrote: > Jono et al, > > Perhaps we can add a flag to commands so that information on those > commands' usage is never sent? Like a "private" flag? > > mitcho (Michael Yoshitaka Erlewine) > > On May 23, 2009, at 1:52 AM, Jonathan Micklos <[email protected] > > > wrote: > > Hi Jono, > > > This program is going to be 100% opt-in only, correct? I am the main > > driver of Ubiquity adoption at Amazon right now and it is going > > well! This is a phenomenal tool! > > > Legal and security teams may forbid certain pieces of technology > > which are perceived to be reporting company confidential > > information. If people start creating Verbs which have confidential > > information in their names or any of the other content that gets > > sent back, I am fairly certain that legal would have something to > > say. As an example, let's say we have a new project at a company and > > John Doe creates various commands with the project's name in it. > > > Thanks! > > > -Jonathan > > > On Fri, May 22, 2009 at 9:29 AM, Jono DiCarlo <[email protected]> > > wrote: > > > Hi Sudhir, > > Absolutely, users would have a right to be concerned if we were going > > to send the contents of the command argument! > > For command usage statistics, all we need to collect is the names of > > the commands, no argument values. > > For detecting common errors, it's a little trickier, since we need to > > look at things in detail. But, I believe we can find a way to > > instrument the client such that the error analysis on the keystrokes > > is done client-side, and anonymized before it is uploaded. For > > instance, part of the anonymization process could be replacing any > > email address with the string "<email address>", and any arbitrary > > text entry with the string "<some text>". That's all that would get > > sent to the server, and it would allow us to get useful data about how > > people are using commands and where they're running into problems, > > without invading their privacy. > > > I should add that Mozilla Labs is now in the planning process of a > > project called Test Pilot (http://labs.mozilla.com/projects/test- > > pilot/ ) which is a program for collecting a representative sample of > > Firefox usage data in order to have a scientific basis for improving > > the user interface. In the course of planning Test Pilot, we are > > figuring out the general guidelines that Mozilla will follow to > > protect users' private information while doing this; those same > > guidelines will of course be used for Ubiquity data collection. > > > --Jono > > > On May 22, 2:11 am, Sudhir <[email protected]> wrote: > > > A new release of Ubiquity is more than welcome! Just a point about > > the > > > data collection point. Users might have issues with privacy and they > > > might decline to provide the statistics. It might be better if only > > > the command data were collected. I mean if I were updating my > > Twitter > > > status from Ubiquity only the twitter command would be collected and > > > not the status message. This might get more people to allow data > > > collection. > > > > On May 22, 6:14 am, Jono <[email protected]> wrote: > > > > > Hello everybody! > > > > There's been a lot of great work done on Ubiquity in the past two > > > > months, but in order to benefit our users we need to roll it up > > into a > > > > release! > > > > I hereby propose that we aim to release Ubiquity 0.1.9 three weeks > > > > from now, early June. > > > > These are the high-level views of the main features that I think > > 0.1.9 > > > > should try to deliver: > > > > > 1. Internationalization. Mitcho and co have been doing great work > > > > rewriting the parser for localizability. Let's try to release > > 0.1.9 > > > > with at least three usable languages and the user interface to > > switch > > > > language. It's OK if the languages are still experimental and > > missing > > > > some commands and/or nountypes; we should focus on providing some > > > > value to non-English speakers and beginning to attract volunteer > > > > localizers. > > > > > 2. Data collection. I want to add a checkbox that users can > > check to > > > > give permission for their copy of Ubiquity to send an anonymized > > > > version of their usage data to Mozilla so that we can use it to > > > > improve the user interface. Specific data that I would like to > > > > collect include the usage rates of various commands (so that we > > can > > > > decide where to focus our effort on improving commands) and also > > data > > > > about common errors that users make, such as input that results > > in no > > > > suggestions, so that we can figure out how to improve the user > > > > interface and how to make better suggestions. > > > > > 3. The new improved introductory documentation and interactive > > > > tutorial, to make it easier for new users to learn Ubiquity. > > This is > > > > mostly done already, but it needs some more polish. > > > > > 4. Overlord verbs (see my blog posthttp:// > > jonoscript.wordpress.com/2009/01/24/overlord-verbs-a-proposal/ > > > > for a description of what this feature means.) This will include > > > > some renaming of existing commands for consistency with the new > > > > standard. > > > > > Additionally, of course, we will include fixes for the most > > important > > > > outstanding bugs and usability problems. > > > > > The tracking bug for the 0.1.9 release is > > > > here:http://ubiquity.mozilla.com/trac/ticket/680 > > > > That contains links to some of the other key bugs. > > > > > There is also a 0.1.9 milestone in trac, where you can see all > > of the > > > > bugs marked as part of the 0.1.9 release. I am still working on > > > > triaging older bugs, so I may still move some other bugs into this > > > > milestone. You can see it > > > > here:http://ubiquity.mozilla.com/trac/query?groupdesc=1&group=priority&mil > > ... > > > > > Please let me know: > > > > > 1. What other bugs should be in this release? > > > > 2. What do you think of the proposed feature additions? > > > > 3. What do you think of the proposed schedule? > > > > 4. Any other questions? > > > > > Thank you very much for your feedback! > > > > --Jono > > > -- > > Jonathan Daniel Micklos | Software Development Engineer | Amazon.com > > [email protected] > > > Work hard. Have fun. Make history. > >http://Amazon.com/Careers --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "ubiquity-firefox" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/ubiquity-firefox?hl=en -~----------~----~----~----~------~----~------~--~---
