Carsten Munk wrote: >2010/12/1 Clark, Joel <[email protected]>: >> >> >> >> Why don't you fold your work back into the build process so the images are >> produced under >>http://repo.meego.com/MeeGo/builds? >> > >I think the challenge is that while there's development ongoing, for >something that might at one point be contributed to the release >process, until you have QA personell and the rest of the needed MeeGo >bureaucracy in place, you need a place to dump your development work >as you can't release from repo.meego.com without this :) > >BR >Carsten Munk
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. Let's use the processes already in place rather than fork off a whole new process. regards Joel _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
