The openSUSE Election Officials committee is proud to announce this
year's official list of candidates for the openSUSE 2013 Board.
They are:
- Matt Baringer
- Richard Brown
- Carl Fletcher
- Manu Gupta
- Chuck Payne
- Robert Schweikertz
- Stefan Seyfried
- Raymond Woonick
The official announcement and relevant links can be read in today's
published news.opensuse.org article at: [1]
Please use the time this week prior to the election to engage with the
candidates and ask them questions about their positions and goals.
Voting begins next week and we want you all to be well-informed
voters. :-)
Sincerely,
The openSUSE Election Officials committee
[1]
https://news.opensuse.org/2012/11/28/meet-the-opensuse-board-candidates/
--
To unsubscribe, e-mail: opensuse-announce+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-announce+help(a)opensuse.org
It's not too late to throw your hat into the ring and represent your
community on the openSUSE Board. The deadline to submit your intention
to run for the board is tomorrow, 27 November, 2012.
Please review the full details of our election procedures on our wiki
[1].
Being a board member is one of the many great ways you can help shape
the direction and future of the openSUSE Project. If you care and want
to give something back to the community, this is your chance.
Sincerely,
The openSUSE Election Officials Team
[1] http://en.opensuse.org/openSUSE:Board_election
--
To unsubscribe, e-mail: opensuse-announce+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-announce+help(a)opensuse.org
I would like to inform all of you that there is an openSUSE KDE Team meeting
planned for next week Wednesday 21 November at 17:30 UTC in the irc channel
#opensuse-kde.
The main agenda for this meeting is:
1) Action Items
2) Status report
3) KDE Team task list (http://en.opensuse.org/openSUSE:KDE_packaging_tasks)
(tittiatcoke)
4) Does the openSUSE KDE Team want to have Apper as updater and application/x-
rpm MIME type handler for 12.3? (unknown)
5) Q&A, Misc
I hope to see you all.
Regards
Raymond
--
To unsubscribe, e-mail: opensuse-announce+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-announce+help(a)opensuse.org
Hi everyone,
If you have joined the openSUSE project within the last 3 years, I
would like to kindly request your help for a survey:
https://limesurvey.sim.vuw.ac.nz/index.php?sid=65151&lang=en
(open until November 21).
The purpose of the project is to work out how newcomers to a FOSS
community become valued sustainable contributors. This is part of my
PhD thesis.
Vincent Untz and Jos Poortvliet are supporting this research.
Thanks!
Kevin Carillo
--
To unsubscribe, e-mail: opensuse-announce+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-announce+help(a)opensuse.org
On the opensuse-packaging mailing list, we've recently formed a team
that will take care of the packaging guidelines and introduced a
small process to change them:
http://en.opensuse.org/openSUSE:Packaging_guidelines_change_process
As part of that process, we're announcing regularly the changes to the
packaging guidelines. Since this is a first such announcement, it
is not a complete change but just points out a few things from the
past few months. In the future, we will send out this email once a
month.
The Packaging guidelines can be found at
http://en.opensuse.org/openSUSE:Packaging_guidelines .
List of changes
===============
1) New Lua Guidelines
2) Reworked font guidelines
3) Documenting changes in packages
4) Teams involved, contact
Details
=======
1) New Lua Guidelines
We now have guidelines for lua:
http://en.opensuse.org/openSUSE:Packaging_Lua.
2) Reworked font guidelines
The packaging of fonts has been completely changed, and is documented
at http://en.opensuse.org/openSUSE:Packaging_Fonts
3) Documenting changes in packages
The openSUSE review team is now also enforcing proper documenting
changes in packages:
First, the .changes entry (rpm changelog) surves two purposes:
- News for the user
- History tracking of packaging changes (often referenced in bugs to
verify if a user has the latest packaging bugfixes).
3.1) Information about updates
A simple "Update to version x.y.z" is, as before, not
accepted. There should be some buzz around the update for the user;
some major reasons to the upgrade should be listed.
Changes on the package itself should be mentioned in a way that any
other contributor to the same package can follow traces of why
something is the way it is. Commonly, Added (build)dependencies are
interesting to be seen, special hacks to make something work in a
particular way [..]: Always consider that package maintenance is a
distributed task and various contributors need to be able to step up
at will.
3.2) Documenting patch life cycle
The rules about patches are listed at
http://en.opensuse.org/openSUSE:Packaging_Patches_guidelines .
Most prominent is likely the mentioning of the patches life cycle,
which forces you to mention additions and removals of patches in the
changelog. As history shows, this can be helpful if a patch got
removed, and later a regression is reported; finding out when a
patch was removed can be crucial in reconstructing feature sets
(including contacting the contributor that dropped it.. which is
easily extracted from the .changes if listed)
The main appeal is to the devel project maintainers / reviewers, to
keep out for those rules, to live according to them, as it is
frustrating for everybody if a package needs to be declined by the
openSUSE Factory Review team:
- The dev prj maintainer is the one getting the 'decline' (as it was
usually a forwarded request), which often leaves the 'fixing' to
the devel project maintainers, where the 'originator' of the fix
would have been willing to actually do that...
Note: The review team is not enforcing the usage of patch markup
unless the package already follows this convention.
4) Teams involved, contact
I mentioned two teams previously, these are the openSUSE review team
(details at http://en.opensuse.org/openSUSE:OpenSUSE_review_team) and
the team taking care of the guidelines (details at
http://en.opensuse.org/openSUSE:Packaging_guidelines_change_process#Team_me…).
You
can reach both via the openSUSE-packaging mailing list.
On behalf of the teams,
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,HRB16746 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
--
To unsubscribe, e-mail: opensuse-announce+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-announce+help(a)opensuse.org
Hi,
With the release of ruby on Monday 5th of November the SUSE sponsored
maintenance of openSUSE 11.4 has ended.
openSUSE 11.4 is now officially discontinued and out of support by SUSE.
openSUSE 11.4 was the first openSUSE distribution maintained using
OpenBuildService methods (known as "OBS Maintenance"), allowing full
community participation. We also migrated it from the old internal
SUSE method to the OBS method on the fly during the lifetime without any
interruption.
openSUSE 11.4 now will be continued to be maintained by the Evergreen
community team. Their wikipage is on http://en.opensuse.org/Evergreen ,
please check it out for more information.
Here are some statistics:
openSUSE 11.4 was released on March 4th 2011, making it 20 months
of security and bugfix support. (2 openSUSE releases + 2 months)
Some statistics on the released patches (compared to 11.3):
Total updates: 723 (+142)
Security: 416 (+58)
Recommended: 306 (+85)
Optional: 1 (-1)
Quite some increase on updates, both security and bugfix wise.
Some of this is due to the 2 months increased lifetime compared to
openSUSE 11.3, some of this is due to a more open community bugfix
involvement.
CVE Entries: 1113 (-99)
Top issues (compared to 11.3 for issues down to 5)
10 seamonkey (-4)
10 MozillaFirefox (-2)
9 php5 (+4)
9 MozillaThunderbird (-2)
8 flash-player (-4)
6 wireshark (+1)
6 opera (-4)
6 java-1_6_0-openjdk (-1)
6 bind ( 0)
5 openssl (-2)
5 libpng14 (new)
5 icedtea-web (new)
And top issues sorted by CVE (Common Vulnerability Enumeration) count down to 10)
(comparison to 11.3 for some ... but due to the OBS maintenance migration some
CVEs are not easily accounted for)
139 MozillaThunderbird (+26)
139 MozillaFirefox (+28)
135 seamonkey (-3)
67 kernel (-61)
56 java-1_6_0-openjdk
44 flash-player (+38)
41 mozilla-nspr
30 mysql-community-server
29 php5
26 mozilla-kde4-integration
21 mariadb
21 freetype2
20 java-1_6_0-sun
18 wireshark
18 mozilla-xulrunner192
17 mysql-cluster
13 rubygem-actionpack-2_3
12 xen
11 rubygem-activerecord-2_3
10 rubygem-activesupport-2_3
10 puppet
10 libpng14
--
Open Linux Security Engineer Position at SUSE: http://bit.ly/Li4RbS