I see different teams announce their team meetings in different ways and
suggest to discuss how to do it the best way - and document it.
Here's one proposal for this:
== Announcing Team Meetings ==
* Create a meeting page in the wiki to collect the agenda
* Add the meeting to http://en.opensuse.org/Portal:Meetings
* Get the meeting in the calendar on news.o.o - this way the openSUSE
Weekly News Team will add it to their calendar
* Announce it via opensuse-announce(a)opensuse.org and
news.o.o. for the first meeting or for special meetings
* Announce it on your team mailing list
* Good practice: Announce a preliminary agenda with topics for the
meeting and not only that it will take place
Right now we have both the wiki calendar in the meetings portal and the
news.o.o calendar, I propose to remove the wiki calendar and point to
news.o.o.
Thoughts on this?
Btw. - I would add the result of our discussion to
http://en.opensuse.org/Portal:Meetings,
Andreas
--
Andreas Jaeger, Program Manager openSUSE, aj(a){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
Hi all,
The last week we again received over 100 comments on the first and second part
of our strategy. A few refinements came in on our description of our target
users, but most of the input was on the second part about what we offer. We
have again incorporated all the comments into the document and a new iteration
can be found on co-ment [1].
And now, the third piece of text has been added: What does openSUSE not do?
[1] Besides this, we added some 'background information' to the strategy,
including ideas on our competition, what openSUSE might gain and loose from
this strategy and how openSUSE should look like in 2 years from now.
Like with "Target Users" and "What does openSUSE offer it's users" we would
really appreciate it if you could give your input on co-ment but we will
accept any kind of input on any channel we can follow. So if co-ment isn't
your thing, feel free to comment below this post, on the forums or anywhere
else. For those new to co-ment [2] - it is a pretty awesome commenting tool
under the GNU Affero GPL [3].
Giving your input on co-ment will make the discussion a bit more structured
and easier for everyone to follow. How-to: select some text you want to
comment on (a word, a few words, a sentence) and choose the little yellow +
sign on the top-left of the page to add your comment. If you click a colored
section of the text, you can see the comments which have been made to that
section it and add your own voice to the discussion. Easy peasy!
For reference find the openSUSE Strategy portal on the wiki [4]. Have fun!
Greetings,
Your strategy team
[1] https://lite.co-ment.com/text/lNPCgzeGHdV/view/
[2] http://www.co-ment.com/about/
[3] http://www.fsf.org/licensing/licenses/agpl-3.0.html
[4] http://en.opensuse.org/Portal:Strategy
Hi all,
Over the last weeks there has been a lot of disussion, both internally and
externally, about the strategies which have been proposed. However, we also
missed a lot of voices from our community. We take responsibility for leaving
many of you behind by focusing on a very corporate-management solution to the
initial question which prompted this process. A question we think still is
relevant: The identity of openSUSE both as a Community and as a Project.
Initially our goal was to answer: “Who is openSUSE and what does it (want to)
do?” prompted by the discussion about the default desktop at the openSUSE
conference last year. In five years the openSUSE project has evolved from a
fully company-driven project to a communty project where everybody can
contribute. This has brought uncertainty and a lack of direction. The current
lack of a clear ‘story behind it all’ is hampering our ability to establish a
common identity and sense of security. From a marketing point of view, it
becomes an uphill battle…
Throughout the process, we consulted some people and the discussion about a
strategy started with the goal to solve this issue. However, many feel that
‘strategy’ and the approach to find one is not fitting our community. We lost
most of you in the second paragraph of the strategy pages on the wiki – too
much talk.
We would like to go back to the start and focus on describing who we are, as a
community, instead of finding new ways to go. The input you all have given us
by mail, forums, IRC and in person was valuable and we will use that. So that
is what we will do:
* Highlight the story behind openSUSE
* Identify what users we target and illustrate what we offer to them,
* Connect it with the issues that matter most to our community
And then we will document this story, image, direction, strategy – or however
your call it ;) .
From you all – we will continue to seek your input on it once we post it. By
mail, forum, IRC or in person – again. Without your help it won’t be much, so
please think about that!
Greetings,
Your strategy team
P.S. Also posted at http://news.opensuse.org/2010/09/03/strategy-sucks/
--
Andreas Jaeger, Program Manager openSUSE, aj(a){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
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
Folks,
SCALE (Southern California Linux Expo) Call for Papers is now open until
December 13, 2010. SCALE will be in Los Angeles February 25-27, 2011.
I would encourage anyone interested in giving talks about openSUSE to
submit their papers to this event. There's lots to talk about openSUSE,
so don't be shy!
Here's the link.
http://www.socallinuxexpo.org/scale9x/blog/scale-9x-call-papers
Also of interesting notice is that SCALE will offer tutorial sessions as
well. A suggestion for any OBS experts out there, perhaps we can
organize a tutorial session showing how to use OBS to package for
different distros, and not just openSUSE?
At some point in the coming months, we'll also see about setting up an
openSUSE booth and will welcome volunteers to support the booth.
Thanks,
Bryen M Yunashko
openSUSE Board Member
openSUSE Marketing Team lead
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
I just received this from US-CERT. Is there a kernel upgrade coming soon?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
US-CERT Current Activity
Linux Root Access Vulnerabilities
Original release date: October 25, 2010 at 10:31 am
Last revised: October 25, 2010 at 10:31 am
US-CERT is aware of public reports of multiple vulnerabilities
affecting Linux. Exploitation of these vulnerabilities may allow an
attacker to access the system with root or "superuser" privileges.
The first of these vulnerabilities is due to a flaw in the
implementation of the Reliable Datagram Sockets (RDS) protocol in
Linux kernel versions 2.6.30 through 2.6.36-rc8. By sending a
specially crafted socket function call, an attacker may be able to
write arbitrary values into kernel memory and escalate privileges to
root.
This vulnerability affects Linux installations where the CONFIG_RDS
kernel configuration option is set and where there are no restrictions
preventing unprivileged users from loading packet family modules.
Reports indicate that this may be the default configuration and that a
patch for this vulnerability has been committed to the Linux kernel.
Users should apply any updates for their Linux distributions to help
mitigate the risks. Additionally, reports indicate that preventing the
RDS kernel module from loading is an effective workaround. This can be
performed by executing the following command as root:
* echo "alias net-pf-21 off" > /etc/modprobe.d/disable-rds
The second vulnerability is due to a flaw in the library loader of the
GNU C library. Exploitation of this vulnerability may allow an
attacker to gain root privileges. Reports indicate that patches have
not yet been released to address this issue.
US-CERT will provide additional information as it becomes available.
====
This entry is available at
http://www.us-cert.gov/current/index.html#linux_root_access_vulnerabilities
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iQEVAwUBTMWqRT6pPKYJORa3AQKmjgf+NoghT77JMj+U5AmBYy6Hy8bd51NNVr6u
tVnIwCD3VgAgC2IIUpObKLGYLQZe2x1J27bz9pcOHUhxQhRDv8vbrISp+MufZgBE
UN9aMDWvNYWkCL16fbHa9A0UhVhIav6APR90MREXLwzsZyLgsMXCsCJ3DPJnB4jh
4ZGok3mkMA+CaWrgcX3Rypz4NXTYHrw+vDgECRzqSgklrmmh2U2VKtB/Cmu5dskV
lXbkD3grrK2jDa7pht944YJo8T3BzJdy/3n48XRBAU+Qy5H03GpGkIKl3kjmXhmO
XcgWvC9TtHleploWjH7u0PwamcCHuc737VQBmLDRCGamVGdSZjYuLg==
=PQ7V
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
Hi there!
Last week a discussion started on opensuse-marketing about creating an
openSUSE manual:
http://lists.opensuse.org/opensuse-marketing/2010-09/msg00259.html
While this is a cool idea, it turned out that many people are unaware of the
existing openSUSE documentation or do not know how to contribute. Being
responsible for the openSUSE documentation, I would like to shine a light on
this ;-) :
Table of contents (beware, lengthy posting):
1. Contributing
1.1 Getting in touch with the SUSE Documentation Team
1.2 Reporting Documentation Bugs or Suggesting Adjustments
1.3 Translating Manuals
1.4 Contributing new Chapters or Books
1.5 Contributing to the Build Environment (susedoc)
2. Outlook: What's in the Pipeline
2.1 Publishing the Book Sources
2.2 Re-writing the Build Environment
2.3 openSUSE BookBuilder
3. List of openSUSE Manuals
###################
# 1. Contributing #
###################
Currently the openSUSE documentation (listed below under 3.) is
maintained mostly within Novell by the SUSE Documentation Team
(http://en.opensuse.org/openSUSE:Documentation_team). The discussion on
opensuse-marketing has shown that people are interested in contributing to
this documentation--a fact that we really welcome!
Our manuals are written in NovDoc XML, a simplified subset of DocBook
(http://www.docbook.org/). The XML sources for the manuals are hosted on an SVN
server. Generating books from the XML sources is done with the susedoc build
environment, which is developed and maintained by the team as
well. This build environment includes _everything_ to build books from DocBook
or NovDoc and is shipped with openSUSE (package: susedoc, license: GPL).
You may also want to point us to ommissions, corrections,
or even to ready articles (wiki, txt, pdf, whatever) that could be
merged or referenced. Let us not get into a struggle about correct
or wrong tools. I really like the original idea of creating a commuity
driven openSUSE book.
We are already looking into ways how to interconnect wiki and/or
openoffice with docbook. Ideas welcome!
1.1 Getting in touch with the SUSE Documentation Team
-----------------------------------------------------
Reaching out to us is pretty easy - either subscribe to the opensuse-doc
mailinglist (http://en.opensuse.org/Mailing_lists#Subscribing) or join the
#opensuse-doc IRC channel on freenode.
If you have typos, questions, suggestions or simply want to say hello,
these are the places to go.
You can also meet us in person at the openSUSE conference in
Nuremberg this week. There will be a talk about one of our latest doc
projects, the openSUSE Book Builder (see 2.3 below or refer to
http://conference.opensuse.org/indico//contributionDisplay.py?contribId=71&…).
We would be glad to see you there!
1.2 Reporting Documentation Bugs or Suggesting Adjustments
----------------------------------------------------------
Currently, two feedback channels are available if you have corrections or
enhancements for us:
- File a bug report (or an enhancement request) against the
Documentation component for the respective product.
Or, much easier:
- Use the doc comment system:
Go to http://www.novell.com/documentation/opensuse113/ where the openSUSE 11.3
documentation is hosted. Click on a manual title and navigate to the page
where you have spotted an error/would like to suggest adjustments. Scroll to
the bottom of that page and click on "Add comment". Insert your comment. If
you are interested in getting feedback, provide your name and email address.
Your comment is directly routed to our team, so we can take care of it.
1.3 Translating Manuals
-----------------------
If you are interested in translating our manuals, we can provide the necessary
infrastructure for you. Currently the Russian translation team already uses
our SVN repository on berliOS to translate the openSUSE 11.3 manuals.
1.4 Contributing new Chapters or Books
--------------------------------------
If you would like to contribute larger amounts of contents (chapters,
sections, etc.), please get in touch with us (see above), and let us know what
you like to contribute. Don't worry, you _DON'T_ have to know XML, susedoc, or
the likes - that is something we can take care of ;-).
1.5 Contributing to the Build Environment (susedoc)
---------------------------------------------------
susedoc is publicly hosted at
https://developer.berlios.de/projects/opensuse-docmaker/ and can be checked
out anonymously. Patches are welcome! If you are interested in contributing
more than an occasional patch, you can get full access to the project.
######################################
# 2. Outlook: What's in the Pipeline #
######################################
The SUSE documentation has a few more projects in the pipeline. First and
foremost we are working on making it easier for you to contribute. Second we
have have planned two major software projects.
2.1 Publishing the Book Sources
-------------------------------
The XML sources for our manuals are hosted on a Novell internal SVN
server. We are currently in the process of moving them to a public SVN at
berliOS, where they will be available for anonymous checkout. Document
maintainers will get write access.
As a first step, the SUSE Studio documentation and the openSUSE Documentation
Style Guide are hosted at
https://developer.berlios.de/projects/opensuse-doc/
More is to come very soon.
We can also provide an infrastructure for manual translations on that server
- in fact our Russian translators already make use of it.
2.2 Re-writing the Build Environment
------------------------------------
Our build environment (susedoc) currently is a mixture of tools using make,
bash, python and perl. Although this tool collections works very well, we
would like to consolidate it in order to make future enhancements easier. We
have started to write a central docmaker library in perl and python which
should provide everything that is needed to manage, monitor and build books
from XML sources. Development of this library is in a very early state - if
you are interested in helping us to develop it, get in contact with us. The
sources are available from
http://svn.berlios.de/wsvn/opensuse-docmaker/trunk/lib/
2.3 openSUSE BookBuilder
------------------------
In short, the openSUSE BookBuilder is a library utilizing susedoc to
automatically build books from XML sources. Added is a web application that
serves as a virtual library. See
http://conference.opensuse.org/indico//contributionDisplay.py?contribId=71&…
for a more detailed description. If you are interested in that project, come
to the talk at the openSUSE conference or contact me directly.
###############################
# 3. List of openSUSE Manuals #
###############################
openSUSE comes with with a lot of manuals in HTML and PDF format with a current
page count of almost 2000 pages. Not all of them are shipped in the box.
The HTML version of all manuals can be installed with the package
opensuse-manuals_en.
http://en.opensuse.org/openSUSE:Documentation_team#List_of_Manualshttp://en.opensuse.org/SDB:Official_documentation
ePUB versions can be downloaded from
http://community.opensuse.org/ebooks/ebooks113/
3.1 Startup Guide
-----------------
Guides you through the installation and basic configuration of your
system. For newcomers, the manual also introduces basic Linux concepts such as
the file system, the user concept and access permissions and gives an overview
of the features openSUSE offers to support mobile computing. Provides
help and advice in troubleshooting.
The Startup Guide is ca. 200 pages and is found in the openSUSE box.
3.2 Reference Guide
-------------------
Gives you a general understanding of openSUSE and covers advanced system
administration tasks. It is intended mainly for system administrators and home
users with basic system administration knowledge. It provides detailed
information about advanced deployment scenarios, administration of your
system, the interaction of key system components and the set-up of various
network and file services openSUSE offers.
3.3 GNOME User Guide
--------------------
Introduces the GNOME desktop of openSUSE. It guides you through using and
configuring the desktop and helps you perform key tasks. It is intended mainly
for end users who want to make efficient use of GNOME desktop as their default
desktop.
3.4 GNOME Quick Start
---------------------
Gives a short introduction to the GNOME desktop and some key applications
running on it.
3.5 KDE User Guide
------------------
Introduces the KDE desktop of openSUSE. It guides you through using and
configuring the desktop and helps you perform key tasks. It is intended mainly
for users who want to make efficient use of KDE as their default desktop.
3.6 KDE Quick Start
-------------------
Gives a short introduction to the KDE desktop and some key applications
running on it.
3.7 Application Guide
---------------------
Learn how to use and configure key desktop applications on openSUSE. This
guide introduces browsers and e-mail clients as well as office applications
and collaboration tools. It also covers graphics and multimedia applications.
3.8 Security Guide
------------------
Introduces basic concepts of system security, covering both local and network
security aspects. Shows how to make use of the product inherent security
software like AppArmor (which lets you specify per program which files the
program may read, write, and execute) or the auditing system that reliably
collects information about any security-relevant events.
3.9 Installation Quick Start
----------------------------
Lists the system requirements and guides you step-by-step through the
installation of openSUSE from DVD.
3.10 AppArmor QUick Start
-------------------------
Helps you understand the main concepts behind AppArmor.
Thanks to Frank, Tanja, Tom for compiling this writeup,
(shame on me for messing it up).
cheers,
JW-
--
o \ Juergen Weigert paint it green! __/ _=======.=======_
<V> | jw(a)suse.de back to ascii! __/ _---|____________\/
\ | 0911 74053-508 __/ (____/ /\
(/) | _____________________________/ _/ \_ vim:set sw=2 wm=8
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg)
"You are trying to use packages from project 'openSUSE:11.3'.
Note that malicious packages can compromise your system."
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
Not entirely certain if this is the right list.
I'm a loyal user/fanboy of the Sonic.net <http://www.sonic.net> ISP here in
Northern California and I've recently found out they run a mirror for their
users of some major projects (debian, openbsd, freebsd, ubuntu, etc).
I've asked, and they're up for mirroring a subset of what's located on
download.opensuse.org so I had a couple of questions for the folks in charge of
openSUSE distrubution:
* Would mirroring of distribution/ and repositories/ be enough?
* The mirror is only accessible to Sonic.net subscribers, would it be
possible to update the MirrorBrain rules to direct Sonic.net IPs to their
internal mirror?
Cheers
- R. Tyler Croy
--------------------------------------
GitHub: http://github.com/rtyler
Twitter: http://twitter.com/agentdero
Hi all!
Friday the 1st of October will be the deadline for requesting travel and hotel sponsorship requests for the openSUSE conference. We will notify those who will receive support next week, some have already had mail about their hotel. Please note that the budget is limited and we like to help those who need it most!
Greetings,
The conference peeps
Dear owner of http://en.opensuse.org,
I would be interested in managing a link exchange campaign for your
company as an independant contractor.
As your "link marketing manager", I can manage your link exchange
campaign to insure that, over time, you will have a consistent reliable and
steady stream of qualified, interested and motivated prospects viewing your
web site. Web traffic is a numbers game, and the more web sites that link
to you, the more traffic you'll get on a referral basis.
Also, when other sites link to you, your Google ranking will improve.
I have many clients with #1-10 Google rankings for their most
competitive keywords as a result of my link exchange marketing efforts!
If you'd like more complete information, including my fees and
referrals, please email me back, or just call me at 561.339.6144. If email,
please include your name and phone number.
Sincerely,
Mike C.
PS ‚ We also create, market and maintain your facebook business page
with the initial goal of securing 5000 targeted facebook fans!
************************************************************************************
*** If you wish to be removed from our data base, respond with
"please remove" in the subject line.
Hello at all,
Some weeks ago made Lars Dieckow an wiki entry and proposed an meet up in a
restaurant for the participants of openSUSE Conference which arrive on
tuesday.
He proposed a chinese restaurant ( http://www.restaurant-sunrise.de/ ) and
reserved a table there. The restaurant is round 5km from conference hotel and
offer an all you can eat buffet with chinese food, sushi and mongolian grill.
I made a wiki page ( http://en.opensuse.org/openSUSE:Socializing ), so you can
make an entry there if you like to join that event. Plz make it so that we
know if we have to reserve another table.
br gnokii
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
