[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [mylar-dev] this week's plan
|
Hi Philippe,
You make some really good points. We've struggled a lot with how to go
about pleasing UBC ethics while being open, warm and fuzzy. You prompted us
to again explore opening the sources early, but due to our ethics
application the tradeoff that we're stuck with is that the monitor is hosted
privately at UBC for the next 6-8 weeks before moving to eclipse.org.
Please note: The monitor only uploads two files over http, a usage log and
error log (<workspace>/.mylar/workspace.xml and mylar-log.txt) and before
uploading shows you everything that it is going to send so that you can view
the files, and provides the URL it will use. Beyond getting my assurance,
subjects can look up our UBC ethics application (B05-0348 Reducing
Information Overload) that gives UBC's assurance that this is the only data
we are allowed to collect. You could also assure yourself 100% by setting
up a proxy server to monitor the traffic during the upload (you can kick off
the upload wizard manually by hitting <ctrl>-N, and selecting the Mylar
upload wizard). If you actually do that it would be great if you could post
the results so that others can share your warm and fuzzies :)
I'm hope that you don't find the wait for the monitor sources too long, and
that this restriction does not prevent too many people from participating in
the study.
Mik
> -----Original Message-----
> From: mylar-dev-bounces@xxxxxxxxxxx [mailto:mylar-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Philippe Ombredanne
> Sent: Wednesday, July 06, 2005 10:41 AM
> To: 'Mylar developer discussions'
> Subject: RE: [mylar-dev] this week's plan
>
> Mike,
> I can understand that the need of your study to keep the sources of the
> monitor non-modifiable, but you may also understand concerns that folks
> can have with having an 'eclipse spyware' closed-source running on their
> machine.
> I think that the likeliness that somebody tempers with your code is low,
> but the likeliness that someone feels quite uncomfortable to submit
> itself to the study without knowing what is being recorded is high.
> For instance, I have no way to check if you are not recording the code I
> write, and I may write confidential code on behalf of a customer.
> So I may not want to run mylar in that case, and that means that I will
> not be using mylar in a real world situation, and the info you'll get
> from the study may not be for real world use, which may defeat the
> purpose of your study in the 1st place.
>
> Look for instance at the org.eclipse.ui.instrumentation which collects
> UI usage data, and is most likely similar to what your monitor does. The
> code is open, and the user can see what data are sent.
> That gives me the warm and fuzzies.
> Your approach is not making me very comfortable, despite I am sure you
> have the best intentions!
> Just being my regular trublion :-)
> Cordially
>
> --
> Cheers
> Philippe
>
> philippe ombredanne | nexB - Open by Design (tm)
> 1 650 799 0949 | pombredanne at nexb.com
> http://www.nexb.com
>
> > -----Original Message-----
> > From: mylar-dev-bounces@xxxxxxxxxxx
> > [mailto:mylar-dev-bounces@xxxxxxxxxxx] On Behalf Of Mik Kersten
> > Sent: Wednesday, July 06, 2005 10:09 AM
> > To: 'Mylar developer discussions'
> > Subject: RE: [mylar-dev] this week's plan
> >
> >
> > Sorry Philippe, I was too vague on that. I've updated the dev page
> > accordingly.
> >
> > For the duration of the user study, which is being announced this week
> > (http://eclipse.org/mylar/ubc-study.html), there is a Mylar monitor
> > component that takes care of recording, obfuscating, and
> > uploading usage
> > statistics to a UBC server. To assure the integrity of the
> > study data, the
> > sources for that component needs to stay on a non-public UBC
> > server for the
> > duration of the study.
> >
> > Please note that the best way to help out with the project
> > right now is to
> > participate in the study, we ask that you avoid building on
> > or extending
> > Mylar until you have completed Phase 2 of the study since
> > that would taint
> > your status as a regular user. Also note that the code will
> > be seeing a
> > *lot* of changes and refactoring for over the next 6 weeks,
> > in response to
> > the first usage data. After that, we should start seeing
> > some APIs forming.
> >
> >
> > But if you are interested in building on or extending Mylar,
> > this month is a
> > great time to get some discussions started on the developers list.
> >
> > Mik
> >
> > > -----Original Message-----
> > > From: mylar-dev-bounces@xxxxxxxxxxx
> > [mailto:mylar-dev-bounces@xxxxxxxxxxx]
> > > On Behalf Of Philippe Ombredanne
> > > Sent: Wednesday, July 06, 2005 9:45 AM
> > > To: 'Mylar developer discussions'
> > > Subject: RE: [mylar-dev] this week's plan
> > >
> > > Mik,
> > > That sounds great!
> > > Just a question, you wrote:
> > > "All sources are up on eclipse.org, other than the monitor feature,
> > > which will have to remain at UBC for the duration of the study. "
> > > I do not have access to cascade.cs.ubc.ca .
> > > Could you elaborate?Cordially
> > >
> > >
> > > --
> > > Cheers
> > > Philippe
> > >
> > > philippe ombredanne | nexB - Open by Design (tm)
> > > 1 650 799 0949 | pombredanne at nexb.com
> > > http://www.nexb.com
> > > -----Original Message-----
> > > From: mylar-dev-bounces@xxxxxxxxxxx
> > > [mailto:mylar-dev-bounces@xxxxxxxxxxx] On Behalf Of Mik Kersten
> > > Sent: Monday, July 04, 2005 12:29 PM
> > > To: mylar-dev@xxxxxxxxxxx
> > > Subject: [mylar-dev] this week's plan
> > >
> > >
> > > The first cut at the Mylar 0.3.1 preview release is
> > scheduled for this
> > > Friday. All sources are up on eclipse.org, other than the monitor
> > > feature, which will have to remain at UBC for the duration
> > of the study.
> > > Planning and discussions should take place on this list from now on.
> > > Each Monday I will report on the tasks that we have completed in the
> > > past week, the P1 tasks that need to be done this week, and
> > the P2 tasks
> > > that would nice to have done this week. All reports marked
> > as P3 should
> > > be considered when we schedule the following week's tasks. For the
> > > duration of the study we'll rev the minor-minor version number each
> > > Friday, making those updates available to study subjects.
> > I'll keep the
> > > following page up-to-date as our conventions evolve:
> > > http://eclipse.org/mylar/dev.html
> > >
> > > The current schedule is:
> > > . By tomorrow: release the Mylar monitor to start
> > Phase 0 of the
> > > study (tracking baseline usage)
> > > . Next Monday: earliest date that users can download Phase 1
> > > (Mylar UI)
> > >
> > > Tasks for this week (22 total)
> > > 101940 maj P1 beatmik@xxxxxxx NEW Landmark notification incorrect
> > > 102365 cri P1 beatmik@xxxxxxx NEW fix crazy explorer
> > selection cascade
> > > 102418 nor P1 beatmik@xxxxxxx NEW Java Browsing views don't update
> > > properly
> > > 102669 nor P1 ksueda@xxxxxxxxx NEW improve deletions of tasks with
> > > context
> > > 100920 nor P2 beatmik@xxxxxxx NEW mylar attempts to select
> > everything
> > > on update from cvs
> > > 101920 nor P2 beatmik@xxxxxxx NEW mylar editor doesn't
> > provide ruler
> > > shortcuts
> > > 102101 nor P2 beatmik@xxxxxxx NEW mylar perspective extensions
> > > 102589 nor P2 beatmik@xxxxxxx NEW decorator flicker in
> > package explorer
> > >
> > > 102595 enh P2 beatmik@xxxxxxx NEW feature for "About" dialog
> > > 102662 enh P2 beatmik@xxxxxxx NEW create summary statistics for
> > > perspective usage
> > > 102667 enh P2 beatmik@xxxxxxx NEW clarify preference
> > wizard effects and
> > > preference page
> > > 102674 nor P2 beatmik@xxxxxxx NEW reduce size of taskscapes
> > > 102675 nor P2 beatmik@xxxxxxx NEW prune dangling predicted interest
> > > nodes
> > > 102676 nor P2 beatmik@xxxxxxx NEW add support for moving from study
> > > phase1 to phase2
> > > 102679 nor P2 beatmik@xxxxxxx NEW add show filtered action
> > to navigator
> > >
> > > 101916 enh P2 ksueda@xxxxxxxxx NEW minor task list UI nits
> > > 102409 nor P2 ksueda@xxxxxxxxx NEW task list drag and drop
> > > 102593 nor P2 ksueda@xxxxxxxxx NEW support for refreshing a single
> > > query
> > > 102671 nor P2 ksueda@xxxxxxxxx NEW automatic elapsed time for tasks
> > > 102672 nor P2 ksueda@xxxxxxxxx NEW closing the task editor
> > > 102673 nor P2 ksueda@xxxxxxxxx NEW task editor dirty state
> > > 102664 enh P2 lkf@xxxxxxxxx NEW monitor activity/capability changes
> > >
> > >
> > >
> > > Tasks completed last week (22 total)
> > > 101891 beatmik@xxxxxxx RESO LATE add support for monitoring
> > preference
> > > changes
> > > 102200 beatmik@xxxxxxx RESO FIXE resetting folding discards unsaved
> > > edits
> > > 102588 beatmik@xxxxxxx RESO FIXE problem with UI hang on startup
> > > 102049 sminto@xxxxxxxxx RESO FIXE add monitor support for
> > upgrading from
> > > baseline to Mylar
> > > 100461 beatmik@xxxxxxx RESO FIXE Unable to Raise Children Properly
> > > 101561 ksueda@xxxxxxxxx RESO FIXE Categories and Tasks should be
> > > different
> > > 101898 beatmik@xxxxxxx RESO FIXE improve icons
> > > 101899 ksueda@xxxxxxxxx RESO FIXE problems with task list refresh
> > > 102249 beatmik@xxxxxxx RESO FIXE on shell de-activation Mylar causes
> > > noticeable slowdown
> > > 102352 ksueda@xxxxxxxxx RESO FIXE adding a new bugzilla
> > report doesn't
> > > cause it to appear
> > > 102382 beatmik@xxxxxxx RESO FIXE perspective change monitoring
> > > 101911 sminto@xxxxxxxxx RESO FIXE Support bugzilla queries
> > > 102399 sminto@xxxxxxxxx RESO FIXE support interest filtering in Java
> > > Browsing Perspective
> > > 99420 beatmik@xxxxxxx RESO FIXE Plugin Xml filtering problems
> > > 100946 ksueda@gmail.comRESO FIXE remove ability to create subtasks
> > > 101562 ksueda@xxxxxxxxx RESO DUPL Add support for creating
> > a bugzilla
> > > query category
> > > 100627 sminto@xxxxxxxxx RESO FIXE Add preference for
> > automatic closing
> > > 100983 sminto@xxxxxxxxx RESO FIXE active search view fails
> > to refresh
> > > when results return
> > > 101661 beatmik@acm.orgRESO FIXE view filters
> > > 101901 sminto@xxxxxxxxx RESO FIXE add keyboard shortcut for
> > "search in
> > > task context"
> > > 102120 sminto@xxxxxxxxx RESO FIXE verify new bugzilla icons
> > > 102243 sminto@xxxxxxxxx RESO FIXE failure to set status of report to
> > > FIXED
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > mylar-dev mailing list
> > > mylar-dev@xxxxxxxxxxx
> > > https://dev.eclipse.org/mailman/listinfo/mylar-dev
> >
> > _______________________________________________
> > mylar-dev mailing list
> > mylar-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/mylar-dev
> >
>
> _______________________________________________
> mylar-dev mailing list
> mylar-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mylar-dev
