yeah all sounds good. My suggestion would be to have a -unstable release that is basically what is being worked on from day to day... Opensuse-edu does this and it works quite well, as we can rsync it, to just get basic changes whenever we wanna check it out. What do you think. Oh... and I'd llike to take the opportunity to be part of the dev team. Let me know what I need to do, and I'll document it for other people wanting to do the same thing. At opensuse, it was just a matter of getting invovled with whatever by getting th source code, then uploading to build service, together with a structured rpm build documnet. I imagine the processwill be similar though somewha les automated and using differet tools like bazaar and other LP sutff, Anyway, a step by steo guide will go a long way, and I'm happy to write this as I go through the prcoedss :-) kind regards, David (nubae) Van Assche <div class="gmail_quote">On Mon, Nov 9, 2009 at 5:04 PM, Jeremy Bicha <<a href="mailto:jeremy@bicha.net">jeremy@bicha.net</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Sounds like a great idea! Jeremy > ...We have a team within Edubuntu, called "edubuntu-dev", it consists of the <div><div></div><div class="h5">> current Edubuntu developers. You can see the team's page here. > > <a href="https://www.launchpad.net/%7Eedubuntu-dev/" target="_blank">https://www.launchpad.net/~edubuntu-dev/</a> > > You'll notice that, about halfway down the page, we have 3 PPA's, namely: > Edubuntu Testing Archive > Edubuntu Stable Updates > Edubuntu Work in Progress > > Work in Progress for "Bleeding edge" or alpha quality work, "Testing" for beta > quality packages, and "Stable Updates" for updates to packages that are > currenly stable, but may have a bugfix that we can apply that hasn't yet made > it to the official archives. > > Per LaserJock's suggestion, I'd like to propose that the developers, and the > users, start taking advantage of this as the "Semi official" Edubuntu updates > repo, over and above the official Ubuntu-sponsored updates. It has several > advantages: > > 1) Users who wish to receive "more frequent" updates may add the appropriate > PPA to their apt config, and gain the benefits. > 2) Users who do NOT want to have anything other than the officially sponsored > updates can simply ignore this ppa. > 3) People who would like to become Edubuntu developers have a much lower > barrier to entry. After doing a bit of packaging or bugfixing work to prove > their worth, the Edubuntu Community Council can simply vote to have them as > part of the "edubuntu-dev" team. This gives them access to the > "edubuntu-dev" PPA's. If they choose, they can use their development work, > when they've done enough of it, to eventually apply for official MOTU-ship. > Or not, as they so choose. > 4) It's a "well known address" where we can point people to to potentially > receive more frequent updates. > > To me, it seems like a good course of action. By way of kicking it off, today > I'll push up a new version of Sabayon to "Testing". This new version will > allow you to apply Sabayon profiles by group, in addition to the usual by-user. > > Thoughts? > > Scott > > -- > Scott L. Balneaves | He that breaks a thing to find out what it is > Systems Department | has left the path of wisdom. > Legal Aid Manitoba | -- J.R.R. Tolkien -- edubuntu-devel mailing list <a href="mailto:edubuntu-devel@lists.ubuntu.com">edubuntu-devel@lists.ubuntu.com</a> Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/edubuntu-devel" target="_blank">https://lists.ubuntu.com/mailman/listinfo/edubuntu-devel</a> </div></div></blockquote></div> -- <a href="http://www.brainyquote.com/quotes/authors/p/pablo_picasso.html" target="_blank">Pablo Picasso</a> - "Computers are useless. They can only give you answers."