https://en.opensuse.org/api.php?action=feedcontributions&user=Pbleser&feedformat=atomopenSUSE Wiki - User contributions [en]2024-03-28T22:03:45ZUser contributionsMediaWiki 1.37.6https://en.opensuse.org/index.php?title=Archive:Hermes_hacking&diff=51324Archive:Hermes hacking2012-05-05T08:17:18Z<p>Pbleser: /* Setup a User */ use exit instead of ^C, fix formatting for last line, it's the shell prompt, not the script/console prompt</p>
<hr />
<div>{{Hermes_navbar}}<br />
__NOTOC__<br />
{{Special info|This page gives some hints on how to start to hack on Hermes. <br />
<br />
If you need further assistance (and you probably will ;-) do not hesitate to ask in IRC on freenode in the boosters channel #opensuse-boosters.<br />
<br />
Probably there are more things useful to know when starting to hack on Hermes.<br />
If you found them, please add them to this page or let me know...}}<br />
<br />
== How to start ==<br />
<br />
Hermes can be hacked on in the git checkout. To checkout the source code run <br />
<br />
git clone https://github.com/openSUSE/hermes.git<br />
<br />
To work with [[openSUSE:Hermes_Subsystems#Herminator|Herminator]], be sure to have set up an http server such as Apache or lighttpd to serve the perl scripts. <br />
<br />
To work on [[openSUSE:Hermes_Subsystems#Starship|Starship]], you need a Ruby on Rails environment. We use the 'official' Ruby for the [https://build.opensuse.org/project/show?project=openSUSE%3ATools openSUSE tools] from the openSUSE Tools [http://download.opensuse.org/repositories/openSUSE:/Tools/ Repository].<br />
<br />
The perl-DBD-mysql package is also needed.<br />
<br />
== Create the Database ==<br />
<br />
To create the database for Hermes, the ruby on rails migration is used, as it is the most powerful mechanism for that. Even if you only want to play with the non ruby parts of Hermes, you need to create the database with starship.<br />
<br />
First, create an empty database in mysql, ie. called hermes, eg. like this as root:<br />
mysql -e "create database hermes character set 'utf8'; grant all on hermes.* to hermes@localhost identified by 'hermes'; flush privileges;"<br />
<br />
Change into the subdirectory "starship":<br />
cd starship<br />
<br />
Check config/database.yml and setup the correct user, host and database name there for your environment (if you want to run hermes in production, configure the "production" environment); note that on some systems, you also have to change the path to the MySQL socket file to /var/run/mysql/mysql.sock instead of /var/lib/mysql/mysql.sock<br />
<br />
You can control which environment (and hence settings) to use [http://guides.rubyonrails.org/configuring.html#rails-environment-settings|through the environment variable RAILS_ENV], eg.:<br />
export RAILS_ENV=development<br />
<br />
For a production system, use<br />
export RAILS_ENV=production<br />
<br />
To actually create and set up all tables, call <br />
rake db:migrate<br />
in the starship directory. That's it. <br />
<br />
== Authentication in Starship ==<br />
<br />
Hermes currently knows three kinds of authentication: <br />
* simulate, ie. the user is hardcoded<br />
* ichain, Novell iChain authentication is used<br />
* basic authentication with a browser window<br />
<br />
To pick the authentication code, set environment variables in starship/config/environments/, for example in development.rb for the development mode:<br />
<br />
# Authentication:<br />
# Starship can either authenticate against Novell iChain or use basic<br />
# auth, which can be be configured with various sources through the<br />
# webserver<br />
# Parameter: AUTHENTICATION<br />
# set this parameter to either<br />
# :simulate => means the user is hardcoded to termite<br />
# :ichain => iChain is used.<br />
# :off => basic auth<br />
AUTHENTICATION = :off<br />
<br />
<br />
== Setup a User ==<br />
<br />
As you need a user at least in [[openSUSE:Hermes_Subsystems#Starship|Starship]], here is how you create it. The easiest way is to use the ruby console in Starship the following way:<br />
<br />
freitag@trixa:~/suse/git/hermes/starship> script/console <br />
Loading development environment (Rails 2.3.8)<br />
Loaded gui abstraction from .../abstraction.xml<br />
Loaded starship config from config/starship.yml<br />
>> p = Person.new<br />
=> #<Person id: nil, email: nil, name: nil, jid: nil, stringid: nil, admin: false, hashed_password: nil, salt: nil><br />
>> p.email='hacker@opensuse.org'<br />
=> "hacker@opensuse.org"<br />
>> p.name='Heino Hack'<br />
=> "Heino Hack"<br />
>> p.stringid='heino'<br />
=> "heino"<br />
>> p.salt = Person.random_string(10)<br />
=> "gMbLgpLPXg"<br />
>> p.hashed_password = Person.encrypt('secret', p.salt)<br />
=> "e81e3d8242e87979756bd94fc8ff8273b9ab11bb"<br />
>> p.save<br />
=> true<br />
>> exit<br />
freitag@trixa:~/suse/git/hermes/starship><br />
<br />
==Creating a Configuration File==<br />
<br />
Hermes needs a global configuration file placed at <br />
/etc/hermes.conf<br />
<br />
To create it, copy the template in conf/hermes.conf.in to /etc and adjust it to your settings. The config file must be valid perl code and can be checked with the perl interpreter for syntax:<br />
<br />
kf@subbotin:~/hermes> perl -c /etc/hermes.conf<br />
/etc/hermes.conf syntax OK<br />
<br />
Some important settings:<br />
<br />
* '''%LOG''': it's recommended to set the ''logpath'' entry for logging, which results in logfiles for the various Hermes processes in the path.<br />
* '''$DB{'default'}''': Specify the database settings you want to use here.<br />
* '''$HerminatorDir''': The base path of the Herminator, where currently the notification plugins are read from<br />
* '''$OBSAPIBase''': The API of the openSUSE Build Service to use (if needed).<br />
<br />
Change others as needed.<br />
<br />
==Creating Notification Types ==<br />
<br />
After the installation, the list of available notification types is empty. They get created with their first use automatically, so there is no need to create them explicitly. Use the command line tool notifyHermes.pl from the top level directory of the Hermes checkout to create notifications, for example using:<br />
<br />
notifyHermes -o 'bla=foo, bar=baz' CheckHermes<br />
<br />
Call notifyHermes.pl -h to get help.<br />
<br />
[[Category:Hermes]]</div>Pbleserhttps://en.opensuse.org/index.php?title=Archive:Hermes_hacking&diff=51323Archive:Hermes hacking2012-05-05T08:12:13Z<p>Pbleser: add a few more details to the database setup routine</p>
<hr />
<div>{{Hermes_navbar}}<br />
__NOTOC__<br />
{{Special info|This page gives some hints on how to start to hack on Hermes. <br />
<br />
If you need further assistance (and you probably will ;-) do not hesitate to ask in IRC on freenode in the boosters channel #opensuse-boosters.<br />
<br />
Probably there are more things useful to know when starting to hack on Hermes.<br />
If you found them, please add them to this page or let me know...}}<br />
<br />
== How to start ==<br />
<br />
Hermes can be hacked on in the git checkout. To checkout the source code run <br />
<br />
git clone https://github.com/openSUSE/hermes.git<br />
<br />
To work with [[openSUSE:Hermes_Subsystems#Herminator|Herminator]], be sure to have set up an http server such as Apache or lighttpd to serve the perl scripts. <br />
<br />
To work on [[openSUSE:Hermes_Subsystems#Starship|Starship]], you need a Ruby on Rails environment. We use the 'official' Ruby for the [https://build.opensuse.org/project/show?project=openSUSE%3ATools openSUSE tools] from the openSUSE Tools [http://download.opensuse.org/repositories/openSUSE:/Tools/ Repository].<br />
<br />
The perl-DBD-mysql package is also needed.<br />
<br />
== Create the Database ==<br />
<br />
To create the database for Hermes, the ruby on rails migration is used, as it is the most powerful mechanism for that. Even if you only want to play with the non ruby parts of Hermes, you need to create the database with starship.<br />
<br />
First, create an empty database in mysql, ie. called hermes, eg. like this as root:<br />
mysql -e "create database hermes character set 'utf8'; grant all on hermes.* to hermes@localhost identified by 'hermes'; flush privileges;"<br />
<br />
Change into the subdirectory "starship":<br />
cd starship<br />
<br />
Check config/database.yml and setup the correct user, host and database name there for your environment (if you want to run hermes in production, configure the "production" environment); note that on some systems, you also have to change the path to the MySQL socket file to /var/run/mysql/mysql.sock instead of /var/lib/mysql/mysql.sock<br />
<br />
You can control which environment (and hence settings) to use [http://guides.rubyonrails.org/configuring.html#rails-environment-settings|through the environment variable RAILS_ENV], eg.:<br />
export RAILS_ENV=development<br />
<br />
For a production system, use<br />
export RAILS_ENV=production<br />
<br />
To actually create and set up all tables, call <br />
rake db:migrate<br />
in the starship directory. That's it. <br />
<br />
== Authentication in Starship ==<br />
<br />
Hermes currently knows three kinds of authentication: <br />
* simulate, ie. the user is hardcoded<br />
* ichain, Novell iChain authentication is used<br />
* basic authentication with a browser window<br />
<br />
To pick the authentication code, set environment variables in starship/config/environments/, for example in development.rb for the development mode:<br />
<br />
# Authentication:<br />
# Starship can either authenticate against Novell iChain or use basic<br />
# auth, which can be be configured with various sources through the<br />
# webserver<br />
# Parameter: AUTHENTICATION<br />
# set this parameter to either<br />
# :simulate => means the user is hardcoded to termite<br />
# :ichain => iChain is used.<br />
# :off => basic auth<br />
AUTHENTICATION = :off<br />
<br />
<br />
== Setup a User ==<br />
<br />
As you need a user at least in [[openSUSE:Hermes_Subsystems#Starship|Starship]], here is how you create it. The easiest way is to use the ruby console in Starship the following way:<br />
<br />
freitag@trixa:~/suse/git/hermes/starship> script/console <br />
Loading development environment (Rails 2.3.8)<br />
Loaded gui abstraction from .../abstraction.xml<br />
Loaded starship config from config/starship.yml<br />
>> p = Person.new<br />
=> #<Person id: nil, email: nil, name: nil, jid: nil, stringid: nil, admin: false, hashed_password: nil, salt: nil><br />
>> p.email='hacker@opensuse.org'<br />
=> "hacker@opensuse.org"<br />
>> p.name='Heino Hack'<br />
=> "Heino Hack"<br />
>> p.stringid='heino'<br />
=> "heino"<br />
>> p.salt = Person.random_string(10)<br />
=> "gMbLgpLPXg"<br />
>> p.hashed_password = Person.encrypt('secret', p.salt)<br />
=> "e81e3d8242e87979756bd94fc8ff8273b9ab11bb"<br />
>> p.save<br />
=> true<br />
>> ^C<br />
>> freitag@trixa:~/suse/git/hermes/starship><br />
<br />
==Creating a Configuration File==<br />
<br />
Hermes needs a global configuration file placed at <br />
/etc/hermes.conf<br />
<br />
To create it, copy the template in conf/hermes.conf.in to /etc and adjust it to your settings. The config file must be valid perl code and can be checked with the perl interpreter for syntax:<br />
<br />
kf@subbotin:~/hermes> perl -c /etc/hermes.conf<br />
/etc/hermes.conf syntax OK<br />
<br />
Some important settings:<br />
<br />
* '''%LOG''': it's recommended to set the ''logpath'' entry for logging, which results in logfiles for the various Hermes processes in the path.<br />
* '''$DB{'default'}''': Specify the database settings you want to use here.<br />
* '''$HerminatorDir''': The base path of the Herminator, where currently the notification plugins are read from<br />
* '''$OBSAPIBase''': The API of the openSUSE Build Service to use (if needed).<br />
<br />
Change others as needed.<br />
<br />
==Creating Notification Types ==<br />
<br />
After the installation, the list of available notification types is empty. They get created with their first use automatically, so there is no need to create them explicitly. Use the command line tool notifyHermes.pl from the top level directory of the Hermes checkout to create notifications, for example using:<br />
<br />
notifyHermes -o 'bla=foo, bar=baz' CheckHermes<br />
<br />
Call notifyHermes.pl -h to get help.<br />
<br />
[[Category:Hermes]]</div>Pbleserhttps://en.opensuse.org/index.php?title=openSUSE:Dreamopensuse&diff=49891openSUSE:Dreamopensuse2012-03-04T12:37:58Z<p>Pbleser: add yaloki's desktop</p>
<hr />
<div>{{Artwork navbar}}<br />
<br />
{|<br />
|-<br />
|style="vertical-align:top"|<br />
<br />
[[File:Workspace 1 001.png|thumb|center|upright=3.0]]<br />
{{Intro|<p>The openSUSE Artwork Team is pleased to announce the Dream openSUSE submission page. It is a place where you can submit your designs of your choice desktop customised to your needs. We all have a way to tweak and change our desktops, whether it be KDE, Gnome, or any others. We would like you to submit a screenshot of this desktop here and show us what your desktop customisations are.<br />
<br />
All of this in preparations for future releases of openSUSE. Maybe many of the changes that you make on your own desktop can be beneficial to many other users who are trying to understand and use openSUSE but would like to have settings that fit them better. Please join us in this effort to understand the way you interact with your computer desktop.</p>}}<br />
<br />
<br />
----<br />
<br />
<gallery caption="openSUSE Dreams" widths="640px" heights="480px"><br />
File:Notification.png|Notification Idea by Anditosan. <br />'''Tag for your page:'''<br /><tt><img src=http://en.opensuse.org/File:Notification.png></tt><br />
<br />
<br />
</gallery><br />
<br />
<gallery caption="" widths="640px" heights="480px"><br />
File:http://www.thelinuxgeek.com/sites/default/files/articles/opensuse_12.1.png|http://www.thelinuxgeek.com/sites/default/files/articles/opensuse_12.1.png <br />'''LCARS'''<br />Everything is functional using conky. The background changes every 2 hours to another random LCARS screen.<br />
</gallery><br />
<br />
<gallery caption="" widths="640px" heights="480px"><br />
File:nmarques_desktop.png|<b>nmarques -- openSUSE 12.1 - GNOME:Cinnamon</b><br />
</gallery><br />
<br />
<gallery caption="" widths="640px" heights="480px"><br />
File:Hudson_Desktop.png|John Hudson's Desktop <br />'''KDE for a regular user:'''<br /><tt><img src=http://en.opensuse.org/File:Hudson_Desktop.png></tt><br />
</gallery><br />
<br />
<gallery caption="" widths="640px" heights="480px"><br />
File:jdd_desktop.jpg|File:jdd_desktop.jpg <br />'''8 desktops''' I use 8 desktops for my regular work, and group my icons on the left of the taskbar. For some historical reasons, I have some of the icons on the background and others on the taskbar. I have many installs on many computer and often do services on other people computers, so try to keep things as near as possible from defaults - jdd<br /><br />
</gallery><br />
<br />
<gallery caption="" widths="640px" heights="480px"><br />
File:pablo_desktop.png|'''Pablo Sanchez's Desktop'''<p>One can readily see my minimalist approach. I am a bit finicky with fonts so I use ''Tahoma'' for proportional and ''SGI Screen'' for non-proportional font needs. <br /><br /> I find I'm more efficient to be able to left-click on my background and invoke the KDE ''Application Launcher''. I've configured the first menu item to include my most commonly used applications. <br /><br >As others, I find eight Virtual Desktops as the ideal number of desktops to support my needs. Each Virtual Desktop is dedicated to one context. If interrupted, I go to a new Desktop, perform the effort and when done, remove all windows.</p><br />
</gallery><br />
<br />
<gallery caption="" widths="640px" heights="480px"><br />
File:Mfoxdogg_desktop.png|'''Michael (mfoxdog) Fox's Desktop''' <br /> I basically use the standard KDE settings except move the panel to the leftside as i have 2 monitors (not shown in the image) and it's far easier and quicker to scan a short vertical bar than a long spanding bar, after all that's how we read a menu. <br /> The mouse action for LMB to open the application menu for quick access to those who hide or remove the panel then they use my machine. The widgets i am using are the hardware monitors and a ball to play with when waiting for the computer to finish a task. <br /> I also use the Slimglow Plasma theme for its minimalistic style but solid appearance to make icons and buttons easily readable.<br />
</gallery><br />
<br />
<gallery caption="" widths="640px" heights="400px"><br />
File:Dreamopensuse_screenshot1_gumb.png|<br />'''Separate taskbar and launcher panels''' by gumb<br />My current default KDE 4.6 desktop on openSUSE 11.4...<br /><br />* On a 13 inch laptop with 1280x800 resolution, maximum vertical space wanted but task manager not practical at the sides, and I need space for when there are many entries for running programs. Twin rows of running apps looks ugly unless there's a minimum panel height. So, my default panel at the bottom is stripped to just the menu launcher and systray, freeing up horizontal space.<br />* Launchers and the rest (i.e. things that don't need to be visible all the time) are separated into an auto-hidden fly-out panel on the left. Tried it at the top but clashes with title bar and menu text visible underneath, and at the right it's too prone to unhiding when scrolling. Obviously the opposite would be true in a RTL environment. Shame the launcher icons at the top can't have a twin-column layout - maybe a later KDE version implements that.<br />* The Kate session launcher plasmoid is nifty when given enough space to expand in a panel, therefore allowing single-click access to common sessions. Also visible is the Activity switcher.<br />* This default activity is clean. Others have customized Folderview plasmoids relevant to the activity, whilst all other widgets (calculator, translator etc.) are housed on a separate activity.<br /><br />I run most apps full-screen so desktop-based widgets and icons aren't too helpful to me. However, I'm prone to completely changing the setup every year or so as new innovations like KDE Activites mature and I find new ways of arranging / organizing things.<br /><br />
</gallery><br />
<br />
<gallery caption="" widths="640px" heights="380px"><br />
File:IlmehtarDesktop.png|Richard Brown<br />'''GNOME untouched'''<br />I use a standard GNOME 12.1 desktop, with the only modifications from default currently being the use of a draft 12.2 wallpaper. Also shown is 'Guake', my terminal of choice which is called by my F12 key<br /><br />
</gallery><br />
<br />
<gallery caption="" widths="640px" heights="380px"><br />
File:Pantallazo10.png|Victorhck <br />'''KDE b/w (by the moment ;) ''' Simply desktop. Only wallpaper and a pair of superkaramba widgets. The font i use is Cholla Wide, it looks like fifth leg, is similar to that used in the openSUSE logo, isn't it? For command line i use Yakuake. And in the taskbar only icons. <br /><br />
</gallery><br />
<br />
<gallery caption="" widths="640px" heights="380px"><br />
File:Luriv-DesktopPCKDE4.png|'''luriv'''<br />KDE Desktop at the moment from PC.<br />
</gallery><br />
<br />
<gallery caption="" widths="640px" heights="400px"><br />
File:Dreamopensuse_screenshot_LAS3_gumb.png|<br />'''Linux Action Show KDE Activity''' by gumb<br />This is a special desktop set up for fans of the Linux Action Show. The LAS team featured this DreamopenSUSE initiative in their news section during their 195th episode, released on 5th February 2012. They requested any viewers uploading their images to this DreamopenSUSE wiki incorporate one of their videos playing on the desktop. I have gone a step further, er... okay, several steps too far, and created an entire themed KDE activity. But if it's publicity they're seeking, they should know: there's no fame without shame...<br /><br />This desktop features:<br /><br />* The KDE Activity bar along the bottom acting - to the delight I'm sure of Jupiter Broadcasting, as a 'lower third', even though everybody else on planet Earth but Chris knows that in fact it's more like a quarter. The 'LAS' activity has its own icon.<br />* A desktop folder widget provides previews and quick access to all Jupiter Broadcasting downloads.<br />* The analogue clock plasmoid displays the current time on the west coast of the USA, where the Linux Action Show is recorded, ensuring worldwide fans don't miss a live broadcast.<br />* Visible in VLC Media Player is an extract from an imaginary dream episode of the Linux Action Show, in which Bryan and Chris finally get their ''femme de fantasme'' Danica Patrick into the studio. Bryan tries his hand at being the daddy (rather too literally), much to Chris's consternation.<br />* Inspired by scorpions, a picture frame plasmoid features Bryan in bed with Fedora's sausage. Now that really would be a beefy miracle!<br /><br />
</gallery><br />
<br />
<gallery caption="" widths="640px" heights="400px"><br />
File:Charly_ey_DesktopGeneralPurpose.png|KDE General Purpose Desktop</gallery><br />
<br />'''KDE 4.7 General Purpose Use'''<br />
<br /><br />
My basic desktop uses only standard elements, however, some details enhance useability a lot in my opinion: The taskbar is on the left, simply for the reason that with modern widescreen displays it is much more "expensive" to waste screen height for the taskbar than to use some of the abundant width you have. <br /><br />
Logout/Shutdown buttons separate from the main menu/program launcher are a must in my opinion. As a separate program launch button on the taskbar for a general purpose desktop I personally only want a file manager, everything else I need often, can be in the favorites of the main menu, e.g. browser, mail client, terminal, system settings etc. <br /><br />
Quite some info is provided by widgets on the desktop, only I would prefer a different way to make them visible when they are covered by lots of windows: I would like to have a control/shortcut to show them on top of the windows with the windows slightly greyed out instead of hiding all windows and showing just the desktop. This would be less interruption, if you just want a quick info in the middle of your work, I think. <br /><br />
I recently started to use KDE Activities, however they do not quite behave as I would wish. I would prefer it, if you had one (or more) base activities which always run. Once you start another activity, it really means starting it: opening the applications you have defined (or restoring the state when you ended it last time) in a defined layout. And when you are done you should be able to "end" the activity, meaning, that all the applications are terminated and nothing of that activity costs any performance any more. Some other details will be explained with my other following screenshot describing my development activity. <br />
<br />
<br />
<gallery caption="" widths="640px" heights="400px"><br />
File:Charly_ey_DesktopDevelopmentActivity.png|KDE Development Activity<br />
</gallery><br />
<br />'''KDE 4.7 Development Activity'''<br /><br />
This screenshot shows my activity layout for development. Since the main taskbar cannot change according to different activities (that might be good), I have a separate launcher bar for the tools I need regularly while developing. Only the widget I found for that does not support slide in from the edge, which I would prefer. This way the tools would be well accessible even when the whole screen is covered by an IDE for example. The same would apply to the activity changer widget. I would be way more useful, if there was a slide in functionality. <br /><br />
To summarise, I personally think that it would improve usability in some places, if helpful information and controls could be shown on top of windows instead of hiding the windows. And it would be helpful, if the new conditions of widescreen displays were better taken into account.<br /><br />
<br /><br />
'''Edit by gumb -''' Note to above poster:<br /><br />
I think the Show Widget Dashboard plasmoid (or whatever name it goes under on your version of KDE - used to be Show Plasma Dashboard) provides what you need for displaying the widgets superimposed above your windows. You can add it to your panel just the same as the Show Desktop icon, but unlike that it does not minimize everything.<br />
----<br />
<gallery caption="" widths="640px" heights="400px">File:GNOME-in-VBox-1.png|If I would be using Gnome then this is what I need. </gallery><br />
This is my Gnome dream layout. Yes is very much like pre-Unity Ubuntu, which was what I was trying to achieve, and on my surprise openSUSE had that. Not as default, but easy to find. Of course that is pre-Gnome3 openSUSE, so up to the openSUSE 11.4 you can have that. <br />
Rajko m 20:32, 27 February 2012 (MST)<br />
<br />
<gallery caption="" widths="640px" heights="400px">File:KDE-custom-1.png|And this is one of many similar incarnations of KDE</gallery><br />
I often have multiple panels with easy to access icons and application launchers. Currently I don't use extra panel, as I don't use Konqueror very often, but once when it had the most sophisticated editor for input boxes used on wiki, it was always present. With Kate (editor) launcher that I still use, it asked for more room then it was possible to provide with one panel.<br />
Rajko m 20:32, 27 February 2012 (MST)<br />
<br />
<gallery caption="" widths="640px" heights="400px"><br />
File:Dreamopensuse_mxttie_Susedesktop2.png</gallery><br />
'''mxttie's desktop''' Opensuse 11.4 - KDE 4.6<br /><br />
* I always keep some space besides the panels to be able to quickly switch desktops by scrolling on it with the mouse.<br /><br />
* left screen has slideshow wallpaper<br />
* above the disk usage widget I have the timer widget, mostly used when cooking<br />
* on the left of the disk usage widget I have a widget I created to monitor bandwidth usage (uses ISP web service)<br />
* I use a maximum of 2 virtual desktops which switch using the cube effect.<br />
* Panel only shows apps on the current virtual desktop and screen.<br />
* I move windows to another desktop by scrolling on the title bar.<br />
<br />
<gallery caption="" widths="640px" heights="400px">File:Dreamopensuse_yaloki_desktop_razorqt_20120304.jpg</gallery><br />
'''yaloki's desktop''' openSUSE 12.1 - razor-qt 0.4.0 with openbox 3.5.0<br /><br />
* after using KDE3 and KDE4 for many years (and Window Maker for many years before that), disappointed by KDE4 and not really needing any of its features, hence went with something simple, stable that fits my needs: openbox (currently with razor-qt for the taskbar and panel, but going to remove that too and replace it with tint2 or fbpanel)<br />
* essentially just need a few windows (firefox, mixxx, eclipse, sonata, ...) and lots of terminals, all multiplexed into one screen session (screen running in rxvt-unicode)<br />
* systray has some artifacts on the screenshot due to current transparency rendering glitches in razor-qt's panel<br />
* wallpaper is not smooth in the middle, but that is irrelevant for me as I have two screens (which doesn't show on the screenshot ;))<br />
* mutt for email, in screen, but thunderbird works too; irssi for IRC; vim/gvim for most editing/development (but eclipse for larger projects), mpd for music, with sonata as a frontend as well as keyboard shortcuts using mpc, configured in openbox<br />
* four virtual desktops, but only really using one<br />
* dual-screen through nVidia twinview<br />
* no desktop icons (although razor-qt can do that) and the wallpaper doesn't matter much as almost all the space is always taken by e.g. firefox, rxvt-unicode with screen, etc... -- if you see your wallpaper, you're not busy enough :)<br />
* no compositing, XGL or any other frills: result is a very stable, very fast desktop that can be tuned a lot and easily configured to use with keyboard shortcuts<br />
<br />
----<br />
Please review the [[Terms of site|Legal notice]] about uploading content to this wiki. <br />
Also, be sure to consider licensing your image under the Creative Commons License. [http://creativecommons.org/ creativecommons.org]<br />
<br />
[[Category:Artwork]]</div>Pbleserhttps://en.opensuse.org/index.php?title=File:Dreamopensuse_yaloki_desktop_razorqt_20120304.jpg&diff=49890File:Dreamopensuse yaloki desktop razorqt 20120304.jpg2012-03-04T12:26:36Z<p>Pbleser: Pascal Bleser's desktop (razor-qt with openbox) as of 2012-03-04.</p>
<hr />
<div>Pascal Bleser's desktop (razor-qt with openbox) as of 2012-03-04.</div>Pbleserhttps://en.opensuse.org/index.php?title=Archive:Board_2011&diff=48065Archive:Board 20112012-01-12T12:50:39Z<p>Pbleser: Undo revision 48056 by Izabelvalverde (talk)</p>
<hr />
<div>{{Board navbar}}<br />
{{Intro|The openSUSE board was setup to lead the overall project. The main tasks for members of the board are: <br />
* Act as a central point of contact<br />
* Help resolve conflicts<br />
* Communicate community interests to Novell<br />
* Facilitate communication with all areas of the community<br />
* Facilitate decision making processes where needed.}}<br />
<br />
The board should provide [[openSUSE:Guiding principles|guidance]] and support existing governance structures, but shouldn't direct or control development, since community mechanisms exist to accomplish the goals of the project. The board should document decisions and policies.<br />
<br />
The board members are elected by the community and the chair person is appointed by Novell. The current chosen members are as follows:<br />
<br />
== Members ==<br />
<br />
{|<br />
|-<br />
| [[Image:AlanClark-Image.jpg|115px|link=]]<br />
| '''Alan Clark (Chair)''' With over 20 years of experience as a Software Engineer, a principal portion of Alan's career has been devoted to the research and development of operating systems and distributed multi-platform server services. His experience is with file systems, Directory Services, LDAP Services, Object Databases, Security, Developer Interfaces, Web Services, Network Protocols. Alan is a member of Novell's Open Platform Systems Senior Staff. Alan participates in several Industry forum Board of Directors, steering committees, technical committees and work groups, including serving as a Director for the Linux Foundation Board.<br />
<br />
|-<br />
| [[Image:Rhorstkoetter-image.png|115px|link=]]<br />
| [http://news.opensuse.org/2008/06/14/people-of-opensuse-rupert-horstkotter '''Rupert Horstkötter'''] lives in Darmstadt, Germany and is studying Business Administration and Electrical Engineering at Darmstadt University of Technology. He has been involved with the openSUSE Project for several years and was employed twice at Novell. In 2007/2008 as an Intern in Product Management and in 2008/2009 as a Workstudent for Community Architecture. He served as the Project Manager of the Forums Merge, contributed to the [[Weekly_news]] and was a moderator at the [http://forums.opensuse.org openSUSE Forums]. He is currently employed by open-slx.com as openSUSE Community Assistant and works on improving openSUSE support and documentation resources in co-work with the Wiki, Booster and Forums Teams.<br />
|-<br />
| <br />
| '''Peter Linnell''' - (Picture to be uploaded) Born in the US, he has lived in France for the past 7 years and before that London. When motivated he speaks decent French and lousy German and can read Dutch when the mood strikes. Peter has been a long time open source participant in a number of areas: Core Team Member and Founder of Scribus, founding organizer of LGM and active packager for a number of upstream applications. He thinks OBS simply rocks. As a part of openSUSE he has worked on the Contrib repo as well as well as a number of other projects. During the daytime, he works for Cloudera, a rocking Silicon Valley start-up. Before that, he was at INRIA working on XtreemOS. When he is not in front of a computer, he likes to be in a boat or in the air in an airplane. He is also old enough to admit to having a copy of Advanced Netware before it had version numbers. Oh and he has the most adorable daughter Stella. :)<br />
|-<br />
| [[Image:PavolRusnak.jpg|link=]]<br />
| [http://stick.gk2.sk '''Pavol Rusnak'''] started to work for Novell in 2006 as a package maintainer and at the same time he became a part of openSUSE project. In July 2009 he happily moved to the openSUSE [[openSUSE:Boosters_team|Boosters Team]], where he's hacking on various parts of infrastructure (including [[Portal:Build_Service|Build Service]]). He also helps the community to gather around particular projects (like [[openSUSE:Contrib|Contrib]], [[Games]], Xfce or LXDE, for example) and boostrap their later independent activity.<br />
|-<br />
| [[Image:Hennevogel.png|115px|link=]]<br />
| [http://www.hennevogel.de '''Hendrik Vogelsang'''] a.k.a. Henne, thirtysomething years old, located in [http://www.panoramen.nuernberg.de/kaiserburg.html Nuremberg]/[http://www.deutschland.de/fileadmin/karte/karte.php?lang=2 Germany]/[http://www.last.fm/music/Europe Europe]. Henne is working for more than 10 years for SUSE as free and open source software developer. Currently as hacking, community guiding and fuzz making project manager. He is a founding and board member of the [[Portal:Project|project]] and participant in various other FOSS projects.<br />
|-<br />
| [[Image:BryenYunashko.jpg|link=]]<br />
| [http://news.opensuse.org/2008/07/12/people-of-opensuse-bryen-yunashko/ '''Bryen Yunashko'''] is a consultant based in the United States specializing in Novell products. Since joining the openSUSE Community, he has been an active contributor in the community by founding the openSUSE Helping Hands project and becoming co-editor of the [http://www.opensuse-tutorials.com '''openSUSE-Tutorials'''] website. As the first known Deaf-Blind member of a Linux-based board, he is also a strong proponent of increasing accessibility through computing and is an active member of the GNOME A11y (Accessibility) Team and maintainer of the [http://www.planet-a11y.net '''Planet A11y'''] aggregator site.<br />
|}<br />
<br />
----<br />
<br />
== Contact ==<br />
* You can reach the board privately via email [mailto:board@opensuse.org board@opensuse.org].<br />
{{Mailinglist|opensuse-board|Everybody can discuss topics with the board on its mailinglist}}<br />
{{Mailinglist|opensuse-project|The board invites everybody to start general discussions on the project mailinglist}}<br />
<br />
----<br />
<br />
== Past Board members ==<br />
<br />
* Pascal Bleser (2007-2010)<br />
* Francis Giannaros (2007-2008)<br />
* Andreas Jaeger (Chair) (2007-2008)<br />
* Stephan Kulow (2007-2008)<br />
* Federico Mena-Quintero (2007-2009)<br />
* Stephan Shaw (2009)<br />
* Bryen Yunashko (2008-2011)<br />
* Pavol Rusnak (2009-2011)<br />
* Rupert Horstkötter (2009-2011)<br />
<br />
----<br />
<br />
== History ==<br />
<br />
* November 8th, 2007 : [[Archive:Board 2007|1st openSUSE Board]] - Pascal Bleser, Francis Giannaros, Andreas Jaeger (chairman), Stephan Kulow, Federico Mena-Quintero.<br />
<br />
* October 27th, 2008 : [[Archive:Board 2008|2nd openSUSE Board]] - Pascal Bleser, Michael Loeffler (chairman), Federico Mena-Quintero*, Stephen Shaw, Henne Vogelsang, Bryen Yunashko (*Stephen Shaw stepped in as interim Board Member for remainder of Federico Mena-Quintero's term May 2009).<br />
<br />
* December 22th, 2009 : [[Archive:Board 2009|3rd openSUSE Board]] - Pascal Bleser, Rupert Horstkötter, Michael Loeffler (chairman), Pavol Rusnak, Henne Vogelsang, Bryen Yunashko.<br />
<br />
* January 26th, 2011 : [[openSUSE:Board 2010|4th openSUSE Board]] - Alan Clark (chairman), Rupert Horstkötter, Peter Linnell, Pavol Rusnak, Henne Vogelsang, Bryen Yunashko.<br />
<br />
* December 19th, 2011 : '''5th openSUSE Board''' - Pascal Bleser, Alan Clark (chairman), Peter Linnel, Will Stephenson, Henne Vogelsang, Andrew Wafaa.<br />
<br />
[[de:Rat]]<br />
[[fr:openSUSE:Board]]<br />
[[ja:Board]]<br />
[[ru:Board]]<br />
[[Category:Community]]<br />
[[Category:Board]]<br />
[[Category:Team pages]]</div>Pbleserhttps://en.opensuse.org/index.php?title=openSUSE:Board_2013&diff=48064openSUSE:Board 20132012-01-12T12:46:13Z<p>Pbleser: removed redirect, backported changes that were erroneously made to "Archive:Board 2011"</p>
<hr />
<div>{{Board navbar}}<br />
{{Intro|The openSUSE board was setup to lead the overall project. The main tasks for members of the board are: <br />
* Act as a central point of contact<br />
* Help resolve conflicts<br />
* Communicate community interests to Novell<br />
* Facilitate communication with all areas of the community<br />
* Facilitate decision making processes where needed.}}<br />
<br />
The board should provide [[openSUSE:Guiding principles|guidance]] and support existing governance structures, but shouldn't direct or control development, since community mechanisms exist to accomplish the goals of the project. The board should document decisions and policies.<br />
<br />
The board members are elected by the community and the chair person is appointed by Novell. The current chosen members are as follows:<br />
<br />
== Members ==<br />
<br />
{|<br />
|-<br />
| [[Image:AlanClark-Image.jpg|115px|link=]]<br />
| '''Alan Clark (Chair) / AlanClark''' With over 20 years of experience as a Software Engineer, a principal portion of Alan's career has been devoted to the research and development of operating systems and distributed multi-platform server services. His experience is with file systems, Directory Services, LDAP Services, Object Databases, Security, Developer Interfaces, Web Services, Network Protocols. Alan is a member of Novell's Open Platform Systems Senior Staff. Alan participates in several Industry forum Board of Directors, steering committees, technical committees and work groups, including serving as a Director for the Linux Foundation Board.<br />
<br />
|-<br />
| [[Image:Hennevogel.png|115px|link=]]<br />
| [http://news.opensuse.org/2008/10/17/people-of-opensuse-henne-vogelsang/ '''Henne Vogelsang / henne'''] cares since a long time at Novell for the SUSE base system. Henne is one of the [http://packman.links2linux.org packman] seniors, runs the [[openSUSE:IRC list|#opensuse/#suse IRC channel]] and maintains all of the [[openSUSE:Mailing lists|opensuse mailing lists]] and the [http://lists.opensuse.org corresponding server]. Trough his work he is also involved in various free and open source projects.<br />
<br />
|-<br />
| [[Image:PascalBleser.jpg|link=]]<br />
| [http://news.opensuse.org/2007/08/09/people-of-opensuse-names-please-do-not-publish/ '''Pascal Bleser / yaloki'''] lives in Belgium and works as a software architect and developer at a large European ISV in Germany.<br/>He contributes most of his time building packages for openSUSE in his now defunct [http://linux01.gwdg.de/~pbleser/ Guru] as well as [http://packman.links2linux.org Packman] and [[Portal:Build Service|openSUSE Build Service]] repositories. He wrote most of the current Packman website, contributes some bits to opensource projects here and there, and tries to support community interaction and communication. He is also a member of the core team that organizes [http://fosdem.org FOSDEM], one of the largest and most appreciated opensource developer conferences in Europe.<br />
<br />
|-<br />
| [[Image:AndrewWafaa1.jpg|link=]]<br />
| [http://www.wafaa.eu/ '''Andrew Awafaa / FunkyPenguin'''] Lives in a small town in the East of England originally come from Aberdeen. Employed as a Senior Solutions Architect at Fujitsu Services in the UK, supposedly dealing with Linux based solutions. Involved in Open Source in one form or another for over 10years, and have been using openSUSE and its predecessors since 6.2. Contributed to numerous aspects of openSUSE from advocacy to code to packages to crazy ideas (I get lots of these). Now heavily involved in the porting effort over to the ARM Architecture.<br />
<br />
|-<br />
| [[Image:WillStephenson1.jpg|link=]]<br />
| [http://lizards.opensuse.org/author/wstephenson/ '''Will Stephenson / wstephenson'''] is from the United Kingdom, have been lived in Germany for 6 years now, since moved to Nuremberg to work for SUSE Linux. Live with wife and daughter a few minutes from the SUSE office. I started out as a student of German, along the way became a computer scientist researching wireless mesh networking, earned my keep working on a J2EE implementation and the odd website, and became a KDE hacker working on instant messaging. Originally came to SUSE to work on the KDE PIM suite and Kopete in SLE, but the role quickly broadened to be part of the general KDE team and from there has evolved into being one of the openSUSE Boosters. Part of the openSUSE project since day one, travelling to tell people about the openSUSE project, the distribution and the Build Service.<br />
<br />
|-<br />
| <br />
| [http://en.opensuse.org/User:Mrdocs/ '''Peter Linnell / mrdocs'''] Born in the US, he has lived in France for the past 7 years and before that London. When motivated he speaks decent French and lousy German and can read Dutch when the mood strikes. Peter has been a long time open source participant in a number of areas: Core Team Member and Founder of Scribus, founding organizer of LGM and active packager for a number of upstream applications. He thinks OBS simply rocks. As a part of openSUSE he has worked on the Contrib repo as well as well as a number of other projects. During the daytime, he works for Cloudera, a rocking Silicon Valley start-up. Before that, he was at INRIA working on XtreemOS. When he is not in front of a computer, he likes to be in a boat or in the air in an airplane. He is also old enough to admit to having a copy of Advanced Netware before it had version numbers. Oh and he has the most adorable daughter Stella. <br />
<br />
|}<br />
<br />
<br />
----<br />
<br />
== Contact ==<br />
* You can reach the board privately via email [mailto:board@opensuse.org board@opensuse.org].<br />
{{Mailinglist|opensuse-board|Everybody can discuss topics with the board on its mailinglist}}<br />
{{Mailinglist|opensuse-project|The board invites everybody to start general discussions on the project mailinglist}}<br />
<br />
----<br />
<br />
== Past Board members ==<br />
<br />
* Pascal Bleser (2007-2010)<br />
* Francis Giannaros (2007-2008)<br />
* Andreas Jaeger (Chair) (2007-2008)<br />
* Stephan Kulow (2007-2008)<br />
* Federico Mena-Quintero (2007-2009)<br />
* Stephan Shaw (2009)<br />
* Bryen Yunashko (2008-2011)<br />
* Pavol Rusnak (2009-2011)<br />
* Rupert Horstkötter (2009-2011)<br />
<br />
----<br />
<br />
== History ==<br />
<br />
* November 8th, 2007 : [[Archive:Board 2007|1st openSUSE Board]] - Pascal Bleser, Francis Giannaros, Andreas Jaeger (chairman), Stephan Kulow, Federico Mena-Quintero.<br />
<br />
* October 27th, 2008 : [[Archive:Board 2008|2nd openSUSE Board]] - Pascal Bleser, Michael Loeffler (chairman), Federico Mena-Quintero*, Stephen Shaw, Henne Vogelsang, Bryen Yunashko (*Stephen Shaw stepped in as interim Board Member for remainder of Federico Mena-Quintero's term May 2009).<br />
<br />
* December 22th, 2009 : [[Archive:Board 2009|3rd openSUSE Board]] - Pascal Bleser, Rupert Horstkötter, Michael Loeffler (chairman), Pavol Rusnak, Henne Vogelsang, Bryen Yunashko.<br />
<br />
* January 26th, 2011 : [[openSUSE:Board 2010|4th openSUSE Board]] - Alan Clark (chairman), Rupert Horstkötter, Peter Linnell, Pavol Rusnak, Henne Vogelsang, Bryen Yunashko.<br />
<br />
* January 26th, 2012 : '''5th openSUSE Board''' - Pascal Bleser, Alan Clark (chairman), Peter Linnel, Will Stephenson, Henne Vogelsang, Andrew Wafaa.<br />
<br />
[[de:Rat]]<br />
[[fr:openSUSE:Board]]<br />
[[ja:Board]]<br />
[[ru:Board]]<br />
[[Category:Community]]<br />
[[Category:Board]]<br />
[[Category:Team pages]]</div>Pbleserhttps://en.opensuse.org/index.php?title=openSUSE:Specfile_guidelines&diff=47983openSUSE:Specfile guidelines2012-01-09T09:12:44Z<p>Pbleser: add a warning about Factory requiring upstream changelog information in any case in the .changes file, and if upstream does not provide any changelog, that must be mentioned as well</p>
<hr />
<div>{{Packaging_navbar}}<br />
{{Intro|RPM itself has very little limitations on what you can do in specfiles, so you can make them very complex. This guidelines tries to minimize the variations in specific areas so the specfiles are maintainable.}}<br />
<br />
==General Rules==<br />
All spec files must be legible. If other packagers are unable to read the spec file, it will be impossible to perform a review and to collaborate on the package.<br />
<br />
===Specfile Template===<br />
When writing a package from scratch, you should base your spec file on the spec file template (see [http://software.opensuse.org/search?q=rpmdevtools rpmdevtools]). A basic setup for a package MYPACK can be generated by<br />
<br />
sudo zypper -p http://download.opensuse.org/repositories/devel:/tools/openSUSE_11.3 -v in osc rpmdevtools<br />
<br />
cd .../MYPROJECT<br />
osc mkpac MYPACK<br />
cd MYPACK<br />
wget http://upstream.example.org/source/.../MYPACK-1.0.tar.gz<br />
rpmdev-newspec -t lib MYPACK<br />
osc vc<br />
vi MYPACK.spec<br />
# later: osc build<br />
# osc ci<br />
<br />
Please put your preferences about spec file formatting and organization aside, and try to conform to this template as much as possible. This is not because we believe this is the only right way to write a spec file, but because it often makes it easier for QA to spot mistakes and quickly understand what you are trying to do. <br />
<br />
Spec files for specific languages can often be created with specialized tools like <tt>cpanspec</tt> or <tt>gem2rpm-opensuse</tt>. See also<br />
<br />
* [[openSUSE:Packaging_Perl]]<br />
* [[openSUSE:Packaging_Python]]<br />
* [[openSUSE:Packaging_Ruby]]<br />
<br />
===Specfile Encoding===<br />
Unless you need to use characters outside the [http://commons.wikimedia.org/wiki/Image:Ascii_full.png ASCII repertoire], you will not need to be concerned about the encoding of the spec file. If you do need non-ASCII characters, save your spec files as UTF-8. If you are in doubt as to what characters are ASCII, please refer to [http://commons.wikimedia.org/wiki/Image:Ascii_full.png an ASCII chart].<br />
<br />
<br />
===Specfile Licensing===<br />
Due to legal reasons, spec files must have a license header. Note that the OBS will add a default spec file license header if you forget this. However, this may not be what you want, you can use the following template instead:<br />
<br />
#<br />
# spec file for package python-$FOO<br />
#<br />
# Copyright (c) $CURRENT_YEAR $YOUR_NAME_WITH_MAIL_ADDRESS<br />
#<br />
# All modifications and additions to the file contributed by third parties<br />
# remain the property of their copyright owners, unless otherwise agreed<br />
# upon. The license for this file, and modifications and additions to the<br />
# file, is the same license as for the pristine package itself (unless the<br />
# license for the pristine package is not an Open Source License, in which<br />
# case the license is the MIT License). An "Open Source License" is a<br />
# license that conforms to the Open Source Definition (Version 1.9)<br />
# published by the Open Source Initiative.<br />
<br />
# Please submit bugfixes or comments via http://bugs.opensuse.org/<br />
#<br />
<br />
<br />
===Macros===<br />
Use macros instead of hard-coded directory names (see [[openSUSE:Packaging Conventions RPM Macros|Packaging Conventions RPM Macros]]). Having macros in a <tt>Source:</tt> or <tt>Patch:</tt> line is a matter of style. Some people enjoy the ready readability of a source line without macros. Others prefer the ease of updating for new versions when macros are used. In all cases, remember to be consistent in your spec file and verify that the URLs you list are valid. If you need to determine the actual string when it contains macros, you can use rpm. For example, to determine the actual <tt>Source:</tt> value, you can run:<br />
<pre><br />
rpm -q --specfile foo.spec --qf "$(grep -i ^Source foo.spec)\n"<br />
</pre><br />
Caution: the above command works with <tt>%name</tt> and <tt>%version</tt>, but may fail with user defined macros.<br />
<br />
====Macros vs RPM variables====<br />
There are two styles of defining the Build Root and Optimization Flags in a spec file.<br />
<br />
{| border="1"<br />
|-<br />
! || macro style || variable style<br />
|-<br />
| Build Root || %buildroot || $RPM_BUILD_ROOT<br />
|-<br />
| Opt. Flags || %optflags || $RPM_OPT_FLAGS<br />
|}<br />
<br />
There is very little value in choosing one style over the other, since they will resolve to the same values in all scenarios. You should pick a style and use it consistently throughout your packaging. Mixing the two styles, while valid, is bad from a QA and usability point of view, and should not be done in openSUSE packages.<br />
<br />
RPM macros are expanded before the shell script that a section comprises, is run. Since sh is notoriously slow, it would seem that the %-style shall be preferred, also because one is already using other macros like <tt>%_bindir</tt> which have no variable equivalent.<br />
<br />
====Conditionals====<br />
If the spec file contains [http://www.rpm.org/wiki/PackagerDocs/ConditionalBuilds conditional dependencies] selected based on presence of optional <code>--with(out) foo</code> arguments to <code>rpmbuild</code>, build the source RPM to be submitted with the default options, i.e. so that none of these arguments are present in the <code>rpmbuild</code> command line. The reason is that those requirements get "serialized" into the resulting source RPM, i.e. the conditionals no longer apply.<br />
<br />
== Preamble ==<br />
These are the rules for the preamble section of a specfile.<br />
<br />
===Naming / versioning ===<br />
See [[openSUSE:Package naming guidelines|Package naming guidelines]].<br />
<br />
===Metadata Tags===<br />
* The ''Packager'' tag must not be used in spec files. Rebuilding the RPM package elsewhere forces this packager value onto the third person, leading to subsequent confusion about who to contact. The identities of the packagers should be specified with changelog entries instead.<br />
* The ''Vendor'' tag must not be used for the same reason. In the Build Service, it is also automatically set; if you want to override it, use a prjconf-level <tt>%define</tt>.<br />
* The ''Copyright'' tag is deprecated. Use the ''License'' tag instead, as detailed in [[openSUSE:Packaging_guidelines#Licensing]].<br />
* The ''Source'' should be a complete URL to the upstream tarball. If the tarball was manually recompressed however, this does not apply. Providing a download page location in a comment is thus welcome.<br />
* The ''Group'' tag should only contain package groups following the [[openSUSE:Package group guidelines]].<br />
* The ''BuildRoot'' tag should always be used, even if newer rpms override it anyway. The preferred path is <code class="filename">%_tmppath/%name-%version-build</code>.<br />
* The ''AutoReqProv'' tag defaults to ''on'', so it is redundant to specify it when not actually wanting to turn it off.<br />
<br />
===Summary===<br />
* It should not end in a period. If this bothers you from a grammatical point of view, sit down, take a deep breath, and get over it.<br />
* It should also be a short and concise description of the package, the maximum length is 80 characters.<br />
* It should fit all standard situations and not assume any special context.<br />
* It should be helpful alone, in alphabetically sorted or unsorted lists of some selected packages, and in alphabetically sorted or unsorted lists of all packages.<br />
* It should describe the package's main function and point out any special properties of the package to support the user comparing similar packages. For example, the two words "Web Browser" summarize any web browser, but using additional adjectives (like minimalistic, text-based or fast) helps characterize a specific package.<br />
<br />
===Description===<br />
The description expands upon the summary. Do not include installation instructions in the description; it is not a manual. If the package requires some manual configuration or there are other important instructions to the user, refer the user to the documentation in the package. Add a ''README.SUSE'', or similar, if you feel this is necessary. Also, please make sure that there are no lines in the description longer than 70 characters. (Linked to the size of the YAST description window in ncurses mode.) Also, the description should not exceed a reasonable size, more than 20 lines is probably too much.<br />
<br />
The package description should help the user decide on the right package for the intended purpose without needing to test other similar packages first. This is the right place to inform the user more precisely about a package's functionality. It should contain further information about features and differences from other, comparable packages. If a package could harm a user's installation, the description should contain clear notes on its potential risks or side effects.<br />
<br />
Please put personal preferences aside and use American English spelling in the summary and description. The RPM spec file contains only the English version of Summary and Description to keep the RPM database small. The localizations are managed by YaST.<br />
<br />
The list of authors at the end of the description should not be included anymore [NB:since summer 2011]. We use a separate AUTHORS file for the credits. If the file is not already part of the upstream package, you should create one, and use it like this:<br />
Source2: AUTHORS<br />
...<br />
%setup<br />
cp %{S:2} .<br />
...<br />
%files<br />
%doc AUTHORS<br />
<br />
==== Trademarks in Summary or Description ====<br />
Packagers should be careful how they use trademarks in Summary or Description. There are a few rules to follow:<br />
* Never use "(TM)" or "(R)" (or the unicode equivalents, ™/®). It is incredibly complicated to use these properly, so it is actually safer for us to not use them at all.<br />
* Use trademarks in a way that is not ambiguous. Avoid phrasing like "similar to" or "like". Some examples:<br />
<br />
* '''BAD:''' It is similar to Adobe Photoshop.<br />
* '''GOOD:''' It supports Adobe Photoshop PSD files, ...<br />
<br />
* '''BAD:''' A Linux version of Microsoft Office<br />
* '''GOOD:''' A word-processor with support for Microsoft Office DOC files<br />
<br />
If you are not sure, ask yourself, is there any chance someone may get confused and think that this package is the trademarked item? When in doubt, try to leave the trademark out.<br />
<br />
===Dependencies===<br />
<br />
====Requires====<br />
RPM has very good capabilities of automatically finding dependencies for libraries and eg. Perl modules. In short, do not reinvent the wheel, but just let rpm do its job. There is usually no need to explicitly list e.g. <tt>Requires: libqt4</tt> when the dependency has already been picked up by rpm in the form of depending on shared libraries in the libqt4 package.<br />
<br />
If your package splits into sub-packages, they may need to require the base-package using a versioned dependency: <code>Requires: %name = %version</code>.<br />
<br />
<tt>-devel</tt> sub-packages need to explicitly depend on packages with the shared libraries that the devel package has symlinks to, i.e. libfoobar-devel needs, for example, <tt>Requires: libfoo2 = %version, libbar5 = %version</tt><br />
<br />
====PreReq====<br />
<br />
Packages should not use the PreReq tag. Once upon a time, in dependency loops, PreReq used to "win" over the conventional Requires when RPM determined the installation order in a transaction. This is no longer the case.<br />
<br />
====BuildRequires====<br />
Unlike with ''Requires'', for BuildRequires there is no automatic procedure to find dependencies. You must explicitly list the packages that your package requires to build successfully. Having proper build requirements saves the time of all developers and testers because they will not need to search for missing build requirements manually. It is also ensures that the build is reproducible and uses always the same features. ''configure'' scripts, for example, may exclude PNG support depending on the availability of libpng in the build system. With <code>BuildRequires: libpng-devel</code> (or since openSUSE 11.4: <tt>BuildRequires: pkgconfig(libpng14)</tt>, you ensure that the build will fail if libpng is not present.<br />
<br />
=====OBS Caveat=====<br />
Conditional BuildRequires are limited to simple variables. RPM usually supports complex constructs like this in an %if expression:<br />
<br />
%if 0%(test "%something" = "enabled" && echo 1)<br />
<br />
But when evaluating BuildRequires, the RPM parser of the BuildService runs in an environment where subshell expansions are disabled. You'll see warnings like this:<br />
<br />
Warning: spec file parser line 109: can't expand %(...)<br />
<br />
The following example uses only a simple variable, which works with BuildRequires:<br />
<br />
%if ! 0%?have_own_mpfr<br />
BuildRequires: mpfr-devel<br />
%endif<br />
<br />
=====Exceptions=====<br />
There is no need to include the following packages or their dependencies as BuildRequires, because they would occur too often. These packages are considered the minimum build environment.<br />
<br />
Also try this command for a list:<br />
{{shell|osc meta prjconf openSUSE:Factory &#x7c; egrep '^(Preinstall:&#x7c;Support:&#x7c;Required:)'}}<br />
<pre>Preinstall: aaa_base acl attr bash coreutils diffutils<br />
Preinstall: filesystem fillup glibc grep insserv libacl libattr<br />
Preinstall: libbz2-1 libgcc%{gcc_version} libxcrypt m4 libncurses5 pam<br />
Preinstall: permissions libreadline6 rpm sed tar zlib libselinux1<br />
Preinstall: liblzma5 libcap2 libpcre0<br />
Preinstall: libpopt0 libelf1 liblua5_1<br />
Required: gcc gcc%{gcc_version} glibc perl rpm tar patch<br />
Support: autoconf automake binutils bzip2 gcc gcc%{gcc_version}<br />
Support: gettext-runtime glibc libtool perl rpm zlib<br />
Support: libncurses5<br />
Support: libaudit1 cpio cpp cpp%{gcc_version} cracklib cvs<br />
Support: file findutils gawk gdbm gettext-tools<br />
Support: glibc-devel glibc-locale groff gzip info less<br />
Support: libbz2-devel libdb-4_8<br />
Support: libstdc++%{gcc_version}<br />
Support: udev<br />
Support: libxcrypt libzio<br />
Support: linux-glibc-devel make man netcfg<br />
Support: net-tools pam-modules patch perl-base sysvinit-tools<br />
Support: texinfo timezone util-linux libmount1 login<br />
Support: libgomp%{gcc_version} libuuid1 psmisc<br />
Support: terminfo-base update-alternatives pwdutils build-mkbaselibs<br />
Support: brp-check-suse post-build-checks rpmlint-Factory<br />
Support: build-compare<br />
Support: libunwind libunwind-devel<br />
</pre><br />
<br />
====Conflicts====<br />
Whenever possible, openSUSE packages should avoid conflicting with each other. Unfortunately, this is not always possible. For full details on openSUSE Conflicts policy, see: [[openSUSE:Packaging conflicts]] .<br />
<br />
====File Dependencies====<br />
RPM gives you the ability to depend on files instead of packages. Whenever possible, you should avoid file dependencies outside of <tt>/etc</tt>, <tt>/bin</tt>, <tt>/sbin</tt>, <tt>/usr/bin</tt>, or <tt>/usr/sbin</tt>. Using file dependencies outside of those directories requires yum (and other depsolvers using the repomd format) to download and parse a large XML file looking for the dependency. Helping the depsolvers avoid this processing by depending on the package instead of the file saves our end users a lot of time. There are times when other technical considerations outweigh these considerations. One specific example is packages installing into <tt>%_libdir/mozilla/plugins</tt>. In this case, mandating a specific browser in your package just to own this directory could drag in a large amount of needless packages. Requiring the directory to resolve the dependency is the better choice.<br />
<br />
=== Patches ===<br />
All patches in openSUSE spec files '''SHOULD''' have a comment above them about their status. For details see [[openSUSE:Packaging Patches guidelines|Packaging Patches guidelines]] page.<br />
<br />
==Preparation Section (%prep)==<br />
These are the rules for the preparation section of the specfile.<br />
<br />
===Quiet %setup===<br />
You should pass the <tt>-q</tt> option to the <tt>%setup</tt> macro. This will reduce the size of the build logfile significantly, especially with source archives that extract a lot of files.<br />
<br />
==Build Section (%build)==<br />
These are the rules for the build section of the specfile.<br />
<br />
=== Compiler flags ===<br />
Compilers used to build packages should honor the applicable compiler flags set in the system rpm configuration. This means in practice <tt>%optflags</tt> (variable: <tt>$RPM_OPT_FLAGS</tt>, see above) for C, C++, and Fortran compilers. Honoring means that the contents of that variable is used as the basis of the flags actually used by the compiler during the package build. Adding to and overriding or filtering parts of these flags is permitted if there is a good reason to do so; the rationale for doing so should be reviewed and documented in the specfile especially in the override and filter cases.<br />
<br />
=== Parallel make ===<br />
Whenever possible, invocations of <code>make</code> should be done as<br />
<br />
make %{?_smp_mflags}<br />
<br />
This generally speeds up builds, especially on SMP machines. This is preferable to <tt>%{?jobs:-j%jobs}</tt>, as it allows alternate make flags to be used, such as <tt>make -l''N''</tt>, and not hardcoding <tt>-j''N''</tt>. Do make sure, however, that the package builds cleanly this way as some make files do not support parallel building, or have broken dependencies.<br />
<br />
In case a source package does not support parallel building, please indicate so in the specfile by placing a comment, and perhaps using <tt>-j1</tt> to facilitate grepping for such packages.<br />
<br />
==Install Section (%install)==<br />
These are the rules for the install section of the specfile.<br />
<br />
Since rpmbuild is run as an unprivileged user, running `<tt>make install</tt>` must not attempt to chown the files (either by running chown directly, or by utilizing, for example, `<tt>install -o root</tt>...`). File ownership shall be set in the later <tt>%files</tt> section instead.<br />
<br />
There are two similarly-named, and thus confusing, install macros provided by rpm and SUSE's rpm macros:<br />
<br />
# The make install analogue of %configure for modern autotools:<br />
%make_install make install DESTDIR=%{?buildroot}<br />
<br />
#------------------------------------------------------------------------------<br />
# Former make install analogue, kept for compatibility and for old/broken<br />
# packages that don't support DESTDIR properly.<br />
%makeinstall \<br />
make \\\<br />
prefix=%{?buildroot:%{buildroot}}%{_prefix} \\\<br />
exec_prefix=%{?buildroot:%{buildroot}}%{_exec_prefix} \\\<br />
[...]<br />
<br />
SUSE's rpm, i.e. <tt>/usr/lib/rpm/suse_macros</tt> redefines both to practically the same thing:<br />
<br />
%make_install make install DESTDIR=%{?buildroot}<br />
%makeinstall make DESTDIR=%{?buildroot:%{buildroot}} install<br />
<br />
Due to this, one should probably use only <tt>%make_install</tt>.<br />
<br />
===Removing the buildroot===<br />
openSUSE marks it as '''bad coding style''' to have <code>rm -rf %{buildroot}</code> or <code>rm -rf $RPM_BUILD_ROOT</code> at the beginning of an <tt>%install</tt> section like this:<br />
%install<br />
rm -rf $RPM_BUILD_ROOT<br />
mkdir -p $RPM_BUILD_ROOT/usr/... or make install<br />
<br />
Why?<br />
<br />
RPM_BUILD_ROOT is normally within /var/tmp and you just opened a trivial race condition to a local attacker on your machine to take over<br />
your account (or event root if you build as root). It is better not to "rm -rf $RPM_BUILD_ROOT" in %install at all (and rely on %clean to do it).<br />
<br />
If you want to clean it, better do:<br />
%install<br />
rm -rf $RPM_BUILD_ROOT<br />
mkdir $RPM_BUILD_ROOT<br />
mkdir -p $RPM_BUILD_ROOT/usr ... or make install<br />
<br />
In this case the "mkdir $RPM_BUILD_ROOT" would fail and the build would abort if an attacker tries to replace the buildroot by his own symlink.<br />
<br />
==Clean Section (%clean)==<br />
<br />
The <tt>%clean</tt> section, if specified, will be run after the binary and source RPMs have been generated. In the Open Build Service, this section is not necessary because chroots and/or VM environments that are used to build the package are generally torn down anyway. Building packages in environments not started from scratch is usually not supported for openSUSE packages (cf. bnc#176528 c4)<br />
<br />
Starting with rpm-4.7/openSUSE_11.3, rpm defaults to "<tt>%clean: rm -Rf %buildroot</tt>" if the <tt>%clean</tt> section is completely absent from the specfile.<br />
<br />
In the distant past, some packages, in <tt>%clean</tt>, checked that <code>%{buildroot}</code> was not <code>/</code> before deleting it. This is not necessary in openSUSE anymore.<br />
<br />
==Scriptlets (%post* / %pre*)==<br />
These are the rules for the scriptlet sections of the specfile. Great care should be taken when using scriptlets. If scriptlets are used, those scriptlets must be sane. Some common scriptlets are documented in [[openSUSE:Packaging scriptlet snippets]].<br />
<br />
=== Scriptlets requirements ===<br />
Your package has to require everything you use in scriptlets. The notation is as follows:<br />
<br />
Requires(pre): ...<br />
Requires(post): ...<br />
<br />
<font color="red"><br />
=== Scriplets are only allowed to write in certain directories ===<br />
Build scripts of packages (<tt>%prep</tt>, <tt>%build</tt>, <tt>%install</tt>, <tt>%check</tt> and <tt>%clean</tt>) may only alter files (create, modify, delete) under <tt>%buildroot</tt>, <tt>%_builddir</tt> and valid temporary locations like <tt>/tmp</tt>, <tt>/var/tmp</tt> (or <tt>$TMPDIR</tt> (valid?) or <tt>%_tmppath</tt> as set by the rpmbuild process) according to the following matrix:<br />
<br />
{| border="1"<br />
|-<br />
! || /tmp, /var/tmp, $TMPDIR, %{_tmppath} || %{_builddir} || %{buildroot}<br />
|-<br />
|%prep || yes || yes || no<br />
|-<br />
|%build || yes || yes || no<br />
|-<br />
|%install || yes || yes || yes<br />
|-<br />
|%check || yes || yes || no<br />
|-<br />
|%clean || yes || yes || yes<br />
|}<br />
<br />
Further clarification: That should hold true irrespective of the builder's uid.<br />
</font><br />
<br />
== Files Section (%files) ==<br />
These are the rules for the files section of the specfile. openSUSE follows the [http://www.pathname.com/fhs/ Filesystem Hierarchy Standard] with regards to filesystem layout. The FHS defines where files should be placed on the system. Any deviation from the FHS should be rationalized as a comment in the spec file.<br />
<br />
===Ownership===<br />
Your package should own all of the files that are installed as part of the <tt>%install</tt> process. Packages must not own files already owned by other packages. The rule of thumb here is that the first package to be installed should own the files that other packages may rely upon. If you feel that you have a good reason to own a file or that another package owns, then please present that at package review time.<br />
<br />
Directory ownership is a little more complex than file ownership. Although the rule of thumb is the same: own all the directories you create but none of the directories of packages you depend on, there are several instances where it is desirable for multiple packages to own a directory. Examples of this are:<br />
<br />
# The package you depend on to provide a directory may choose to own a different directory in a later version and your package will run unmodified with that later version. One common example of this is a Perl module. Assume ''perl-A-B'' depends on ''perl-A'' and installs files into <tt>/usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/A/B</tt>. The base Perl package guarantees that it will own <tt>/usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi</tt> for as long as it remains compatible with version 5.8.8, but a future upgrade of the ''perl-A'' package may install into (and thus own) <tt>/usr/lib/perl5/vendor_perl/5.9.0/i386-linux-thread-multi/A</tt>. So the ''perl-A-B'' package needs to own <tt>/usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/A</tt> as well as <tt>/usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/A/B</tt> in order to maintain proper ownership.<br />
# Multiple packages have files in a common directory but none of them requires others. An example where <br />
<br />
Foo-Animal-Emu puts files into /usr/share/Foo/Animal/Emu<br />
Foo-Animal-Llama puts files into /usr/share/Foo/Animal/Llama<br />
<br />
Neither package depends on the other one. Neither package depends on any other package which owns the <tt>/usr/share/Foo/Animal</tt> directory. In this case, each package must own the <tt>/usr/share/Foo/Animal</tt> directory.<br />
<br />
In all cases, we are guarding against unowned directories being present on a system. Please see [[Packaging/Unowned_Directories]] for the details.<br />
<br />
An openSUSE package must not contain any duplicate files in the <code>%files</code> listing, both in the sense of one file packaged twice or more (in two or more subpackages), and in the sense of content. Run <tt>%fdupes %buildroot</tt> (requires adding <tt>BuildRequires: fdupes</tt>) to smartly elimiate duplicate content by replacing those files with hardlinks to one another.<br />
<br />
===Permissions===<br />
Permissions on files must be set properly. Executables should be set with executable permissions, for example. Every <code>%files</code> section must include a <code>%defattr(...)</code> line. Here is a good default:<br />
<pre><br />
%files<br />
%defattr(-,root,root)<br />
</pre><br />
Unless you have a very good reason to deviate from that, you should use <code>%defattr(-,root,root)</code> for all <code>%files</code> sections in your package.<br />
<br />
====SUID bits====<br />
<br />
'' '''FIXME:''' this section is based mostly on trial-and-error. Haven't found any documentation on this.''<br />
<br />
Security-relevant permissions are handled via <code>/etc/permissions*</code> on openSUSE. Package-specific permissions can be defined through files in <code>/etc/permissions.d/</code>. Read the files <code>/etc/permissions*</code> to learn about the basics.<br />
<br />
If you want to create a package with suid programs, you do the following:<br />
<br />
* Add a <code>Requires(post): permissions</code> header to your spec file.<br />
* Create <code>permissions{,.easy,.secure,.paranoid}</code> files for your package. <code>permissions</code> is used if no file <code>permissions.*</code> matching the system's current security setting is found. As a rule of thumb, <code>permissions.easy</code> should contain permissions as installed by <code>make install</code>, <code>permissions.paranoid</code> should remove all suid bits (even if this breaks functionality), and <code>permissions.secure</code> can be something inbetween.<br />
* Add these permissions files as sources to the spec file, and have <code>%install</code> install them in <code>%{buildroot}%{_sysconfdir}/permissions.d/''packagename''[.''suffix'']</code>.<br />
* In the <code>%files</code> section, define the attributes of the files listed in your permissions files as they are defined for <code>permissions.secure</code>. Instruct <code>rpmverify</code> to '''not''' check ownership or permissions.<br />
* Add a <code>%post</code> scriptlet that sets your package's permissions according to the system's current security level.<br />
* Add a <code>%verifyscript</code> scriptlet that checks your package's permissions according to the system's current security level.<br />
* In order to avoid rpmlint's error messages about disallowed permissions files, create a file <code>''packagename''-rpmlintrc</code> containing the line <code>setBadness('permissions-unauthorized-file', 333)</code>, and list it as a Source in your spec file. (Modify the "333" if you have fewer or more than 3 disallowed files.)<br />
<br />
And because the above contains a few non-obvious details, here's a stripped down example:<br />
<br />
[...]<br />
Source2: permissions<br />
Source3: permissions.easy<br />
Source4: %{name}-rpmlintrc<br />
[...]<br />
PreReq: permissions<br />
[...]<br />
<br />
%install<br />
[...]<br />
mkdir -p %{buildroot}%{_sysconfdir}/permissions.d/<br />
install -m 644 %{S:2} %{buildroot}%{_sysconfdir}/permissions.d/%{name}<br />
install -m 644 %{S:3} %{buildroot}%{_sysconfdir}/permissions.d/%{name}.easy<br />
<br />
%if 0%{?suse_version} >= 1120<br />
%verifyscript<br />
%verify_permissions -e %{_bindir}/mysuidprogram<br />
%endif<br />
<br />
%post<br />
%if 0%{?set_permissions:1} > 0<br />
%set_permissions %{name}<br />
%else<br />
%run_permissions<br />
%endif<br />
<br />
%files<br />
%defattr(-,root,root,-)<br />
[...]<br />
%verify(not user group mode) %attr(0711,root,root) %{_bindir}/mysuidprogram<br />
[...]<br />
<br />
This works at least for packages in your home project.<br />
<br />
===Documentation files===<br />
Any relevant documentation included in the source distribution should be included in the package. Irrelevant documentation include build instructions, the omnipresent ''INSTALL'' file containing generic build instructions, for example, and documentation for non-Linux systems, e.g. ''README.MSDOS''. Also pay attention about which subpackage you include documentation in, for example API documentation belongs in the <tt>-devel</tt> subpackage, not the main one. Or if there is a lot of documentation, consider putting it into a subpackage of its own. In this case, it is recommended to use <code>*-doc</code> as the subpackage name, and <code>Documentation</code> as the value of the <code>Group</code> tag.<br />
<br />
Also, if a package includes something as <code>%doc</code>, it must not affect the runtime of the application. To summarize: If it is in <code>%doc</code>, the program must run properly if it is not present.<br />
<br />
===Configuration files===<br />
Configuration files must be marked as such in packages. As a rule of thumb, use <code>%config(noreplace)</code> instead of plain <code>%config</code> unless your best, educated guess is that doing so will break things. In other words, think hard before overwriting local changes in configuration files on package upgrades. An example case when ''not'' to use <code>noreplace</code> is when a package's configuration file changes so that the new package revision would not work with the config file from the previous package revision. Whenever plain <code>%config</code> is used, add a brief comment to the specfile explaining why.<br />
<br />
Do not use <tt>%config</tt> or <tt>%config(noreplace)</tt> under <tt>/usr</tt>. <tt>/usr</tt> is deemed to not contain configuration files in openSUSE.<br />
<br />
=== Development files ===<br />
If the software being packaged contains files intended solely for development, those files should be put in a <tt>-devel</tt> subpackage. The following are examples of file types which should be in <tt>-devel</tt>:<br />
<br />
* Header files (e.g. .h files)<br />
* Unversioned shared libraries (e.g. libfoo.so). Versioned shared libraries, e.g. <tt>libfoo.so.3</tt>, <tt>libfoo.so.3.0.0</tt> should not be in <tt>-devel</tt>.<br />
* pkgconfig files. A reasonable exception is when the main package itself is a development tool, e.g. gcc or gdb.<br />
<br />
Packages containing pkgconfig (<tt>.pc</tt>) files must utilize <tt>BuildRequires: pkg-config</tt> so that the proper runtime dependency <tt>Requires: pkg-config</tt> is added.<br />
<br />
===Locale files===<br />
openSUSE includes an rpm macro called <code>%find_lang</code>. This macro will locate all of the locale files that belong to your package (by name), and put this list in a file. You can then use that file to include all of the locales. <code>%find_lang</code> should be run in the <tt>%install</tt> section of your spec file, after all of the files have been installed into the buildroot. Using <code>%find_lang</code> helps keep the spec file simple, and helps avoid several other packaging mistakes.<br />
<br />
* Packages that use <code>%{_datadir}/*</code> to grab all the locale files in one line also grab ownership of the locale directories, which is not permitted.<br />
* Most packages that have locales have lots of locales. Using <code>%find_lang</code> is much easier in the spec file than having to do:<br />
<pre><br />
%{_datadir}/locale/ar/LC_MESSAGES/%{name}.mo<br />
%{_datadir}/locale/be/LC_MESSAGES/%{name}.mo<br />
%{_datadir}/locale/cs/LC_MESSAGES/%{name}.mo<br />
%{_datadir}/locale/de/LC_MESSAGES/%{name}.mo<br />
%{_datadir}/locale/es/LC_MESSAGES/%{name}.mo<br />
...<br />
</pre><br />
* As new locale files appear in later package revisions, <code>%find_lang</code> will automatically include them when it is run, preventing you from having to update the spec any more than is necessary.<br />
<br />
===Non-ASCII Filenames===<br />
Filenames that contain non-ASCII characters must be encoded as UTF-8. Since there is no way to note which encoding the filename is in, using the same encoding for all filenames is the best way to ensure users can read the filenames properly. If upstream ships filenames that are not encoded in UTF-8, you can use a utility like <tt>convmv</tt> (from the convmv package) to convert the filename in your <tt>%install</tt> section.<br />
<br />
=== Libexecdir ===<br />
The [http://www.pathname.com/fhs/ Filesystem Hierarchy Standard] does not include any provision for libexecdir, but openSUSE packages can store appropriate files there. Libexecdir (which is redefined to <tt>/usr/lib</tt> on openSUSE systems) should be used as the directory for executable programs that are designed primarily to be run by other programs rather than by users.<br />
openSUSE rpm includes a macro for libexecdir, <code>%{_libexecdir}</code>. Packagers are highly encouraged to store libexecdir files in a package-specific subdirectory of <code>%{_libexecdir}</code>, such as <code>%{_libexecdir}/%{name}</code>.<br />
<br />
==Changelog section (%changelog)==<br />
Every time you make changes to the package, you must add a changelog entry. This is important not only to have an idea about the history of a package, but also to enable users, fellow packages, and QA people to easily spot the changes that you make.<br />
<br />
The Open Build Service uses a separate file for package changes. This file is called like the specfile, but has <tt>.changes</tt> at the end instead of <tt>.spec</tt>. Changelog entries have to be in chronological order. Newer changelog entries are listed in the file above older entries, thus the first entry is the most recent one. No fixes of previous changelog entries are allowed if a package is "checked in" to official repository. <br />
<br />
Entries in this changes file have the following structure:<br />
<br />
<pre><br />
-------------------------------------------------------------------<br />
Tue Apr 22 20:54:26 UTC 2011 - your@email.com<br />
<br />
- bullet point 1<br />
* bullet point 1.1 with long<br />
long long description<br />
* bullet point 1.2<br />
- bullet point 2 with long long long<br />
description<br />
* bullet point 2.1<br />
</pre><br />
<br />
Patches in the changes file should follow the [[openSUSE:Packaging_Patches_guidelines|patches guidelines]] (especially the abbreviations part).<br />
<br />
{{Warning|Packages in openSUSE:Factory require that changes are listed with every new upstream release, and if upstream does not provide any changelog information, you must still provide that information in the .changes file, such as "update to 1.2.3: no changelog available"}}<br />
<br />
[[Category:Packaging|{{PAGENAME}}]]<br />
<br />
[[zh:openSUSE:Specfile_guidelines]]</div>Pbleserhttps://en.opensuse.org/index.php?title=openSUSE:Board_election_2011_platform_template_yaloki&diff=47030openSUSE:Board election 2011 platform template yaloki2011-12-02T00:02:33Z<p>Pbleser: /* Foundation */</p>
<hr />
<div>{{Board navbar}}<br />
== Platform ==<br />
{{Info|'''Note:''' This page is used by the candidate of the board election as a platform to show his views and answer some standard questions. }}<br />
<br />
==Introduction and Biography==<br />
[[File:pascal_bleser_osc11.jpg|thumb|Me at the openSUSE Conference 2011]]<br />
<br />
Hi! My name is Pascal Bleser and I'm currently 36 years old. I live in the east of Belgium with my wife and our two children (Gaëlle is 6, and Thomas is 3).<br />
<br />
My native languages are French and German, my Dutch is extremely rusty, my English is pretty fluent, I know how to order a beer in Croatian, and I know a few curse words in other languages, but that probably doesn't count :)<br />
<br />
* My email address is my first name, then a dot, then my last name at opensuse.org,<br />
* [http://dev-loki.blogspot.com my blog is here],<br />
* my [https://twitter.com/#!/yaloki tweety tweets are there],<br />
* my [irc://irc.freenode.net/yaloki,isnick IRC nickname on freenode is yaloki],<br />
* and [https://picasaweb.google.com/117680951975244630647/ photos of my holidays, kittens and the openSUSE conference are over here].<br />
<br />
I have been working as a software engineer for a large independent software vendor which is currently named Atos Worldline at their site in Aachen (Germany), in a great team where we mostly develop high performance systems in Java for the purpose of security, cryptography, payment, banking, telecoms, etc... In essence, it means I'm a very good Java hacker :)<br />
<br />
As far as my involvement in open source projects goes, it concentrates mostly on two things: obviously the openSUSE project, but also the [http://fosdem.org FOSDEM conference].<br />
<br />
I have been involved with openSUSE since the very beginning, and have even been contributing things when it was still S.u.S.E., which was much harder back then, needless to say.<br />
<br />
I have mostly been contributing packages since the beginning of times (which means something like 10 years, I can't even remember): I first had my own repository of packages (the "guru repository", in case anyone remembers) which was used by a massive amount of people. Later on it was merged with [http://packman.links2linux.org Packman] to avoid duplication of work and provide a better experience to users. I obviously also joined the Packman project and I have and still am creating and maintaining an endless amount of packages there, with the likes of good people like Detlef Reichelt, Manfred Tremmel, Herbert Graeber, to name a few.<br />
I actually developed the whole [http://packman.links2linux.org website of Packman] together with Marc Schiffbauer a long time ago, it was PHP4, I still remember the pain :)<br />
<br />
I have participated in several hackweeks in Nürnberg, and attended and spoken at the openSUSE conferences too, which has often given me the opportunity of meeting many of the fine people in our community, including at SUSE (often around many beers, obviously ;)), several of which I even consider to be good friends. I participated in a few specific workshops, including the one that resulted in [http://en.opensuse.org/openSUSE:Strategy the current openSUSE strategy].<br />
<br />
I have served the community on what I like to call the "bootstrap board", as well as on the first and second board terms as I was elected to do so. After two consecutive terms, I stepped back (as the terms of the board requires -- a rule I actually insisted on ^^) and am now posing my candidacy for the upcoming board.<br />
<br />
As far as contributions go, I have also implemented and am still maintaining the [http://planet.opensuse.org Planet openSUSE] aggregator, as well as taking care of the opensu.se server (which includes the [http://opensuse-community.org/Main_Page opensuse-community wiki] as well as [http://r.opensu.se the repo link shortener] and [http://i.opensu.se the 1-click-installer automater], an idea of [http://lizards.opensuse.org/author/bmwiedemann/ Bernhard Wiedemann], the genius behind [http://openqa.opensuse.org openQA]), together with my good friend Marcus "darix" Rueckert, whom is never tired of doing so many essential things for this project.<br />
<br />
Benjamin Weber and I also developed the openSUSE software portal project, which is currently defunct, and on which I have been working on a replacement since way too long.<br />
<br />
My other main contribution to open source at large is my involvement as a core organization team member of [http://fosdem.org FOSDEM], which is the best and largest open source contributor conference in Europe (and probably on this planet).<br />
<br />
I have been deeply involved there as part of a team of great people and friends since many years (too many to count, I think it's since 2004), mostly taking care of the developer rooms and gently pushing open source projects together to work together, which culminates in the concept of the "distribution mini-conference". As such, I have been in touch with many great people who are at the center of many open source projects, and have a strong culture of working together rather than fighting, especially in the realm of Linux distributions. People in Fedora, Debian, Mageia, etc... (yes, that list would really be too long :)) are our friends, our allies, in an undertaking for the greater good of people and technology.<br />
<br />
FOSDEM means many hours of sleepless nights, and that my wife is very understanding, but it is an essential tool for a very long list of open source projects that get the opportunity of being there and, more importantly, for people to meet, exchange ideas, and, well, have way too many Belgian beers.<br />
<br />
Generally speaking, I have evolved from concentrating on technical bits to enjoying the people part of such projects more than anything else. I truly and deeply believe that as much as we are producing excellent technical elements such as our great openSUSE distribution, it is all about the people, the environment in which we spend so much time doing hard work for no other retribution than the fun of doing it, the good feeling of doing something great, the excellence at which we do, or any other reason that is specific to every single person.<br />
<br />
That must happen in the realm of friends, of people with whom we can talk, people we can trust. Essentially, it must be a fun place.<br />
<br />
Of course, people with great ideas, or hard work, or experience in specific domains, or just with their heart and guts into what they do, they are the ones who make the difference, and they are key to our project, but if it isn't in an environment that is welcoming, friendly, where what people do is recognized as such, then it is pointless. Well, at least, it is what I believe.<br />
<br />
== Major Issues ==<br />
=== Environment and diversity ===<br />
Won't be the first time I'm saying this, but to me, the prime priority is about the environment we spend our time and efforts in. It must be rewarding, it must be fun, it must be amongst a group of friends.<br />
<br />
Right now, the project and the people therein are not sufficiently approachable, not sufficiently "human". Most of us are just emails or IRC nicknames, and that's not quite good enough, as that, amongst other things, puts a needless barrier for entry.<br />
<br />
I have seen the evolution of the project and its community for a very long time now (at least on the scale of a project like openSUSE :)), and I believe we're at a potential turning point right now. A lot of great people have been joining the project lately, focusing on non- or less technical aspects, bringing a lot of skills, energy, enthusiasm and ideas. It is very refreshing and they don't quite have the visibility and network they ought to have.<br />
<br />
Do we have an "openSUSE mold" in which you have to fit in order to be accepted?<br />
Most probably, as most communities have, and probably in an unconscious manner.<br />
<br />
Do we need to break it, change it ?<br />
We should certainly be aware of that influencing our behavior and respect or lack thereof for certain contributors in the project. I believe we should evolve from there into something more open and more encompassing, because diversity is always an improvement, for everyone. It's not just about men and women, it's also about nationalities and culture, languages, technical and non-technical contributors. It's even a point of view I don't only believe in as a human being, but also as an engineer: more (purposeful and constructive) points of view and experience is better. More input is better. Take some more time to discuss and have the better solution.<br />
<br />
=== Communication ===<br />
Specifically, now, it's the elephant in the room. Information needs to be spread out, not contained into micro communities in the community. This is really something we must put a lot of effort in, because<br />
* it avoids needless duplication of work (better to work together)<br />
* it can put more people with ideas, experience, time, skills on the matter at hands into the loop, and hence turn out into a better solution<br />
* we are pretty bad at showing what we're good at, and we are very good at quite a few things (no, it's not for bragging or for distrowars, surely not -- instead, it is quite motivating)<br />
<br />
We have way too many communication channels, on one side, and we also have too much confined information. We cannot expect people to help and contribute if we don't spread out information about what's going on in the first place.<br />
<br />
=== Community caretaking ===<br />
On paper, we do have a community manager as well as a boosters team, and even a board but, effectively, I believe that no one is currently really (pro)actively taking care of the community aspects of the community.<br />
<br />
That is communicating with people, taking care of our communication channels (not accepting bikeshedding has been talked about recently), helping out and mentoring our teams, putting people together where it makes sense. Have a trustworthy landing base where people feel they can get in touch with, to ask for support, to complain about situations that are not fair or that keep them from developing themselves in the project.<br />
<br />
I believe that the board should be morphed into something like that. The community nannies, if you will :)<br />
<br />
=== Mentoring ===<br />
(Or the lack thereof.)<br />
Gregory Zysk, and most probably other people before him, and certainly other people after him, has proposed mentoring as a topic we should think about as a project. I agree and believe that mentoring is particularly important to take away fears (of not being accepted, of failing, or caused by lack of self-confidence, ...) of engaging with our community.<br />
<br />
It would simply make a huge difference to have a person that<br />
* takes some time to talk to you,<br />
* take your hand and guide you through the project and its people,<br />
* knows whom to put you in touch with for this and that,<br />
* has a network in the community,<br />
* listens.<br />
<br />
A few of us are already doing this on an occasional (or not so occasional) basis, but we can do better, and put some thought into designing a landing spot for people who'd like to join us, but would like to have some assistance in doing so.<br />
<br />
So let's not let that good idea fade away.<br />
<br />
=== Leadership ===<br />
This is a pretty tricky one to explain. I mean leadership in a positive way, not in a dictatorial or top-down way :)<br />
<br />
Our project enjoys a pretty unstructured, "just do it" (to cite Henne), informal, bottom-up way of doing things. We don't have a ton of committees, of deciders, of structure and processes. And that, I believe, is an excellent thing. It is primordial to keep it that way, because that, I think, is actually what most people really enjoy here. Meritocracy really works, with a few caveats we need to be aware of and work on (the mold thing I wrote about above, and the hurdles for getting into the project as a contributor.)<br />
<br />
But sometimes, we lack direction, visibility, some hand holding (without its negative connotation). With leadership, I mean that we need more people to step forward a bit and facilitate decisions and directions. Not take those decisions, but help them happen. Leadership by example, of course, and by merit, obviously.<br />
<br />
=== Foundation ===<br />
It is obviously a topic that deserves a few words on its own.<br />
<br />
I was actually the one who pushed for having an openSUSE foundation (as a non-for-profit) when I was on the board, even though the first one who vocally mentioned the idea was Martin Lasarsch, quite some time ago (Martin, I totally miss you in the project).<br />
<br />
The goal was and still is very clear, even though it probably has not been sufficiently communicated since then: act as a recipient for funding and donations because, at that time, there was no possibility for individuals and other sponsors to contribute money to the openSUSE project through Novell. The idea is to be able to use those funds in order to support activities in the project where our current sponsors would not be interested in, or could not provide money for, for reasons of budgeting or political reasons (as in, being a company in the US, where software patents are enforced, where DMCA exists, etc...). Examples would be hosting infrastructure for things that cannot be hosted at opensuse.org, or fund travels and expenses for Ambassadors, etc...<br />
<br />
Since then, it has probably become everything to everyone, and the expectations are high (trademark ownership, control the project "independently", etc...). But those expectations, if they differ from the above, would not be met anyway. The idea was also to set *something* up, something supposedly smaller, but at least have something. And we could see where we would go from there, if it turns out to work well and have the right people to run it.<br />
<br />
At the last openSUSE conference, in Nürnberg, back in September, Cornelius Schumacher (whom isn't only fame for his technical contributions to openSUSE and KDE, but also for being a member of the KDE board since quite some time) raised a funny question: do we really need a foundation ?<br />
<br />
At first, I thought (and replied): well, yes, of course we do. Oh well :)<br />
<br />
Then we talked a bit about it, along with the insights and laser sharp view of Coolo, whom joined the discussion.<br />
<br />
Right now, my opinion is as follows:<br />
* the openSUSE board itself hasn't "stabilized" yet:<br />
** the openSUSE board, as it is now, hasn't been working optimally yet, to say the least: besides for this election (yay!), we barely had enough candidates to fill the seats, with one election even turning out not to be one, because the amount of candiates was equal to the amount of seats<br />
** we're still in a finding phase for the board, where the board itself (well, whomever is on the board) needs to be more proactive and find its right place in the community, and with "place" I mean activities and duties<br />
** the community, too, needs to find its place for the board, and bring up ideas, requests, missions to the board<br />
** I believe we might actually be able to do so with the coming term, but it is simply a thing that takes a little time to happen (as it showed to be the case for other boards in other open source projects too)<br />
* the situation has changed:<br />
** Attachmate has liberated SUSE from being the cash cow that saves the financial balance of one or another business unit of Novell and being moved around under structures that didn't necessarily make sense, into an entity of its own, with more control over its fate, and the ability to work better<br />
** there has already been quite some progress on the options for funding the openSUSE project through SUSE, thanks to the work behind the scenes of Andreas Jaeger and Alan Clark<br />
** we're quite positive that we will be able to achieve most goals we wanted the foundation to exist for through the current infrastructure, with SUSE as its main sponsor<br />
* a foundation bares a lot of risk, too:<br />
** if it turns out to not work well (e.g. not finding the right people to run it, not being able to find enough sponsors and funding, or even worse, abuse), the damage could be irreversible: there are no guarantees that we could simply go back to the current situation, none at all<br />
** a non-for-profit comes with an enormous legal framework it has to comply with, and that's not only something pretty much all of us don't like having to take care of, but it is also tedious, not fun, and quite abrasive as far as motivation is concerned<br />
** we will probably have to attract and have totally different people on the foundation board than the ones that are on the openSUSE board, most probably even people who aren't active in the project in the first place, because we will need people with experience and background on the matter, as well as specific skills (running after sponsors, managing the funds well, accounting)<br />
* it works pretty well as of now (as explained in a few points above):<br />
** it's not perfect, of course, and there is still quite some room for improvements, but<br />
** some of those improvements have already been implemented or are being worked on, as mentioned above, and we will surely be able to explain them in more detail in a near future<br />
<br />
Essentially, when weighing the pros and cons, I personally believe that the better option, right now, and in the context we have now, as opposed to some time ago when we decided to have a foundation, is to not have a foundation and work with the current model.<br />
<br />
Hey, only fools never change their mind ;)<br />
(and thanks again to Cornelius and Coolo for their wake-up call)<br />
<br />
That being said, it is still a worthwhile goal to pursue in terms of independence and I believe that a more optimal solution would be to have several major sponsors and not just one. But we should put it on ice and have the discussion again in 1 or 2 years from now, when the board will have taken its right spot in the bigger picture, when we can assess whether the possibilities with SUSE have worked well or not, and when we'll have more food for thought.<br />
<br />
== Minor Issues ==<br />
=== Ambassador program ===<br />
Right now, the Ambassador program is not very successful, especially in the way that it is a bit misleading. We keep running into people who believe that they must be Ambassadors in order to promote or participate in the project, or people who simply aren't connected to anyone else in the project and whom, hence, cannot really get what they need to do their activities efficiently.<br />
It is quite a bit of a chicken/egg issue too.<br />
<br />
I believe we should rather think about a more appropriate model for<br />
* people who want to promote openSUSE at conferences, LUGs, etc...<br />
* people who act as local contact points and coordinators amongst contributors<br />
<br />
Manu and Kostas have already put quite some thought about that in the past, and Kostas is actively working in a more apt concept, but I believe it should get more focus, more input, and more support.<br />
<br />
=== Collaboration ===<br />
With other distributions, that is. I believe that we're quite uniquely non hierarchical in our (lack of) structure, which is mostly a good thing, and for several reasons, we're a good middle ground to actively engage with other distribution projects to get more collaboration going on.<br />
<br />
There is simply too much duplication of work, lack of exchange of experience, too much not invented here syndrome happening. We can do better, as it will improve things for everyone: contributors and users. Less work, better quality.<br />
<br />
We have our differences, obviously, and that's good, but we have so much in common too.<br />
<br />
== Role of the board ==<br />
I already mentioned a few bits about that above and hence I won't reiterate everything here, I know I'm already way to verbose :D<br />
<br />
Basically:<br />
* caretaking of the community aspects of the community<br />
* actively think about initiatives, discussions, and proposals of solutions about matters that revolve around the human aspects of our community<br />
<br />
And, well, everything I wrote above :)<br />
<br />
==Why you should vote for me?==<br />
I have been actively contributing to this project for quite some time now and I do have quite a network of people I know, met, talked to at length, exchanged ideas with, learned from, and appreciate deeply. That is quite an essential part of the puzzle, especially if the goal is to concentrate more on the "people" aspects of the community.<br />
Due to my activities outside of openSUSE, and most specifically FOSDEM, I also have quite a few connections to people in the larger realm of open source.<br />
I've seen the openSUSE project evolve over time, from an outsiders perspective during S.u.S.E. times to an insider role at its very core.<br />
<br />
It could also be a drawback, because of tunnel vision, lack of fresh ideas, etc..., but I have also been in touch with people who do bring that fresh air into the project recently, and have really started to take a step back to try to get a bigger picture of things. Tunnel vision may always happen though, but that is why we all need to talk with each other :)<br />
<br />
I think that my track record in terms of contributions speaks for itself, especially in the more technical/developer part of things. I am both having a deep understanding of technical things as well as caring for the human aspects.<br />
<br />
I've been told to be a pretty good listener too, and I do my best to always have an open ear. I believe that emotions are equally important as actions and facts, because everything is emotion, perception and subjective anyway. As I would like the board to move a lot more into community support, I believe that it is a necessary quality. Yes, I deeply care about the people in this project, at least equally as much as for the more "technical" aspects.<br />
<br />
Also, I believe that I have a pretty good idea of how the board should evolve, and I'm a pretty pragmatic person -- not that I don't have any ideals or things I believe in, but let's try to find solutions that work.<br />
<br />
And last but not least, you can count on me for staying honest and keeping others honest if needed, care about giving credit where it's due, and deeply care about our project in general.<br />
<br />
== Aims/Goals ==<br />
I won't mention any aims or goals of technical nature, as that is totally irrelevant for the openSUSE board (as the board, by its very definition, a definition I contributed to shape up, may not have or take any influence on technical aspects, unless if conflict resolution is needed.)<br />
<br />
We need to do a better job at supporting people and ideas within our project, through our experience, our qualities and our networks in it.<br />
<br />
Generally speaking, and most of them being at least outlined above, my goals are clearly on the people side of things within our project. I want to do my best at making our project a nicer, friendlier place to spend time in, to do, to learn, to have feedback, and just to spend time with friends in.<br />
<br />
== Endorsements ==<br />
''Room for your supporters to leave a word about you''</div>Pbleserhttps://en.opensuse.org/index.php?title=openSUSE:Board_election_2011_platform_template_yaloki&diff=47029openSUSE:Board election 2011 platform template yaloki2011-12-01T23:56:02Z<p>Pbleser: filled out the rest! :)</p>
<hr />
<div>{{Board navbar}}<br />
== Platform ==<br />
{{Info|'''Note:''' This page is used by the candidate of the board election as a platform to show his views and answer some standard questions. }}<br />
<br />
==Introduction and Biography==<br />
[[File:pascal_bleser_osc11.jpg|thumb|Me at the openSUSE Conference 2011]]<br />
<br />
Hi! My name is Pascal Bleser and I'm currently 36 years old. I live in the east of Belgium with my wife and our two children (Gaëlle is 6, and Thomas is 3).<br />
<br />
My native languages are French and German, my Dutch is extremely rusty, my English is pretty fluent, I know how to order a beer in Croatian, and I know a few curse words in other languages, but that probably doesn't count :)<br />
<br />
* My email address is my first name, then a dot, then my last name at opensuse.org,<br />
* [http://dev-loki.blogspot.com my blog is here],<br />
* my [https://twitter.com/#!/yaloki tweety tweets are there],<br />
* my [irc://irc.freenode.net/yaloki,isnick IRC nickname on freenode is yaloki],<br />
* and [https://picasaweb.google.com/117680951975244630647/ photos of my holidays, kittens and the openSUSE conference are over here].<br />
<br />
I have been working as a software engineer for a large independent software vendor which is currently named Atos Worldline at their site in Aachen (Germany), in a great team where we mostly develop high performance systems in Java for the purpose of security, cryptography, payment, banking, telecoms, etc... In essence, it means I'm a very good Java hacker :)<br />
<br />
As far as my involvement in open source projects goes, it concentrates mostly on two things: obviously the openSUSE project, but also the [http://fosdem.org FOSDEM conference].<br />
<br />
I have been involved with openSUSE since the very beginning, and have even been contributing things when it was still S.u.S.E., which was much harder back then, needless to say.<br />
<br />
I have mostly been contributing packages since the beginning of times (which means something like 10 years, I can't even remember): I first had my own repository of packages (the "guru repository", in case anyone remembers) which was used by a massive amount of people. Later on it was merged with [http://packman.links2linux.org Packman] to avoid duplication of work and provide a better experience to users. I obviously also joined the Packman project and I have and still am creating and maintaining an endless amount of packages there, with the likes of good people like Detlef Reichelt, Manfred Tremmel, Herbert Graeber, to name a few.<br />
I actually developed the whole [http://packman.links2linux.org website of Packman] together with Marc Schiffbauer a long time ago, it was PHP4, I still remember the pain :)<br />
<br />
I have participated in several hackweeks in Nürnberg, and attended and spoken at the openSUSE conferences too, which has often given me the opportunity of meeting many of the fine people in our community, including at SUSE (often around many beers, obviously ;)), several of which I even consider to be good friends. I participated in a few specific workshops, including the one that resulted in [http://en.opensuse.org/openSUSE:Strategy the current openSUSE strategy].<br />
<br />
I have served the community on what I like to call the "bootstrap board", as well as on the first and second board terms as I was elected to do so. After two consecutive terms, I stepped back (as the terms of the board requires -- a rule I actually insisted on ^^) and am now posing my candidacy for the upcoming board.<br />
<br />
As far as contributions go, I have also implemented and am still maintaining the [http://planet.opensuse.org Planet openSUSE] aggregator, as well as taking care of the opensu.se server (which includes the [http://opensuse-community.org/Main_Page opensuse-community wiki] as well as [http://r.opensu.se the repo link shortener] and [http://i.opensu.se the 1-click-installer automater], an idea of [http://lizards.opensuse.org/author/bmwiedemann/ Bernhard Wiedemann], the genius behind [http://openqa.opensuse.org openQA]), together with my good friend Marcus "darix" Rueckert, whom is never tired of doing so many essential things for this project.<br />
<br />
Benjamin Weber and I also developed the openSUSE software portal project, which is currently defunct, and on which I have been working on a replacement since way too long.<br />
<br />
My other main contribution to open source at large is my involvement as a core organization team member of [http://fosdem.org FOSDEM], which is the best and largest open source contributor conference in Europe (and probably on this planet).<br />
<br />
I have been deeply involved there as part of a team of great people and friends since many years (too many to count, I think it's since 2004), mostly taking care of the developer rooms and gently pushing open source projects together to work together, which culminates in the concept of the "distribution mini-conference". As such, I have been in touch with many great people who are at the center of many open source projects, and have a strong culture of working together rather than fighting, especially in the realm of Linux distributions. People in Fedora, Debian, Mageia, etc... (yes, that list would really be too long :)) are our friends, our allies, in an undertaking for the greater good of people and technology.<br />
<br />
FOSDEM means many hours of sleepless nights, and that my wife is very understanding, but it is an essential tool for a very long list of open source projects that get the opportunity of being there and, more importantly, for people to meet, exchange ideas, and, well, have way too many Belgian beers.<br />
<br />
Generally speaking, I have evolved from concentrating on technical bits to enjoying the people part of such projects more than anything else. I truly and deeply believe that as much as we are producing excellent technical elements such as our great openSUSE distribution, it is all about the people, the environment in which we spend so much time doing hard work for no other retribution than the fun of doing it, the good feeling of doing something great, the excellence at which we do, or any other reason that is specific to every single person.<br />
<br />
That must happen in the realm of friends, of people with whom we can talk, people we can trust. Essentially, it must be a fun place.<br />
<br />
Of course, people with great ideas, or hard work, or experience in specific domains, or just with their heart and guts into what they do, they are the ones who make the difference, and they are key to our project, but if it isn't in an environment that is welcoming, friendly, where what people do is recognized as such, then it is pointless. Well, at least, it is what I believe.<br />
<br />
== Major Issues ==<br />
=== Environment and diversity ===<br />
Won't be the first time I'm saying this, but to me, the prime priority is about the environment we spend our time and efforts in. It must be rewarding, it must be fun, it must be amongst a group of friends.<br />
<br />
Right now, the project and the people therein are not sufficiently approachable, not sufficiently "human". Most of us are just emails or IRC nicknames, and that's not quite good enough, as that, amongst other things, puts a needless barrier for entry.<br />
<br />
I have seen the evolution of the project and its community for a very long time now (at least on the scale of a project like openSUSE :)), and I believe we're at a potential turning point right now. A lot of great people have been joining the project lately, focusing on non- or less technical aspects, bringing a lot of skills, energy, enthusiasm and ideas. It is very refreshing and they don't quite have the visibility and network they ought to have.<br />
<br />
Do we have an "openSUSE mold" in which you have to fit in order to be accepted?<br />
Most probably, as most communities have, and probably in an unconscious manner.<br />
<br />
Do we need to break it, change it ?<br />
We should certainly be aware of that influencing our behavior and respect or lack thereof for certain contributors in the project. I believe we should evolve from there into something more open and more encompassing, because diversity is always an improvement, for everyone. It's not just about men and women, it's also about nationalities and culture, languages, technical and non-technical contributors. It's even a point of view I don't only believe in as a human being, but also as an engineer: more (purposeful and constructive) points of view and experience is better. More input is better. Take some more time to discuss and have the better solution.<br />
<br />
=== Communication ===<br />
Specifically, now, it's the elephant in the room. Information needs to be spread out, not contained into micro communities in the community. This is really something we must put a lot of effort in, because<br />
* it avoids needless duplication of work (better to work together)<br />
* it can put more people with ideas, experience, time, skills on the matter at hands into the loop, and hence turn out into a better solution<br />
* we are pretty bad at showing what we're good at, and we are very good at quite a few things (no, it's not for bragging or for distrowars, surely not -- instead, it is quite motivating)<br />
<br />
We have way too many communication channels, on one side, and we also have too much confined information. We cannot expect people to help and contribute if we don't spread out information about what's going on in the first place.<br />
<br />
=== Community caretaking ===<br />
On paper, we do have a community manager as well as a boosters team, and even a board but, effectively, I believe that no one is currently really (pro)actively taking care of the community aspects of the community.<br />
<br />
That is communicating with people, taking care of our communication channels (not accepting bikeshedding has been talked about recently), helping out and mentoring our teams, putting people together where it makes sense. Have a trustworthy landing base where people feel they can get in touch with, to ask for support, to complain about situations that are not fair or that keep them from developing themselves in the project.<br />
<br />
I believe that the board should be morphed into something like that. The community nannies, if you will :)<br />
<br />
=== Mentoring ===<br />
(Or the lack thereof.)<br />
Gregory Zysk, and most probably other people before him, and certainly other people after him, has proposed mentoring as a topic we should think about as a project. I agree and believe that mentoring is particularly important to take away fears (of not being accepted, of failing, or caused by lack of self-confidence, ...) of engaging with our community.<br />
<br />
It would simply make a huge difference to have a person that<br />
* takes some time to talk to you,<br />
* take your hand and guide you through the project and its people,<br />
* knows whom to put you in touch with for this and that,<br />
* has a network in the community,<br />
* listens.<br />
<br />
A few of us are already doing this on an occasional (or not so occasional) basis, but we can do better, and put some thought into designing a landing spot for people who'd like to join us, but would like to have some assistance in doing so.<br />
<br />
So let's not let that good idea fade away.<br />
<br />
=== Leadership ===<br />
This is a pretty tricky one to explain. I mean leadership in a positive way, not in a dictatorial or top-down way :)<br />
<br />
Our project enjoys a pretty unstructured, "just do it" (to cite Henne), informal, bottom-up way of doing things. We don't have a ton of committees, of deciders, of structure and processes. And that, I believe, is an excellent thing. It is primordial to keep it that way, because that, I think, is actually what most people really enjoy here. Meritocracy really works, with a few caveats we need to be aware of and work on (the mold thing I wrote about above, and the hurdles for getting into the project as a contributor.)<br />
<br />
But sometimes, we lack direction, visibility, some hand holding (without its negative connotation). With leadership, I mean that we need more people to step forward a bit and facilitate decisions and directions. Not take those decisions, but help them happen. Leadership by example, of course, and by merit, obviously.<br />
<br />
=== Foundation ===<br />
It is obviously a topic that deserves a few words on its own.<br />
<br />
I was actually the one who pushed for having an openSUSE foundation (as a non-for-profit) when I was on the board, even though the first one who vocally mentioned the idea was Martin Lasarsch, quite some time ago (Martin, I totally miss you in the project).<br />
<br />
The goal was and still is very clear, even though it probably has not been sufficiently communicated since then: act as a recipient for funding and donations because, at that time, there was no possibility for individuals and other sponsors to contribute money to the openSUSE project through Novell. The idea is to be able to use those funds in order to support activities in the project where our current sponsors would not be interested in, or could not provide money for, for reasons of budgeting or political reasons (as in, being a company in the US, where software patents are enforced, where DMCA exists, etc...). Examples would be hosting infrastructure for things that cannot be hosted at opensuse.org, or fund travels and expenses for Ambassadors, etc...<br />
<br />
Since then, it has probably become everything to everyone, and the expectations are high (trademark ownership, control the project "independently", etc...). But those expectations, if they differ from the above, would not be met anyway. The idea was also to set *something* up, something supposedly smaller, but at least have something. And we could see where we would go from there, if it turns out to work well and have the right people to run it.<br />
<br />
At the last openSUSE conference, in Nürnberg, back in September, Cornelius Schumacher (whom isn't only fame for his technical contributions to openSUSE and KDE, but also for being a member of the KDE board since quite some time) raised a funny question: do we really need a foundation ?<br />
<br />
At first, I thought (and replied): well, yes, of course we do. Oh well :)<br />
<br />
Then we talked a bit about it, along with the insights and laser sharp view of Coolo, whom joined the discussion.<br />
<br />
Right now, my opinion is as follows:<br />
* the openSUSE board itself hasn't "stabilized" yet:<br />
** the openSUSE board, as it is now, hasn't been working optimally yet, to say the least: besides for this election (yay!), we barely had enough candidates to fill the seats, with one election even turning out not to be one, because the amount of candiates was equal to the amount of seats<br />
** we're still in a finding phase for the board, where the board itself (well, whomever is on the board) needs to be more proactive and find its right place in the community, and with "place" I mean activities and duties<br />
** the community, too, needs to find its place for the board, and bring up ideas, requests, missions to the board<br />
** I believe we might actually be able to do so with the coming term, but it is simply a thing that takes a little time to happen (as it showed to be the case for other boards in other open source projects too)<br />
* the situation has changed:<br />
** Attachmate has liberated SUSE from being the cash cow that saves the financial balance of one or another business unit of Novell and being moved around under structures that didn't necessarily make sense, into an entity of its own, with more control over its fate, and the ability to work better<br />
** there has already been quite some progress on the options for funding the openSUSE project through SUSE, thanks to the work behind the scenes of Andreas Jaeger and Alan Clark<br />
** we're quite positive that we will be able to achieve most goals we wanted the foundation to exist for through the current infrastructure, with SUSE as its main sponsor<br />
* a foundation bares a lot of risk, too:<br />
** if it turns out to not work well (e.g. not finding the right people to run it, not being able to find enough sponsors and funding, or even worse, abuse), the damage could be irreversible: there are no guarantees that we could simply go back to the current situation, none at all<br />
** a non-for-profit comes with an enormous legal framework it has to comply with, and that's not only something pretty much all of us don't like having to take care of, but it is also tedious, not fun, and quite abrasive as far as motivation is concerned<br />
** we will probably have to attract and have totally different people on the foundation board than the ones that are on the openSUSE board, most probably even people who aren't active in the project in the first place, because we will need people with experience and background on the matter, as well as specific skills (running after sponsors, managing the funds well, accounting)<br />
* it works pretty well as of now (as explained in a few points above):<br />
** it's not perfect, of course, and there is still quite some room for improvements, but<br />
** some of those improvements have already been implemented or are being worked on, as mentioned above, and we will surely be able to explain them in more detail in a near future<br />
<br />
Essentially, when weighing the pros and cons, I personally believe that the better option, right now, and in the context we have now, as opposed to some time ago when we decided to have a foundation, is to not have a foundation and work with the current model.<br />
<br />
Hey, only fools never change their mind ;)<br />
(and thanks again to Cornelius and Coolo for their wake-up call)<br />
<br />
== Minor Issues ==<br />
=== Ambassador program ===<br />
Right now, the Ambassador program is not very successful, especially in the way that it is a bit misleading. We keep running into people who believe that they must be Ambassadors in order to promote or participate in the project, or people who simply aren't connected to anyone else in the project and whom, hence, cannot really get what they need to do their activities efficiently.<br />
It is quite a bit of a chicken/egg issue too.<br />
<br />
I believe we should rather think about a more appropriate model for<br />
* people who want to promote openSUSE at conferences, LUGs, etc...<br />
* people who act as local contact points and coordinators amongst contributors<br />
<br />
Manu and Kostas have already put quite some thought about that in the past, and Kostas is actively working in a more apt concept, but I believe it should get more focus, more input, and more support.<br />
<br />
=== Collaboration ===<br />
With other distributions, that is. I believe that we're quite uniquely non hierarchical in our (lack of) structure, which is mostly a good thing, and for several reasons, we're a good middle ground to actively engage with other distribution projects to get more collaboration going on.<br />
<br />
There is simply too much duplication of work, lack of exchange of experience, too much not invented here syndrome happening. We can do better, as it will improve things for everyone: contributors and users. Less work, better quality.<br />
<br />
We have our differences, obviously, and that's good, but we have so much in common too.<br />
<br />
== Role of the board ==<br />
I already mentioned a few bits about that above and hence I won't reiterate everything here, I know I'm already way to verbose :D<br />
<br />
Basically:<br />
* caretaking of the community aspects of the community<br />
* actively think about initiatives, discussions, and proposals of solutions about matters that revolve around the human aspects of our community<br />
<br />
And, well, everything I wrote above :)<br />
<br />
==Why you should vote for me?==<br />
I have been actively contributing to this project for quite some time now and I do have quite a network of people I know, met, talked to at length, exchanged ideas with, learned from, and appreciate deeply. That is quite an essential part of the puzzle, especially if the goal is to concentrate more on the "people" aspects of the community.<br />
Due to my activities outside of openSUSE, and most specifically FOSDEM, I also have quite a few connections to people in the larger realm of open source.<br />
I've seen the openSUSE project evolve over time, from an outsiders perspective during S.u.S.E. times to an insider role at its very core.<br />
<br />
It could also be a drawback, because of tunnel vision, lack of fresh ideas, etc..., but I have also been in touch with people who do bring that fresh air into the project recently, and have really started to take a step back to try to get a bigger picture of things. Tunnel vision may always happen though, but that is why we all need to talk with each other :)<br />
<br />
I think that my track record in terms of contributions speaks for itself, especially in the more technical/developer part of things. I am both having a deep understanding of technical things as well as caring for the human aspects.<br />
<br />
I've been told to be a pretty good listener too, and I do my best to always have an open ear. I believe that emotions are equally important as actions and facts, because everything is emotion, perception and subjective anyway. As I would like the board to move a lot more into community support, I believe that it is a necessary quality. Yes, I deeply care about the people in this project, at least equally as much as for the more "technical" aspects.<br />
<br />
Also, I believe that I have a pretty good idea of how the board should evolve, and I'm a pretty pragmatic person -- not that I don't have any ideals or things I believe in, but let's try to find solutions that work.<br />
<br />
And last but not least, you can count on me for staying honest and keeping others honest if needed, care about giving credit where it's due, and deeply care about our project in general.<br />
<br />
== Aims/Goals ==<br />
I won't mention any aims or goals of technical nature, as that is totally irrelevant for the openSUSE board (as the board, by its very definition, a definition I contributed to shape up, may not have or take any influence on technical aspects, unless if conflict resolution is needed.)<br />
<br />
We need to do a better job at supporting people and ideas within our project, through our experience, our qualities and our networks in it.<br />
<br />
Generally speaking, and most of them being at least outlined above, my goals are clearly on the people side of things within our project. I want to do my best at making our project a nicer, friendlier place to spend time in, to do, to learn, to have feedback, and just to spend time with friends in.<br />
<br />
== Endorsements ==<br />
''Room for your supporters to leave a word about you''</div>Pbleserhttps://en.opensuse.org/index.php?title=openSUSE:Board_election_2011_platform_template_yaloki&diff=46878openSUSE:Board election 2011 platform template yaloki2011-11-27T11:08:26Z<p>Pbleser: added a photo</p>
<hr />
<div>{{Board navbar}}<br />
== Platform ==<br />
{{Info|'''Note:''' This page is used by the candidate of the board election as a platform to show his views and answer some standard questions. }}<br />
<br />
==Introduction and Biography==<br />
[[File:pascal_bleser_osc11.jpg|thumb|Me at the openSUSE Conference 2011]]<br />
<br />
Hi! My name is Pascal Bleser and I'm currently 36 years old. I live in the east of Belgium with my wife and our two children (Gaëlle is 6, and Thomas is 3).<br />
<br />
My native languages are French and German, my Dutch is extremely rusty, my English is pretty fluent, I know how to order a beer in Croatian, and I know a few curse words in other languages, but that probably doesn't count :)<br />
<br />
* My email address is my first name, then a dot, then my last name at opensuse.org,<br />
* [http://dev-loki.blogspot.com my blog is here],<br />
* my [https://twitter.com/#!/yaloki tweety tweets are there],<br />
* my [irc://irc.freenode.net/yaloki,isnick IRC nickname on freenode is yaloki],<br />
* and [https://picasaweb.google.com/117680951975244630647/ photos of my holidays, kittens and the openSUSE conference are over here].<br />
<br />
I have been working as a software engineer for a large independent software vendor which is currently named Atos Worldline at their site in Aachen (Germany), in a great team where we mostly develop high performance systems in Java for the purpose of security, cryptography, payment, banking, telecoms, etc... In essence, it means I'm a very good Java hacker :)<br />
<br />
As far as my involvement in open source projects goes, it concentrates mostly on two things: obviously the openSUSE project, but also the [http://fosdem.org FOSDEM conference].<br />
<br />
I have been involved with openSUSE since the very beginning, and have even been contributing things when it was still S.u.S.E., which was much harder back then, needless to say.<br />
<br />
I have mostly been contributing packages since the beginning of times (which means something like 10 years, I can't even remember): I first had my own repository of packages (the "guru repository", in case anyone remembers) which was used by a massive amount of people. Later on it was merged with [http://packman.links2linux.org Packman] to avoid duplication of work and provide a better experience to users. I obviously also joined the Packman project and I have and still am creating and maintaining an endless amount of packages there, with the likes of good people like Detlef Reichelt, Manfred Tremmel, Herbert Graeber, to name a few.<br />
I actually developed the whole [http://packman.links2linux.org website of Packman] together with Marc Schiffbauer a long time ago, it was PHP4, I still remember the pain :)<br />
<br />
I have participated in several hackweeks in Nürnberg, and attended and spoken at the openSUSE conferences too, which has often given me the opportunity of meeting many of the fine people in our community, including at SUSE (often around many beers, obviously ;)), several of which I even consider to be good friends. I participated in a few specific workshops, including the one that resulted in [http://en.opensuse.org/openSUSE:Strategy the current openSUSE strategy].<br />
<br />
I have served the community on what I like to call the "bootstrap board", as well as on the first and second board terms as I was elected to do so. After two consecutive terms, I stepped back (as the terms of the board requires -- a rule I actually insisted on ^^) and am now posing my candidacy for the upcoming board.<br />
<br />
As far as contributions go, I have also implemented and am still maintaining the [http://planet.opensuse.org Planet openSUSE] aggregator, as well as taking care of the opensu.se server (which includes the [http://opensuse-community.org/Main_Page opensuse-community wiki] as well as [http://r.opensu.se the repo link shortener] and [http://i.opensu.se the 1-click-installer automater], an idea of [http://lizards.opensuse.org/author/bmwiedemann/ Bernhard Wiedemann], the genius behind [http://openqa.opensuse.org openQA]), together with my good friend Marcus "darix" Rueckert, whom is never tired of doing so many essential things for this project.<br />
<br />
Benjamin Weber and I also developed the openSUSE software portal project, which is currently defunct, and on which I have been working on a replacement since way too long.<br />
<br />
My other main contribution to open source at large is my involvement as a core organization team member of [http://fosdem.org FOSDEM], which is the best and largest open source contributor conference in Europe (and probably on this planet).<br />
<br />
I have been deeply involved there as part of a team of great people and friends since many years (too many to count, I think it's since 2004), mostly taking care of the developer rooms and gently pushing open source projects together to work together, which culminates in the concept of the "distribution mini-conference". As such, I have been in touch with many great people who are at the center of many open source projects, and have a strong culture of working together rather than fighting, especially in the realm of Linux distributions. People in Fedora, Debian, Mageia, etc... (yes, that list would really be too long :)) are our friends, our allies, in an undertaking for the greater good of people and technology.<br />
<br />
FOSDEM means many hours of sleepless nights, and that my wife is very understanding, but it is an essential tool for a very long list of open source projects that get the opportunity of being there and, more importantly, for people to meet, exchange ideas, and, well, have way too many Belgian beers.<br />
<br />
Generally speaking, I have evolved from concentrating on technical bits to enjoying the people part of such projects more than anything else. I truly and deeply believe that as much as we are producing excellent technical elements such as our great openSUSE distribution, it is all about the people, the environment in which we spend so much time doing hard work for no other retribution than the fun of doing it, the good feeling of doing something great, the excellence at which we do, or any other reason that is specific to every single person.<br />
<br />
That must happen in the realm of friends, of people with whom we can talk, people we can trust. Essentially, it must be a fun place.<br />
<br />
Of course, people with great ideas, or hard work, or experience in specific domains, or just with their heart and guts into what they do, they are the ones who make the difference, and they are key to our project, but if it isn't in an environment that is welcoming, friendly, where what people do is recognized as such, then it is pointless. Well, at least, it is what I believe.<br />
<br />
I will fill out the more interesting bits below very soon :)<br />
<br />
== Major Issues ==<br />
''Please list any issues you feel are of a high priority that need to be addressed by the Board and how you would like to address them should you be elected''<br />
<br />
<br />
<br />
== Minor Issues ==<br />
''Please list any issues you feel are of a medium/low priority that could be addressed by the Board and how you would like to address them should you be elected''<br />
<br />
<br />
<br />
== Role of the board ==<br />
''Please describe your vision for the Board and how you would like to see the Board shaped under your tenure''<br />
<br />
<br />
<br />
==Why you should vote for me?==<br />
<br />
<br />
<br />
== Aims/Goals ==<br />
''Please list your aims and goals for both the openSUSE project and also the openSUSE distribution. You may highlight specific projects within openSUSE or sow the seed for new ones.''<br />
<br />
<br />
== Endorsements ==<br />
''Room for your supporters to leave a word about you''</div>Pbleserhttps://en.opensuse.org/index.php?title=File:Pascal_bleser_osc11.jpg&diff=46877File:Pascal bleser osc11.jpg2011-11-27T11:06:21Z<p>Pbleser: Pascal Bleser at the openSUSE Conference 2011</p>
<hr />
<div>Pascal Bleser at the openSUSE Conference 2011</div>Pbleserhttps://en.opensuse.org/index.php?title=openSUSE:Board_election_2011_platform_template_yaloki&diff=46876openSUSE:Board election 2011 platform template yaloki2011-11-27T11:03:59Z<p>Pbleser: first brain dump!</p>
<hr />
<div>{{Board navbar}}<br />
== Platform ==<br />
{{Info|'''Note:''' This page is used by the candidate of the board election as a platform to show his views and answer some standard questions. }}<br />
<br />
==Introduction and Biography==<br />
Hi! My name is Pascal Bleser and I'm currently 36 years old. I live in the east of Belgium with my wife and our two children (Gaëlle is 6, and Thomas is 3).<br />
<br />
My native languages are French and German, my Dutch is extremely rusty, my English is pretty fluent, I know how to order a beer in Croatian, and I know a few curse words in other languages, but that probably doesn't count :)<br />
<br />
* My email address is my first name, then a dot, then my last name at opensuse.org,<br />
* [http://dev-loki.blogspot.com my blog is here],<br />
* my [https://twitter.com/#!/yaloki tweety tweets are there],<br />
* my [irc://irc.freenode.net/yaloki,isnick IRC nickname on freenode is yaloki],<br />
* and [https://picasaweb.google.com/117680951975244630647/ photos of my holidays, kittens and the openSUSE conference are over here].<br />
<br />
I have been working as a software engineer for a large independent software vendor which is currently named Atos Worldline at their site in Aachen (Germany), in a great team where we mostly develop high performance systems in Java for the purpose of security, cryptography, payment, banking, telecoms, etc... In essence, it means I'm a very good Java hacker :)<br />
<br />
As far as my involvement in open source projects goes, it concentrates mostly on two things: obviously the openSUSE project, but also the [http://fosdem.org FOSDEM conference].<br />
<br />
I have been involved with openSUSE since the very beginning, and have even been contributing things when it was still S.u.S.E., which was much harder back then, needless to say.<br />
<br />
I have mostly been contributing packages since the beginning of times (which means something like 10 years, I can't even remember): I first had my own repository of packages (the "guru repository", in case anyone remembers) which was used by a massive amount of people. Later on it was merged with [http://packman.links2linux.org Packman] to avoid duplication of work and provide a better experience to users. I obviously also joined the Packman project and I have and still am creating and maintaining an endless amount of packages there, with the likes of good people like Detlef Reichelt, Manfred Tremmel, Herbert Graeber, to name a few.<br />
I actually developed the whole [http://packman.links2linux.org website of Packman] together with Marc Schiffbauer a long time ago, it was PHP4, I still remember the pain :)<br />
<br />
I have participated in several hackweeks in Nürnberg, and attended and spoken at the openSUSE conferences too, which has often given me the opportunity of meeting many of the fine people in our community, including at SUSE (often around many beers, obviously ;)), several of which I even consider to be good friends. I participated in a few specific workshops, including the one that resulted in [http://en.opensuse.org/openSUSE:Strategy the current openSUSE strategy].<br />
<br />
I have served the community on what I like to call the "bootstrap board", as well as on the first and second board terms as I was elected to do so. After two consecutive terms, I stepped back (as the terms of the board requires -- a rule I actually insisted on ^^) and am now posing my candidacy for the upcoming board.<br />
<br />
As far as contributions go, I have also implemented and am still maintaining the [http://planet.opensuse.org Planet openSUSE] aggregator, as well as taking care of the opensu.se server (which includes the [http://opensuse-community.org/Main_Page opensuse-community wiki] as well as [http://r.opensu.se the repo link shortener] and [http://i.opensu.se the 1-click-installer automater], an idea of [http://lizards.opensuse.org/author/bmwiedemann/ Bernhard Wiedemann], the genius behind [http://openqa.opensuse.org openQA]), together with my good friend Marcus "darix" Rueckert, whom is never tired of doing so many essential things for this project.<br />
<br />
Benjamin Weber and I also developed the openSUSE software portal project, which is currently defunct, and on which I have been working on a replacement since way too long.<br />
<br />
My other main contribution to open source at large is my involvement as a core organization team member of [http://fosdem.org FOSDEM], which is the best and largest open source contributor conference in Europe (and probably on this planet).<br />
<br />
I have been deeply involved there as part of a team of great people and friends since many years (too many to count, I think it's since 2004), mostly taking care of the developer rooms and gently pushing open source projects together to work together, which culminates in the concept of the "distribution mini-conference". As such, I have been in touch with many great people who are at the center of many open source projects, and have a strong culture of working together rather than fighting, especially in the realm of Linux distributions. People in Fedora, Debian, Mageia, etc... (yes, that list would really be too long :)) are our friends, our allies, in an undertaking for the greater good of people and technology.<br />
<br />
FOSDEM means many hours of sleepless nights, and that my wife is very understanding, but it is an essential tool for a very long list of open source projects that get the opportunity of being there and, more importantly, for people to meet, exchange ideas, and, well, have way too many Belgian beers.<br />
<br />
Generally speaking, I have evolved from concentrating on technical bits to enjoying the people part of such projects more than anything else. I truly and deeply believe that as much as we are producing excellent technical elements such as our great openSUSE distribution, it is all about the people, the environment in which we spend so much time doing hard work for no other retribution than the fun of doing it, the good feeling of doing something great, the excellence at which we do, or any other reason that is specific to every single person.<br />
<br />
That must happen in the realm of friends, of people with whom we can talk, people we can trust. Essentially, it must be a fun place.<br />
<br />
Of course, people with great ideas, or hard work, or experience in specific domains, or just with their heart and guts into what they do, they are the ones who make the difference, and they are key to our project, but if it isn't in an environment that is welcoming, friendly, where what people do is recognized as such, then it is pointless. Well, at least, it is what I believe.<br />
<br />
I will fill out the more interesting bits below very soon :)<br />
<br />
== Major Issues ==<br />
''Please list any issues you feel are of a high priority that need to be addressed by the Board and how you would like to address them should you be elected''<br />
<br />
<br />
<br />
== Minor Issues ==<br />
''Please list any issues you feel are of a medium/low priority that could be addressed by the Board and how you would like to address them should you be elected''<br />
<br />
<br />
<br />
== Role of the board ==<br />
''Please describe your vision for the Board and how you would like to see the Board shaped under your tenure''<br />
<br />
<br />
<br />
==Why you should vote for me?==<br />
<br />
<br />
<br />
== Aims/Goals ==<br />
''Please list your aims and goals for both the openSUSE project and also the openSUSE distribution. You may highlight specific projects within openSUSE or sow the seed for new ones.''<br />
<br />
<br />
== Endorsements ==<br />
''Room for your supporters to leave a word about you''</div>Pbleserhttps://en.opensuse.org/index.php?title=Archive:Board_election_2011&diff=46455Archive:Board election 20112011-11-20T17:33:52Z<p>Pbleser: add Chuck and Will to the list, and add links to their emails on project</p>
<hr />
<div>{{Board navbar}}<br />
{{Intro|Board election 2011}}<br />
<br />
<br />
'''This is a draft page. This information on this page may not be correct. This page will be updated by the election committee once the committee is formed.'''<br />
<br />
== Candidates ==<br />
{{Info|'''Note:''' The persons with the most votes will be elected for the board. Note that no single organization or company can control more than 40 per cent of the electable board seats (more than 2 seats). Please read the [[openSUSE:Board_election_rules|full description of the election process]]. }}<br />
<br />
''This is the list of candidates so far (you can still stand up until the 24th!):''<br />
<br />
* Pascal Bleser (yaloki) [http://lists.opensuse.org/opensuse-project/2011-11/msg00127.html (announcement)]<br />
* Andrew Wafaa (FunkyPenguin) [http://lists.opensuse.org/opensuse-project/2011-11/msg00071.html (announcement)]<br />
* Marcus Moeller<br />
* Chuck Payne [http://lists.opensuse.org/opensuse-project/2011-11/msg00123.html (announcement)]<br />
* Will Stephenson (wstephenson) [http://lists.opensuse.org/opensuse-project/2011-11/msg00124.html (announcement)]<br />
<br />
<br />
[[openSUSE:Board_election_2011_platform_template|Platform template]]<br />
<br />
<!-- <br />
* [[User:Example|Example Full Name]], Candidate Title, pointer to blog [[Image:Example.png|230x20px|link=]] [[openSUSE:Example_board_election_platform|Platform]]<br />
<br />
<br />
Please check the candidates' platform pages to read more about their vision and plans. <br />
--><br />
----<br />
<br />
== Timeline == <br />
; 2011-10-28 (Phase 0)<br />
* Announcement of the openSUSE Board election for 2011.<br />
* Start of 4 week period to apply for an [[openSUSE:Members|openSUSE membership]] (in order to vote).<br />
* Start of 4 week phase to stand for a position in the [[openSUSE:Board|openSUSE Board]].<br />
; 2011-11-24 <br />
* Notification of intent to run, and application for an openSUSE membership close (end of phase 0).<br />
; 2011-11-25 (Phase 1) <br />
* Start of 1 week campaign for the candidates before the ballots open (campaign might be done until ballots close).<br />
; 2011-12-02 (Phase 2) <br />
* Ballots open<br />
; 2011-12-16 [http://www.timeanddate.com/worldclock/fixedtime.html?day=16&month=12&year=2011&hour=21&min=0&sec=0&p1=0]<br />
* Ballots close (end of phase 2)<br />
; 2011-12-19<br />
* Announcement of the results<br />
<br />
All phases start and end on the given dates at 12:00 [[wikipedia:Coordinated_Universal_Time|UTC]]. For an overview what time this is in different timezones use the links above.<br />
<br />
----<br />
<br />
== Election committee ==<br />
* [[User:bear454|James Mason]]<br />
* [[User:warlordfff|Kostas Koudaras]]<br />
* [[User:izabelvalverde|Izabel Valverde]]<br />
* [[User:bekun|Kai-Uwe Behrmann]]<br />
* [[User:digitaltomm|Thomas Schmidt]]<br />
<br />
=== Contact ===<br />
You can contact the committee using the mail address [mailto:election-officials@opensuse.org election-officials@opensuse.org]. <br />
<br />
----<br />
<br />
== Detailed explanation of all phases ==<br />
=== Phase 0: Notification of Intent to Run or nomination ===<br />
Only [[openSUSE:Members|openSUSE members]] have the right to run for a board seat, except if they are in the Election Committee. To stand for a position in the openSUSE board please send a mail to<br />
* [mailto:opensuse-project@opensuse.org opensuse-project@opensuse.org] '''and''' <br />
* [mailto:election-officials@opensuse.org election-officials@opensuse.org].<br />
<br />
In the application candidates should write a short introduction of themselves and probably a short manifesto/platform/program that gives answers to these topics: <br />
<br />
'''Goal statement, Past work summary, Future plans'''<br />
<br />
The election committee also needs the openSUSE username, irc nickname and a userpage in the wiki to reference the candidate. It is recommended that they blog about their candidacy as this will reach a much wider audience of voters. If their blog is not syndicated on [http://planet.opensuse.org Planet SUSE], please advise the committee who will ensure it does get added.<br />
<br />
Potential candidates are advised to read the [http://lwn.net/Articles/211548/ Board Member Application Mini-HOWTO] to get an idea of what is involved.<br />
<br />
Also, if you want to nominate somebody else, tell the election officials and they will contact the nominated person and ask whether s/he will run for the board.<br />
<br />
=== Phase 0: Application for an openSUSE membership ===<br />
To apply for a membership, applicants should read through [[openSUSE:Members#How_to_become_a_Member|How to become a member]] at the [[openSUSE:Members|membership page]]. <br />
<br />
{{Info|'''Note:''' Applicants need to apply as soon as possible to give the [[openSUSE:Membership officials|Membership officials]] enough time to review and approve/reject applications. Even if applicants meet the deadline, it may not be ensured that their openSUSE membership will be approved until just before the ballots open.}}<br />
<br />
=== Phase 1: Campaign ===<br />
During the campaign-phase there should be<br />
* plenty of blog entries on the upcoming election by the candidates<br />
* interviews with all candidates by the openSUSE news team<br />
* a moderated Q&A session on IRC possibly during one of the regular Project meetings or a separate meeting<br />
<br />
=== Phase 2: Election ===<br />
All persons with voting right will be able to [https://connect.opensuse.org/pg/polls/read/digitaltomm/10769/opensuse-board-election-2011 cast their votes] using [[openSUSE:Connect|openSUSE Connect]]. Once a vote has been submitted it may not be changed afterwards. All votes are stored anonymously in the electronic system.<br />
<br />
----<br />
<br />
== Seats to get elected ==<br />
<br />
In this election we will have 3 seats to get elected. Bryen Yunashko's seat is being vacated due to term limits and Pavol Rusnak and Rupert Horstkotter' are completing their first terms, thus eligible to run for a second term. All board members have a limit of two consecutive terms.<br />
<br />
----<br />
<br />
== External links ==<br />
<br />
=== Articles for candidates ===<br />
* [http://lwn.net/Articles/211548/ Board Member Application Mini-HOWTO] written by Federico Mena Quintera about the GNOME Foundation board<br />
* [http://zonker.opensuse.org/2009/11/18/what-does-the-opensuse-board-do/ What does the openSUSE Board do?]<br />
<br />
=== Related articles ===<br />
* [http://nowwhatthe.blogspot.com/2010/12/opensuse-board-elections.html Jos about the election]<br />
<br />
=== Similar elections ===<br />
* [http://www.debian.org/vote/2009/ Debian Project Leader Election 2009], [http://www.debian.org/vote/2009/platforms/ Platforms]<br />
* [https://fedoraproject.org/wiki/Board/Elections Fedora Board Elections 2009], [https://fedoraproject.org/wiki/Board/Elections/Nominations Nominations]<br />
<br />
[[Category:Board]]</div>Pbleserhttps://en.opensuse.org/index.php?title=openSUSE:GCI_tasks_2011&diff=44462openSUSE:GCI tasks 20112011-10-24T21:27:21Z<p>Pbleser: add Pbleser + factoid plugin task</p>
<hr />
<div><div class="center"><br />
[[File:GCI.jpg]]<br />
</div><br />
<br />
<br />
<div style="background-color:#E5E5E6;text-align:center;color:#000000"><br />
=== Mentors ===<br />
</div><br />
<br />
People willing to mentor students can sign up being a mentor in one or more categories below<br />
<br />
* Code writing or refactoring<br />
** {{User|Digitaltomm}}<br />
** [[User:Vuntz|Vincent Untz]]<br />
** [[User:Mbarringer|Matt Barringer]]<br />
** [[User:rjschwei|Robert Schweikert]]<br />
** [[User:Pbleser|Pascal Bleser]]<br />
* Documentation: Creating and editing documents<br />
** {{User|Mrdocs}}<br />
** [[User:rjschwei|Robert Schweikert]]<br />
** {{User|Diamond_gr}}<br />
** {{User|Warlordfff}}<br />
* Outreach: Community management and outreach, as well as marketing<br />
** {{User|Byunashko}}<br />
** {{User|Rlihm}}<br />
** [[User:Pbleser|Pascal Bleser]]<br />
* Quality Assurance: Testing and ensuring code is of high quality<br />
** {{User|RBrownCCB}}<br />
** [[User:Vuntz|Vincent Untz]]<br />
* Research: Studying a problem and recommending solutions<br />
** {{User|Digitaltomm}}<br />
** [[User:Mbarringer|Matt Barringer]]<br />
* Training: Helping others learn more<br />
** [[User:Vuntz|Vincent Untz]]<br />
** [[User:rjschwei|Robert Schweikert]]<br />
* Translation: Localization (adapting code to your region and language)<br />
** {{User|Warlordfff}}<br />
** {{User|Diamond_gr}}<br />
* User interface: User experience research or user interface design and interaction<br />
** {{User|Rlihm}}<br />
* Introductory to Packaging - Create your first openSUSE package<br />
** {{User|Mrdocs}}<br />
** [[User:Vuntz|Vincent Untz]]<br />
** [[User:rjschwei|Robert Schweikert]]<br />
** [[User:Pbleser|Pascal Bleser]]<br />
<div style="background-color:#E5E5E6;text-align:center;color:#000000"><br />
<br />
=== List Of Tasks ===<br />
</div><br />
<br />
One very useful resources of task list can be found at [[Junior_jobs]], however it can be restructured into tasks that suit more for GCI's reference for eg [http://wiki.sahanafoundation.org/doku.php/community:gci:gci2010ideas Sahana Foundation]<br />
<br />
Tasks are divided into 3 categories :- Easy, Medium and Difficult<br />
<br />
{| style="background:#d9e5bf;font-size:100%; border:1px solid #aaa;" border="1" cellpadding="2" cellspacing="3"<br />
!style="background:#fff;color:#669900"| Task<br />
!style="background:#fff;color:#669900"| Category<br />
!style="background:#fff;color:#669900"| Difficulty<br />
!style="background:#fff;color:#669900"| Status<br />
|-<br />
| Describe your task here, || Category of the task || Easy / difficult / medium || Claimed / Open / Reopened<br />
|-<br />
| Cleanup SUSEhelp factoids on IRC<br />
| Community & Outreach <br />
| Easy<br />
| Open<br />
|-<br />
| Assess and recommend improvements to workflow of online shop <br />
| Community & Outreach <br />
| Easy <br />
| Open<br />
|-<br />
| Investigate online resellers for online openSUSE Shop <br />
| Community & Outreach <br />
| Easy <br />
| Open<br />
|-<br />
| Create Geeko Plushie Campaign <br />
| Community & Outreach <br />
| Easy <br />
| Open<br />
|-<br />
| Improve the Bento Theme <br />
| User Interface <br />
| Hard <br />
| Open<br />
|-<br />
| Review marketing and ambassador wiki pages <br />
| Documentation <br />
| Easy <br />
| Open<br />
|-<br />
| Create Marketing Materials Artwork: <br />
| Community & Outreach <br />
| Easy <br />
| Open<br />
|-<br />
| Review Wiki Howtos (SDB Portals) for accuracy <br />
| Documentation <br />
| Medium <br />
| Open<br />
|-<br />
| Review Wiki 12.1 Portals for accuracy <br />
| Documentation <br />
| Medium <br />
| Open<br />
|-<br />
| Install a page counter for each page on the wiki <br />
| Documentation <br />
| Hard <br />
| Open<br />
|-<br />
| Review and build all KIWI examples as documented on the wiki <br />
| Documentation <br />
| Hard <br />
| Open<br />
|-<br />
| Propose improvements to openSUSE main page to improve navigation and usability <br />
| Documentation <br />
| Medium <br />
| Open<br />
|-<br />
| Translate .po files or wiki articles improving the localization of the Project<br />
| Translation/Documentation<br />
| Medium <br />
| Open<br />
|-<br />
| Evaluate, adapt, document or write a factoid plugin for supybot for our openSUSE IRC channels<br />
| Code writing or refactoring (python)<br />
| Hard<br />
| Open<br />
|}<br />
<br />
[[Category:Google Summer of Code]]<br />
__NOTOC__</div>Pbleserhttps://en.opensuse.org/index.php?title=openSUSE:What_to_improve_osc11_session&diff=44256openSUSE:What to improve osc11 session2011-10-19T23:14:27Z<p>Pbleser: added data about IRC channels</p>
<hr />
<div>During the [http://conference.opensuse.org openSUSE Conference 2011] a BoF session with the topic "What do we need to improve" took place. The discussion was framed such that we would not end up with a long "pie in the sky" list that cannot be implemented. The goal was to have items that are actionable in a reasonable (6 month to 1 year) time frame. The notes below contain the items discussed:<br />
<br />
= Eliminate iChain =<br />
== Reason ==<br />
* outdated<br />
* buggy<br />
* proprietary<br />
== Potential issues ==<br />
* This is a potential political issue, an there may be push-back from people within the Attachmate organization<br />
== Potential solution ==<br />
Using openID is a potential solution to replace iChain. Connect can be openID provider and we could tie things to Connect, i.e. someone would need a Connect account instead of having a Novell account today. The issue with Connect is that it currently uses iChain for authentication and can't act as openID provider while using iChain. So many people would need to set up their passwords. Also as it let's people to enter many information, it may provide false impression that all this is needed and scare some people away.<br />
<br />
== Action ==<br />
* Discuss in project meeting how we can go about this<br />
<br />
= Improve installer to handle multi boot =<br />
The multiboot installer is not working and an effort needs to be made to improve the situation. There is some work going on, but progress is slow as more helping hands are needed.<br />
== Action ==<br />
* FATE will be filed (BoF participant)<br />
* Helping hands are desperately needed, call for volunteers on factory list.<br />
<br />
There is a script lying around on the forum that reads the partitions and copy the needed information on menu.lst. I don't have the name of the script right now, but will try to find it [[User:Jdd|Jdd]] 01:11, 20 September 2011 (MDT)<br />
<br />
= Wiki =<br />
== More pages should be translated ==<br />
* There is no real entry barrier<br />
=== Problem ===<br />
* There is no priority to translate<br />
* There is no connection between translators<br />
* Translated pages need to be kept up to date, this is a long term commitment<br />
==== Potential solutions ====<br />
* Publish page views to generate some kind of ranking?<br />
* Make ranking available to translators?<br />
* Can we/ambassadors compile list of people working on translation?<br />
* When translators are connected maintenance should be easier as it can be done by committee<br />
== Improved usability/navigation ==<br />
=== Problem ===<br />
* We have a lot of documentation and information in the wiki, but it is difficult to access and find.<br />
* Information if a page is available in another language is hidden<br />
* There is no way to know if the translated page is up to date<br />
=== Potential solutions ===<br />
* Maybe setup topics in a B-tree like structure<br />
* Maybe display in a bar at the top of each page languages into which this page has been translated<br />
* Invent some kind of mechanism to inform people if translated page is up to date<br />
== Improve search ==<br />
=== Problem ===<br />
* Search is broken and we need a better solution<br />
** Example search for %{?suse_version} using the wiki search and the top result is a link related to SAMBA and not to packaging<br />
=== Potential solutions ===<br />
* Can we use Google?<br />
** Maybe pipe our search to Google in the background and just re-display the results that start with en.opensuse.org?<br />
** Use the Google engine (there maybe concerns about the license)<br />
* Make sure we allow the "public" Google crawler to crawl the wiki<br />
* Maybe have no search on wiki and point people to Google?<br />
== Actions ==<br />
* Discuss at next project meeting some details<br />
* Wiki team needs to get involved<br />
<br />
= openSUSE needs its own bugzilla =<br />
== Reason ==<br />
* Not having a bugzilla we control creates problems<br />
** Categorization is not what we would like<br />
** We are connected into iChain and Novell accounts<br />
** Cannot be themed<br />
** ...<br />
== Potential issues ==<br />
* This is a potential political issue, an there may be push-back from people within the Attachmate organization<br />
* Easy duplication/sharing of SLE bugs<br />
* What is the entry barrier to file a bug? (this is connected to the iChain discussion)<br />
** Having no entry barrier, i.e. no registration, potentially creates a flood of duplicates and invalid bugs<br />
== Status ==<br />
This issue was raised during last years SUSE Labs conference Jeff M. and Greg KH did the initial work to get an openSUSE bugzilla running.<br />
<br />
=== Jeff and Greg, insert status here please ===<br />
<br />
== Action ==<br />
* Determine current status<br />
* Discuss in project meeting once status is known<br />
<br />
= Improve communication infrastructure =<br />
== Reason ==<br />
* It appears that it is difficult to get information dispersed in the community<br />
** Too many mailing lists<br />
** Too many IRC channels<br />
== Problem ==<br />
* We need to agree what channels and lists should go away or be merged<br />
=== Discussed towards end of project meeting 2011-10-19 ===<br />
* Mailing lists<br />
** Message limit to get new list is not a favored approach<br />
*** tumbleweed appears to be working OK with sending related messages to factory (this does not imply that factory should be a "catch all" bucket). But this does not necessarily imply that this would work for other list "merges"<br />
** Possibly need some sort of evaluation on "related topics" such as<br />
*** maybe merge ''boosters'' with the ''project'' list<br />
*** maybe ''packaging'' should be merged with ''buildservice''<br />
*** maybe ''web'' and ''wiki'' should be merged<br />
*** it might also be easier to merge low volume lists than to merge two high volume lists<br />
*** it is possibly difficult to merge development specific lists such as ''ham'' and ''mobile'', while it might not be unreasonable to merge ''cloud'' and ''virtualization''<br />
** Thus the problem remains that even if we find someone willing to look at all the lists and come up with a proposal, what are the guideline we would provide to that person to develop the proposal?<br />
*** Related topics - yes<br />
*** Volume guideline?<br />
*** Number of subscribers?<br />
=== IRC Channels ===<br />
* [http://linux01.gwdg.de/~pbleser/files/opensuse-irc.html List of openSUSE/SUSE IRC channels as of 2011-10-19]<br />
* we have 82 channels, obviously way too much<br />
* most are almost empty<br />
* language specific channels must remain in place, for obvious reasons<br />
* #opensuse-packaging should be closed, as it's almost empty, and #opensuse-buildservice serves the same purpose (similar issue as to the similarly named mailing-lists)<br />
<br />
== Proposals ==<br />
* boosters channel and project channel should be merged<br />
* packaging channel and buildservice channel should be merged<br />
<br />
= Better usability/navigation of main page at www.opensuse.org =<br />
== Reason ==<br />
* Current site does not draw people in<br />
* Information is difficult to find<br />
== Action ==<br />
* Get web team involved<br />
* Discuss at project meetings<br />
<br />
[[Category:Conference]]<br />
[[Category:Osc11_session_notes]]</div>Pbleserhttps://en.opensuse.org/index.php?title=openSUSE:Countdown&diff=42053openSUSE:Countdown2011-08-07T23:54:29Z<p>Pbleser: added instructions for the opensuse conference counter</p>
<hr />
<div>{{Artwork navbar}}<br />
{{Intro|You can help spreading new release of openSUSE by adding these fabulous countdown timers to your website.}}<br />
<br />
==Introduction==<br />
The pictures are statically generated on the countdown.opensuse.org server by a cron job, updated at 12:00 CET. This approach optimizes the performance on the server and also enables Apache to serve HTTP cache-control headers properly.<br />
<br />
It is translated in many languages (english, german, czech, french, danish, russian, polish, dutch, finnish, spanish, italian, greek, swedish, croatian, norwegian, portuguese, hungarian, romanian, galician) and is automatically displayed in the language configured in the visitor's preferred language(s), with the same URL.<br />
<br />
==Usage==<br />
Just copy and paste the code under the picture into your webpage:<br />
<br />
===square, original (256x256)===<br />
http://countdown.opensuse.org/11.4/medium.en.png<br />
<br />
<nowiki><a href="http://en.opensuse.org/Portal:11.4"><img src="http://countdown.opensuse.org/11.4/medium" border="0"/></a></nowiki><br />
for wiki (XX is your language, eg. 'en'):<br />
<nowiki>[http://XX.opensuse.org/Portal:11.4 http://countdown.opensuse.org/11.4/medium.XX.png]</nowiki><br />
<br />
===square, small (130x130)===<br />
http://countdown.opensuse.org/11.4/small.en.png<br />
<br />
<nowiki><a href="http://en.opensuse.org/Portal:11.4"><img src="http://countdown.opensuse.org/11.4/small" border="0"/></a></nowiki><br />
for wiki (XX is your language, eg. 'en'):<br />
<nowiki>[http://XX.opensuse.org/Portal:11.4 http://countdown.opensuse.org/11.4/small.XX.png]</nowiki><br />
<br />
===square, large (400x400)===<br />
http://countdown.opensuse.org/11.4/large.en.png<br />
<br />
<nowiki><a href="http://en.opensuse.org/Portal:11.4"><img src="http://countdown.opensuse.org/11.4/large" border="0"/></a></nowiki><br />
for wiki (XX is your language, eg. 'en'):<br />
<nowiki>[http://XX.opensuse.org/Portal:11.4 http://countdown.opensuse.org/11.4/large.XX.png]</nowiki><br />
<br />
===Advanced version by Sylvester Lykkehus===<br />
<br />
<nowiki>http://solidonline.dk/11.3.php?red=<redval>&green=<greenval>&blue=<blueval>&alpha=<alphaval>&gamma=<gammaval>&lang=<lang>&size=<resx>x<resy></nowiki><br />
<br />
where<br />
<br />
* redval is 0 ... 255 (red value)<br />
* greenval is 0 ... 255 (green value)<br />
* blueval is 0 ... 255 (blue value)<br />
* alphaval is 0 ... 127 (alpha value)<br />
* gammaval is 0.1 ... 2.0 (gamma value)<br />
* lang is language (default en)<br />
* resx is 1 ... 256 (horizontal size)<br />
* resy is 1 ... 256 (vertical size)<br />
<br />
* example: http://solidonline.dk/11.4.php?red=127&green=0&blue=127&alpha=30&gamma=0.6&lang=jp<br />
<br />
* source: http://solidonline.dk/11.4.phps<br />
<br />
==Conference Countdown==<br />
There is another countdown counter for the [http://conference.opensuse.org openSUSE Conference].<br />
<br />
Just copy and paste the code under the picture into your webpage:<br />
<br />
===square, medium (256x256)===<br />
http://countdown.opensuse.org/conf/2011/medium.png<br />
<br />
<nowiki><a href="http://conference.opensuse.org"><img src="http://countdown.opensuse.org/conf/2011/medium" border="0"/></a></nowiki><br />
for wiki:<br />
<nowiki>[http://conference.opensuse.org/ http://countdown.opensuse.org/conf/2011/medium.png]</nowiki><br />
<br />
===square, large (400x400)===<br />
http://countdown.opensuse.org/conf/2011/large.png<br />
<br />
<nowiki><a href="http://conference.opensuse.org"><img src="http://countdown.opensuse.org/conf/2011/large" border="0"/></a></nowiki><br />
for wiki:<br />
<nowiki>[http://conference.opensuse.org/ http://countdown.opensuse.org/conf/2011/large.png]</nowiki><br />
<br />
===square, small (130x130)===<br />
http://countdown.opensuse.org/conf/2011/small.png<br />
<br />
<nowiki><a href="http://conference.opensuse.org"><img src="http://countdown.opensuse.org/conf/2011/small" border="0"/></a></nowiki><br />
for wiki:<br />
<nowiki>[http://conference.opensuse.org/ http://countdown.opensuse.org/conf/2011/small.png]</nowiki><br />
<br />
<br />
[[Category:Artwork]]<br />
<br />
[[de:Countdown]]<br />
[[ru:openSUSE:Обратный_отсчет]]<br />
[[pt: Countdown]]</div>Pbleserhttps://en.opensuse.org/index.php?title=openSUSE:Conference_Planning_2011&diff=38647openSUSE:Conference Planning 20112011-04-21T23:48:15Z<p>Pbleser: add link to meeting for 20110421</p>
<hr />
<div>{{Intro|This is the start of collecting information, requirements and ideas about the next openSUSE Conference. If you like to volunteer organizing, please add your name in the relevant sections. Please also add more information!}}<br />
<br />
== Program Committee meetings ==<br />
* [[openSUSE:Conference Planning 2011 Meeting 20110421|2011-04-21]]<br />
<br />
== Setup ==<br />
There is a proposal to have the SUSE Labs Conference and the openSUSE Conference together at the same time.<br />
<br />
=== Timeframe ===<br />
* We like to do this in 2011.<br />
* October is booked with other events.<br />
* Proposal: Wednesday to Saturday or Tuesday to Friday<br />
* Dates to avoid: <br />
** Desktop Summit, Aug 6-12<br />
** Linux Con NA, Aug 17-19<br />
** Novell Brainshare, Oct. 10-14<br />
** Linux Kernel Summit, Oct 24 - 26<br />
** Linux Con EU, Oct 26-28<br />
** Linux Con Brazil, Nov 17-18<br />
<br />
=== Background SUSE Labs Conference ===<br />
<br />
The SUSE Labs are a part of Novell OPS that consists of engineers working on areas like Linux Kernel, toolchain (GCC), X.org and Samba.<br />
<br />
In the past, this was the description of the SUSE Labs conference:<br />
The SUSE Labs conference is the occasion of the year where all the SUSE Labs hackers get together to meet face-to-face to share their knowledge and experience with each other and learn new things. People from Novell who work on related topics or who interact a lot with SUSE Labs are invited to the conference as well.<br />
<br />
The SUSE Labs conference usually is more closed than the openSUSE conference and while most sessions could be open, some do need to be closed off.<br />
<br />
== Teams ==<br />
<br />
* Location search team:<br />
** general: [[User:mrdocs|Peter Linnell]]<br />
** focus on Nuernberg: [[User:a_jaeger|Andreas Jaeger]]<br />
* Nuernberg local organization team:<br />
** handling accomodation, food, venue, <br />
** figure out logistics (transport hotel-faculty-hotel and around the city)<br />
* Program Committee: [[User:byunashko|Bryen Yunasko]], Alan Clark, [[User:jospoortvliet|Jos Poortvliet]], [[User:pbleser|Pascal Bleser]], [[User:vuntz|Vincent Untz]], [[User:Wstephenson|Will Stephenson]]<br />
* technical support (preparation of classrooms, audio-video equipment)<br />
* Promotion: Marketing Team<br />
* Dealing with sponsor: Izabel Valverde<br />
* Registration (setting up the registration process, checking people in at the conference, ...)<br />
* ''Please add more''<br />
<br />
== Venue/Location ==<br />
<br />
Requirements:<br />
* 400-500 people (last year: 300 at openSUSE conference, 100 at Labs conference)<br />
* 5 tracks and therefore:<br />
** 1 large room that fits all people<br />
** 4 smaller rooms<br />
*** at least one of which could be closed off (have a color on badges and someone check at the door?)<br />
* space to meet and talk<br />
* Inexpensive accommodation<br />
** preferably a hostel option close by with a range of rooms (1/2/4 ppl etc) so anyone can find something<br />
** accommodation preferably in walking distance of venue<br />
* Food in walking distance or available at the venue<br />
* Good wifi that can actually handle the 4-500 ppl<br />
<br />
== Sponsor ==<br />
<br />
What can we do to attract sponsors?<br />
* create a good sponsorship brochure and send it to our contacts<br />
* create specific benefits for sponsors, eg allowing them to attend the 'closed doors' SUSElabs meetings; organizing a networking dinner for sponsors & speakers<br />
** Caveat, it will not be possible for sponsors to attend all 'closed doors' SUSElabs meetings as some of these are truly private department internal meetings. Therefore, we have to be careful how this is worded.<br />
* have a tiered system with:<br />
** €0 student/home user admission<br />
** €250 professional admission (access to networking dinner)<br />
** €1000 small sponsor admission (access to networking dinner & SUSE Labs Meeting & banner on site & banner on site)<br />
** big sponsors get a few access passes to networking dinner & SUSE labs meeting besides the other benefits and get 1 minute lightning talk at the closing ceremony to introduce themselves and big banner(s) etc<br />
<br />
== High Priority Items ==<br />
<br />
At this point of time the main items are:<br />
* Finding venue (incl. time)<br />
* Finding Motto of the conference<br />
* Setting up of program committee<br />
<br />
== Conference Objectives ==<br />
# attract new contributors ("newcomers")<br />
# share expertise and knowledge, make workshops, brainstorm, which is more of an "inwards" perspective on us, what we do, and what we want to do (which includes what we suck at, what's badly missing, cool new ideas, and gather expertise from the very knowledgeable people in the project)<br />
# trigger collaboration with other projects and distributions<br />
# get to know each other<br />
<br />
== Open Questions ==<br />
Just a brainstorming list, feel free to sort and consolidate.<br />
<br />
* Can we collaborate not only with other Open Source communities and distributions but also with some other communities? Klaas suggested e.g. Geocacher or Open Street Map.<br />
* Linux Con EU and the Kernel Summit are both in Prague, maybe having the conference before or after might be beneficial.<br />
** We might get savings on the venue??<br />
** Save travel costs for Novell staff<br />
** We inquired after that already. The costs would be about 9000 per day for the venue excluding food (which is very expensive there). In other words, forget about that... Way outside of our budget.<br />
* We need keynote speakers<br />
* We need posters/handouts to announce conference time and call-for-paper<br />
* how to market/advertise/broadcast the event<br />
* what "sort" of contributors we would like to attract (and, hence, what topics/workshops to present)<br />
* hot topics<br />
* future topics<br />
* projects we want to collaborate with<br />
* social events<br />
* workshop-alike sessions with an introductory presentation and then have enough time (or another session later) to share ideas, experience, etc..?<br />
** Presenters just need to make sure that they make 2 or 3 slides with bullet points (not more than 4 per slide! ;)) about future directions and tasks, and how people can help.<br />
** And also be prepared to put a few things up for discussion.<br />
** There can't be collaboration if you're not ready to share your "baby."<br />
** be prepared to do some moderation or assign someone else in the room, if there are too many talks and ideas going on at the same time<br />
* Hold an un-conference or barcamp style session within the conference?<br />
* Time available to organize hackfests around the conference dates? ( Marketing hackfest to get the 12.1 release notes completed, QA, global Mxx test)</div>Pbleserhttps://en.opensuse.org/index.php?title=openSUSE:Conference_Planning_2011_Meeting_20110421&diff=38646openSUSE:Conference Planning 2011 Meeting 201104212011-04-21T23:47:53Z<p>Pbleser: Created page with "=openSUSE Conference 2011 team meeting 2011-04-21= The program committee for the openSUSE Conference 2011 held its first meeting today, on [irc://irc.freenode.net/opensuse-proje..."</p>
<hr />
<div>=openSUSE Conference 2011 team meeting 2011-04-21=<br />
<br />
The program committee for the openSUSE Conference 2011 held its first meeting today, on [irc://irc.freenode.net/opensuse-project #opensuse-project].<br />
<br />
The team consists of the following:<br />
* [[User:Vuntz|Vincent Untz]]<br />
* [[User:Byunashko|Bryen Yunashko]]<br />
* Alan Clark<br />
* [[User:Jospoortvliet|Jos Poortvliet]]<br />
* [[User:Wstephenson|Will Stephenson]]<br />
* [[User:Pbleser|Pascal Bleser]]<br />
<br />
Everyone was present, except [[User:Wstephenson|Will]] who couldn't attend at that time of day.<br />
<br />
The complete log is [http://community.opensuse.org/meetings/opensuse-project/2011/opensuse-project.2011-04-21-21.16.log.html available online], as well as the [http://community.opensuse.org/meetings/opensuse-project/2011/opensuse-project.2011-04-21-21.16.html summary of action items and decisions].<br />
<br />
==Topics==<br />
The predefined topics for this meeting were as follows:<br />
# Theme<br />
# Format<br />
As usual, a few more topics arose during the meeting.<br />
<br />
==Theme==<br />
The discussion around the theme of the conference revolved around two aspects:<br />
* the motto (or tag line) of the conference, with two proposals currently floating around:<br />
** "Collaboration across borders" (same as 2010)<br />
** "rwxrwxrwx" (openSUSE: read, write, execute, for you, the project, and the world)<br />
<br />
The debate mostly went about how much collaboration, and how much openSUSE centric sessions should be held.<br />
<br />
Collaboration is important in many ways:<br />
* openSUSE is an open minded project that actively seeks collaboration with other open source projects<br />
* doing so at the conference makes it more visible in the press and marketing wise in general (as in: we know it's like that, but not everyone knows nor sees us like that just yet)<br />
* of course, it also gives us opportunities to get in touch with other people and projects who are not in the openSUSE community and not directly contributing to openSUSE, but still of high interest for current or future undertakings of our project, as well as to mutually benefit both our project and other open source projects<br />
<br />
Nevertheless, the openSUSE Conference in 2010 was felt as not making up enough time for topics that are specific to our project. As such, we agree that the focus needs to be shifted a bit more towards openSUSE itself.<br />
<br />
The team agreed on the following:<br />
* the motto is not critical right now, and may still be decided upon later, especially as it also involves other people in the community, such as the marketing and artwork teams<br />
* the program committee will request the support of the openSUSE marketing team for the motto, albeit the general theme of the conference will be decided by the program committee; also, the final say on the motto will remain with the committee, but only to veto in if it does not match the theme<br />
* the program committee will have as goal to reach a ratio of around 2/3 of sessions being openSUSE centric, and 1/3 about collaboration with other projects<br />
* for sessions on collaboration, we will reach out to projects and people who work on things that have a direct connection with what we do<br />
<br />
[[User:Byunashko|Bryen]] will contact the marketing team to gather their support on the conference motto.<br />
<br />
==Format==<br />
We had a few discussions and ideas about the format of the conference -- more specifically, how to organize the schedule and the sessions themselves.<br />
<br />
We agreed on the following:<br />
* the program committee will write up guidelines and good practices for presentations and BoFs (or what we call "read-only" and "read/write" sessions, respectively) to provide some support for speakers<br />
* the program committee will put a strong focus and favor "read/write" session proposals, as we believe that it provides more value to the community, give more people a chance to chime in with their ideas and experience, and also because we are (or at least try to be) an open project without much bureaucracy<br />
<br />
==Venue==<br />
Neither the date nor the location of the conference are known at this time.<br />
<br />
[[User:A_jaeger|Andreas Jaeger]] is currently actively seeking options in the area of Nürnberg in Germany, and we hope to have a solution very soon.<br />
<br />
The venue will have to have at least 5 distinct rooms (of which one will be used by the SUSE Labs conference) to provide sufficient capacity for the attendees, as well as enough flexibility to organize the schedule.<br />
<br />
<br />
==Call for Papers==<br />
Not having the date nor the location at this point is a major hurdle for a Call for Papers. Indeed, most people will be reluctant to post a proposal if they don't know where and when.<br />
<br />
Nevertheless, making the Call for Papers is quite pressing, as it typically involves a somewhat longer period of time for people to send their proposals, as much as it needs to take a few days into account for the program committee to decide on those.<br />
<br />
[[User:Jospoortvliet|Jos]] will write up a draft for the Call for Papers, which will then be quickly circulated across the conference committee for amendments. It will not be published just yet, as we prefer to have a confirmation on the date and the location before we do (for the reasons mentioned above.)<br />
<br />
The next program committee is next week, where we will decide what to do with the Call for Papers (publish or wait for the confirmation of location and date), especially if location and date are not known at that time.<br />
<br />
Alan will send out emails to several openSUSE mailing-lists to ask for input on<br />
* current or upcoming topics, e.g. in terms of technology<br />
* major undertakings and tasks that need to be addressed soon, and where one or more sessions during the conference could be helpful for collective brainstorming<br />
* people/projects to invite for close collaboration during the conference (e.g. systemd, smolt, OBS, Fedora marketing team, etc...)<br />
<br />
The program committee will collect a few proposals for topics/tracks in order to facilitate the submission of sessions during the Call for Papers phase.<br />
<br />
==Infrastructure==<br />
The cfp@opensuse.org mailing-list will be used again to contact the program committee as well as to submit proposals after the publication of the CfP (unless we come up with a better solution in the mean time.) [[User:Byunashko|Bryen]] will contact Henne (our mailing-list admin) to configure the mailing-list for the program committee for 2011.<br />
<br />
We also agreed on using [http://cdsware.cern.ch/indico/ Indico] [http://conference.opensuse.org/indico//conferenceDisplay.py?confId=0 again], mostly because it is already in place.<br />
<br />
==Next meeting==<br />
The next meeting of the program committee is scheduled for next week, 2011-04-28, at 19:00 UTC.</div>Pbleserhttps://en.opensuse.org/index.php?title=openSUSE:Conference_Planning_2011&diff=38206openSUSE:Conference Planning 20112011-04-08T22:36:51Z<p>Pbleser: Pascal Bleser: add myself to the program committee</p>
<hr />
<div>{{Intro|This is the start of collecting information, requirements and ideas about the next openSUSE Conference. If you like to volunteer organizing, please add your name in the relevant sections. Please also add more information!}}<br />
<br />
== Setup ==<br />
There is a proposal to have the SUSE Labs Conference and the openSUSE Conference together at the same time.<br />
<br />
=== Timeframe ===<br />
* We like to do this in 2011.<br />
* October is booked with other events.<br />
* Proposal: Wednesday to Saturday or Tuesday to Friday<br />
* Dates to avoid: <br />
** Desktop Summit, Aug 6-12<br />
** Linux Con NA, Aug 17-19<br />
** Novell Brainshare, Oct. 10-14<br />
** Linux Kernel Summit, Oct 24 - 26<br />
** Linux Con EU, Oct 26-28<br />
** Linux Con Brazil, Nov 17-18<br />
<br />
=== Background SUSE Labs Conference ===<br />
<br />
The SUSE Labs are a part of Novell OPS that consists of engineers working on areas like Linux Kernel, toolchain (GCC), X.org and Samba.<br />
<br />
In the past, this was the description of the SUSE Labs conference:<br />
The SUSE Labs conference is the occasion of the year where all the SUSE Labs hackers get together to meet face-to-face to share their knowledge and experience with each other and learn new things. People from Novell who work on related topics or who interact a lot with SUSE Labs are invited to the conference as well.<br />
<br />
The SUSE Labs conference usually is more closed than the openSUSE conference and while most sessions could be open, some do need to be closed off.<br />
<br />
== Teams ==<br />
<br />
* Location search team:<br />
** general: [[User:mrdocs|Peter Linnell]]<br />
** focus on Nuernberg: [[User:a_jaeger|Andreas Jaeger]]<br />
* Program Committee: [[User:byunashko|Bryen Yunasko]], Alan Clark, [[User:jospoortvliet|Jos Poortvliet]], [[User:pbleser|Pascal Bleser]]<br />
* logistics (transport hotel-faculty-hotel and around the city)<br />
* technical support (preparation of classrooms, audio-video equipment)<br />
* Promotion: Marketing Team<br />
* Dealing with sponsor: Izabel Valverde<br />
* Registration (setting up the registration process, checking people in at the conference, ...)<br />
* ''Please add more''<br />
<br />
== Venue/Location ==<br />
<br />
Requirements:<br />
* 400-500 people (last year: 300 at openSUSE conference, 100 at Labs conference)<br />
* 5 tracks and therefore:<br />
** 1 large room that fits all people<br />
** 4 smaller rooms<br />
*** at least one of which could be closed off (have a color on badges and someone check at the door?)<br />
* space to meet and talk<br />
* Inexpensive accommodation<br />
** preferably a hostel option close by with a range of rooms (1/2/4 ppl etc) so anyone can find something<br />
** accommodation preferably in walking distance of venue<br />
* Food in walking distance or available at the venue<br />
* Good wifi that can actually handle the 4-500 ppl<br />
<br />
== Sponsor ==<br />
<br />
What can we do to attract sponsors?<br />
* create a good sponsorship brochure and send it to our contacts<br />
* create specific benefits for sponsors, eg allowing them to attend the 'closed doors' SUSElabs meetings; organizing a networking dinner for sponsors & speakers<br />
** Caveat, it will not be possible for sponsors to attend all 'closed doors' SUSElabs meetings as some of these are truly private department internal meetings. Therefore, we have to be careful how this is worded.<br />
* have a tiered system with:<br />
** €0 student/home user admission<br />
** €250 professional admission (access to networking dinner)<br />
** €1000 small sponsor admission (access to networking dinner & SUSE Labs Meeting & banner on site & banner on site)<br />
** big sponsors get a few access passes to networking dinner & SUSE labs meeting besides the other benefits and get 1 minute lightning talk at the closing ceremony to introduce themselves and big banner(s) etc<br />
<br />
== High Priority Items ==<br />
<br />
At this point of time the main items are:<br />
* Finding venue (incl. time)<br />
* Finding Motto of the conference<br />
* Setting up of program committee<br />
<br />
== Open Questions ==<br />
Just a brainstorming list, feel free to sort and consolidate.<br />
<br />
* What is the Motto of the conference?<br />
** Let's keep "Collaboration Across Borders", it fits us very well...<br />
* Can we collaborate not only with other Open Source communities and distributions but also with some other communities? Klaas suggested e.g. Geocacher or Open Street Map.<br />
* Linux Con EU and the Kernel Summit are both in Prague, maybe having the conference before or after might be beneficial.<br />
** We might get savings on the venue??<br />
** Save travel costs for Novell staff<br />
** We inquired after that already. The costs would be about 9000 per day for the venue excluding food (which is very expensive there). In other words, forget about that... Way outside of our budget.<br />
* We need keynote speakers<br />
* We need posters/handouts to announce conference time and call-for-paper</div>Pbleserhttps://en.opensuse.org/index.php?title=Additional_package_repositories&diff=36567Additional package repositories2011-03-13T00:26:21Z<p>Pbleser: rewrite instructions for Packman</p>
<hr />
<div>{{Repositories navbar}}<br />
<br />
{{Intro|This is a list of currently existing '''third-party repositories''', meaning they're external to openSUSE. These packages are not supported by openSUSE, the packages may not be tested and the repositories can contain beta versions and other bleeding edge packages.<br />
*For official repositories ('''OSS''', '''non-OSS''', '''updates''') and semi official repositories (including '''KDE''', '''GNOME''' and '''Java''' repositories) see [[Package repositories]].<br />
*For information on how to add package repositories see [[SDB:Add package repositories|Add package repositories]].<br />
*For new Linux and openSUSE users it is recommended to use the 3 default repositories (OSS, Non-OSS, Update) and Packman. Later on when you familiarize yourself with package management you can add more.<br />
* Please, make sure that you actually need a specific repository instead of blindly adding it. More repositories means more complexity in software management and needs some experience to avoid problems and, in extreme cases, system failure.<br />
}}<br />
{{Warning|Use it at your own risk.}} <br /> <br /> <br />
<br />
__TOC__<br />
<br />
==Popular external repositories==<br />
<br />
{{Info|To easily add the popular third-party repositories, see the [http://opensuse-community.org/Welcome_to_openSUSE-Community.org openSUSE Community] website.}}<br />
<br />
===Packman===<br />
[http://packman.links2linux.org Packman] offers various additional packages for openSUSE, especially but not limited to multimedia related applications and libraries. It's the largest external repository of openSUSE packages.<br />
<br />
The [http://packman.links2linux.org Packman project] provides four repositories that may be added individually:<br />
* [http://pmbs.links2linux.org/project/packages?project=Essentials Essentials]: provides codecs and audio and video player applications, to fulfil the most essential needs<br />
* [http://pmbs.links2linux.org/project/packages?project=Multimedia Multimedia]: contains many more multimedia related applications<br />
* [http://pmbs.links2linux.org/project/packages?project=Extra Extra]: additional non multimedia related applications, mostly network related<br />
* [http://pmbs.links2linux.org/project/packages?project=Games Games]: obviously, games<br />
<br />
Note that the three latter repositories are built upon and require [http://pmbs.links2linux.org/project/packages?project=Essentials Essentials] and, hence, if you add e.g. the Multimedia repository, you '''MUST''' also add the Essentials repository.<br />
<br />
Essentials is built for openSUSE 11.2, 11.3, 11.4, Factory, Tumbleweed and Evergreen (11.1), while the other repositories are only built for openSUSE 11.2, 11.3 and 11.4<br />
<br />
A list of [http://packman.links2linux.org/mirrors repository mirrors is available on the Packman site].<br />
<br />
Note that for reasons of convenience and personal preference, Packman also provides, for each distribution, a single repository that aggregates all the packages in the above mentioned repositories.<br />
<br />
Here is how to add the Packman repository for your distribution -- using Essentials and Multimedia in this example, where applicable (Factory, Tumbleweed and Evergreen_11.1 don't have Multimedia):<br />
<br />
{{Version note|Factory|Essentials<br />
<code>zypper ar -n packman-essentials http://packman.inode.at/suse/Factory/Essentials packman-essentials</code>}}<br />
{{Version note|Tumbleweed|Essentials<br />
<code>zypper ar -n packman-essentials http://packman.inode.at/suse/openSUSE_Tumbleweed/Essentials packman-essentials</code>}}<br />
{{Version note|11.4|Essentials and Multimedia<br />
<code>zypper ar -n packman-essentials http://packman.inode.at/suse/openSUSE_11.4/Essentials packman-essentials<br/><br />
>zypper ar -n packman-multimedia http://packman.inode.at/suse/openSUSE_11.4/Multimedia packman-multimedia</code>}}<br />
{{Version note|11.3|Essentials and Multimedia<br />
<code>zypper ar -n packman-essentials http://packman.inode.at/suse/openSUSE_11.3/Essentials packman-essentials<br/><br />
zypper ar -n packman-multimedia http://packman.inode.at/suse/openSUSE_11.3/Multimedia packman-multimedia</code>}}<br />
{{Version note|11.2|Essentials and Multimedia<br />
<code>zypper ar -n packman-essentials http://packman.inode.at/suse/openSUSE_11.2/Essentials packman-essentials<br/><br />
zypper ar -n packman-multimedia http://packman.inode.at/suse/openSUSE_11.2/Multimedia packman-multimedia</code>}}<br />
{{Version note|Evergreen 11.1|Essentials<br />
<code>zypper ar -n packman-essentials http://packman.inode.at/suse/openSUSE_Tumbleweed/Essentials packman-essentials</code>}}<br />
<br />
And here is how to add the all-in-one Packman repository (which doesn't make any difference for Factory, Tumbleweed and Evergreen_11.1):<br />
{{Version note|Factory|All of Packman<br />
<code>zypper ar -n packman http://packman.inode.at/suse/Factory packman</code>}}<br />
{{Version note|Tumbleweed|All of Packman<br />
<code>zypper ar -n packman http://packman.inode.at/suse/openSUSE_Tumbleweed packman</code>}}<br />
{{Version note|11.4|All of Packman<br />
<code>zypper ar -n packman http://packman.inode.at/suse/openSUSE_11.4 packman</code>}}<br />
{{Version note|11.3|All of Packman<br />
<code>zypper ar -n packman http://packman.inode.at/suse/openSUSE_11.3 packman</code>}}<br />
{{Version note|11.2|All of Packman<br />
<code>zypper ar -n packman http://packman.inode.at/suse/openSUSE_11.2 packman</code>}}<br />
{{Version note|Evergreen 11.1|All of Packman<br />
<code>zypper ar -n packman http://packman.inode.at/suse/openSUSE_Tumbleweed packman</code>}}<br />
<br />
To pick a mirror near you, please consult the [http://packman.links2linux.org/mirrors mirror list on the Packman site].<br />
<br />
===VLC VideoLan client===<br />
[http://download.videolan.org/pub/videolan/vlc/SuSE/ VLC Repositories] for openSUSE contains all the required libraries that are not shipped with original openSUSE. (Do Not Mix with Packman)<br />
<br />
{{Version note|Factory|http://download.videolan.org/pub/vlc/SuSE/Factory}}<br />
{{Version note|11.3|http://download.videolan.org/pub/vlc/SuSE/11.3}}<br />
{{Version note|11.2|http://download.videolan.org/pub/vlc/SuSE/11.2}}<br />
{{Version note|11.1|http://download.videolan.org/pub/vlc/SuSE/11.1}}<br />
<br />
===ATI video drivers===<br />
<br />
Proprietary drivers for ATI video cards. See the [[SDB:ATI|ATI install HOWTO]].<br />
<br />
{{Info|This repository is not browsable with a web browser and does not seem to be as up to date as the drivers they offer for download from the web site.}}<br />
<br />
{{Version note|11.3|http://www2.ati.com/suse/11.3/}}<br />
{{Version note|11.2|http://www2.ati.com/suse/11.2/}}<br />
{{Version note|11.1|http://www2.ati.com/suse/11.1/}}<br />
{{Version note|SLE 11|http://www2.ati.com/suse/sle11}}<br />
{{Version note|SLE 11 SP1|http://www2.ati.com/suse/sle11sp1}}<br />
{{Version note|SLE 10 SP2|http://www2.ati.com/suse/sle10sp2}}<br />
<br />
===NVIDIA drivers===<br />
<br />
Proprietary drivers for nVidia video cards. See the [[SDB:NVIDIA|nVidia install HOWTO]].<br />
<br />
{{Info|The nVidia repositories are only browseable via ftp.}}<br />
<br />
{{Version note|11.4|ftp://download.nvidia.com/opensuse/11.4/}}<br />
{{Version note|11.3|ftp://download.nvidia.com/opensuse/11.3/}}<br />
{{Version note|11.2|ftp://download.nvidia.com/opensuse/11.2/}}<br />
{{Version note|11.1|ftp://download.nvidia.com/opensuse/11.1/}}<br />
{{Version note|SLE 11 SP1|ftp://download.nvidia.com/novell/sle11sp1}}<br />
{{Version note|SLE 11|ftp://download.nvidia.com/novell/sle11}}<br />
{{Version note|SLE 10 SP3|ftp://download.nvidia.com/novell/sle10sp3}}<br />
{{Version note|SLE 10 SP2|ftp://download.nvidia.com/novell/sle10sp2}}<br />
{{Version note|SLE 10 SP1|ftp://download.nvidia.com/novell/sle10sp1}}<br />
{{Version note|SLE 10|ftp://download.nvidia.com/novell/sle10}}<br />
<br />
----<br />
<br />
==Other external repositories==<br />
<br />
=== j.eng ===<br />
<br />
This repository provides<br />
* Security and network related packages with enhancements<br />
* Linux kernel; functional realtime extension and Netfilter developments for state-of-the-art firewalls. Prebuilt packages for NVIDIA, fglrx, VMware, Virtualbox, etc..<br />
<br />
BSweb: http://build.medozas.de/<br />
<br />
{{Version note|11.3|http://jftp.medozas.de/openSUSE_11.3/}}<br />
{{Version note|11.2|http://jftp.medozas.de/DISCONTINUED/SUSE-11.2/}}<br />
{{Version note|11.1|http://jftp.medozas.de/DISCONTINUED/SUSE-11.1/}}<br />
<br />
----<br />
<br />
== Popular Build Service repositories ==<br />
<br />
The [[Portal:Build_Service|openSUSE Build Service]] contains a large variety of [http://download.opensuse.org/repositories additional repositories].<br />
<br />
<!-- Cleaned the big nightmare mess - feel free to re-add useful repositories --><br />
<br />
===Apache===<br />
openSUSE Build Service Repository for the Apache HTTP server. See the guides at [[Apache]].<br />
<br />
{{Version note|11.3|http://download.opensuse.org/repositories/Apache/openSUSE_11.3/}}<br />
{{Version note|11.2|http://download.opensuse.org/repositories/Apache/openSUSE_11.2/}}<br />
{{Version note|11.1|http://download.opensuse.org/repositories/Apache/openSUSE_11.1/}}<br />
{{Version note|SLE10|http://download.opensuse.org/repositories/Apache/SLE_10/}}<br/><br />
<br />
===Apache modules===<br />
Third-party apache modules built for the '''Build Service Apache'''.<br />
<br />
{{Version note|11.3|http://download.opensuse.org/repositories/Apache:/Modules/Apache_openSUSE_11.3/}}<br />
{{Version note|11.2|http://download.opensuse.org/repositories/Apache:/Modules/Apache_openSUSE_11.2/}}<br />
{{Version note|11.1|http://download.opensuse.org/repositories/Apache:/Modules/Apache_openSUSE_11.1/}}<br />
{{Version note|SLE10|http://download.opensuse.org/repositories/Apache:/Modules/Apache_SLE_10/}}<br />
<br />
{{Info|If you use the '''standard distro Apache''' and only want the modules from the Build Service, you'll find them here:}}<br />
{{Version note|11.3|http://download.opensuse.org/repositories/Apache:/Modules/openSUSE_11.3/}}<br />
{{Version note|11.2|http://download.opensuse.org/repositories/Apache:/Modules/openSUSE_11.2/}}<br />
{{Version note|11.1|http://download.opensuse.org/repositories/Apache:/Modules/openSUSE_11.1/}}<br />
{{Version note|SLE10|http://download.opensuse.org/repositories/Apache:/Modules/SLE_10/}}<br/><br />
<br />
===Apache PHP modules===<br />
There are variants. See the [[SDB:Linux_Apache_MySQL_PHP|LAMP guide]], for a separate page which will guide you to the correct PHP repository. <br />
<br />
If you use the Build Service Apache from above, you'll find the right mod_php for your system here.<br />
<br />
{{Version note|11.3|http://download.opensuse.org/repositories/server:/php/openSUSE_11.3/}}<br />
{{Version note|11.2|http://download.opensuse.org/repositories/server:/php/server_apache_openSUSE_11.2/}}<br />
{{Version note|11.1|http://download.opensuse.org/repositories/server:/php/server_apache_openSUSE_11.1/}}<br />
{{Version note|SLE10|http://download.opensuse.org/repositories/server:/php/server_apache_SLE_10/}}<br />
<br />
=== Mozilla ===<br />
Most recent versions of Firefox, Thunderbird, Seamonkey, etc.<br />
<br />
{{Version note|11.3|http://download.opensuse.org/repositories/mozilla/openSUSE_11.3/}}<br />
{{Version note|11.2|http://download.opensuse.org/repositories/mozilla/openSUSE_11.2/}}<br />
{{Version note|11.1|http://download.opensuse.org/repositories/mozilla/openSUSE_11.1/}}<br />
{{Version note|SLES 10|http://download.opensuse.org/repositories/mozilla/SLE_10/}}<br />
{{Version note|SLES 11|http://download.opensuse.org/repositories/mozilla/SLE_11/}}<br />
<br />
=== OpenOffice.org STABLE ===<br />
Updated and stable OpenOffice.org.<br />
<br />
{{Version note|11.3|http://download.opensuse.org/repositories/OpenOffice.org:/STABLE/openSUSE_11.3/}}<br />
{{Version note|11.2|http://download.opensuse.org/repositories/OpenOffice.org:/STABLE/openSUSE_11.2/}}<br />
{{Version note|11.1|http://download.opensuse.org/repositories/OpenOffice.org:/STABLE/openSUSE_11.1/}}<br />
{{Version note|SLED 11|http://download.opensuse.org/repositories/OpenOffice.org:/STABLE/SLE_11/}}<br />
{{Version note|SLED 10|http://download.opensuse.org/repositories/OpenOffice.org:/STABLE/SLED_10/}}<br />
<br />
=== Wine ===<br />
Most recent versions of Wine.<br />
<br />
{{Version note|11.3|http://download.opensuse.org/repositories/Emulators:/Wine/openSUSE_11.3/}}<br />
{{Version note|11.2|http://download.opensuse.org/repositories/Emulators:/Wine/openSUSE_11.2/}}<br />
{{Version note|11.1|http://download.opensuse.org/repositories/Emulators:/Wine/openSUSE_11.1/}}<br />
{{Version note|SLE-11|http://download.opensuse.org/repositories/Emulators:/Wine/SLE-11/}}<br />
<br />
----<br />
==See also==<br />
* [[Package repositories|Official repositories]]<br />
* [[SDB:Add package repositories|Add package repositories]]<br />
* [[SDB:Vendor_change_update|Vendor change update]]<br />
<br />
----<br />
<br />
==External links==<br />
* [http://download.opensuse.org/repositories/ openSUSE Build Service repositories]<br />
* [http://packages.opensuse-community.org/ Webpin Package Search]<br />
* [http://opensuse-community.org/Package_Sources openSUSE Community website]<br />
<br />
<br />
<br />
[[cs:Další_repozitáře_pro_Yast]]<br />
[[de:Zusätzliche_Paketquellen_für_YaST]]<br />
[[es:Additional_YaST_Package_Repositories]]<br />
[[fr:Additional_YaST_Package_Repositories]]<br />
[[it:Repository_Aggiuntivi_Per_YaST]]<br />
[[ja:Additional_YaST_Package_Repositories]]<br />
[[nl:Additional_YaST_Package_Repositories]]<br />
[[tr:Additional_YaST_Package_Repositories]]<br />
[[ru:Additional_YaST_Package_Repositories]]<br />
[[zh:第三方供应源]]<br />
<br />
[[Category:Repositories]]</div>Pbleserhttps://en.opensuse.org/index.php?title=openSUSE:Marketing_and_Artwork_repository&diff=34677openSUSE:Marketing and Artwork repository2011-02-16T20:26:50Z<p>Pbleser: correct removing files; add TODO; add section about moving files; a few other layout enhancements</p>
<hr />
<div>{{Marketing resources navbar}}<br />
<br />
We keep our marketing and artwork material in [http://gitorious.org/opensuse-artwork/opensuse-artwork our git repository at gitorious.org]. While a version control system such as [http://git-scm.com/ git] may seem daunting, it is by far the best option for collaborative authoring.<br />
<br />
==Initial setup==<br />
If you would like to modify or add material to our repository, you need to do the following things first:<br />
# [https://secure.gitorious.org/users/new register an account on gitorious.org], if you don't already have one<br />
# create an SSH (Secure Shell) key pair, if you don't already have one (<code>ssh-keygen -t rsa -b 2048</code> and just accept the defaults by typing the Return key, except when it asks you to pick a passphrase, which is like a password, choose a good one there!)<br />
# paste your SSH public key (<code>~/.ssh/id_rsa.pub</code>) into your gitorious account, here: https://secure.gitorious.org/~XXX/keys/new (where you replace XXX with your gitorious account name) -- to paste it, you may proceed as follows:<br />
## <code>less ~/.ssh/id_rsa.pub</code><br />
## select the content with your mouse<br />
## switch to your browser and paste it there (right-click your mouse)<br />
# ask [mailto:pascal.bleser@opensuse.org Pascal Bleser] or [mailto:bruno.friedmann@opensuse.org Bruno Friedmann] (or on admin@opensuse.org) to add your user account to the [http://gitorious.org/+opensuse-artwork opensuse-artwork team on gitorious], which will give you write access to the [http://gitorious.org/opensuse-artwork/opensuse-artwork opensuse-artwork repository]<br />
# install <code>git</code> (<code>zypper install git</code>), if you don't have it already<br />
# run the following commands in a shell:<br />
## <code>git config user.email ''my.email.address@opensuse.org''</code> (obviously with your real email address ;))<br />
## <code>git config user.name "''John Doe''"</code> (again, with your real name)<br />
# pick some directory where you'll want the files to reside, e.g. <code>~/Documents</code> and go there in your shell, e.g. <code>cd ~/Documents</code><br />
# retrieve the repository with the following command: <code>git clone git@gitorious.org:opensuse-artwork/opensuse-artwork.git</code> (which will create a subdirectory "opensuse-artwork")<br />
<br />
==Workflow==<br />
===Getting the latest changes===<br />
In order to pull the latest changes that have been stored in the repository, use the following command:<br />
<br />
<code>git pull</code><br />
<br />
That will download the latest version of everything that is in the repository on gitorious, and store it on your disk.<br />
<br />
Of course, that command needs to be ran from a shell while being in your local <code>opensuse-artwork</code> directory (e.g. <code>~/Documents/opensuse-artwork</code>)<br />
<br />
===Adding new files or directories===<br />
When you create a new file or directory, you have to tell <code>git</code> that you would like to add it to the repository first, using the following command:<br />
<br />
<code>git add ''filename''</code><br />
<br />
(where you replace ''filename'' with the actual name of the file or directory you want to add).<br />
<br />
Note that adding a file does not upload it to the repository yet, it merely instructs <code>git</code> that you want to put it under version control.<br />
<br />
===Committing changes===<br />
When you change files and you would like to store their state in the repository (e.g. when you think it's good enough to be used by others), use the following command:<br />
<br />
<code>git commit -m "some comment about the change I just made" ''filename''</code><br />
<br />
Please use meaningful comments (what's after <code>-m</code>) as that will help everyone to keep track of the changes that were made. Also, make sure to put the comment into quotes (between "") or the shell will interpret it as several parameters for the <code>git</code> command, which it isn't.<br />
<br />
You can also commit changes of several files at once, which is the preferred approach when the changes do apply to several files (e.g. you just changed the color palette on a dozen Inkscape files): that way, your changes will show up as one "action" in the history of the repository.<br />
<br />
To do so, just pass several filenames to the <code>git commit</code> command, like this:<br />
<br />
<code>git commit -m "changed palette to the right colors" ''filename1'' ''filename2'' ''filename3''</code><br />
<br />
You can also commit all the changes to all the files in your local copy of the repository, by using the <code>-a</code> switch, like this:<br />
<br />
<code>git commit -m "changed palette to Bento colors" -a</code><br />
<br />
===Pushing changes===<br />
When you commit changes, <code>git</code> will only store them in your local repository on your hard disk, and not to the [http://gitorious.org/opensuse-artwork/opensuse-artwork opensuse-artwork repository on gitorious], which means that no one else will be able to see your changes.<br />
<br />
<code>git</code> works that way because you may choose to make changes locally, on your hard disk, and keep track of those changes to be able to revert to a previous version, without necessarily pushing those changes to all the other people who work on the repository just yet.<br />
<br />
Once you want to share your changes with everyone else, you must "push" those changes to the repository, with the following command:<br />
<br />
<code>git push</code><br />
<br />
Note that the ''very first time'' you will do a <code>git push</code>, you will have to use this command: <code>git push origin master</code><br />
<br />
From then on, you will only need to use <code>git push</code><br />
<br />
Furthermore, when you want to push your changes to gitorious, it is possible that someone else already pushed other changes there. <code>git</code> will tell you see when that happened, and you will just need to make a <code>git pull</code> before the <code>git push</code><br />
<br />
===Status===<br />
With the command <code>git status</code>, you can see whether you have files on your hard disk that have changes (or new files, or deleted files) that have not been committed yet.<br />
<br />
Example:<br />
<br />
<code>git status</code><br />
<br />
would output something like this:<br />
<pre># On branch master<br />
# Changed but not updated:<br />
# (use "git add <file>..." to update what will be committed)<br />
# (use "git checkout -- <file>..." to discard changes in working directory)<br />
#<br />
# modified: git-mini-howto.txt<br />
#<br />
no changes added to commit (use "git add" and/or "git commit -a")<br />
</pre><br />
<br />
The output above means that the file <code>git-mini-howto.txt</code> is locally modified: you have made changes to that file, but those changes are not committed (yet).<br />
<br />
===Removing files===<br />
If you want to delete a file from the repository, use <code>git rm</code> instead of removing it as you would normally do (using <code>rm ''filename''</code> or your favourite file browser), like this:<br />
<br />
<code>git rm ''filename''</code><br />
<br />
Removing a file is just yet another change for <code>git</code> and, hence, to commit the change: <code>git commit -m "removed that file, it's obsolete now" ''filename''</code> (or the other <code>commit</code> commands as explained above, such as <code>git commit -a -m "..."</code>)<br />
<br />
To push that change to gitorious, for everyone: <code>git push</code><br />
<br />
===Renaming or moving files or directories===<br />
When you want to rename a file or directory, or move it elsewhere, do not use the regular command-line or file manager options to do so. If you do that, <code>git</code> will consider the renamed/moved file to be a new one and hence will lose the history of changes.<br />
<br />
The proper way of doing so is by using <code>git mv</code>, like this:<br />
<br />
<code>git mv ''old_filename'' ''new_filename''</code><br />
<br />
As usual, you will need to <code>commit</code> and <code>push</code> for that change to be visible for everyone.<br />
<br />
===History===<br />
One of the most obvious advantages of version control systems such as <code>git</code> is the ability to see the history of a file, which is a log of the modifications that have been made, with the commit messages (see the <code>-m</code> option for <code>git commit</code>), when changes were made and by whom.<br />
<br />
To see the history of a file, use the following command:<br />
<br />
<code>git log ''filename''</code><br />
<br />
That will display something like this:<br />
<pre>commit bbcf4e3a848d65fc28d1fb6d20d0ce7add040a33<br />
Author: Pascal Bleser <pascal.bleser@opensuse.org><br />
Date: Tue Feb 15 23:46:11 2011 +0100<br />
<br />
add LICENSE<br />
</pre><br />
<br />
There is only one change on the file above, but it shows<br />
* whom made the change: Pascal Bleser<br />
* when that change was made: Tue Feb 15<br />
* what was changed (the commit message): "add LICENSE"<br />
<br />
You can also see the all the changes, of the whole repository (and not just of a single file), by using<br />
<br />
<code>git log</code><br />
<br />
(without passing a file name)<br />
<br />
Please note that <code>git log</code> commands automatically put the output into a pager (normally that is <code>/usr/bin/less</code>), which gives you the ability to navigate the output (with expected keys, such as arrow up, arrow down, page up, page down, ...). To leave the pager and return to the shell, simply press the key "q" (mnemonics: "q" as in "quit").<br />
<br />
<code>git log</code> has quite a few more options, which you can read about by typing <code>git log --help</code> (also opens in the pager, press "q" to quit.)<br />
<br />
==TODO==<br />
* document how to retrieve previous revisions of a file (<code>git checkout</code>)<br />
* document how to reset your working environment to the state of the repository, to remove all your local changes (<code>git reset --hard</code>)<br />
* mention graphical user interfaces (<code>gitk</code>, <code>qgit</code>, ...)<br />
* link to other howtos, cheat sheets, etc, such as http://cheat.errtheblog.com/s/git<br />
<br />
[[Category:Marketing artwork]]<br />
[[Category:Artwork]]</div>Pbleserhttps://en.opensuse.org/index.php?title=openSUSE:Marketing_and_Artwork_repository&diff=34656openSUSE:Marketing and Artwork repository2011-02-15T23:43:48Z<p>Pbleser: add section about removing files</p>
<hr />
<div>We keep our marketing and artwork material in [http://gitorious.org/opensuse-artwork/opensuse-artwork our git repository at gitorious.org]. While a version control system such as [http://git-scm.com/ git] may seem daunting, it is by far the best option for collaborative authoring.<br />
<br />
==Initial setup==<br />
If you would like to modify or add material to our repository, you need to do the following things first:<br />
# [https://secure.gitorious.org/users/new register an account on gitorious.org], if you don't already have one<br />
# create an SSH (Secure Shell) key pair, if you don't already have one (<code>ssh-keygen -t rsa -b 2048</code> and just accept the defaults by typing the Return key, except when it asks you to pick a passphrase, which is like a password, choose a good one there!)<br />
# paste your SSH public key (<code>~/.ssh/id_rsa.pub</code>) into your gitorious account, here: https://secure.gitorious.org/~XXX/keys/new (where you replace XXX with your gitorious account name) -- to paste it, you may proceed as follows:<br />
## <code>less ~/.ssh/id_rsa.pub</code><br />
## select the content with your mouse<br />
## switch to your browser and paste it there (right-click your mouse)<br />
# ask [mailto:pascal.bleser@opensuse.org Pascal Bleser] or [mailto:bruno.friedmann@opensuse.org Bruno Friedmann] (or on admin@opensuse.org) to add your user account to the [http://gitorious.org/+opensuse-artwork opensuse-artwork team on gitorious], which will give you write access to the [http://gitorious.org/opensuse-artwork/opensuse-artwork opensuse-artwork repository]<br />
# install <code>git</code> (<code>zypper install git</code>), if you don't have it already<br />
# run the following commands in a shell:<br />
## <code>git config user.email my.email.address@opensuse.org</code> (obviously with your real email address ;))<br />
## <code>git config user.name "John Doe"</code> (again, with your real name)<br />
# pick some directory where you'll want the files to reside, e.g. <code>~/Documents</code> and go there in your shell, e.g. <code>cd ~/Documents</code><br />
# retrieve the repository with the following command: <code>git clone git@gitorious.org:opensuse-artwork/opensuse-artwork.git</code> (which will create a subdirectory "opensuse-artwork")<br />
<br />
==Workflow==<br />
===Getting the latest changes===<br />
In order to pull the latest changes that have been stored in the repository, use the following command: <code>git pull</code><br />
That will download the latest version of everything that is in the repository on gitorious, and store it on your disk.<br />
<br />
Of course, that command needs to be ran from a shell while being in your local <code>opensuse-artwork</code> directory (e.g. <code>~/Documents/opensuse-artwork</code>)<br />
<br />
===Adding new files===<br />
When you create a new file, you have to tell <code>git</code> that you would like to add it to the repository first, using the following command: <code>git add filename</code> (where you replace filename with the actual name of the file you want to add).<br />
<br />
Note that adding a file does not upload it to the repository yet, it merely instructs <code>git</code> that you want to put it under version control.<br />
<br />
===Committing changes===<br />
When you change files and you would like to store their state in the repository (e.g. when you think it's good enough to be used by others), use the following command:<br />
<br />
<code>git commit -m "some comment about the change I just made" filename</code><br />
<br />
Please use meaningful comments (what's after <code>-m</code>) as that will help everyone to keep track of the changes that were made. Also, make sure to put the comment into quotes (between "") or the shell will interpret it as several parameters for the <code>git</code> command, which it isn't.<br />
<br />
You can also commit changes of several files at once, which is the preferred approach when the changes do apply to several files (e.g. you just changed the color palette on a dozen inkscape files): that way, your changes will show up as one "action" in the history of the repository.<br />
<br />
To do so, just pass several filenames to the <code>git commit</code> command, like this:<br />
<br />
<code>git commit -m "changed palette to the right colors" filename1 filename2 filename3</code><br />
<br />
You can also commit all the changes to all the files in your local copy of the repository, by using the <code>-a</code> switch, like this:<br />
<br />
<code>git commit -m "changed palette to Bento colors" -a</code><br />
<br />
===Pushing changes===<br />
When you commit changes, <code>git</code> will only store them in your local repository on your hard disk, and not to the [http://gitorious.org/opensuse-artwork/opensuse-artwork opensuse-artwork repository on gitorious], which means that no one else will be able to see your changes.<br />
<br />
<code>git</code> works that way because you may choose to make changes locally, on your hard disk, and keep track of those changes to be able to revert to a previous version, without necessarily pushing those changes to all the other people who work on the repository just yet.<br />
<br />
Once you want to share your changes with everyone else, you must "push" those changes to the repository, with the following command:<br />
<br />
<code>git push</code><br />
<br />
Note that the ''very first time'' you will do a <code>git push</code>, you will have to use this command: <code>git push origin master</code><br />
<br />
From then on, you will only need to use <code>git push</code><br />
<br />
Furthermore, when you want to push your changes to gitorious, it is possible that someone else already pushed other changes there. <code>git</code> will tell you see when that happened, and you will just need to make a <code>git pull</code> before the <code>git push</code><br />
<br />
===Status===<br />
With the command <code>git status</code>, you can see whether you have files on your hard disk that have changes (or new files, or deleted files) that have not been committed yet.<br />
<br />
===Removing files===<br />
If you want to delete a file from the repository, simply remove it from your hard disk (using <code>rm ''filename''</code> or your favourite file browser), as it is just another change for <code>git</code>.<br />
<br />
To commit the change: <code>git commit -m "removed that file, it's obsolete now" ''filename''</code> (or the other <code>commit</code> commands as explained above)<br />
<br />
To push that change to gitorious, for everyone: <code>git push</code></div>Pbleserhttps://en.opensuse.org/index.php?title=openSUSE:Marketing_and_Artwork_repository&diff=34655openSUSE:Marketing and Artwork repository2011-02-15T23:38:46Z<p>Pbleser: add help for pasting the ssh pubkey</p>
<hr />
<div>We keep our marketing and artwork material in [http://gitorious.org/opensuse-artwork/opensuse-artwork our git repository at gitorious.org]. While a version control system such as [http://git-scm.com/ git] may seem daunting, it is by far the best option for collaborative authoring.<br />
<br />
==Initial setup==<br />
If you would like to modify or add material to our repository, you need to do the following things first:<br />
# [https://secure.gitorious.org/users/new register an account on gitorious.org], if you don't already have one<br />
# create an SSH (Secure Shell) key pair, if you don't already have one (<code>ssh-keygen -t rsa -b 2048</code> and just accept the defaults by typing the Return key, except when it asks you to pick a passphrase, which is like a password, choose a good one there!)<br />
# paste your SSH public key (<code>~/.ssh/id_rsa.pub</code>) into your gitorious account, here: https://secure.gitorious.org/~XXX/keys/new (where you replace XXX with your gitorious account name) -- to paste it, you may proceed as follows:<br />
## <code>less ~/.ssh/id_rsa.pub</code><br />
## select the content with your mouse<br />
## switch to your browser and paste it there (right-click your mouse)<br />
# ask [mailto:pascal.bleser@opensuse.org Pascal Bleser] or [mailto:bruno.friedmann@opensuse.org Bruno Friedmann] (or on admin@opensuse.org) to add your user account to the [http://gitorious.org/+opensuse-artwork opensuse-artwork team on gitorious], which will give you write access to the [http://gitorious.org/opensuse-artwork/opensuse-artwork opensuse-artwork repository]<br />
# install <code>git</code> (<code>zypper install git</code>), if you don't have it already<br />
# run the following commands in a shell:<br />
## <code>git config user.email my.email.address@opensuse.org</code> (obviously with your real email address ;))<br />
## <code>git config user.name "John Doe"</code> (again, with your real name)<br />
# pick some directory where you'll want the files to reside, e.g. <code>~/Documents</code> and go there in your shell, e.g. <code>cd ~/Documents</code><br />
# retrieve the repository with the following command: <code>git clone git@gitorious.org:opensuse-artwork/opensuse-artwork.git</code> (which will create a subdirectory "opensuse-artwork")<br />
<br />
==Workflow==<br />
===Getting the latest changes===<br />
In order to pull the latest changes that have been stored in the repository, use the following command: <code>git pull</code><br />
That will download the latest version of everything that is in the repository on gitorious, and store it on your disk.<br />
<br />
Of course, that command needs to be ran from a shell while being in your local <code>opensuse-artwork</code> directory (e.g. <code>~/Documents/opensuse-artwork</code>)<br />
<br />
===Adding new files===<br />
When you create a new file, you have to tell <code>git</code> that you would like to add it to the repository first, using the following command: <code>git add filename</code> (where you replace filename with the actual name of the file you want to add).<br />
<br />
Note that adding a file does not upload it to the repository yet, it merely instructs <code>git</code> that you want to put it under version control.<br />
<br />
===Committing changes===<br />
When you change files and you would like to store their state in the repository (e.g. when you think it's good enough to be used by others), use the following command:<br />
<br />
<code>git commit -m "some comment about the change I just made" filename</code><br />
<br />
Please use meaningful comments (what's after <code>-m</code>) as that will help everyone to keep track of the changes that were made. Also, make sure to put the comment into quotes (between "") or the shell will interpret it as several parameters for the <code>git</code> command, which it isn't.<br />
<br />
You can also commit changes of several files at once, which is the preferred approach when the changes do apply to several files (e.g. you just changed the color palette on a dozen inkscape files): that way, your changes will show up as one "action" in the history of the repository.<br />
<br />
To do so, just pass several filenames to the <code>git commit</code> command, like this:<br />
<br />
<code>git commit -m "changed palette to the right colors" filename1 filename2 filename3</code><br />
<br />
You can also commit all the changes to all the files in your local copy of the repository, by using the <code>-a</code> switch, like this:<br />
<br />
<code>git commit -m "changed palette to Bento colors" -a</code><br />
<br />
===Pushing changes===<br />
When you commit changes, <code>git</code> will only store them in your local repository on your hard disk, and not to the [http://gitorious.org/opensuse-artwork/opensuse-artwork opensuse-artwork repository on gitorious], which means that no one else will be able to see your changes.<br />
<br />
<code>git</code> works that way because you may choose to make changes locally, on your hard disk, and keep track of those changes to be able to revert to a previous version, without necessarily pushing those changes to all the other people who work on the repository just yet.<br />
<br />
Once you want to share your changes with everyone else, you must "push" those changes to the repository, with the following command:<br />
<br />
<code>git push</code><br />
<br />
Note that the ''very first time'' you will do a <code>git push</code>, you will have to use this command: <code>git push origin master</code><br />
<br />
From then on, you will only need to use <code>git push</code><br />
<br />
===Status===<br />
With the command <code>git status</code>, you can see whether you have files on your hard disk that have changes (or new files, or deleted files) that have not been committed yet.</div>Pbleserhttps://en.opensuse.org/index.php?title=openSUSE:Marketing_and_Artwork_repository&diff=34654openSUSE:Marketing and Artwork repository2011-02-15T23:34:28Z<p>Pbleser: add some more commands</p>
<hr />
<div>We keep our marketing and artwork material in [http://gitorious.org/opensuse-artwork/opensuse-artwork our git repository at gitorious.org]. While a version control system such as [http://git-scm.com/ git] may seem daunting, it is by far the best option for collaborative authoring.<br />
<br />
==Initial setup==<br />
If you would like to modify or add material to our repository, you need to do the following things first:<br />
* [https://secure.gitorious.org/users/new register an account on gitorious.org], if you don't already have one<br />
* create an SSH (Secure Shell) key pair, if you don't already have one (<code>ssh-keygen -t rsa -b 2048</code>)<br />
* paste your SSH public key (<code>~/.ssh/id_rsa.pub</code>) into your gitorious account, here: https://secure.gitorious.org/~XXX/keys/new (where you replace XXX with your gitorious account name)<br />
* ask [mailto:pascal.bleser@opensuse.org Pascal Bleser] or [mailto:bruno.friedmann@opensuse.org Bruno Friedmann] (or on admin@opensuse.org) to add your user account to the [http://gitorious.org/+opensuse-artwork opensuse-artwork team on gitorious], which will give you write access to the [http://gitorious.org/opensuse-artwork/opensuse-artwork opensuse-artwork repository]<br />
* install <code>git</code> (<code>zypper install git</code>), if you don't have it already<br />
* run the following commands in a shell:<br />
** <code>git config user.email my.email.address@opensuse.org</code> (obviously with your real email address ;))<br />
** <code>git config user.name "John Doe"</code> (again, with your real name)<br />
* pick some directory where you'll want the files to reside, e.g. <code>~/Documents</code> and go there in your shell, e.g. <code>cd ~/Documents</code><br />
* retrieve the repository with the following command: <code>git clone git@gitorious.org:opensuse-artwork/opensuse-artwork.git</code> (which will create a subdirectory "opensuse-artwork")<br />
<br />
==Workflow==<br />
===Getting the latest changes===<br />
In order to pull the latest changes that have been stored in the repository, use the following command: <code>git pull</code><br />
That will download the latest version of everything that is in the repository on gitorious, and store it on your disk.<br />
<br />
Of course, that command needs to be ran from a shell while being in your local <code>opensuse-artwork</code> directory (e.g. <code>~/Documents/opensuse-artwork</code>)<br />
<br />
===Adding new files===<br />
When you create a new file, you have to tell <code>git</code> that you would like to add it to the repository first, using the following command: <code>git add filename</code> (where you replace filename with the actual name of the file you want to add).<br />
<br />
Note that adding a file does not upload it to the repository yet, it merely instructs <code>git</code> that you want to put it under version control.<br />
<br />
===Committing changes===<br />
When you change files and you would like to store their state in the repository (e.g. when you think it's good enough to be used by others), use the following command:<br />
<br />
<code>git commit -m "some comment about the change I just made" filename</code><br />
<br />
Please use meaningful comments (what's after <code>-m</code>) as that will help everyone to keep track of the changes that were made. Also, make sure to put the comment into quotes (between "") or the shell will interpret it as several parameters for the <code>git</code> command, which it isn't.<br />
<br />
You can also commit changes of several files at once, which is the preferred approach when the changes do apply to several files (e.g. you just changed the color palette on a dozen inkscape files): that way, your changes will show up as one "action" in the history of the repository.<br />
<br />
To do so, just pass several filenames to the <code>git commit</code> command, like this:<br />
<br />
<code>git commit -m "changed palette to the right colors" filename1 filename2 filename3</code><br />
<br />
You can also commit all the changes to all the files in your local copy of the repository, by using the <code>-a</code> switch, like this:<br />
<br />
<code>git commit -m "changed palette to Bento colors" -a</code><br />
<br />
===Pushing changes===<br />
When you commit changes, <code>git</code> will only store them in your local repository on your hard disk, and not to the [http://gitorious.org/opensuse-artwork/opensuse-artwork opensuse-artwork repository on gitorious], which means that no one else will be able to see your changes.<br />
<br />
<code>git</code> works that way because you may choose to make changes locally, on your hard disk, and keep track of those changes to be able to revert to a previous version, without necessarily pushing those changes to all the other people who work on the repository just yet.<br />
<br />
Once you want to share your changes with everyone else, you must "push" those changes to the repository, with the following command:<br />
<br />
<code>git push</code><br />
<br />
Note that the ''very first time'' you will do a <code>git push</code>, you will have to use this command: <code>git push origin master</code><br />
<br />
From then on, you will only need to use <code>git push</code><br />
<br />
===Status===<br />
With the command <code>git status</code>, you can see whether you have files on your hard disk that have changes (or new files, or deleted files) that have not been committed yet.</div>Pbleserhttps://en.opensuse.org/index.php?title=openSUSE:Marketing_and_Artwork_repository&diff=34653openSUSE:Marketing and Artwork repository2011-02-15T23:05:45Z<p>Pbleser: initial version</p>
<hr />
<div>We keep our marketing and artwork material in [http://gitorious.org/opensuse-artwork/opensuse-artwork our git repository at gitorious.org]. While a version control system such as [http://git-scm.com/ git] may seem daunting, it is by far the best option for collaborative authoring.<br />
<br />
==Howto==<br />
If you would like to modify or add material to our repository, you need to do the following things first:<br />
* [https://secure.gitorious.org/users/new register an account on gitorious.org], if you don't already have one<br />
* create an SSH (Secure Shell) key pair, if you don't already have one (<code>ssh-keygen -t rsa -b 2048</code>)<br />
* paste your SSH public key (<code>~/.ssh/id_rsa.pub</code>) into your gitorious account, here: https://secure.gitorious.org/~XXX/keys/new (where you replace XXX with your gitorious account name)<br />
* ask [mailto:pascal.bleser@opensuse.org Pascal Bleser] or [mailto:bruno.friedmann@opensuse.org Bruno Friedmann] (or on admin@opensuse.org) to add your user account to the [http://gitorious.org/+opensuse-artwork opensuse-artwork team on gitorious], which will give you write access to the [http://gitorious.org/opensuse-artwork/opensuse-artwork opensuse-artwork repository]<br />
* install <code>git</code> (<code>zypper install git</code>), if you don't have it already<br />
* run the following commands in a shell:<br />
** <code>git config user.email my.email.address@opensuse.org</code> (obviously with your real email address ;))<br />
** <code>git config user.name "John Doe"</code> (again, with your real name)<br />
* pick some directory where you'll want the files to reside, e.g. <code>~/Documents</code> and go there in your shell, e.g. <code>cd ~/Documents</code><br />
* retrieve the repository with the following command: <code>git clone git@gitorious.org:opensuse-artwork/opensuse-artwork.git</code> (which will create a subdirectory "opensuse-artwork")</div>Pbleserhttps://en.opensuse.org/index.php?title=Portal:Marketing/Topics&diff=34652Portal:Marketing/Topics2011-02-15T22:53:24Z<p>Pbleser: add link to openSUSE:Marketing_and_Artwork_repository</p>
<hr />
<div><div class="subcolumns"><br />
<div class="c33l"><br />
<div class="subcl"><br />
{{Point here|[[Image:Icon-community.png|48px]]|<br />
'''Events'''<br />
<br />
* [[openSUSE:Ambassadors_events|Ambassador events]]<br />
* [[openSUSE:Marketing_meeting|Marketing team meeting]]<br />
<br />
}}<br />
</div><br />
</div><br />
<div class="c33l"><br />
<div class="subc"><br />
{{Point here|[[Image:Icon-template.png|48px]]|<br />
'''Resources'''<br />
<br />
* [[openSUSE:Marketing_materials|Marketing materials like folders and presentations]]<br />
* [[openSUSE:Events|Launch Parties, Booth organizing and other Events How To]]<br />
* [[openSUSE:Talking_points|Talking points, cool things and arguments]]<br />
* [[openSUSE:Marketing_jobs|Marketing tasks and plans]]<br />
* [[openSUSE:Marketing_and_Artwork_repository|Marketing and artwork repository]]<br />
}}<br />
</div><br />
</div><br />
<div class="c32r"><br />
<div class="subcr"><br />
{{Point here|[[Image:Icon-irc.png|48px]]|<br />
'''Communicate'''<br />
{{Mailinglist|opensuse-marketing|openSUSE Marketing Mailing List}}<br />
* [irc://irc.opensuse.org/opensuse-marketing #openSUSE-marketing] on irc.freenode.net (Freenode).<br />
}}<br />
<br />
</div><br />
</div><br />
</div></div>Pbleserhttps://en.opensuse.org/index.php?title=openSUSE:Countdown&diff=33010openSUSE:Countdown2011-01-16T10:46:38Z<p>Pbleser: updated for 11.4</p>
<hr />
<div>{{Artwork navbar}}<br />
{{Intro|You can help spreading new release of openSUSE by adding these fabulous countdown timers to your website.}}<br />
<br />
==Introduction==<br />
The pictures are statically generated on the countdown.opensuse.org server by a cron job, updated at 12:00 CET. This approach optimizes the performance on the server and also enables Apache to serve HTTP cache-control headers properly.<br />
<br />
It is translated in many languages (english, german, czech, french, danish, russian, polish, dutch, finnish, spanish, italian, greek, swedish, croatian, norwegian, portuguese, hungarian, romanian, galician) and is automatically displayed in the language configured in the visitor's preferred language(s), with the same URL.<br />
<br />
==Usage==<br />
Just copy and paste the code under the picture into your webpage:<br />
<br />
===square, original (256x256)===<br />
http://countdown.opensuse.org/11.4/medium.en.png<br />
<br />
<nowiki><a href="http://en.opensuse.org/openSUSE_11.4"><img src="http://countdown.opensuse.org/11.4/medium.en.png" border="0"/></a></nowiki><br />
for wiki (XX is your language, eg. 'en'):<br />
<nowiki>[http://XX.opensuse.org/openSUSE_11.4 http://countdown.opensuse.org/11.4/medium.XX.png]</nowiki><br />
<br />
===square, small (130x130)===<br />
http://countdown.opensuse.org/11.4/small.en.png<br />
<br />
<nowiki><a href="http://en.opensuse.org/openSUSE_11.4"><img src="http://countdown.opensuse.org/11.4/small" border="0"/></a></nowiki><br />
for wiki (XX is your language, eg. 'en'):<br />
<nowiki>[http://XX.opensuse.org/openSUSE_11.4 http://countdown.opensuse.org/11.4/small.XX.png]</nowiki><br />
<br />
===square, large (400x400)===<br />
http://countdown.opensuse.org/11.4/large.en.png<br />
<br />
<nowiki><a href="http://en.opensuse.org/openSUSE_11.4"><img src="http://countdown.opensuse.org/11.4/large" border="0"/></a></nowiki><br />
for wiki (XX is your language, eg. 'en'):<br />
<nowiki>[http://XX.opensuse.org/openSUSE_11.4 http://countdown.opensuse.org/11.4/large.XX.png]</nowiki><br />
<br />
===Advanced version by Sylvester Lykkehus===<br />
<br />
<nowiki>http://solidonline.dk/11.3.php?red=<redval>&green=<greenval>&blue=<blueval>&alpha=<alphaval>&gamma=<gammaval>&lang=<lang>&size=<resx>x<resy></nowiki><br />
<br />
where<br />
<br />
* redval is 0 ... 255 (red value)<br />
* greenval is 0 ... 255 (green value)<br />
* blueval is 0 ... 255 (blue value)<br />
* alphaval is 0 ... 127 (alpha value)<br />
* gammaval is 0.1 ... 2.0 (gamma value)<br />
* lang is language (default en)<br />
* resx is 1 ... 256 (horizontal size)<br />
* resy is 1 ... 256 (vertical size)<br />
<br />
* example: http://solidonline.dk/11.3.php?red=127&green=0&blue=127&alpha=30&gamma=0.6&lang=jp<br />
<br />
* source: http://solidonline.dk/11.3.phps<br />
<br />
[[Category:Artwork]]<br />
<br />
[[de:Countdown]]<br />
[[ru:Обратный отсчет]]<br />
[[pt: Countdown]]</div>Pbleserhttps://en.opensuse.org/index.php?title=openSUSE:Planet&diff=31133openSUSE:Planet2010-12-09T01:52:03Z<p>Pbleser: remove Connect profile information</p>
<hr />
<div>{{Intro|[http://planet.opensuse.org Planet openSUSE] is a web feed aggregator that collects blog posts from people who contribute to openSUSE.}}<br />
<br />
<br />
'''Latest posts on Planet openSUSE:'''<br />
<feed url="http://planet.opensuse.org/global/rss20.xml" date="M d" ><br />
*'''{DATE}:''' [{PERMALINK} {TITLE}] by {AUTHOR}<br />
</feed><br />
<br />
==Connect your blog==<br />
In order to have your blog feed added to [http://planet.opensuse.org Planet openSUSE], send an email to [mailto:admin@opensuse.org the administrators] with the following information:<br />
* the URL of your blog or, even better, the URL to the RSS/Atom feed of your blog<br />
* in which language you blog, especially if it's not in English<br />
* your full name (e.g. John Doe)<br />
* your IRC nickname on Freenode, if you have any (e.g. jdoe)<br />
* whether you are an [[openSUSE:Members|openSUSE Member]] so that a "member" button can be placed besides your name on the feedlist<br />
* a [http://en.wikipedia.org/wiki/Hackergotchi hackergotchi] -- while it's not mandatory, it is a lot nicer for the readers. If you need help with this send a picture to the [mailto:opensuse-artwork@opensuse.org openSUSE Artwork team].<br />
----<br />
<br />
==See also==<br />
* [[openSUSE:Planet team|Planet openSUSE team]]<br />
----<br />
<br />
==External links==<br />
* [http://planet.opensuse.org Planet openSUSE]<br />
<br />
{{IW|PlanetSUSE}}</div>Pbleserhttps://en.opensuse.org/index.php?title=Archive:Conference_party_2010&diff=27943Archive:Conference party 20102010-10-15T23:17:23Z<p>Pbleser: </p>
<hr />
<div>{{Conference navbar}}<br />
<br />
<div style="background-color:#000000; width:100%"><br />
[[File:Lizard-lounge.png|center|link=]]<br />
</div><br />
<br />
<div style="float:left; text-align:center; color:#21d91c; font-size:250%; background-color:#000000; width:50%; height:500px"><br />
<br><br />
Thursday, 21. October<br><br />
19:00<br><br />
Maxfeldstrasse 5<br><br />
90409 Nürnberg<br><br><br />
</div><br />
<br />
<div style="float:right; background-color:#000000; width:48%; height:500px; padding-right:2%;"><br />
{{<br />
#display_point:<br />
49.45966586541941, 11.082560420036316~Lizard Lounge<br>Maxfeldstr. 5<br>90409 Nürnberg<br>+491605557827<br>http://en.opensuse.org/openSUSE:Conference_party;<br />
|service=openlayers<br />
|layers=osm-mapnik<br />
|zoom=17<br />
}}<br />
</div><br />
<br />
<div style="text-align:center; color:#21d91c; font-size:250%; background-color:#000000; width:100%" class="center"><br />
http://news.opensuse.org/wp-content/uploads/2010/09/fun.png<br />
<br />
[http://www.b1-systems.de B1] sponsored<br><br />
food, drinks and fun<br><br />
for everyone registered at the<br><br />
[[Portal:Conference|openSUSE Conference]]. <br />
</div><br />
<br />
==Other Social Events==<br />
===Socialising Dinner===<br />
There is a dinner for socialising before the conference starts.<br />
<br />
It takes places on Tuesday, 2010‑10‑19 at 6:30pm in the [http://www.restaurant-sunrise.de/ Restaurant Sunrise] ([http://maps.google.com/maps?saddr=Schleswiger+Stra%C3%9Fe+101,+N%C3%BCrnberg&daddr=Staffelsteiner+Stra%C3%9Fe+3,+N%C3%BCrnberg&dirflg=w directions from the venue]) to get to know each other over dinner. The restaurant offers an all you can eat buffet with Chinese food, Sushi and Mongolian grill. If you like to go there please put your name/nick here:<br />
<br />
# Geeko himself<br />
# Bryen "suseROCKs" Yunashko<br />
# Jamie Miller<br />
# Lars Dieckow<br />
# Christine Hitchcock<br />
# Bruno "tigerfoot" Friedmann<br />
# Rémy Marquis<br />
# Pascal "yaloki" Bleser<br />
<br />
===KDE Team Social Event===<br />
<br />
This also takes place on Tuesday 19 October at 1800 in Barfüßer in the old town. For more details see [[openSUSE:Conference_Kde_Social|here]]<br />
<br />
===Movie Night===<br />
On Friday, 2010‑10‑22 at 9:15pm there is again the [http://www.kommkino.com/programm/filminfo.php?filmnummer=485&monatswert=102010 Creative-Commons-Movie-Night] at the [http://www.kommkino.com/ KommKino Nuremberg]. They will show open content/free films, for instance the German premier of the the newest short movie [http://www.sintel.org/ Sintel] from the Blender Foundation (in full-HD). There is no entry fee and the program is in English.<br />
<br />
<br />
<br />
[[Category:Conference]]</div>Pbleserhttps://en.opensuse.org/index.php?title=User:Pbleser&diff=17597User:Pbleser2010-07-20T00:27:35Z<p>Pbleser: fixed profile pic</p>
<hr />
<div><div style="width:76%; float:left"><br />
{{Box-header|About Me|{{FULLPAGENAME}}|}}<br />
Hi, my name is Pascal Bleser. As of 2010, I'm 35 years old, live in Belgium, work in Germany, am living with my girlfriend Ingrid and (last but most important (to me)) father of my 4 year old daughter [http://www.flickr.com/photos/dev-loki/4092302825/ Gaëlle] and my 1.5 yea old son [http://www.flickr.com/photos/dev-loki/3609765519/in/photostream/ Thomas].<br />
<br />
I'm using Linux since a little over 10 years (started with Slackware, had Redhat for a few days, switched to S.u.S.E. Linux 5.0 and stayed with it since then) and take actively part in the community since about 5-6 years.<br />
<br />
I'm working for a large European ISV as a software architect and developer, mostly busy with designing and coding technology-related Java components and frameworks (yeah, I actually really, really like Java). Apart from that, on the technical side of things, I've done and still do a lot of coding in PHP, Python, Ruby, SQL, bash, and also did a lot of C/C++ coding (but I'd prefer not to any more).<br />
<br />
My native language is French, my German is near perfect and I guess my English is quite fluent.<br />
<br />
My main contribution to the openSUSE community is to maintain lots and lots of packages in my [http://linux01.gwdg.de/~pbleser/ "Guru" repository] (now sort of defunct) as well as in the [http://packman.links2linux.org Packman repository] and the [http://download.opensuse.org/repositories openSUSE Build Service].<br />
<br />
I've also been a member of the initial, "bootstrap" openSUSE Board, and have been elected to serve on the current openSUSE board for 2 years.<br />
<br />
Furthermore, I'm one of the members of the [http://fosdem.org FOSDEM (Free and Opensource Software Developers European Meeting)] organization team, one of the largest and most appreciated FOSS events in Europe, part of a great team of dedicated, highly skilled people^Wfriends.<br />
<br />
On a side note, I authored the current implementation of [http://planet.opensuse.org Planet openSUSE].<br />
<br />
Finally (sort of), here and then, as time permits, a do a little bit of editing on [http://opensuse-community.org the opensuse-community.org website].<br />
{{Box-footer|}}<br />
</div><br />
<div style="width:22%; float:right"><br />
{{Box-header|Contact|{{FULLPAGENAME}}|}}<br />
[[Image:PascalBleser.jpg|100px|center]]<br />
* [mailto:pascal.bleser@opensuse.org email]<br />
* [http://dev-loki.blogspot.com blog]<br />
* [http://delicious.com/devloki bookmarks]<br />
* [irc://irc.freenode.net/yaloki,isnick IRC:yaloki]<br />
{{Box-footer|}}<br />
</div></div>Pbleserhttps://en.opensuse.org/index.php?title=User:Pbleser&diff=17596User:Pbleser2010-07-20T00:25:33Z<p>Pbleser: create</p>
<hr />
<div><div style="width:76%; float:left"><br />
{{Box-header|About Me|{{FULLPAGENAME}}|}}<br />
Hi, my name is Pascal Bleser. As of 2010, I'm 35 years old, live in Belgium, work in Germany, am living with my girlfriend Ingrid and (last but most important (to me)) father of my 4 year old daughter [http://www.flickr.com/photos/dev-loki/4092302825/ Gaëlle] and my 1.5 yea old son [http://www.flickr.com/photos/dev-loki/3609765519/in/photostream/ Thomas].<br />
<br />
I'm using Linux since a little over 10 years (started with Slackware, had Redhat for a few days, switched to S.u.S.E. Linux 5.0 and stayed with it since then) and take actively part in the community since about 5-6 years.<br />
<br />
I'm working for a large European ISV as a software architect and developer, mostly busy with designing and coding technology-related Java components and frameworks (yeah, I actually really, really like Java). Apart from that, on the technical side of things, I've done and still do a lot of coding in PHP, Python, Ruby, SQL, bash, and also did a lot of C/C++ coding (but I'd prefer not to any more).<br />
<br />
My native language is French, my German is near perfect and I guess my English is quite fluent.<br />
<br />
My main contribution to the openSUSE community is to maintain lots and lots of packages in my [http://linux01.gwdg.de/~pbleser/ "Guru" repository] (now sort of defunct) as well as in the [http://packman.links2linux.org Packman repository] and the [http://download.opensuse.org/repositories openSUSE Build Service].<br />
<br />
I've also been a member of the initial, "bootstrap" openSUSE Board, and have been elected to serve on the current openSUSE board for 2 years.<br />
<br />
Furthermore, I'm one of the members of the [http://fosdem.org FOSDEM (Free and Opensource Software Developers European Meeting)] organization team, one of the largest and most appreciated FOSS events in Europe, part of a great team of dedicated, highly skilled people^Wfriends.<br />
<br />
On a side note, I authored the current implementation of [http://planet.opensuse.org Planet openSUSE].<br />
<br />
Finally (sort of), here and then, as time permits, a do a little bit of editing on [http://opensuse-community.org the opensuse-community.org website].<br />
{{Box-footer|}}<br />
</div><br />
<div style="width:22%; float:right"><br />
{{Box-header|Contact|{{FULLPAGENAME}}|}}<br />
[[Image:Pbleser.jpg|48px|center]]<br />
* [mailto:pascal.bleser@opensuse.org email]<br />
* [http://dev-loki.blogspot.com blog]<br />
* [http://delicious.com/devloki bookmarks]<br />
* [irc://irc.freenode.net/yaloki,isnick IRC:yaloki]<br />
{{Box-footer|}}<br />
</div></div>Pbleserhttps://en.opensuse.org/index.php?title=Main_Page&diff=11332Main Page2010-07-01T06:31:46Z<p>Pbleser: use the newly available "wide" counter</p>
<hr />
<div><center><br />
http://counter.opensuse.org/11.3/wide.png<br />
</center><br />
<br />
==Project==<br />
{{Point here|[[File:icon-community.png|48px|link=Portal:Project|Project]]|{{Portal:Project/Intro}}}}<br />
==Distribution==<br />
{{Point here|[[Image:Icon-distribution.png|48px|link=Portal:Distribution|Distribution]]|{{Portal:Distribution/Intro}}<br />
}}<br />
==Wiki==<br />
{{Point here|[[File:Icon-wiki.png|48px|link=Portal:Wiki|Wiki]]|{{Portal:Wiki/Intro}}}}<br />
<br />
__NOTOC____NOEDITSECTION__</div>Pbleserhttps://en.opensuse.org/index.php?title=openSUSE:Services_help&diff=21622openSUSE:Services help2010-06-16T18:41:48Z<p>Pbleser: add francis and darix to contacts for bugbot</p>
<hr />
<div>If you experience problems with any of our services contact the responsible persons. <br />
<br />
Note: for known downtimes/ problems, we have a special [[Downtime]] page in the wiki.<br />
<br />
=For Users=<br />
<br />
==account, profile, change password==<br />
<br />
[https://secure-www.novell.com/selfreg/jsp/protected/manageAccount.jsp?target=http://www.opensuse.org https://secure-www.novell.com/selfreg/jsp/protected/manageAccount.jsp]<br />
<br />
==mailinglists/lists.opensuse.org==<br />
<br />
LISTNAME+owner@opensuse.org<br />
<br />
ml-admin@opensuse.org<br />
<br />
==forums.opensuse.org==<br />
<br />
http://forums.opensuse.org/sendmessage.php<br />
<br />
==irc channels==<br />
<br />
ircops@opensuse.org<br />
<br />
==packages.opensuse-community.org==<br />
<br />
Use [https://bugzilla.novell.com/enter_bug.cgi?classification=7340&product=openSUSE.org&submit=Use+This+Product&component=Software%20Portal Bugzilla with the Product openSUSE.org and the Component Software Portal]<br />
<br />
==packman.links2linux.org==<br />
<br />
packman@links2linux.de<br />
<br />
Use [https://bugzilla.novell.com/enter_bug.cgi?classification=7340&product=openSUSE.org&submit=Use+This+Product&component=3rd%20party%20software Bugzilla with the Product openSUSE.org and the Component 3rd party software]<br />
<br />
==build.opensuse.org==<br />
<br />
opensuse-buildservice@opensuse.org<br />
<br />
or use [https://bugzilla.novell.com/enter_bug.cgi?classification=7340&product=openSUSE.org&submit=Use+This+Product&component=BuildService Bugzilla with the Product openSUSE.org and the Component BuildService]<br />
<br />
==software.opensuse.org==<br />
<br />
admin@opensuse.org<br />
<br />
==download.opensuse.org==<br />
<br />
ftpadmin@opensuse.org<br />
<br />
mirror@opensuse.org<br />
<br />
or use [https://bugzilla.novell.com/enter_bug.cgi?classification=7340&product=openSUSE.org&submit=Use+This+Product&component=Download%20Infrastructure Bugzilla with the Product openSUSE.org and the Component Download Infrastructure]<br />
<br />
==hermes.opensuse.org==<br />
<br />
Use [https://bugzilla.novell.com/enter_bug.cgi?classification=7340&product=openSUSE.org&submit=Use+This+Product&component=Hermes Bugzilla with the Product openSUSE.org and the Component Hermes]<br />
<br />
==www.opensuse.org==<br />
<br />
opensuse-web@opensuse.org<br />
<br />
==en.opensuse.org (or any other wiki)==<br />
<br />
admin@opensuse.org<br />
<br />
or use [https://bugzilla.novell.com/enter_bug.cgi?classification=7340&product=openSUSE.org&submit=Use+This+Product&component=wiki Bugzilla with the Product openSUSE.org and the Component wiki]<br />
<br />
==planetsuse.org==<br />
<br />
Contact [[User:Riggwelter]]<br />
<br />
==bugbot on freenode==<br />
Poke apokryphos or darix on [irc://irc.freenode.net/opensuse-project IRC] for urgent matters, else send an email to admin@opensuse.org<br />
<br />
=For [[Members]]=<br />
<br />
==lizards.opensuse.org==<br />
<br />
news-submit@opensuse.org<br />
<br />
==news.opensuse.org==<br />
<br />
news-submit@opensuse.org<br />
<br />
==opensuse email aliases==<br />
<br />
admin@opensuse.org<br />
<br />
==opensuse freenode cloaks==<br />
<br />
admin@opensuse.org<br />
<br />
==features.opensuse.org==<br />
<br />
featureadmin@suse.de<br />
<br />
Use [https://bugzilla.novell.com/enter_bug.cgi?classification=7340&product=openSUSE.org&submit=Use+This+Product&component=openFATE Bugzilla with the Product openSUSE.org and the Component openFATE]<br />
<br />
=Anything Else=<br />
<br />
Use [https://bugzilla.novell.com/enter_bug.cgi?classification=7340&product=openSUSE.org&submit=Use+This+Product Bugzilla with the openSUSE Class and the openSUSE.org Product]<br />
<br />
[[pt:FAIL]]</div>Pbleserhttps://en.opensuse.org/index.php?title=openSUSE:Services_help&diff=21614openSUSE:Services help2009-05-08T21:16:03Z<p>Pbleser: add link to novell selfreg</p>
<hr />
<div>If you experience problems with any of our services contact the responsible persons. <br />
<br />
=For Users=<br />
<br />
==account, profile, change password==<br />
<br />
[https://secure-www.novell.com/selfreg/jsp/protected/manageAccount.jsp?target=http://www.opensuse.org https://secure-www.novell.com/selfreg/jsp/protected/manageAccount.jsp]<br />
<br />
==mailinglists/lists.opensuse.org==<br />
<br />
ml-admin@opensuse.org<br />
<br />
==forums.opensuse.org==<br />
<br />
http://forums.opensuse.org/sendmessage.php<br />
<br />
==irc channels==<br />
<br />
ircops@opensuse.org<br />
<br />
==packages.opensuse-community.org==<br />
<br />
Use [https://bugzilla.novell.com/enter_bug.cgi?classification=7340&product=openSUSE.org&submit=Use+This+Product&component=Software%20Portal Bugzilla with the Product openSUSE.org and the Component Software Portal]<br />
<br />
==packman.links2linux.org==<br />
<br />
packman@links2linux.de<br />
<br />
Use [https://bugzilla.novell.com/enter_bug.cgi?classification=7340&product=openSUSE.org&submit=Use+This+Product&component=3rd%20party%20software Bugzilla with the Product openSUSE.org and the Component 3rd party software]<br />
<br />
==build.opensuse.org==<br />
<br />
opensuse-buildservice@opensuse.org<br />
<br />
or use [https://bugzilla.novell.com/enter_bug.cgi?classification=7340&product=openSUSE.org&submit=Use+This+Product&component=BuildService Bugzilla with the Product openSUSE.org and the Component BuildService]<br />
<br />
==software.opensuse.org==<br />
<br />
admin@opensuse.org<br />
<br />
==download.opensuse.org==<br />
<br />
ftpadmin@opensuse.org<br />
<br />
mirror@opensuse.org<br />
<br />
or use [https://bugzilla.novell.com/enter_bug.cgi?classification=7340&product=openSUSE.org&submit=Use+This+Product&component=Download%20Infrastructure Bugzilla with the Product openSUSE.org and the Component Download Infrastructure]<br />
<br />
==hermes.opensuse.org==<br />
<br />
Use [https://bugzilla.novell.com/enter_bug.cgi?classification=7340&product=openSUSE.org&submit=Use+This+Product&component=Hermes Bugzilla with the Product openSUSE.org and the Component Hermes]<br />
<br />
==www.opensuse.org==<br />
<br />
opensuse-web@opensuse.org<br />
<br />
==en.opensuse.org (or any other wiki)==<br />
<br />
admin@opensuse.org<br />
<br />
or use [https://bugzilla.novell.com/enter_bug.cgi?classification=7340&product=openSUSE.org&submit=Use+This+Product&component=wiki Bugzilla with the Product openSUSE.org and the Component wiki]<br />
<br />
==planetsuse.org==<br />
<br />
Contact [[User:Riggwelter]]<br />
<br />
=For [[Members]]=<br />
<br />
==lizards.opensuse.org==<br />
<br />
news-submit@opensuse.org<br />
<br />
==news.opensuse.org==<br />
<br />
news-submit@opensuse.org<br />
<br />
==opensuse email aliases==<br />
<br />
admin@opensuse.org<br />
<br />
==opensuse freenode cloaks==<br />
<br />
admin@opensuse.org<br />
<br />
==features.opensuse.org==<br />
<br />
Use [https://bugzilla.novell.com/enter_bug.cgi?classification=7340&product=openSUSE.org&submit=Use+This+Product&component=openFATE Bugzilla with the Product openSUSE.org and the Component openFATE]<br />
<br />
=Anything Else=<br />
<br />
Use [https://bugzilla.novell.com/enter_bug.cgi?classification=7340&product=openSUSE.org&submit=Use+This+Product Bugzilla with the openSUSE Class and the openSUSE.org Product]</div>Pbleser