Hi, Clark, Joel wrote: > First we need someone to be the image maintainer for the beagleboard. > Someone to own bugs found. If Till is building images to share with > the community then please just go the next step and agree to maintain > that image, so we can leverage the existing build and bugs > infrastructure to support the beagleboard community. I don't believe > there is significant additional "needed MeeGo bureaucracy". 2 or 3 > folks would be nice but 1 person could do it. What is needed is a > kernel maintainer for beagleboard, platform maintainer for > beagleboard, and someone to ensure the build scripts (i.e. kickstart) > is right and the resulting images actually boots. Sure it would be > nice to have a full QA team dedicated to the board, but the community > can provide that capability and file any bugs found. But someone has > to own the bugs found.
Does all of this really need to be a prerequisite to allowing a long-time, active community member to upload & distribute an image? We can help draft the big red-type disclaimer on the top, if you like, that will say "This is not an official image! Beware, it may break stuff, and it'll all be your fault! Don't come crying to us afterwards, we'll only tell you we told you so!" And then Till can write, in really small letters underneath, "If anyone has problems with the image, contact me at [email protected]" and then Till will be doing your triage for you. I'm all for process before we ship software on devices and put it in the hands of people who don't know what they're getting into - but downloading binary images for the beagleboard does not fall into that category - can't we make it easier for people to get hold of the work of other community members? The parallel I would make is with the various staging trees & the old ac kernels. People knew what they were getting when they got it, you didn't accidentally download an ac kernel on the front page of kernel.org, and Caveat Emptor was in full effect. Cheers, Dave. -- maemo.org docsmaster Email: [email protected] Jabber: [email protected] _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
