[texrat]

Update: we now have an online application for requests: https://meego.com/community/device-program

Greetings all,

You may have seen a recent email update from Dawn Foster on the MeeGo Community device program. I'd like to update you on further developments.

The main wiki page has been streamlined; individual device providers now have their own wiki pages to manage the MeeGo side of their programs.

There have also been some additions to the submittal form functionality and general updates to descriptive text.

Note that device providers (such as TI) may offer multiple devices. In addition, they will likely have their own request forms. In the case of the latter, anyone participating in this program should use the MeeGo form once it's developed. A member of the program team will fill out provider-specific forms as your proxy. In th future, we would like to see automated bridging of electronic web forms as one possibility.

I will be designing a workflow to include on the wiki page to make the process clear. As always, community suggestions are welcomed!

NOTE: Please discuss process issues here or on meego-community email list. Thanks.

Randall (Randy) Arnold
Community Device Program Lead

http://wiki.meego.com/Community_Office/Community_device_program


EDIT: device champions wanted! see below.

[texrat]

First pass at data model for device program app done:

MeeGo_Community_device_program_model1.pdf

[arfoll]

I have to be honest this seems very complicated to me. I have been donated quite a few devices now and never has anything this complicated been done.

1. Developer proposes idea for which he needs a device
2. Vendor decides wether he should give one away
3. Developer sends his details
4. Vendor ships
5. Success!

Anyways your model seems really good, but vendors would probably appreciate a serial number field in the "Devices" table. Also I'm not sure I understand why the "Quantity" field is in the "Device-Provider_Matrix". Is that for quantity of Devices? If so this field should not be static!

[texrat]

It's not as complicated as it appears.

The Quantity is in the right table, and isn't static. The Provider can update it at any time.

Thanks for the S/N suggestion!

EDIT: arfoll, don't confuse the data model with the actual workflow-- which will actually match closely with what you described. Often the solutions that appear the simplest on the surface are built on hidden engines of necessary complexity.

[lm]

I'm not sure this part should be in the general requirements:

Agree to blog/tweet/present about your experience with the device.

It's a bit vague (what exactly is a recipient agreeing to do? do they have to set up a blog, get a tweeter account and travel around the world to give presentations?), and probably not applicable in all cases (eg pre-release devices loaned under an NDA).

Individual device programs are of course free to insist on something like that if they want.

[texrat]

Originally Posted by lm

I'm not sure this part [Texrat's edit: blogging, etc] should be in the general requirements:

It's a bit vague (what exactly is a recipient agreeing to do? do they have to set up a blog, get a tweeter account and travel around the world to give presentations?), and probably not applicable in all cases (eg pre-release devices loaned under an NDA).

Individual device programs are of course free to insist on something like that if they want.

Maybe I just need to add an "/etc"? The idea is to *share* their experiences somehow. And IMO it really does need to be a MeeGo requirement. But the wording Dawn and I have used is not ironclad-- by all means, offer an alternative!

[texrat]

Okay, process stuff is "gelling" now so time to work on adding devices and providers.

We're looking for device champions to step forward. This is defined very simply: excited about a product? have some expertise with it? Know someone in the right position inside a provider's organization? All of the above?

Then YOU are a device champion! So jump in! Edit the wiki, contact providers, or whatever else you think you can do to contribute. I will happily coordinate efforts but I am depending on the community to pitch in!

http://wiki.meego.com/Community_Office/Community_device_program
http://wiki.meego.com/Community_Offi...vice_Providers

[meegoexperts]

Brilliant idea guys. I have my fingers in a few pies at the moment, not sure whats going to come to fruition but I can certainly help out in this field :-)

[lm]

Originally Posted by texrat

The idea is to *share* their experiences somehow.

My preferred medium would be code, but even that might not be possible in all cases (eg someone fixing non-free graphics drivers under NDA).

And IMO it really does need to be a MeeGo requirement.

At least my understanding is that these devices are given for development purposes rather than reviewing, media attention etc. I think a hard requirement for blogging etc may put some potential contributors off.

(It would certainly put me off, though I have no intention of asking for one anyway).

[texrat]

Originally Posted by lm

At least my understanding is that these devices are given for development purposes rather than reviewing, media attention etc. I think a hard requirement for blogging etc may put some potential contributors off..

Nothing was said about reviewing or media attention. Again, the hard requirement is sharing. I provided 3 examples, but they are not necessarily the only means. A wiki page could be another. But publicly documenting the device's usage should be of great interest and use to the community.

EDIT: a general question-- is asking recipients to, say, periodically tweet about their project's progress asking too much? A serious question.