> ----- Original message ----- > From: "Foster, Dawn M" <[email protected]> > To: "Quim Gil" <[email protected]> > cc: "Randall Arnold" <[email protected]>, "MeeGo community" > <[email protected]> > Subject: Re: [MeeGo-community] Progressing on the community device program > Date: Thu, 9 Dec 2010 13:22:59 -0800 > > > > On Dec 9, 2010, at 1:11 PM, Quim Gil wrote: > > > On Wed, 2010-12-08 at 19:14 -0800, ext Foster, Dawn M wrote: > >> I've added some feedback to the wiki page, but I have one larger > >> question. 1) Should this be a standalone device program under the Linux > >> Foundation responsible for shipping devices? > >> or 2) Should we morph this program into a way for each device provider to > >> point people to their own program where they would ship the devices? > > > > I would start with 2, since it's already an improvement over the current > > situation, it's an incremental step and doesn't add much overhead to > > anybody. > > > > I can imagine this scenario being quite common: > > > > - A company is willing to distribute some hardware with some reasons in > > mind. > > > > - That company has already a % of devices being distributed through > > their own channels, but would be happy adding a % for the MeeGo project, > > who would find the best recipients for the occasion. > > > > - Contact made: the company says it has a number of devices and after > > some time the MeeGo project can provide a list of names & addresses for > > those devices, organize an event where this people will take part, come > > up with another proposal, etc. > > > > - The cost of distributing that hardware is covered by the company, but > > the hours and skills to find the right people is contributed by the > > MeeGo project. > > > I like this approach - it's a little more hands-on than I pictured with my > original option 2, but I think it's a better idea. > > I think we'll have 2 scenarios as part of this program: > a) Information-only: Provide information about how devices would be > distributed to MeeGo Community members. Community member applies > at the provider website and provider decides who to distribute them to based > on their own criteria. > b) Information + decision: Come to agreement with the provider on the > criteria, > community members apply for devices, and MeeGo gives the provider a list > of names / addresses of community members to receive the devices. > > This relieves us of the inventory / shipping / administration burdens of my > original proposal. > > Dawn >
I had originally expected we would wind up with at least 2 paths per provider. ;) But even with the above solution, we're still left with REdistribution of loaned (or unused gifted) devices. Should recipients bear that burden? If so I envision devices gathering dust. Should the Linux Foundation be prepared to send prepaid shipping labels for that purpose? Do we ask original providers to do so? Randy -------------------------------------------------------------- Ovi Mail: Making email access easy http://mail.ovi.com _______________________________________________ MeeGo-community mailing list [email protected] http://lists.meego.com/listinfo/meego-community
