> Dave Neary wrote
>
> You are proposing that this uploading & distribution of imageshave some
> QA stuff as a prerequisite:
The only QA I ask for was someone to see if the image booted on the target
board.
> some place in Bugzilla where bugs against
> the image get created & assigned to the image creator,
very easy to do
> integration into
> the existing build infrastructure (which, presumably, will require some
> extra access),
The build infrastructure is ready to turn this on as soon as there is maintainer
> associate the distribution of the image with a named
> kernel maintainer, platform maintainer and build scripts maintainer.
Yes, the key point of what is needed. Is this one or more persons?
How about Till, Dave and Carsten?
> Rudolf suggested that "eventually we'll need the full infrastructure",
> implying even more overhead.
He wants to see released products. I'd like to see baby steps first.
> I don't understand why all of this is necessary before you can allow
> someone to upload an image & publish a URL to it, so that interested
> parties can download & play with it. Creating the necessary bugzilla &
> build stuff will add hours or days to requests, and is not a scalable
> approach to community builds.
> Cheers,
> Dave
It's not that hard. Just need a maintainer volunteer can work within the
MeeGo build system to make images for everyone to work with rather than keeping
this stuff private and unmaintained.
OK fine. I've tried more than I probably should. If anybody decides they want
to see Beagleboard images built within the MeeGo build system and are willing
to
work to make that happen please speak up. Until then I'll shut-up.
regards
Joel
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
