So, Here is the plan; I've assigned items on it - I hope that is ok; Vincent you suggested we could borrow some of your time ? Actions: 1. empty / clean out Moblin:UI as a repository + this will eventually be the devel repository for the new Moblin packages going into oS:F - that can't find a home elsewhere. AdrianS - we can't do this because of stale links; can you over-ride those & delete the contents of Moblin:UI ? 2. create Moblin 2.2 repository + check in the packages from ibs' SUSE:SLE-11:Moblin:2.1 here (yes 2.1 for now). + *why* ? + autobuild 'cleans up' .spec files making them un-diffable, and this causes us -tons- of work if we continue to have different internal and external spec files => we need to close the loop + check in all the ibs Moblin:2.1 packages from that channel 3. start migrating packages: + for each migrated package, merge in Federico's changes from Moblin:Cleanup a) Merge all *new* GNOMEish packages into GNOME:Apps & GNOME:Factory and link back into Moblin:2.2 b) Merge all *existing* GNOMEish package changes into GNOME:Factory and GNOME:STABLE:2.28 and link back into Moblin:2.2 from GNOME:STABLE:2.28 (with versioned link) c) rationalise non-GNOME packages, merge patches into oS:F where possible, in the meantime link Moblin:2.2 to oS:11.2 with the same patches applied. 4. get Moblin:2.2 building vs. oS:11.2 (only) get Moblin:UI building vs. oS:Factory, and oS:11.2 + get images built etc. 5. when Aaron is happy rename Moblin:UI to Moblin:Factory to provide a cleaner, meaner naming scheme :-) 6. Development / packaging work to reconcile the mutter issue: more parallel installation & packaging goodness. ---- Q & A ---- * What about the kernel ? + there will be some packages that continue to 'live' in Moblin:2.2 - c'est la vie. * What about heavily patched base-system packages: aaa_base etc. ? + oS:F works quite nicely without these, at some boot time performance hit. + oS:F can take that for now; we should focus first on getting the UI working on top of oS:F, and do these later * What about heavily patched GNOME packages ? + see 3. c) if we can't get the packages into GNOME:STABLE:2.28 - then we need to keep them and merge them later. + some examples might be the telepathy hacks; some of these may require development work, but for now - we should drive to getting new packages submitted & -something- working on oS:F (IMHO etc.) :-) Does that make sense ? I've created Moblin:2.2 and set Andrew, Vuntz & the usual suspects as maintainers; can we go wild ? :-) ... Remember - step 1 is the (automatic, scripted import from ibs - I guess we should set that running ...). I'll beg Adrian for the Moblin:UI cleanup now. Regards, Michael. -- michael.meeks@novell.com <><, Pseudo Engineer, itinerant idiot -- To unsubscribe, e-mail: opensuse-goblin+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-goblin+help@opensuse.org