[MeeGo-dev] Urgent: We need community ftp space or similar
dneary at maemo.org
Wed Dec 1 10:26:46 PST 2010
Clark, Joel wrote:
>> Dave Neary wrote:
>> Does all of this really need to be a prerequisite to allowing a
>> long-time, active community member to upload & distribute an image?
> I don't get it either. If the "long-time, active community member" is
> willing to build, test, upload, distribute and deal with problems from
> anybody who uses his image, why not take advantage of the existing
> automated processes for code management, build, distribution and issue
> tracking? Is the goal here to make sure the beagleboard is not
> supported on meego.com?
I get the feeling we're talking at cross purposes :)
Going back to Till's original message, he's asking for a distribution
channel to be created on meego.com where he (and others) can upload
custom meego images they build.
You are proposing that this uploading & distribution of imageshave some
QA stuff as a prerequisite: some place in Bugzilla where bugs against
the image get created & assigned to the image creator, integration into
the existing build infrastructure (which, presumably, will require some
extra access), associate the distribution of the image with a named
kernel maintainer, platform maintainer and build scripts maintainer.
Rudolf suggested that "eventually we'll need the full infrastructure",
implying even more overhead.
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.
Email: dneary at maemo.org
Jabber: bolsh at jabber.org
More information about the MeeGo-dev