multi-touch-dev team mailing list archive

["Duncan M. McGreggor" <duncan.mcgreggor@xxxxxxxxxxxxx>]

Note: moving conversation to mail list.

Rick and I chatted about scope on IRC, and he provided some excellent  
perspective. To restate the goal of the Lucid work:

Provide MT support in the kernel so that developers can start building  
exciting tactile apps for Ubuntu ASAP.

As such, here's what I'd like to propose:

Phase 1:
 * Lucid-targeted
 * use the current blueprint
 * focus on getting kernel work completed for Lucid
 * we want to do the kernel bits right
 * this may mean taking option 1) below for the user-space bits, but  
putting this work in a PPA, not in Lucid

Phase 2:
 * Lucid+1-targeted
 * create a new blueprint
 * move non-Lucid tasks from Phase 1 blueprint to Phase 2 blueprint
 * take the usable user-space bits from Phase 1 and follow the  
development plan of option 2) below.

The understanding in this approach would be that we will be throwing  
away some of the work done now in order to get the MT kernel code  
ready for Lucid.

Thoughts?

d


On Mar 15, 2010, at 5:35 PM, Rick Spencer wrote:

> Be sure to keep your eye on the prize, which is [developers] can demo
> ntrig mt working with the Lucid kernel. Anything else is scope creep.
>
> Cheers, Rick
>
> On Mon, 2010-03-15 at 17:18 -0600, Duncan M. McGreggor wrote:
> > Hey Mark,
> >
> > Bryce and I just had a conversation on IRC about the email from Peter
> > Hutterer that Bryce forwarded to the multi-touch list. The plan of
> > attack that Peter laid out there feels good to Bryce, however, there
> > are concerns regarding how we should best do this given our time
> > constraints and expected deliverables.
> >
> > In particular, Bryce outlined two possible directions:
> >
> > 1) One is to cobble together whatever we can to get as much
> > functionality enabled in as little time possible, and not worry so
> > much about upstream or long term directions.
> >
> > 2) The other option is to take the time to get the underlying
> > infrastructure stuff done, in accord with the larger plans upstream  
> > is
> > laying out, and thereby establish a solid base to get multitouch
> > working later in 10.10.
> >
> > We both have the sense that your preference is with the latter, but I
> > want to make sure that you're well-informed about the time costs
> > involved. Is there anything else you need from us in order to make a
> > direction decision?
> >
> > Thanks,
> >
> > d