News and Editorials
By Rebecca Sobol
November 5, 2008
The
openSUSE project recently welcomed
the first community elected board. The previous board was appointed by
Novell. The new
board consists
of both Novell employees and non-Novell members of the community. From the
Non-Novell side of the community Pascal Bleser and Bryen Yunashko were
elected, and from the Novell side Henne Vogelsang and Federico
Mena-Quintero were elected. Novell appointed Michael Löffler as chairman
of the board. We asked the new board a few questions and are pleased to
present their responses.
LWN: There was some discussion in the mailing lists prior to the
election about the definition of a member. The current definition says:
"openSUSE Members" are specifically distinguished contributors who have
brought a continued and substantial contribution to the openSUSE project."
Do you agree with this definition? What is your definition of "continued
and substantial"?
Pascal: We agree to that definition. The only potential issue with
it is the name "Members". We had a long discussion on our opensuse-project
mailing-list (that is open to everyone) about a proper name (and the
process too), but we didn't manage to come up with something less
ambiguous. Fedora's "Ambassador" title wouldn't be too bad, but actually
even more confusing as it is not the same role. Unfortunately there is
no red line we can cross between "non substantial" and "substantial",
which is why the Board discusses and votes on each membership request.
Typically, membership is granted to individuals who have been
contributing to the community since more than half a year, in domains
such as packaging, translating, authoring content on the Wiki, hacking,
helping out by answering questions or administrating mailing-lists, our
forum, or on IRC, etc... This is by no means an exhaustive list. We are
looking for verifiable contributions though, and we will discuss how to
proceed for granting Member status in the future, as the current process
doesn't scale that well. Several other options were discussed on our
opensuse-project mailing-list when we initiated the idea.
Bryen: This will always be a continuously evolved definition as we
identify people who contribute to the project as a whole, or in part, in
new ways we might not have thought of previously. Myself, I became a
member for my advocacy for a11y (accessibility through computing) and
encouraging others to think about the needs of people with accessibility
issues. I talked about it, I provided relevant information and I
participated regularly in openSUSE meetings. I see "continued and
substantial contribution" as someone who opens doors to making openSUSE
a more relevant platform for users.
LWN: Does Novell adequately support openSUSE? Should Novell do more
to support the project?
Henne: Novell is investing a lot in openSUSE. Nearly the whole
technical infrastructure of the project is taken care of by Novell. Novell
is also putting a lot of manpower and money into the project. But of course
we could always use more, the project is unsatisfiable in that regard. So
is Novell adequately supporting openSUSE? Yes. Could Novell do more?
Definitely. Should Novell do more: Yes please.
Bryen: One of the things that attracted me to the openSUSE Community
was the active participation of Novell developers within the project. They
continue to make themselves accessible and over time, they have given the
reins to other people from the community and empowering us all to do more
for the project. While I think Novell could stand to do a bit more
promoting of openSUSE to the general public, I think they've done a fine
job with Community Manager Joe Brockmeier. In many ways, I think it is
premature to determine whether Novell *needs* to do more. It's only been a
week since the polls closed for our new Board and we've had a good outcome
of voter turnout at 75%. This makes it the first time that our Board has a
community-backed mandate and a strong one at that. So it isn't a question
of whether they've done enough thus far, but more a question of what more
will they do now that Novell sees how strongly vested Community members are
in the project as stakeholder.
Pascal: But this doesn't mean it's one-way. The non-Novell
contributors in the community also do a lot, most of them during their free
time, as in almost any FOSS project. The community is very important to
Novell, and I believe that the relationship should be seen as being equal
partners.
Michael: Could Novell do more? Of course as everybody could do more.
But would it make sense? I doubt it. Rather than having even more support
by Novell I'd love to see more sponsors stepping up to base the openSUSE
project on broader shoulders and loose the dependency on one sponsor.
LWN: Does Novell exert too much control over the project? Where are
the areas where Novell could allow more community control?
Bryen: The only time I've ever really seen any resistance from
Novell is when they are unable to provide adequate manpower and support for
a particular feature or request. But beyond that, there seems to be great
transparency by the teams within openSUSE. If we were to go down the
path towards greater community control, it is more about whether there
is adequate manpower within the community to provide the support it
needs. I don't think Novell is resistant to that at this time, but
ultimately, it is about increasing membership where we can all work
together seamlessly.
Pascal: I don't believe that Novell exerts too much control over the
project. It's rather the opposite. It is important to understand that this
is an evolving process, where we started from (more or less) everything
closed except for a few when S.u.S.E. GmbH was acquired by Novell to the
point where Novell pushed for opening up many things around openSUSE when
it launched opensuse.org three years ago. More and more domains and teams
have opened up towards the community, and the community has grown with it.
Right now, we're rather in a position where Novell is actually looking for
more contributors from the community, with existing open processes (open
discussions on our mailing-lists, source code available in public
Subversion repositories, etc...).
There are still a few areas where we're still at the beginning of
opening up (actually rather at the point of starting to think about ways
to do that properly), such as having non-Novell employees co-maintain
core distribution packages or the openSUSE reference guide.
As said, it's in flux, and certain things take time, but Novell
definitely hasn't been standing in the way, quite the contrary.
And while Novell ultimately has the most resources in certain or even
most areas of the project, especially in building the distribution and
providing security maintenance during the openSUSE release lifetime,
there is always room for discussion.
One notable example was the thread about whether KDE 3 should be removed
from openSUSE 11.1, as KDE 4 is where almost all KDE developers put
their efforts in. At first, Novell's product management position was to
drop KDE 3 because it would mean supporting it for 2 years. But the
discussion lead to a compromise, as many believe that KDE 4 wasn't quite
ready enough. In the end, openSUSE 11.1 will still have KDE 3, but KDE 3
will be dropped in 11.2. The KDE3 maintenance during the lifetime of
openSUSE 11.1 will be taken care of by Novell employees. So, again, while
Novell commits most of the resources, the opinion of the community is
important to them, for obvious reasons.
Michael: With regards to more community control I think we (the
project) need to define clearer rules how to contribute and I'd love to
see co-maintainership for more and more packages, long term even core
packages.
LWN: Is the current board, with 5 members (2 Novell + 3 non), a good
size and does it achieve the right balance of corporate vs. community?
Pascal: I believe that 5 individuals form a good team size to
effectively get things done. The background of each member also happens
to strike an interesting, diverse and good balance of opinions and
influences both from within Novell employees as well as from the
non-Novell employees in the community. This is clearly very healthy and
can only lead to better representation of the community's opinions.
I can also imagine that at some point, that differentiation between Novell
employee and non-Novell employee Board position shall be removed. Remember
that it is our first elected Board. We take some decision and define some
processes because we believe that they offer a good balance. Actually, the
idea behind that separation was to make sure that there were two seats
occupied by non-Novell employees (and not less).
Bryen: What is important is that we ensure adequate representation
of the community and that the community is heard. As the Community grows,
we might have to revisit the size of the Board and consider adding adequate
representation.
Henne: I also have the feeling that on the topic of Novell and
openSUSE there is a big misconception. There really is no versus in that
relationship. In fact the openSUSE community consist of people that support
the openSUSE project and its goals. Some of those people are employed by
Novell, some of them are not. So its not "corporate vs. community" but
rather "community equals corporate and non-corporate". Also, the openSUSE
Board isn't the dictator of this project. The project consists of many many
different areas where people lead and make decisions on a daily basis. Some
of those people are employed by Novell, some of them are not. So to execute
control over this Board does not give you control over the openSUSE
project. Just over the openSUSE Board.
We understand that this is a controversial topic. But you shouldn't get
too theoretical while reflecting upon it. It is very tempting but this
is a total non-issue in reality. We are not trying to find the best
theoretical possibility to govern a project. We are hackers that try to
get things done.
LWN: In the openSUSE election members were able to name another
contributor (non-member) to be a voter. Would you like to see this continue
in future elections? Do you know if there were many non-members who voted
in this election?
Henne: I think we all agree with our election officials that his was
a special rule for the first election (see
Board Election page. So this
will not continue for future elections. There were 25 non-members
eligible. How many of them voted is not public.
Bryen: The non-member voters really represented a small fraction of
the electors as a whole. 25 out of 237. There were certainly mixed feelings
across the board about the idea of franchising votes, but the idea was
noble by the election committee to find ways to further identify potential
members and increase membership. Since one of the Board's mandates is to
grow the Community, I don't see the need for franchising votes in upcoming
elections. By the time the next election comes along, we should have done
significant work in reaching out to more new potential members.
LWN: How do regular users get more involved? How can they
contribute to both the technical work and the decision making?
Henne: As with any other open source project: Be there or be square!
Seriously, its as simple as showing up and participate. That's one of the
beauty's of free and open source projects. To contribute to our user
support just subscribe to one of our mailing lists, join one of our IRC
channels or login to our forum and help people as best as you can; as
described
here.
To contribute to our documentation go and help organizing and authoring in
our Wiki. To help to translate the
openSUSE distribution into your language join one of our various translation teams and translate
strings to your native language.
To contribute to the distribution use the openSUSE Build service. And those
are just the four main entrances into our project. You can have it as
specialized as helping openSUSE HAM users to transmit via radio, spinning
your own version of openSUSE for educational use or create artwork to be
included in the distribution. The same holds true for decision making.
All of the different areas make their own decisions. So to influence
decisions you go there, participate and voice your opinion.
Decisions that concern the overall project are always discussed at the
opensuse-project mailing list or are a topic in the bi-weekly
opensuse-project meeting. So you just go there and do the same.
It is really as simple as that.
Bryen: I think my personal story is the best example of all. Of all
the members on the Board, I'm probably the least technical. I'm more of an
active user than anything else. How did I get involved? I attended
meetings on IRC, advocated a11y, got involved in education by forming the
openSUSE Helping Hands project and as co-editor of the
openSUSE-Tutorials.com web
site.
Users can become members through advocacy, promoting openSUSE regularly
at local events, getting online and providing support to new users in
IRC and the forums. It's really not that difficult to become a member
and you don't have to be a technical genius to become a member.
Pascal: I'd like to add that while a number of things are in place,
we clearly have to work even further on lowering the barriers for people
who are willing to contribute. Even better tools, better documentation,
even more translations. As always, and as for any other FOSS project, there
is always room for improvement.
Michael: I can just support Pascal's opinion that it would be
beneficial for us to lower barriers and provide a clearer description in
what and how everybody can contribute and present our existing tools
better. Especially implement some cross-functionality like better
integration of our Bugzilla and the openSUSE build service for instance.
LWN: Do you see areas of collaboration with other distributions
either currently or in the future?
Henne: Collaboration is our foundation. We would cease to exist if
we wouldn't collaborate with everyone else in the free an open source
community. Among them are, of course, also other distributions. Whether
openSUSE project members hack with members of the Debian or Slackware
projects on some upstream project like the Linux kernel, or that we
coordinate when it comes to security issues with everyone else on
vendor-sec, or that we try to consolidate tools we use like we do with
Fedora on smolts.org. There are of course also the big collaboration
projects we support like the Linux Standard Base or freedesktop.org. So we
are collaborating heavily with other distributions already and we will
continue to do so in the future.
Bryen: Generally speaking, collaboration is an integrated feature of
open source, so yes, collaboration exists across the board between openSUSE
and other distributions.
Pascal: I'd like to see that going even further. As one of the
organizers of the FOSDEM conference, one of our primary goals there is
to foster cross-pollination between projects with similar goals and
domains. While difference and choice are some of the key features of
FOSS (yes, I believe that having many distributions is very healthy),
there are situations where working together on a few things makes sense.
There isn't always a point in reinventing the wheel. Sharing development
efforts and commoditizing tools for contributors is clearly something
I'd like to see happening more often.
While openSUSE is definitely a brilliant distribution in many regards
and while we have a healthy community that consists of great people, we
still have a lot to do, and so do the other distribution projects.
They're not less good nor less deserving, we all have our strengths and
weaknesses, so we should work together to make Linux and FOSS a better
experience to everyone. If you're feeling at home with another
distribution, great, contribute there! And if you think you'd like to
contribute to our distribution or to our community, you are definitely
welcome here too. And if you believe there are domains where we can work
together, please get in touch with us at board -AT- opensuse.org.
Editor's note: We would like to thank the openSUSE Board for taking the
time to answer our questions. Readers may notice that not all board
members have answered every question. This was their choice and not due to
any censorship on our part.
Comments (none posted)
New Releases
The Fedora 10 preview release is now available. "
Doesn't it smell yummy? We know you can't resist, and we don't want you
to. We want everyone in the Fedora community to take an early sample and
tell us what you find. The recipe is pretty good, but now is the time to
make it perfect." This is the last testing release for this cycle.
See
the release
notes for an overview of what Fedora 10 brings.
Full Story (comments: 10)
Fedora has a Sugar Spin available, which incorporates the Sugar Desktop
Environment on a Fedora Live CD. "
So, what is this in specific?
With this spin, you'll be able to run Sugar, which is developed by
Sugarlabs and the desktop environment used on the OLPC, directly from a
Live CD!"
Full Story (comments: none)
The OpenBSD project has announced the official release of OpenBSD 4.4.
Click below for a list of new features, new platform support and more.
Full Story (comments: 3)
The openSUSE Project has announced the availability of openSUSE 11.1 beta
4. "
This release includes a number of important bugfixes since the
last beta, as well as a few new bugs that need to be squashed before the
final release. Read on for details about this release and how to get
involved with testing."
With the release of openSUSE 11.1 Beta4 comes a
call for feature testing.
Full Story (comments: none)
Red Hat has
released
the Beta of Red Hat Enterprise Linux 5.3. This version has
kernel-2.6.18-120.el5 and includes versions for x86, x86/64, Itanium, IBM
POWER and System z. The Beta runs until January 6, 2009.
The CentOS community has issued
a call for testing of this release. "So if we can improve the
testing during the RHEL Beta program, everyone in the CentOS community
directly benefits from that as well. Therefore it makes a lot of sense to
encourage the large CentOS community to take part in the RHEL Beta program
and help with improving the next CentOS releases."
Comments (none posted)
A new release of Tin Hat Linux is out, with bugs/security fixes.
Full Story (comments: none)
Ubuntu 8.10 "Intrepid Ibex" has been released.
"
The Ubuntu team is pleased to announce Ubuntu 8.10 Desktop and Server,
continuing Ubuntu's tradition of integrating the latest and greatest open
source technologies into a high-quality, easy-to-use Linux
distribution."
Full Story (comments: 21)
Distribution News
Fedora
The
RPM Fusion project has announced the availability of its repositories of Fedora and Red Hat compatible software. "
RPM Fusion is a project started by the Dribble, Freshrpms and Livna
teams. It aims to bring together many packagers from various 3rd party
repositories and build a single add-on repository for Fedora and Red
Hat Enterprise Linux. We hope to attract new Fedora packagers and hope
that other 3rd party repositories will join us." Click below for the full announcement.
Full Story (comments: 2)
The #fedora-classroom irc channel (on irc.freenode.net) will be open soon
for some classroom sessions. "
These sessions are intended to be
short (30min to an hour) sessions on the IRC network where you can learn
about a specific Fedora related topic." Check
the
schedule to see what topics will be offered.
Full Story (comments: none)
Click below for a brief recap of the October 28, 2008 meeting of the Fedora
Board. Topics include Trademark guidelines, Fedora Sugar Spin, Upcoming
Elections, and FUDCon Fedora 11.
Full Story (comments: none)
Click below for a summary of the Fedora Engineering Steering Committee
meeting for October 29, 2008. Topics include features, elections and
comps.
Full Story (comments: none)
SUSE Linux and openSUSE
SUSE Security has announced that the maintenance, security and L3 support
for Service Pack 1 of the SUSE Linux Enterprise 10 line of products will
end November 30, 2008. "
We recommend strongly that customers upgrade
now to Service Pack 2 of SUSE Linux Enterprise 10."
Full Story (comments: none)
Ubuntu family
The Ubuntu Project has started the development cycle leading up to the 9.04
release, currently
planned for
April 23. "
We do not recommend that users upgrade to Jaunty at this time; it is
likely to be in very considerable flux until the initial round of merges
is complete. As ever, any developers wishing to take the plunge at this
early stage should ensure that they are comfortable with recovering from
anything up to complete system failure."
Full Story (comments: none)
Distribution Newsletters
The
DistroWatch
Weekly for November 3, 2008 is out. "
It was the Ubuntu week,
with much of the Linux-related coverage on many web sites dominated by the
brand new "Intrepid Ibex", the project's latest. A plethora of reviews
followed almost instantly, but some subtle hardware issues and lack of real
breakthrough features have left some of the users and reviewers
unimpressed. In other news, Fedora has unveiled Plymouth, a new
flicker-free boot process, Sabayon has hinted at a large number of
never-seen-before features for the upcoming 4.0 release, Yellow Dog Linux
has launched a beta testing period for its forthcoming version 6.1, and
NetBSD is about to branch version 5.0 with some unexpected
improvements. Also in this week's issue - Ubuntu has published a draft
release schedule for "Jaunty Jackalope" or Ubuntu 9.04. Finally, we are
pleased to announce that the recipient of the October 2008 DistroWatch.com
donation is GoblinX, a slick Slackware-based live CD made in
Brazil."
Comments (none posted)
The
Echo
Monthly News for October 2008 is out, covering the news about Fedora's
Echo Theme. Topics include new icons, new templates, Echo Won't Be F10's
Default Icon Theme, Icon Check Script and Echo Future.
Comments (none posted)
The Fedora Weekly News for November 2, 2008 is out. "
In this week's
issue, featured content includes announcements on a new Fedora Sugar Spin,
and development freeze for Fedora 10. The Translation beat this week
features an interview with Fedora Translation project member Diego Zacarao
(Rasther). In Developments, details on resume from suspend problems with
Intel i945s, details on "[a] gigantic multi-thread flamewar consum[ing]
many list participants" over moving X from VT7 to VT1 and POSIX file
capabilities for Fedora 11. The Artwork beat features discussion of new
wallpaper extras, and final fixes for the Fedora 10 Solar backgrounds. The
Security Advisory beat rounds out this issue and updates us with fixes
released in the last week for Fedora 8 and 9."
Full Story (comments: none)
This issue of the
OpenSUSE Weekly
News looks at Less then 50 days to openSUSE 11.1, Results of the 1st
openSUSE Board Election, Ben Kevan: fslint - Take control about your
Filesystem, OpenOffice.org 3.0 final, counter.opensuse.org updated, and
more.
Comments (none posted)
The Ubuntu Weekly Newsletter for November 1, 2008 covers: Ubuntu 8.10
released, Ubuntu 8.10: significant new features, UDSJaunty, Ubuntu Open
Week, New Contributing Developer, Dustin Kirkland interview #2, Ubuntu
Brainstorm 8.10 report, SFD in Tunisia, Launchpad EPIC, Over 6 million
Forum posts and counting, Ubuntu Sighting, Full Circle Magazine #18, New
TurnKey Linux release, Release week for Ubuntu and CohesiveFT, and much
more.
Full Story (comments: none)
Distribution meetings
Ubuntu Open Week starts next Monday, November 3. "
Ubuntu Open Week is
a week of IRC tuition and Q+A sessions all about getting involved in the
rock-and-roll world that is the Ubuntu community. We organise this week for
the beginning of a new release cycle to help new contributors get
involved. Thanks to Jorge for helping to get the week together and for
everyone who is helping to run sessions. Its going to be a fun
week!" Tune into #ubuntu-classroom on Freenode to join in the fun.
Full Story (comments: none)
Newsletters and articles of interest
Phoronix
takes
a look at Plymouth, a flicker-free boot process previewing in Fedora
10. "
Plymouth has an extensive API that allows artists and
programmers to develop graphically rich Plymouth plug-ins. Plymouth is,
however, compiled into the system's initial RAM disk (initrd) so there are
some limitations. Plug-ins though can rely on loading PNG images as libpng
is linked to Plymouth. The plug-ins currently available through the
project's git repository currently include details, fade-in, pulser, solar,
spinfinity, and text. These plug-ins are also packaged in RPM form on
Fedora 10. The Fedora 10 RPMs include plymouth (the main graphical boot
package), plymouth-devel (the libraries and headers), plymouth-gdm-hooks
(provides integrated with GDM), plymouth-libs (the Plymouth libraries),
plymouth-plugin-fade-in, plymouth-plugin-label, plymouth-plugin-pulser,
plymouth-plugin-solar, plymouth-plugin-spinfinity, plymouth-scripts
(scripts to assist in configuring Plymouth), plymouth-text-and-details-only
(intended for those not interested in a rich boot experience), and
plymouth-utils (utilities related to Plymouth)."
Comments (none posted)
Joe "Zonker" Brockmeir
reports
on the Google Summer of Code Mentor's Summit. "
Overall, I think
the FOSS community in general, and distros in particular, are pretty good
at being willing to communicate and work together -- the fall-down comes in
when a contributor from Project A doesn't know who to contact with Project
B. (Hint: Start with the project leader or community manager if you don't
know who to start with_) One of the larger discussions was -- how do
projects get picked for GSoC and how do projects get passed over."
Comments (none posted)
Distribution reviews
Linux Journal
takes
a look at the final release of Ubuntu 8.10 "Intrepid Ibex".
"
Among Intrepid's shiny new packages are upgrades to core portions of
the operating system including the kernel itself, which has been updated to
the 2.6.27 release. The latest version of X.Org, 7.4, which appeared in
September after months of repeated delays, is included, and boasts improved
hot-plugging for keyboards, mice, and other input peripherals, a failsafe
mechanism to provide better troubleshooting for startup glitches, and for
many users, the end of the xorg.conf configuration file."
Comments (none posted)
KDE.News
takes a quick look at
Kubuntu 8.10 with KDE 4.1. "
The Kubuntu developers have been
hard at work, integrating this major new version into a completed
desktop. The settings and artwork have been kept close to KDE's defaults to
ensure the best face of our favourite desktop shines through."
Comments (3 posted)
Page editor: Rebecca Sobol
Next page: Development>>