[MeeGo-community] Nudging the Community Device Program
texrat at ovi.com
Wed Dec 8 06:29:26 PST 2010
> ----- Original message -----
> From: "Dave Neary" <dneary at maemo.org>
> To: "Andrew Flegg" <andrew at bleb.org>
> cc: "Randall Arnold" <texrat at ovi.com>, "MeeGo community" <meego-community at meego.com>
> Subject: Re: [MeeGo-community] Nudging the Community Device Program
> Date: Wed, 08 Dec 2010 11:35:18 +0100
> Andrew Flegg wrote:
> > Indeed, I wasn't suggesting that it was insurmountable; just that each
> > vendor will want to enter into a device programme to get something in
> > return. The things they want in return will vary (I guess) depending
> > on the end-user readiness of the boards; their involvement in the
> > community to do; their other programmes; the cost of the hardware etc.
> I agree. I would be fearful that a central "clearing-house" approach
> would reduce the value for any individual donor - you need hardware to
> be targeted at people who want it & will do useful community stuff with
> it afterwards. And that will be different for each device type.
I'm going to clarify my original suggestion, which was that a single point of contact would be useful. I was mainly thinking from a logistical sense, as in coordination of the program for starters. I think that no matter how individual device providers contribute, there needs to be a single coordinator working with them, and that should come under the auspices of the Linux Foundation. We can next debate the final scope of that role.
I am also still of the opinion that the potential issues expressed above are unlikely to occur simply because there would/could be a "clearing house" approach. The solution to preventing them is a robust nomination/screening/etc process that takes individual needs on both sides of the equation into account. Let's create it and solve the problem proactively. ;)
> > Yes, and this seems to be the core of the programme. Perhaps some kind
> > of profile-based approach; i.e. a collection of programme *templates*
> > which can be picked and chosen from?
Exactly, and that could even be done with a "clearing house" approach
> I'd like to propose a couple of those templates.
> One I mentioned earlier which I really like is to have the hardware as a
> giveaway after a training workshop that people have to sign up for. You
> get the hardware at the end (like the Nexus One giveaway at OSCON last
> year, which was in conjunction with an Android workshop/tutorial where
> everyone got their first Android program working).
> Another if to give hardware as rewards for efforts already furnished -
> development contests, application contests, etc (a nice way to do it
> would be to advertise that there are "some" devices for the top
> entrants, and then at the end have a hardware giveaway for all entrants,
> with a small something extra for winners).
Both are excellent ideas and in fact I was planning to propose a Pandaboard giveaway to TI for one of our local meetups.
> My least favourite methods (because lowest ROI as far as I can tell) are
> giveaways where either (a) all attendees at a conference/session get a
> device, or (b) community members apply for devices & get them based on
> what they say they will do afterwards, or (c) donating hardware to high
> profile community members (except in cases where those people have
> publicly said "give me your hardware + specs, and I'll write device
> drivers for it", as Alan Cox said at one stage). As I said before, the
> highest profile kernel guys all have piles of hardware they've received
> in donations that they don't want or need.
I see the Lenovo giveaway as an exception to the first concern. Look at the bug and other solution work that erupted immediately after they were handed out. I'm betting there's been (or ultimately will be a very nice ROI.
Anyway there's been some useful ideas proposed so I have enough to get started on redoing the wiki page. Hopefully more will join in. It would be nice to hear more from those who would be actually managing Nokia and Intel provisions...
Ovi Mail: Making email access easy
More information about the MeeGo-community