Poll for our Weekly News Translators

The last Poll was for our Readers. Now the next Poll is for our Translators.

As shown in http://en.opensuse.org/openSUSE:Weekly_news_contribute we have different possibilities for our Translators to create own Translations:

  • XML Source (You get the Sourcecode and you use it to create any other Format like Mediawiki)
  • XML with using QT Linguist r Lokalize (Then you use the english Stylesheets. You just translate the *.po Files and after translation it goes to the English XMLs and we create a native Issue for you)
  • Mediawiki: You want to have a Version in the en.o.o Wiki and translate it from there to any other Format like Mediawiki
  • HTML/news.opensuse.org: You use the HTML File to translate
  • XML/Docbook: You want to have a own Space with own Stylesheets and want to publish into HTML or PDF.

The poll is placed there: https://connect.opensuse.org/pg/polls/read/saigkill/11690/what-is-your-prefered-input-format

Please vote and help clarifying…

openSUSE Weekly News, Issue 160 is out

We are pleased to announce: Issue 160 of openSUSE Weekly News is out!

For a list of available translations see this page: http://en.opensuse.org/openSUSE:Weekly_news_translations

Get it:
[0] http://news.opensuse.org/?p=6387 (in HTML/ Bento Theme)


How to set up my Blog to the Creative Commons License

Today we had discussed on the opensuse-project List about Copyright and Licenses. So i try to clear this a little bit.


Wikipedia says: "Copyright is a set of exclusive rights granted by the law of a jurisdiction to the author or creator of an original work, including the right to copy, distribute and adapt the work. Exceptions and limitations to these rights strive to balance the public interest in the wide distribution of the material produced and to encourage creativity. Exceptions include fair dealing and fair use, and such use does not require the permission of the copyright owner. All other uses require permission and copyright owners can license or permanently transfer or assign their exclusive rights to others."

So we see: Every author or creator of any Document (like a Blog) is automaticly the Copyright Holder. The Copyright Holder can give special permissions for others who using their work.

Free Licenses

Well known free Licenses are the Creative Commons or the GFDL. The GNU General Public License, originally written by Richard Stallman, was the first copyleft license to see extensive use, and continues to dominate the licensing of copylefted software. Creative Commons, a non-profit organization founded by Lawrence Lessig, provides a similar license called ShareAlike.

The Copyright Holder can set one of these licenses to his work. In case of CC-BY-SA all other ppl have now the permission to redistribute the stuff. A little Document in Wikipedia explains the difference between CC and GFDL.


For CC there is a great Site who gives an little HowTo for integrating the CC into a Blog.

For GFDL is there a little HowTo.

New/Updated Applications

The last days i’ve updated or added new Packages.

Have a lot of fun with it 🙂

openSUSE Weekly News Poll

Hey you’re reading the openSUSE Weekly News? Then you’re the right person who fill up this poll:

The more who are polling the better is it 🙂

Auf zu neuen Ufern

Habe gestern den Artikel geschrieben:


HowTo contributing the openSUSE Weekly News

Today i prepared a little HowTo for contributing the openSUSE Weekly News.


If you have written an Blogpost, Article or you have found any interesting Stuff you can post this to:

  • news@opensuse.org

Facebook Fanpage

You can also post on our Facebook Fanpage. That postings are going to the next available Weekly News Issue.


If you just would like to provied an short Link, you can send a direct twitterpost to @saigkill.

Regular Articles

You also can post regular Articles in different sizes. We have Larry Finger, who provides every week some lines about the Testing team. Also we have Rares Aioanei who provides the Weekly Kernel Review.

In normal cases we trying to publish the Contributions with the Realname and without any cut.

Editorial Office

The Editorial Office collects every day interesting Stuff for the Weekly News. Satoru Matsumoto, is our Proofreader and he collects for all Subcategories inside the Weekly News.

All Stuff from the Weekly News are inside the SVN from BerliOS.

How can i be a part of the Editorial Office

1.) Please go to http://developer.berlios.de/account/register.php and register yourself as Developer on BerliOS.
2.) Write to saigkill@opensuse.org and tell him your choosed Nickname in BerliOS.
3.) Sascha adds you as Developer to http://developer.berlios.de/projects/osweeklynews/.
4.) Checkout the Repository with:

svn checkout  https://YOURdevelopername@svn.berlios.de/svnroot/repos/osweeklynews/trunk osweeklynews
  • You can checkout the svn on every place. In my case i have a Folder „svn“ and put all SVNs inside that Folder.

5.) Please read the README and the Docs inside docs/.
6.) Choose your Subsection what you like to contribute.
7.) All needed Files are under trunk/en/xml.
8.) Have Fun

Translating into other Languages

The easiest way (You don’t know XML)

The easiest way is, that we send you after the official en issue, some *.po files. Then you just have to start lokalize or other translating tool, and just start to translate. If you open a *.po File you have the english part on the top of the window, and you just can insert your translation on the bottom of the window. After translating all *.po files, you send it back to saigkill@opensuse.org. Sascha puts the content from the *.po files back to the original english issue. Then you can use the same style like the en issue and make your own issue with a script. You can export now to HTML and PDF.

The hard way (You know XML)

The hard way is, that you can get your own place in the SVN from BerliOS. There we place our stylesheets and all needed content. Every Section (Announcements, In the Community, …) are in a seperate XML file. You just have to fill the XMLs with your localized content. After finishing you can export it to HTML or PDF with a script.