Moin all, I'd like to ask you guys if, what and how we should provide Moblin to openSUSE users? We see Moblin gets high attention and with Goblin Andrew already based a version of Moblin on openSUSE and it is appreciated by the users. I heard the request to add Moblin to our major distribution (maybe considered for openSUSE 11.3) and offer it with our "desktop selection" page. So what would such an Moblin desktop add in space to the DVD? (as the DVD is already pretty crowded) Others are asking for a seperate Moblin image for each stable openSUSE release. So please let us know your opinion if and how to integrate Moblin with openSUSE? Best Michael -- Michael Löffler, Product Management SUSE LINUX Products GmbH - Nürnberg - AG Nürnberg - HRB 16746 - GF: Markus Rex -- To unsubscribe, e-mail: opensuse-goblin+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-goblin+help@opensuse.org
Providing the Moblin user experience on top of a standard openSUSE
base is something we are interested in doing, but it's not something
that will feasibly happen very soon. We are locking down to freeze on
an openSUSE/SLE-based Moblin 2.0.
We have a few repositories, that build on openSUSE 11.1 or SLE 11:
* Moblin:Base - provides modified/updated kernel, xorg, HAL, etc. -
much of what is here can be ignored for a Moblin user experience on a
stock openSUSE (e.g. like we have GNOME and KDE desktops, we could
have a Moblin one).
However, these packages are critical for providing the entire Moblin
OS, and many patches would also need to be merged into
openSUSE:Factory (e.g. we require KMS + DRI2). Much of this
requirement is satisfied by xorg 1.6.3.
* Moblin:UI - provides updated GNOME packages and the core Moblin
components like mutter, mutter-moblin, bickley, etc. Most of what is
here can be run on top of a standard openSUSE 11.1
We produce the SLE-based images directly from Moblin:Factory, which is
an aggregate project taking in packages from the two devel projects
(Moblin:UI and Moblin:Base) and a few packages from other devel
projects (e.g. mozilla for FF 3.5). We do all the core work in the
public OBS, and there is an openSUSE 11.1 image project (KIWI) for
producing a full image in OBS as well.
This image is a little bit stale, but the goal is to derive the SLE
image from the openSUSE kiwi file, so that nothing gets horribly out
of sink or stale. Andrew can speak more to this.
For the 11.2 cycle, I think the most reasonable approach is to offer a
Moblin 2.0 image download next to the regular openSUSE. I do not think
it's really feasible to integrate the full Moblin stack into 11.2
proper, but it is something we would like to do for +1.
I'm very interested in Andrew's feedback here, and anyone else's
interested in Moblin.
HTH,
Aaron
On Thu, Aug 13, 2009 at 11:12 AM, Michael Loeffler
Moin all,
I'd like to ask you guys if, what and how we should provide Moblin to openSUSE users?
We see Moblin gets high attention and with Goblin Andrew already based a version of Moblin on openSUSE and it is appreciated by the users.
I heard the request to add Moblin to our major distribution (maybe considered for openSUSE 11.3) and offer it with our "desktop selection" page. So what would such an Moblin desktop add in space to the DVD? (as the DVD is already pretty crowded) Others are asking for a seperate Moblin image for each stable openSUSE release.
So please let us know your opinion if and how to integrate Moblin with openSUSE?
Best Michael -- Michael Löffler, Product Management SUSE LINUX Products GmbH - Nürnberg - AG Nürnberg - HRB 16746 - GF: Markus Rex
-- To unsubscribe, e-mail: opensuse-goblin+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-goblin+help@opensuse.org
-- To unsubscribe, e-mail: opensuse-goblin+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-goblin+help@opensuse.org
On Thu, Aug 13, 2009 at 12:36:09PM -0400, Aaron Bockover wrote:
Providing the Moblin user experience on top of a standard openSUSE base is something we are interested in doing, but it's not something that will feasibly happen very soon. We are locking down to freeze on an openSUSE/SLE-based Moblin 2.0.
We have a few repositories, that build on openSUSE 11.1 or SLE 11:
* Moblin:Base - provides modified/updated kernel, xorg, HAL, etc. - much of what is here can be ignored for a Moblin user experience on a stock openSUSE (e.g. like we have GNOME and KDE desktops, we could have a Moblin one).
However, these packages are critical for providing the entire Moblin OS, and many patches would also need to be merged into openSUSE:Factory (e.g. we require KMS + DRI2). Much of this requirement is satisfied by xorg 1.6.3.
This should be working all in 11.2 by the time it releases, as 11.2 will have a newer kernel than what we currently have in M:B. I'll be testing the 11.2 kernels to make sure they work with the Moblin userspace. The only bad thing will be that a lot of the fast-boot stuff we have done in the Moblin kernel, will not be in 11.2, due to the wider range of hardware we have to support there. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-goblin+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-goblin+help@opensuse.org
Le jeudi 13 août 2009, à 12:36 -0400, Aaron Bockover a écrit :
I'm very interested in Andrew's feedback here, and anyone else's interested in Moblin.
FWIW, I plan to clean up the packages so they can be pushed to oS:F, however there are various issues: + the development in Moblin:Factory doesn't follow the openSUSE development cycle. So how should the packages be handled? I doubt we can use M:F as a devel project for oS:F, at least for now :/ Would some "forking" be a good thing? + we need a plan to know what we should release. I have no idea what the Moblin schedule is, but if we think 11.2, we're basically frozen for upstream versions now. Is it reasonable to release 11.2 with a Moblin version that is basically what we have today + bugfixes? + Moblin currently uses git version of various modules. This is at least a bit inconvenient. Real releases would be much better, especially for packages where we already have an openSUSE package. (this is getting fixed upstream, I think) + there might be conflicts between what's needed in M:F and what's needed in openSUSE. The mutter packages might be an example of this (no idea how mutter is packaged in Moblin, but we now have a mutter package from GNOME upstream mutter). I guess we can only be careful there, since there's no magic solution. The real blocker for me is the first item. If I push Moblin packages to Factory now, they will possibly move at a different pace from the packages in M:F, and quite some synchronization work should be done every now and then :/ Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-goblin+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-goblin+help@opensuse.org
On Fri, 2009-08-14 at 02:36 +0200, Vincent Untz wrote:
FWIW, I plan to clean up the packages so they can be pushed to oS:F, however there are various issues:
Great :-)
+ the development in Moblin:Factory doesn't follow the openSUSE development cycle. So how should the packages be handled? I doubt we can use M:F as a devel project for oS:F, at least for now :/ Would some "forking" be a good thing?
A mini fork seems to be the only real option as of now.
+ we need a plan to know what we should release. I have no idea what the Moblin schedule is, but if we think 11.2, we're basically frozen for upstream versions now. Is it reasonable to release 11.2 with a Moblin version that is basically what we have today + bugfixes?
Yes; Indeed - I'm somewhat dismayed by all this talk of 11.3 - I was under the impression that the openSUSE team were committed to getting this into 11.2 - we have a great opportunity to leverage our leadership here, and be first to market; it would be really sad to ceede that to Ubuntu. Of course, whether it is a top-level desktop selection, and/or whether it carries a heavy 'Experimental' tag, is up to us :-) Of course, for our next release, I imagine we'll be based on the 11.2 packages, and hopefully we'll come increasingly into sync there package wise (if not time-line wise). HTH, 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
On Friday 14 August 2009 18:24:27 Michael Meeks wrote:
On Fri, 2009-08-14 at 02:36 +0200, Vincent Untz wrote:
FWIW, I plan to clean up the packages so they can be pushed to oS:F, however there are various issues:
Great :-)
+ the development in Moblin:Factory doesn't follow the openSUSE development cycle. So how should the packages be handled? I doubt we can use M:F as a devel project for oS:F, at least for now :/ Would some "forking" be a good thing?
A mini fork seems to be the only real option as of now.
+ we need a plan to know what we should release. I have no idea what the Moblin schedule is, but if we think 11.2, we're basically frozen for upstream versions now. Is it reasonable to release 11.2 with a Moblin version that is basically what we have today + bugfixes?
Yes;
Indeed - I'm somewhat dismayed by all this talk of 11.3 - I was under the impression that the openSUSE team were committed to getting this into 11.2 - we have a great opportunity to leverage our leadership here, and be first to market; it would be really sad to ceede that to Ubuntu.
Whom to you mean with openSUSE team? You asked some time ago on the project list as well, and there I said already "hurry up" ;) We're beyond feature deadline and therefore we're limited to what we can do now. I would love to have a stable Moblin UI - but a coordinated release of a Moblin image with 11.2 is fine as well and might be the better option since it gives you much more flexibility. And the message I heard so far on this list, is that nobody is targetting 11.2 except you ;)
Of course, whether it is a top-level desktop selection, and/or whether it carries a heavy 'Experimental' tag, is up to us :-)
Of course, for our next release, I imagine we'll be based on the 11.2 packages, and hopefully we'll come increasingly into sync there package wise (if not time-line wise).
Andreas -- Andreas Jaeger, aj@{novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Fri, Aug 14, 2009 at 9:54 PM, Michael Meeks
Indeed - I'm somewhat dismayed by all this talk of 11.3 - I was under the impression that the openSUSE team were committed to getting this into 11.2 - we have a great opportunity to leverage our leadership here, and be first to market; it would be really sad to ceede that to Ubuntu.
< Boring story > When I was involved in the development of Evolution, we were doing some new attractive work. Some of the users who read our blog posts, wanted to try these features. We (openSUSE) have not had any daily builds for evolution at that time. Ubuntu was very methodical and promptly gave updates by doing regular builds, with the latest commits. This led to some users mentioning in irc: Ubuntu people add new features to Evolution, whereas openSUSE just consumes it in next releases : This was absolutely wrong as openSUSE had more developers for Evo. than Ubuntu, then. So, the moral of the story is: Users tend to think the people who bring the technology to them first are the creators of it. So, it is better to get Moblin on 11.2 itself, as it will be heartbreaking to see someone else get the first-to-market-craze after the openSUSE community put in all the efforts to do the development. And, promo-dvds, magazines etc. ship whatever that comes with the 11.2 GM. Reviews and blogposts are made for the GM widely than an addon product. IMHO, an addon moblin image is not as impactful as First-ever-distro-with-moblin. I understand that there could be time/resource crunch., but being the optimists we are, all problems should be solveable. A Moblin week can be celebrated to get more people from the rest of the community (GNOME, KDE, etc.) , may be some packagers from Novell non-OSS departments etc. to help for openSUSE shipping Mobling by 11.2 itself. My 0.1 cent -- Sankar P http://psankar.blogspot.com -- To unsubscribe, e-mail: opensuse-goblin+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-goblin+help@opensuse.org
On Thursday 13 August 2009 18:36:09 Aaron Bockover wrote:
[...] For the 11.2 cycle, I think the most reasonable approach is to offer a Moblin 2.0 image download next to the regular openSUSE. I do not think it's really feasible to integrate the full Moblin stack into 11.2 proper, but it is something we would like to do for +1.
For integration of Moblin into 11.3, I suggest that you sync with Coolo on how to do the following: * Submit all packages to openSUSE:Factory - I suggest an early first round * Integrate patches that you need (I pushed the boot up changes to the maintainers and hope that everything is in for 11.2 that Michael Meeks considered generally usefull and stable) * Send Coolo a list of packages (without dependencies) that a Moblin Desktop should have so that he can create a pattern for it Andreas -- Andreas Jaeger, aj@{novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Sorry for the delay in responding, going on holiday and playing catch up on my return is never easy. Aaron Bockover wrote:
Providing the Moblin user experience on top of a standard openSUSE base is something we are interested in doing, but it's not something that will feasibly happen very soon. We are locking down to freeze on an openSUSE/SLE-based Moblin 2.0.
If I remember correctly there was a conversation on IRC a while ago about how the Moblin UX was going to be delivered on an openSUSE base.
We have a few repositories, that build on openSUSE 11.1 or SLE 11:
* Moblin:Base - provides modified/updated kernel, xorg, HAL, etc. - much of what is here can be ignored for a Moblin user experience on a stock openSUSE (e.g. like we have GNOME and KDE desktops, we could have a Moblin one).
However, these packages are critical for providing the entire Moblin OS, and many patches would also need to be merged into openSUSE:Factory (e.g. we require KMS + DRI2). Much of this requirement is satisfied by xorg 1.6.3.
* Moblin:UI - provides updated GNOME packages and the core Moblin components like mutter, mutter-moblin, bickley, etc. Most of what is here can be run on top of a standard openSUSE 11.1
Getting the changes in these repos merged into openSUSE Factory is key. The question is which repo is to be the devel project? I intend to go through and run Vincent's new script to sanitise the packages to try and ensure a straight forward acceptance.
We produce the SLE-based images directly from Moblin:Factory, which is an aggregate project taking in packages from the two devel projects (Moblin:UI and Moblin:Base) and a few packages from other devel projects (e.g. mozilla for FF 3.5). We do all the core work in the public OBS, and there is an openSUSE 11.1 image project (KIWI) for producing a full image in OBS as well.
This image is a little bit stale, but the goal is to derive the SLE image from the openSUSE kiwi file, so that nothing gets horribly out of sink or stale. Andrew can speak more to this.
I initially wasn't aware of any staleness in the images until advised by Mr. Meeks. This has not prevented me from creating and running a functional build. The question is how do we get the image back in sync with the internal build? I thought all work was being done in the OBS and then synced to the IBS?
For the 11.2 cycle, I think the most reasonable approach is to offer a Moblin 2.0 image download next to the regular openSUSE. I do not think it's really feasible to integrate the full Moblin stack into 11.2 proper, but it is something we would like to do for +1.
I think initially this will be the easiest option as there are already tough cut off dates to be met. IIRC this was going to be the only method, although I would love to see Moblin available as an option on the DVD - the problem will be how to make space on the DVD. Would it be possible to still have an official ISO available around release time (give or take a week or two) and ensure that in the release announcement it is mentioned?
I'm very interested in Andrew's feedback here, and anyone else's interested in Moblin.
So far I've been using the "stale" images without any major issue, and to be honest things are generally speedy and if anything it works much better than my previous Studio Built images (running GNOME/KDE/XFCE). One of my goals is to create a Moblin 1-Click so that users can easily add it to their existing installs. People that now of the repos are confused as to what packages need to be installed (tbh so am I at times :D ). So basically I have created three tasks for myself in no particular priority (feel free to prioritise them for me) - 1. Clean up packages and submit to Factory; 2. Create 1-Click .ymp for Moblin; 3. Create images and make them publicly available - once the image is in sync should we use the OBS for this. There is a fairly big issue that I may have caused - sorry. The issue is that of the name, Now I came up with "Goblin" whilst bored at work, and at the time it seemed like a brilliant fit. After all Goblins are green ;-) There could well be an issue with Intel as I have been advised that they don't like the idea of word play on their products, and that their is already an LGPL project called Goblin which "is a C++ class library focussed on graph optimization and network programming problems". So my question is - what do we do about the name? Do we use "Goblin - powered by openSUSE & Moblin", "openSUSE Moblin Edition" or something completely different? Regards, Andy -- Andrew Wafaa, openSUSE Member: FunkyPenguin openSUSE: Get It, Discover It, Create It at http://www.opensuse.org -- To unsubscribe, e-mail: opensuse-goblin+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-goblin+help@opensuse.org
On Wednesday 19 August 2009 13:49:23 Andrew Wafaa wrote:
Sorry for the delay in responding, going on holiday and playing catch up on my return is never easy.
Aaron Bockover wrote:
Providing the Moblin user experience on top of a standard openSUSE base is something we are interested in doing, but it's not something that will feasibly happen very soon. We are locking down to freeze on an openSUSE/SLE-based Moblin 2.0.
If I remember correctly there was a conversation on IRC a while ago about how the Moblin UX was going to be delivered on an openSUSE base.
We have a few repositories, that build on openSUSE 11.1 or SLE 11:
* Moblin:Base - provides modified/updated kernel, xorg, HAL, etc. - much of what is here can be ignored for a Moblin user experience on a stock openSUSE (e.g. like we have GNOME and KDE desktops, we could have a Moblin one).
However, these packages are critical for providing the entire Moblin OS, and many patches would also need to be merged into openSUSE:Factory (e.g. we require KMS + DRI2). Much of this requirement is satisfied by xorg 1.6.3.
* Moblin:UI - provides updated GNOME packages and the core Moblin components like mutter, mutter-moblin, bickley, etc. Most of what is here can be run on top of a standard openSUSE 11.1
Getting the changes in these repos merged into openSUSE Factory is key. The question is which repo is to be the devel project? I intend to go through and run Vincent's new script to sanitise the packages to try and ensure a straight forward acceptance.
We produce the SLE-based images directly from Moblin:Factory, which is an aggregate project taking in packages from the two devel projects (Moblin:UI and Moblin:Base) and a few packages from other devel projects (e.g. mozilla for FF 3.5). We do all the core work in the public OBS, and there is an openSUSE 11.1 image project (KIWI) for producing a full image in OBS as well.
This image is a little bit stale, but the goal is to derive the SLE image from the openSUSE kiwi file, so that nothing gets horribly out of sink or stale. Andrew can speak more to this.
I initially wasn't aware of any staleness in the images until advised by Mr. Meeks. This has not prevented me from creating and running a functional build. The question is how do we get the image back in sync with the internal build? I thought all work was being done in the OBS and then synced to the IBS?
For the 11.2 cycle, I think the most reasonable approach is to offer a Moblin 2.0 image download next to the regular openSUSE. I do not think it's really feasible to integrate the full Moblin stack into 11.2 proper, but it is something we would like to do for +1.
I think initially this will be the easiest option as there are already tough cut off dates to be met. IIRC this was going to be the only method, although I would love to see Moblin available as an option on the DVD - the problem will be how to make space on the DVD. Would it be possible to still have an official ISO available around release time (give or take a week or two) and ensure that in the release announcement it is mentioned? I'd support that way. Having a Moblin ISO available and yes we should promote it - not only in the release notes but in pre-annoucments as well. The world should know that openSUSE has an "Moblin" edition. Is it feasible to provide a development release with one of the general openSUSE milestones in September or October?
I'm very interested in Andrew's feedback here, and anyone else's interested in Moblin.
So far I've been using the "stale" images without any major issue, and to be honest things are generally speedy and if anything it works much better than my previous Studio Built images (running GNOME/KDE/XFCE).
One of my goals is to create a Moblin 1-Click so that users can easily add it to their existing installs. People that now of the repos are confused as to what packages need to be installed (tbh so am I at times
:D ).
So basically I have created three tasks for myself in no particular priority (feel free to prioritise them for me) - 1. Clean up packages and submit to Factory; 2. Create 1-Click .ymp for Moblin; 3. Create images and make them publicly available - once the image is in sync should we use the OBS for this.
There is a fairly big issue that I may have caused - sorry. The issue is that of the name, Now I came up with "Goblin" whilst bored at work, and at the time it seemed like a brilliant fit. After all Goblins are green ;-) There could well be an issue with Intel as I have been advised that they don't like the idea of word play on their products, and that their is already an LGPL project called Goblin which "is a C++ class library focussed on graph optimization and network programming problems". So my question is - what do we do about the name? Do we use "Goblin - powered by openSUSE & Moblin", "openSUSE Moblin Edition" or something completely different? I'm not much in love with the name Goblin because of the issues Andy describes above. As Moblin is pretty well know I'd stick with the name. But that's something more for marketing guys.
Best M
Regards,
Andy
-- Andrew Wafaa, openSUSE Member: FunkyPenguin openSUSE: Get It, Discover It, Create It at http://www.opensuse.org
-- Michael Löffler, Product Management SUSE LINUX Products GmbH - Nürnberg - AG Nürnberg - HRB 16746 - GF: Markus Rex -- To unsubscribe, e-mail: opensuse-goblin+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-goblin+help@opensuse.org
On Wed, 2009-08-19 at 15:07 +0200, Michael Loeffler wrote:
Andrew wrote: There is a fairly big issue that I may have caused - sorry. The issue is that of the name, Now I came up with "Goblin" whilst bored at work, and at the time it seemed like a brilliant fit. After all Goblins are green ;-) There could well be an issue with Intel as I have been advised that they don't like the idea of word play on their products, and that their is already an LGPL project called Goblin which "is a C++ class library focussed on graph optimization and network programming problems". So my question is - what do we do about the name? Do we use "Goblin - powered by openSUSE & Moblin", "openSUSE Moblin Edition" or something completely different?
I'm not much in love with the name Goblin because of the issues Andy describes above. As Moblin is pretty well know I'd stick with the name. But that's something more for marketing guys.
Lets have a community voting contest, in openfate, and let the community decide [ or perhaps not ]. But wait, the SUSE / Moblin community so far is mostly Andrew ;-) so lets just ask him. To me the attraction of Goblin - apart from the green-ness, and the fact that Andrew picked it, is that it is not Moblin - which is an Intel owned(?) trademark, and also a heavily overloaded term with 3+ conflicting meanings - and there is a real risk we cannot use it for one reason or another [ and/or some arbitrary compliance process to go through to do so ]. Another attraction of Goblin is that it potentially a re-usable term that could be describe the GUI part of Moblin in a way that is not screwed over by the other two meanings of Moblin - a reference distribution and a specification to which we must comply. When I spoke with Intel, they were not that worried about the Goblin name - indeed, liked people taking it & running with it. The conflict with the C++ library is a concern - but I'm more worried about the generic nature of the name (making it hard to google) - but we're already in the first page from google, without any intense marketing so ... ;-) Also the C++ 'goblin2' library seems a typical sourceforge project - it hasn't had a commit for over a year and seems dead (to me). So - I think SUSE / Goblin is a good enough choice for now; perhaps we'll have to change it later, or get approval for the use of the name in some way but ... so be it (?). Then again - Guy - what is your take ? Jakub can you come up with an awesome, not-moblin-but-netbooky sort of more suse-like brand that has artwork potential, is suitably green etc. ? :-) 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
On Wed, Aug 19, 2009 at 12:49:23PM +0100, Andrew Wafaa wrote:
Sorry for the delay in responding, going on holiday and playing catch up on my return is never easy.
Aaron Bockover wrote:
Providing the Moblin user experience on top of a standard openSUSE base is something we are interested in doing, but it's not something that will feasibly happen very soon. We are locking down to freeze on an openSUSE/SLE-based Moblin 2.0.
If I remember correctly there was a conversation on IRC a while ago about how the Moblin UX was going to be delivered on an openSUSE base.
Yeah, it is a wish to do this. But it might be difficult due to the mismatch of a number of different packages.
We have a few repositories, that build on openSUSE 11.1 or SLE 11:
* Moblin:Base - provides modified/updated kernel, xorg, HAL, etc. - much of what is here can be ignored for a Moblin user experience on a stock openSUSE (e.g. like we have GNOME and KDE desktops, we could have a Moblin one).
However, these packages are critical for providing the entire Moblin OS, and many patches would also need to be merged into openSUSE:Factory (e.g. we require KMS + DRI2). Much of this requirement is satisfied by xorg 1.6.3.
* Moblin:UI - provides updated GNOME packages and the core Moblin components like mutter, mutter-moblin, bickley, etc. Most of what is here can be run on top of a standard openSUSE 11.1
Getting the changes in these repos merged into openSUSE Factory is key. The question is which repo is to be the devel project? I intend to go through and run Vincent's new script to sanitise the packages to try and ensure a straight forward acceptance.
They are all in Moblin:Factory right now, so it might not be that hard to see what is needed to do here.
We produce the SLE-based images directly from Moblin:Factory, which is an aggregate project taking in packages from the two devel projects (Moblin:UI and Moblin:Base) and a few packages from other devel projects (e.g. mozilla for FF 3.5). We do all the core work in the public OBS, and there is an openSUSE 11.1 image project (KIWI) for producing a full image in OBS as well.
This image is a little bit stale, but the goal is to derive the SLE image from the openSUSE kiwi file, so that nothing gets horribly out of sink or stale. Andrew can speak more to this.
I initially wasn't aware of any staleness in the images until advised by Mr. Meeks. This has not prevented me from creating and running a functional build. The question is how do we get the image back in sync with the internal build? I thought all work was being done in the OBS and then synced to the IBS?
yes it is.
For the 11.2 cycle, I think the most reasonable approach is to offer a Moblin 2.0 image download next to the regular openSUSE. I do not think it's really feasible to integrate the full Moblin stack into 11.2 proper, but it is something we would like to do for +1.
I think initially this will be the easiest option as there are already tough cut off dates to be met. IIRC this was going to be the only method, although I would love to see Moblin available as an option on the DVD - the problem will be how to make space on the DVD. Would it be possible to still have an official ISO available around release time (give or take a week or two) and ensure that in the release announcement it is mentioned?
I don't see why this wouldn't be possible to do. It's pretty trivial to build an image these days for Moblin, so we just need to get someone on the release team to do this.
I'm very interested in Andrew's feedback here, and anyone else's interested in Moblin.
So far I've been using the "stale" images without any major issue, and to be honest things are generally speedy and if anything it works much better than my previous Studio Built images (running GNOME/KDE/XFCE).
One of my goals is to create a Moblin 1-Click so that users can easily add it to their existing installs. People that now of the repos are confused as to what packages need to be installed (tbh so am I at times :D ).
Try just adding Moblin:Factory as a repo and see what happens if you do a 'zypper dup' :)
There is a fairly big issue that I may have caused - sorry. The issue is that of the name, Now I came up with "Goblin" whilst bored at work, and at the time it seemed like a brilliant fit. After all Goblins are green ;-) There could well be an issue with Intel as I have been advised that they don't like the idea of word play on their products, and that their is already an LGPL project called Goblin which "is a C++ class library focussed on graph optimization and network programming problems". So my question is - what do we do about the name? Do we use "Goblin - powered by openSUSE & Moblin", "openSUSE Moblin Edition" or something completely different?
I like the Goblin name. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-goblin+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-goblin+help@opensuse.org
Hello, 2009-08-13 17:12 keltezéssel, Michael Loeffler írta:
So please let us know your opinion if and how to integrate Moblin with openSUSE?
I don't know, if it is technically possible, but I would be happy, if at least the UI part could be integrated into 11.2. I installed it on my desktop machine, on openSUSE 11.1, and it was pretty impressive, even if not bug free. I also wanted to try it on my netbook, but had no luck. 11.1 has problems running on my Dell Inspiron Mini (no network, broxen Xorg). With factory these problems are gone, but I had dependency problems when tried to install it, so most of UI could not be installed. Using the OEM installer is not an option for me, as I need to keep some partitions untouched. Bye, CzP -- To unsubscribe, e-mail: opensuse-goblin+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-goblin+help@opensuse.org
participants (9)
-
Aaron Bockover -
Andreas Jaeger -
Andrew Wafaa -
Greg KH -
Michael Loeffler -
Michael Meeks -
Peter Czanik -
Sankar P -
Vincent Untz