Dave, Speaking as a teacher, this would be a fantastic idea! We could have a tool to build our own spin. I am not a developer, but would happy to work on requirements. Thanks. Gerald <div class="gmail_quote"> On Thu, May 27, 2010 at 10:31 AM, Dave Bauer <<a href="mailto:dave@solutiongrove.com">dave@solutiongrove.com</a>> wrote: <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> On Wed, May 26, 2010 at 3:50 PM, Daniel Drake <<a href="mailto:dsd@laptop.org">dsd@laptop.org</a>> wrote: ... > > 4. Build/customization documentation - in addition to actually > adjusting the process to make customization clean and possible, > they've written *good documentation* on how to do it, even ready for > the release date and not done as an afterthought: > <a href="http://download.sugarlabs.org/soas/docs/customization-guide/" target="_blank">http://download.sugarlabs.org/soas/docs/customization-guide/</a> > > > Thanks to the SoaS contributors, great work! > Daniel > ... and thanks to Daniel for the email that inspired this idea. Based on the idea of making it easy to customize SoaS I had an advanced idea to make it even easier. I can't personally work on this, but maybe there is someone who can develop this idea further. I am thinking of a web-based form that would allow deployments to customize their own SoaS spin. This would simplify things because the deployment wouldn't need a lot of bandwidth to build the custom SoaS, and would not have to setup a Fedora 13 install to do the builds. This is sort of like <a href="http://susestudio.com/" target="_blank">http://susestudio.com/</a> which is supported by Novell, and unfortunately the underlying platform is not open source. I chatted with Mel and Sebastian on #sugar last night and we agreed this was an interesting idea. The first step could be just a web based form to generate a correct custom kickstart file, which a deployment would download to do a custom build. The next step would be to setup a local Fedora repository so the packages don't need to be downloaded for every build. Then after that a system could be designed to take the custom kickstart files and build custom ISOs. It would probably make sense to limit this to registered deployments in the beginning until it was known exactly how much resources would be consumed. I hope this summary idea will be useful, and I regret I cannot personally build this, I really like the idea. Dave -- Dave Bauer <a href="mailto:dave@solutiongrove.com">dave@solutiongrove.com</a> <a href="http://www.solutiongrove.com" target="_blank">http://www.solutiongrove.com</a> <div><div></div><div class="h5">_______________________________________________ Sugar-devel mailing list <a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> </div></div></blockquote></div>