Hi all,
April 16-17 in Antwerp, Belgium, the Linux Open Administration Days will
take place. This free event offers a chance for LPI certification as
well as meeting and talking to linux sysadmins. There is a call for
presentations here: http://www.loadays.org/content/call-presentations
If you want to go and give a talk there about openSUSE tech - that's be
awesome. If you can't afford to go there due to travel or hotel costs,
let me know, we might be able to work something out ;-)
cheers,
Jos
Hi,
We had a short go/no-go meeting on #opensuse-factory and decided
that the fuser problem may be the cause of all evil and now that it's gone,
we can go forward and release beta1.
We even managed to get most of the artwork updated in the days slippage.
If you come around it, I will upload build315 to the mirrors tomorrow morning.
When to announce publically I leave to the marketing guys, I'll be mainly
off the internet till tuesday as monday is public holiday for me and I'm told
publishing news on friday is bad - but I'll make sure the ISOs are available
for interested testers. I hope that's ok for the team.
Now the interesting question is what about the RC1. We didn't really loose
time in development as we checked in almost everything that came in during
the time we waited for the fixes - this includes e.g. kernel 3.1rc7. But we
can't hold the schedule as it is - the original deadline for RC1 checkins is
october 7th - that's around 4 days after public announcment of the beta
and even before the pizza party.
With the new factory work flow we have some more flexibility in terms of
checkin deadlines, so let's make use of that. My proposal would be:
Move RC1 from October 13th to 21st for release date - checkin deadline
would be 18th.
Move RC2 from October 27th to November 3th - checkin deadline would be
October 28th (November 1st and the monday in front are blackout in Nuremberg
and we rely too much on Nuremberg to move the date where it's perfect ;( )
Move Final release from November 11th (who set that date anyway? :) to
November 16th. GM would be on 11th.
Note, that I don't want to move the final date too much and if we all agree to
some discipline, RC2 will already be perfect and we only apply some polishing
up to GM. I know that shuffles our usual weekdays for release a bit and I'm
pretty sure I made some mistakes in my proposal, so please feel free to
give ideas of yours.
Greetings, Stephan
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
Hello Mates,
don't worry about this mail. I just would like to remind that our next
openSUSE Weekly News 195 comes out at Saturday evening (UTC +2).
Until Saturday 08:00:00 (CEST) +0200 UTC you can propose Articles, Links
and all such stuff for integrating into the Weekly News.
For people who don't want to write it in XML, you can use our Pad:
http://os-news.ietherpad.com/2.
I've planned to send this Mail each Wednesday to remind on the Weekly
News.
Have a lot of fun :-)
--
Sincereley yours
Sascha Manns
http://saigkill.homelinux.net
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
Dear Webmaster
As we found your website http://en.opensuse.org and saw that it meets our terms of use, we were interested in adding it to our webpage directory in English.
This directory http://www.web-ref.org/ is free and will have your website gain popularity and traffic, since it is visited by 20 thousand people monthly.
If you agree, please answer this email with the word Yes and we will include you.
Paul McMillan
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
Hello community,
this mail is the result of years of continuous development in my (corporate and private) environment as engineer favoring SUSE, and I kindly invite anyone to send thoughts, comments and ideas regarding this mail. I see this topic "as in progress" and if there aren't any ultimately bad reasons why not to do so, I will continue and support this as long as I can.
- Disclaimer: This is all IMHO ;) -
My idea is to build a SLES binary-compatible distribution completely supported by the community (and optionally supported by companies which are willing to do so) - most of you will probably see lots of similarities with CentOS in this way - And in fact: This is exactly what I intend it to be.
Why?
- SLES is one of two key players in the major distribution league. RH has CentOS, and whereever you see "respins" like for appliances, they use CentOS (or maybe some debian/ubuntu/knoppix-stuff) - no SUSE. Examples: Trixbox, ESVA, and _lots_ of projects in which I've been involved in development however its not officially communicated as CentOS.
- SUSE is the best Distro in terms of packaging and distribution technology (OBS), has a huge community-base and uses technology which IMHO is unmatched for various reasons such as KIWI (thx to Marcus Schaefer ;)).
- openSUSE is a "moving target" in terms of its faster release cycle and it in fact is a problem that older releases disappear from the mirrors pretty soon. (I would not change anything here) - But: This doesn't really allow you a "LTS"-like behaviour if things change so fast.
- SUSE has a great community of highly motivated and skilled guys (and gals) ;) - lots of developments in openSUSE find their way right into SLES, approved and tested by SUSE engineers.
What I can and will provide:
- I'm just building up a rack to provide various build nodes. Target arch's include: x86, x86_64, sparc64, ia64, ppc64. Most of the parts are already available, but since I'm currently moving and I need to get a stable permanent internet connection this could take up to 2 months. So this enables us right from scratch to set up a parallel OBS for the intial build setup. Official OBS could always be used as soon as we have reached a "staging" level where we can provide a base set of packages.
- I will provide anyone with an account and try to build a full "infrastructure" which then should also should get the transition to "community-controlled" behaviour.
For all (eventually) upcoming questions:
- Yes, I do know about openSUSE Evergreen, but it lacks some points I've mentioned above like "Enterprise Features", 1-on-1-("binary")compatibility with SLES and the great quality work by SUSE to get SLES certified by OEM's etc. - and no one really points its OBS tree to build against Evergreen, it points it to major channels like SLES11, SLES11SP1, oS11.4, etc.
- No, I do not want to work "against" SUSE or anything like that. The complete opposite is the case: Without SUSE this would not work well. In fact I really think SUSE also can profit from a community base around the SLES packages. Take a look at CentOS - Does it really hurt RHEL? I don't think so, at least not to a major extent. Lets get the facts straight: If you are in a corporate environment you _will_ (or at least you _should_) buy a SLES. Reasons: Support, Updates, Faster upstream process, tracking, direct contact, etc. But: If you want to build a steady home system which you do not want to upgrade less than every year in a major way or you might want to build a distro fork for special purpose (like for system integrators, etc.) you (probably) wouldn't want to go with the fully blown SLES.
- Yes, I see this as lots of work. Please let me know if you are willing to help. ;)
Can't await reading your comments.
Cheers,
- mike
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
Sorry for the cross posting, but I thought it worth the extra noise ;-)
One of the things that came out of the recent Geeko Love-In for me was a
new project to immerse myself in within openSUSE. Yeah I know, we have
enough existing projects already so why create a new one? Simples!
Believe it or not but openSUSE is behind the curve in a specific
segment, and that segment has yet to explode to its full potential. That
segment is ARM. No I'm not talking about your upper body appendages, but
the architecture that powers most of your little devices (and some
bigger ones too). Almost all smartphones, tablets and many other
consumer devices are powered by ARM from one of the numerous licensees.
Didn't openSUSE do something about this a while ago? Yes we did.
Unfortunately the effort seems to have bitrotted somewhat, there were
numerous reasons and I don't even prophesise to know the all either.
As such I'm going to try and kickstart things, and see it through and
hopefully see it grow. As I mentioned, this idea came up at the
conference when I was talking to numerous people (I forget how it all
started, but that doesn't really matter). There was an overwhelmingly
positive view on the matter, and that for me was all that counts. Now
let me be crystal clear here, *THIS WILL NOT BE A ONE MAN SHOW!!* I
mentioned previously that my view is that we as a community are pretty
lazy at times with getting our hands dirty. As such if you think things
are going slow or not going in the direction you would like, don't moan.
Get your hands dirty and help make a difference.
The process will not be an easy one either, so don't expect a port to
magically appear over night. If we're lucky we might be able to have a
working port in 6 months. Maybe longer, maybe shorter; ultimately that
lies with us as a community.
Stage one has begun already thanks to Adrian Schroeter, Alex Graf and
Dirk Mueller. Stage one comprises of getting the boot strap process to
work. At a cursory level this means getting the packages required for
setting up a build chroot environment and for building these packages on
the target ARM architecture. This will possibly take a fair amount of
time, and no I won't give any timelines for this - how long is a piece
of string?
openSUSE has a couple of advantages here, 1) we have the OBS which can
cross build and if need be cross compile packages for numerous
architectures (ARM included) so we are going to make a start with that;
2) SUSE are going to be doing another HackWeek (I think it is next week)
which means Adrian, Alex, Dirk and anyone else that has knowledge,
experience or interest can join in the fun and pain almost full time for
a week - let's not kid ourselves here there is a high probability for
lots of pain, but also fun ;-) Thing is HackWeek is not just for SUSE
staff, it is also for the community. You can join in and spend some
quality time on the project with those that know a whole heap of stuff,
and learn from them and maybe even teach them something too.
We are going to be targeting ARMv7 nothing older I'm afraid this means
CORTEX-A8 and above (looking at A9 primarily and then the new A15 when
it's available), it gets too messy otherwise and it is already messy
enough.If you have knowledge and experience, please help out. If you
don't take part you have no justification to complain - you've got to be
in it to win it ;-)
So I'm basically just giving you all a heads up on this effort, and will
update you as regularly as possible (I'm hoping to do something weekly
maybe). In the meantime, if you're interested join #opensuse-arm on
Freenode and the opensuse-arm mailing list. *DO NOT HARRASS* for
updates, if there is something to say it will be said. If you've got a
question, ask and *WAIT* for an answer. If you want to help out but want
to know how ask and *WAIT* for an answer. I will try and get something
on the wiki soon, with a todo list etc.
Thanks and here's to getting our Geeko some ARMs.
Regards,
Andy
--
Andrew Wafaa
IRC: FunkyPenguin
GPG: 0x3A36312F
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
OpenSUSE has jumped way ahead of all the other major distributions by pushing guile-2.0 to factory, this may cause problems for packages
such as gnucash if it uses guile to the extent that lilypond does. Lilypond uses guile extensively and are working on porting lily to guile
2.0 but this is their timeline quoted from one of my emails from Graham Percival to the devel list please note that lilypond 2.16.0 may not
be released before openSUSE 12.1 and I'm working on 2.14.2 atm the current release :
There is absolutely zero chance of lilypond 2.16 using guile 2.0.
There is maybe a 10% chance that any version of lilypond will
support guile 2.0 in 2011. Total guesswork for future
predictions: 50% chance of supporting guile 2.0 before July 2012,
80% chance of support guile 2.0 before the end of 2012.
What that means for opensuse is up to you. If you particularly
want guile 2.0, then by all means jump in; the more people working
on it, the higher the chances are that it'll get done sooner. But
based on the amount of work that currently goes into guile 2.0,
those are my estimates.
Cheers,
- Graham
and I think this is also relevant, another lily developers reply from the same message:
Given that the upcoming ubuntu oneiric apparently does not include guile 2.0, I also don't see a switch to guile 2.0 in the near future.
I suppose that we should ask the ubuntu people when they'll finally package guile 2.0.
Cheers,
Reinhold
I've looked at parallel installation of guile 1.8.8 (we jumped from 1.8.7 to 2.0.1) and it doesn't look easy otherwise I would have
submitted guile1 but I'm still working on it although I'm not that familiar with the autoconf/automake build system at this level.
What this means for openSUSE, lilypond is a very popular musical notation type setting program, the developers pride themselves in the
accuracy of the notation positions, it is also used, for musical notation by rosegarden, a popular music and midi composition program. Both
of these applications have no substitutes in the open source world and only have costly equivalents in the ms windows world, neither being
available for ms windows although there are requests to port for both this won't happen in the immediate future. Rosegarden can work
without lilypond as it is only bound to lilyponds notation fonts but the sheet music it exports will be useless so it will lose major
functionality.
Lilypond won't even be able to be installed via tarball on openSUSE 12.1 without the user removing guile 2.0 completely and installing
guile 1.8 via tarball, as a result these users of lilypond and rosegarden will drop openSUSE.
I started as a community maintainer by saving both lilypond and rosegarden from being dropped, I'm now very active in maintaining
multimedia apps and libs and losing these programs will mean losing a large section of professionals in music related professions that have
migrated from the windows world including the people that I've converted from ms windows just by showing them rosegarden although ms's
change from xp to vista also helped.
For the other packages that directly depend on guile : guile aisleriot gnucash autogen and slib, the change back to guile-1.8.8 won't
AFAICS have any negative effects, all of these packages simply have patches for guile 2.0 and after looking at the patches, will most
probably build with the patches still in place. I don't know what the situation is with guile users but it is an app for use by apps and
not a direct users app. Guile-1.8.7 builds for factory, guile-1.8.7 doesn't build for 11.4.
What are we going to do? Drop lilypond, I will keep it alive in home:plater:lilypond with guile-1.8.8 to replace guile-2.0.2 or revert to
guile-1.8.8 in line with the other linux distributions?
Thanks
Dave Plater
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
At the recent 12.1 Marketing hackfest, we devised an editorial schedule
and folks have begun writing articles for promoting 12.1. However, some
of these articles haven't been submitted yet. We suggest that in order
to minimize confusion and reduce excessive pinging, you create an
ietherpad with your article and link to it in the editorial schedule at
http://ietherpad.com/sked or send your article directly to
news(a)opensuse.org.
Using a pad such as ietherpad or piratepad has proven to be such a
valuable tool for crowdsourcing an article and getting it really spiffed
up.
Submitting your article links will enable us to ensure the articles are
published in a timely manner and also allows the news team to be able to
review and polish (not change!) the article itself ahead of time so that
it becomes publishable.
And while I'm at it, I'll use this opportunity to invite anyone who
thinks they have an article in mind to go ahead and start writing it.
There's still plenty of topics in our schedule that don't have an
assigned writer yet. And as I tell people often, don't worry about your
writing skills. Just write! Braindump it! Our news team is dedicated
to being there to help polish and make it presentable for you. And
wherever possible, we'll make sure that a subject matter expert also
reviews the article for accuracy. Our stories do get picked up by other
news media outlets and this is a chance to make you shine with a byline!
Thanks,
Bryen M Yunashko
openSUSE News Team
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
On Fri, September 23, 2011 9:16 pm, Jan-Simon Möller wrote:
> <snip>
> Well cool - why did it take us ~ 1.5 years to notice ;) .
> I just dropped factory pack then as it is too much for just one penguin.
>> > 2) SUSE are going to be doing another HackWeek (I think it is next
>> week)
>> > which means Adrian, Alex, Dirk and anyone else that has knowledge,
experience or interest can join in the fun and pain almost full time
>> for
>> > a week - let's not kid ourselves here there is a high probability for
lots of pain, but also fun ;-) Thing is HackWeek is not just for SUSE
staff, it is also for the community. You can join in and spend some
quality time on the project with those that know a whole heap of
>> stuff,
>> > and learn from them and maybe even teach them something too.
>> > We are going to be targeting ARMv7 nothing older I'm afraid this
means
>> > CORTEX-A8 and above (looking at A9 primarily and then the new A15
when
>> > it's available), it gets too messy otherwise and it is already messy
enough.If you have knowledge and experience, please help out. If you
don't take part you have no justification to complain - you've got to
>> be
>> > in it to win it ;-)
>> > So I'm basically just giving you all a heads up on this effort, and
>> will
>> > update you as regularly as possible (I'm hoping to do something
weekly
>> > maybe). In the meantime, if you're interested join #opensuse-arm on
Freenode and the opensuse-arm mailing list. *DO NOT HARRASS* for
updates, if there is something to say it will be said. If you've got
a
>> > question, ask and *WAIT* for an answer. If you want to help out but
>> want
>> > to know how ask and *WAIT* for an answer. I will try and get
something
>> > on the wiki soon, with a todo list etc.
>> I think we should get people like Jan-Simon Möller on board as he started
>> the first openSuSE ARM build in 2009 and also the ARM build in OBS. I
think it'll kick-start the ARM port.
>> > Thanks and here's to getting our Geeko some ARMs.
> So let get a crew together - we have the knowledge and the tools. I'm
willing to do my part on the weekends and continue what I did back then.
> Time to wipe android from the transformer ?! ;)
That'll be one mean machine. (Certainly the upcoming Transformer 2 (TF201
?) with the Tegra Kal El)
I have looked into the Tegra2.
I've read this story in connection with hardfp.
http://www.slashgear.com/meego-tegra-2-drivers-could-end-android-monopoly-o…http://www.meegoexperts.com/2011/07/nvidia-meego-battle-ground/
This looks quite promising. I don't know when these drivers will be
available I couldn't find any information yet.
> Best,
> Jan-Simon
Just some information as people are looking into hardware.
The trimslice might also be an option as you'll get 45% off as a
developer, I don't know if it's still valid.
http://trimslice.com/web/dev-kit
IMHO the advantage it that there are a lot of Tegra devices Tablets etc.
The disadvantage is IMHO that the driver is closed source. I don't know if
the nouveau project could change this?
Regards,
Joop.
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
If you participated in the openSUSE and Labs conference 2011, please read on:
We have created a short survey about the conference and would like you
to use it to give us feedback:
http://www.surveymonkey.com/s/HD3QDDH
If you're a speaker, please upload your slides as part of your
abstract. Use the following URL:
http://conference.opensuse.org/indico//myconference.py?confId=2
If you have attended a BOF or workshop, you can also add your notes to
the wiki. To have them show up at
http://en.opensuse.org/Portal:Conference under "Session Notes", just
add as wiki markup: [[Category:Osc11_session_notes]] .
Thanks for your feedback,
Andreas
--
Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org