Hi, 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 :)
... and I would say that if there are enough people proposing custom MeeGo images that disk space is a concern, then that's a nice problem to have ;-) Till doesn't need anonftp or anything, but something with trust-based access rights (where you have to ask to get a password allowing you to upload images) with directories organised by username (so you know whose images you're downloading) would be great as a way for people to share their work in an informal way. Cheers, Dave. -- maemo.org docsmaster Email: [email protected] Jabber: [email protected] _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
