https://en.opensuse.org/api.php?action=feedcontributions&user=Kfreitag&feedformat=atomopenSUSE Wiki - User contributions [en]2024-03-29T15:35:59ZUser contributionsMediaWiki 1.37.6https://en.opensuse.org/index.php?title=openSUSE:Packaging_Conventions_RPM_Macros&diff=119417openSUSE:Packaging Conventions RPM Macros2017-04-28T13:17:52Z<p>Kfreitag: /* %desktop_database_post / %desktop_database_postun */ - made the Warning box less confusing.</p>
<hr />
<div>{{Packaging_docnav}}<br />
== RPM Macros ==<br />
<br />
=== Syntax ===<br />
<br />
{{warning|The validity of the claims in this subsection are uncertain. It is actually possible to mix options with parameters, as is commonly done in, for example, '''%kernel_module_package -p preamble -x xen xenpae'''.}}<br />
<br />
This section describes predefined RPM macros used in the SUSE packages. Some of them are generic RPM macros. Some are SUSE-specific macros. For other existing generic macros, other documentation should be consulted, such as [http://www.rpm.org/max-rpm-snapshot/ Maximum RPM] or [http://rpm.org/user_doc/macros.html Macro syntax]. The Java-related macros are described in the [[openSUSE:Packaging Java]] page. KDE macros are documented at [[openSUSE:KDE RPM Macros]]. If you wish to perform advanced rpm macro programming, rpm has built in support for the [http://www.lua.org/manual/5.1/manual.html#5.1 Lua programming language]<br />
<br />
You can find all the predefined macros in the <tt>/usr/lib/rpm/macros</tt> and <tt>suse_macros</tt> files with some explanation. Additional package specific macros are added by files in <tt>/etc/rpm</tt>. If you place the macro <tt>%dump</tt> in your spec file and use `<tt>rpmbuild -bp specfile</tt>`, it will cause a dump of all the macros available on your system. It is however easier to just execute `<tt>rpm --showrc</tt>`.<br />
<br />
One important difference between RPM macros and normal Linux commands is how the options and parameters are defined. RPM provides only a simple support for processing options. One limitation is that all options must be defined before parameters and it is not possible to simply use pairs created from an option and a related value. For example, the Linux command <span>'''top'''</span> uses the following synopsis:<br />
<br />
<code>'''top'''</code> [<code>-bcisS</code>] [<code>-d</code> ''<code>delay</code>''] [<code>-n</code> ''<code>iterations</code>''] [<code>-p</code> ''<code>pid</code>''] [, ''<code>pid</code>'' ...]<br />
<br />
The used pairs <tt>-d</tt> ''<tt>delay</tt>'', <tt>-n</tt> ''<tt>iterations</tt>'', <tt>-p</tt> ''<tt>pid</tt>'' and all the parameters are optional. The option before a parameter defines which parameter is really used on the command line. This makes it possible to call:<br />
<br />
Example 1: <code>'''top -n 20 -p 10345'''</code><br />
<br />
Example 2: <code>'''top -d 1 -p 10345'''</code><br />
<br />
and the command knows that <tt>20</tt> is a number of iterations, <tt>1</tt> is a delay and <tt>10345</tt> is a PID.<br />
<br />
Due to the limitation in RPM, the synopsis of a related RPM macro would look like:<br />
<br />
<code>'''%top'''</code> [<code>-bcisSdnp</code>] [''<code>delay</code>''] [''<code>iterations</code>''] [''<code>pid</code>''] [,''<code>pid</code>'' ...]<br />
<br />
All the options must be defined before parameters and the option again defines which parameter is really used. This means that the related call of the potential RPM macro of the examples above would be:<br />
<br />
Example 1: <code>'''%top -n -p 5 10345'''</code><br />
<br />
Example 2: <code>'''%top -d -p 1 460'''</code><br />
<br />
=== %_docdir ===<br />
<br />
This macro is substituted with the default directory for documentation, <tt>/usr/share/doc/packages</tt>. It may be redefined by the <tt>Docdir</tt> tag. Usually, it is used to install a documentation in the <tt>%install</tt> section if it is not sufficient to do it in the <tt>%files</tt> with the <tt>%doc</tt> tag. Furthermore, the <tt>%doc</tt> tag need not be used together with <tt>%_docdir</tt> in the <tt>%files</tt> section. It is done automatically for this directory.<br />
<br />
This example is taken from the ''aeolus'' package:<br />
<br />
%install<br />
[...]<br />
mkdir -p "%buildroot/%_docdir/%name"<br />
cp -a .aeolusrc "%buildroot/%_docdir/%name/aeolusrc"<br />
cp -Ra stops-* "%buildroot/%_docdir/%name"<br />
[...]<br />
<br />
%files<br />
[...]<br />
%_docdir/%name<br />
<br />
=== %_infodir ===<br />
<br />
This macro is substituted with the default directory for info pages, <tt>/usr/share/info</tt>. It is often used with `<code>./configure --infodir="%_infodir"</code>`, with the the <tt>%install_info</tt> macro, and in the file list. As with <tt>%_docdir</tt>, the tag <tt>%doc</tt> need not be used together with <tt>%_infodir</tt> in the <tt>%files</tt> section. It is done automatically for this directory.<br />
<br />
=== %_lib ===<br />
<br />
This macro substitutes with either <tt>lib</tt> or <tt>lib64</tt>, as appropriate. The second variant appears on 64-bit architectures which support running both 64-bit and 32-bit programs in parallel (biarch systems). On such systems, two variants of the same libraries must coexist. Therefore, the 64-bit libraries are installed in <tt>lib64</tt> directories and 32-bit libraries in the traditional <tt>lib</tt> directories.<br />
<br />
<tt>%_lib</tt> itself is used when the macro <tt>%_libdir</tt> is not sufficient, for example, when libraries are supposed to go into <tt>/usr/X11R6/%_lib</tt>. It is often used with `<code>./configure -–libdir="/usr/X11R6/%_lib"</code>` and in the file list.<br />
<br />
=== %_libdir ===<br />
<br />
This macro is substituted with <tt>%_prefix/%_lib</tt>. It has the same function as <tt>%_lib</tt> and is used even more often than it, because the libraries usually are installed into <tt>/usr/lib(64)</tt>. Used with `<code>./configure --libdir="%_libdir"</code>` and in the file list.<br />
<br />
=== %_mandir ===<br />
<br />
This macro is substituted with the default directory for manual pages, <tt>/usr/share/man</tt>. It is often used with `<code>./configure --mandir="%_mandir"</code>` and in the <tt>%files</tT> section, such as in<br />
<br />
%files<br />
%_mandir/*/*<br />
<br />
As with <tt>%_docdir</tt>, the <tt>%doc</tt> tag need not be used together with <tt>%_mandir</tt> in the <tt>%files</tt> section. It is done automatically for this directory.<br />
<br />
=== %_rundir ===<br />
<br />
This macro is substituted with the default directory for volatile<br />
runtime data which is by default <tt>/run</tt>. The macro was<br />
introduced April 2014. For older distribution you may want to add<br />
the following snippet:<br />
<br />
%if ! %{defined _rundir}<br />
%define _rundir %{_localstatedir}/run<br />
%endif<br />
<br />
=== %desktop_database_post / %desktop_database_postun ===<br />
<br />
These macros need to be called for every application which installs a .desktop file. This will update the system media type cache by calling update-desktop-database.<br />
<br />
{{Warning|Most packagers forget to do this! This can lead to hard-to-debug bugs, for example after installing your application, GNOME Shell/GDM missing all its panel icons. So normally these macros need to run after you install .desktop files in the package.}}<br />
<br />
These macros are available from 11.4 on!<br />
<br />
It requires <tt>desktop-file-utils</tt> package. Example from <tt>meld</tt> package:<br />
...<br />
BuildRequires: update-desktop-files<br />
<br />
...<br />
<br />
%if 0%{?suse_version} >= 1140<br />
%post<br />
%desktop_database_post<br />
%endif<br />
<br />
%if 0%{?suse_version} >= 1140<br />
%postun<br />
%desktop_database_postun<br />
%endif<br />
{{Info|<code>BuildRequires: desktop-file-utils</code> is not needed if <code>BuildRequires: update-desktop-files</code> is already added to the specfile preamble, as the latter already requires <tt>desktop-file-utils</tt> package.}}<br />
<br />
=== %define ===<br />
This macro is used to define custom macros inside a specific spec file. Use this as a placeholder for recurring words like a custom name for the package<br />
<br />
%define custom_version 12.6_64<br />
..<br />
%setup -qn %name-%custom_version<br />
<br />
=== %fdupes ===<br />
<br />
The %fdupes macro replaces duplicate files by hard links or soft links. Duplicate files waste space in the installed system. %fdupes thus reduces the installed size of your package. There is a [[openSUSE:Packaging_checks|RPMLint]] check that will give an error for the package if it is wasting a considerable amount of space with duplicate files. In that case you have to use %fdupes. <br />
<br />
To use %fdupes, you must include <tt>BuildRequires: fdupes</tt> in the spec file.<br />
<br />
You will receive a "no job control" error if you do not BuildRequire fdupes.<br />
The "%fdupes" macro is then undefined and it is copied into the shell script, and the shell treats '%' for job control, resulting in the error.<br />
<br />
Please be careful that these duplicated files do not end up in different subpackages; we have not tried yet what rpm does in the hardlink case. If in doubt, you can use <tt>%fdupes -s</tt>, which will create symlinks that are easier to grasp for rpm and rpmlint will give a "dangling symlink" error if the file and link ended up in different packages.<br />
<br />
Here is an example, combining both symbolic and hard links:<br />
..<br />
# define %fdupes<br />
<strong>BuildRequires: fdupes</strong><br />
..<br />
%install<br />
..<br />
# create symlinks for man pages<br />
%fdupes -s %{buildroot}/%{_mandir}<br />
# create hardlinks for the rest<br />
%fdupes %{buildroot}/%{_prefix}<br />
<br />
fdupes must NOT be used on (%buildroot)/etc and /var when creating hardlinks. All files in /etc are meant to be readily editable, and the presence of hardlinks leads to unexpected behavior, as some editing programs may modify files in-place, and others may recreate the file.<br />
<br />
<tt>%fdupes</tt> is generally safe for use on <tt>/bin</tt>, <tt>/lib</tt>*, <tt>/usr</tt> (= <tt>%_prefix</tt>) and <tt>/sbin</tt>. Do note however that files with same content but different ownership, when hardlinked, will get the ownership of any of its content siblings.<br />
<br />
=== %fillup_and_insserv ===<br />
<br />
This macro can be used to fill up sysconfig files and insserv init scripts.<br />
<br />
Synopsis:<br />
<br />
'''<code>%fillup_and_insserv</code>''' [<code>-finyY</code>] [''<code>sysconfig_filename</code>''] [''<code>init_script_name</code>''] ...<br />
<br />
The <tt>%fillup_and_insserv</tt> macro combines two functions in one command. It is used to insert (fill up) config files in <tt>/etc/sysconfig</tt> and to enable (insserv) services in runlevels. The fillup part assumes a template stored in <tt>/var/adm/fillup-templates/''sysconfig_filename''.%name</tt>.<br />
<br />
The macro is used in the <tt>%post</tt> section of packages that install an init script and want to enable it by default. See [[openSUSE:Packaging_init_scripts#Installation|“Installation”]] for more details. Do not forget to mention the used utilities used in the <tt>PreReq</tt>. The <tt>%insserv_prereq</tt> and <tt>%fillup_prereq</tt> serve this purpose.<br />
<br />
(Actually, since insserv/fillup is only called in <tt>%post</tt>, should <tt>Requires(post)</tt> not be more appropriate than <tt>PreReq</tt>?)<br />
<br />
Options:<br />
<br />
* <code>-f</code> skips the fillup part.<br />
* <code>-i</code> skips the insserv part.<br />
* <code>-n</code> defines that the parameter ''<code>sysconfig_filename</code>'' is used (see below).<br />
* <code>-y</code> causes enabling the init-script by default if the package is installed for the first time (not during an update). It is ignored if <code>X-UnitedLinux-Default-Enabled</code> is specified in the init script.<br />
* <code>-Y</code> forcefully enables the service. This means the service is always activated regardless of the setting before an update.<br />
<br />
Parameters:<br />
<br />
* ''<tt>sysconfig_filename</tt>'' creates a pair with the option <tt>-n</tt> and defines the filename where the configuration is filled up, <tt>/etc/sysconfig/''sysconfig_filename''</tt>. In addition, it defines a name of the file with templates. The macro searches for two possible template files. It prefers <tt>/var/adm/fillup-templates/sysconfig.''sysconfig_filename''.%name</tt> if it is available. Otherwise, it searches for <tt>/var/adm/fillup-templates/sysconfig.''sysconfig_filename''</tt>. The longer variant must be used if multiple packages write to the same config file. By default (that is, when the <tt>-n</tt> option is not used), the template is <tt>/var/adm/fillup-templates/sysconfig.%name</tt> and the target sysconfig file is <tt>/etc/sysconfig/%name</tt>.<br />
* ''<tt>init_script_name</tt>'' defines a name of the init script processed by `<code>insserv</code>`. It must be defined if the <tt>-i</tt> option is not used. More init scripts names can be defined (see examples below).<br />
<br />
Example from the ''mailman'' package:<br />
<br />
Requires(post): %insserv_prereq %fillup_prereq ...<br />
<br />
%post<br />
%{fillup_and_insserv mailman}<br />
<br />
It fills the configuration file <tt>/etc/sysconfig/mailman</tt> from the template <tt>/var/adm/fillup-templates/sysconfig.mailman</tt>.<br />
<br />
Example taken from the ''hwinfo'' package:<br />
<br />
Requires(post): %insserv_prereq<br />
<br />
%post<br />
%{fillup_and_insserv -f -y hwscan}<br />
<br />
It runs `<code>insserv</code>` on <tt>/etc/init.d/hwscan</tt> and enables the service by default. Note that only the <tt>insserv</tt> part is in <tt>PreReq</tt> because the <tt>fillup</tt> part is omitted, as the <tt>-f</tt> option was used.<br />
<br />
Example from the ''openssh'' package:<br />
<br />
%{fillup_and_insserv -n -y ssh sshd}<br />
<br />
It fills the configuration file <tt>/etc/sysconfig/ssh</tt>. The template is taken either from <tt>/var/adm/fillup-templates/sysconfig.ssh.openssh</tt> or from <tt>/var/adm/fillup-templates/sysconfig.ssh</tt>. The first one is preferred. It runs `<code>insserv</code>` on <tt>/etc/init.d/sshd</tt> and enables the service by default during a new installation.<br />
<br />
Example from the ''openldap2'' package:<br />
<br />
%{fillup_and_insserv -n openldap ldap slurpd}<br />
<br />
It fills the configuration file <tt>/etc/sysconfig/openldap</tt>. The template is taken either from <tt>/var/adm/fillup-templates/sysconfig.openldap.openldap2</tt> or from <tt>/var/adm/fillup-templates/sysconfig.openldap</tt>. The former is preferred.<br />
<br />
=== %fillup_only ===<br />
<br />
This macro can be used to fill up sysconfig files.<br />
<br />
Synopsis:<br />
<br />
<code>'''%fillup_only'''</code> [<code>-adns</code>] [''<code>sysconfig_filename</code>''] [''<code>suffix</code>''] [''<code>sysconfig_subdir</code>'']<br />
<br />
The '''%fillup_only''' macro is used to insert (fill up) the variables from a template <tt>/var/adm/fillup-templates/sysconfig.''sysconfig_filename''[-''suffix'']</tt> into a config file <tt>/etc/sysconfig/''sysconfig_filename''</tt>. The base function is similar to '''%fillup_and_insserv -i''', but it allows modifying config files in subdirectories of <tt>/etc/sysconfig</tt>.<br />
<br />
The macro is typically used in the <tt>%post</tt> section. Do not forget to mention the utilities used in the <tt>PreReq</tt> tag. The macro <tt>%fillup_prereq</tt> is intended for this purpose.<br />
<br />
Options:<br />
<br />
* <code>-a</code> uses the package name as a suffix of the syconfig template filename.<br />
* <code>-d</code> defines that the parameter ''<code>sysconf_subdir</code>'' is used (see below).<br />
* <code>-n</code> defines that the parameter ''<code>sysconfig_filename</code>'' is used (see below).<br />
* <code>-s</code> defines that the parameter ''<code>suffix</code>'' is used (see below).<br />
<br />
Parameters:<br />
<br />
* ''<tt>sysconfig_filename</tt>'' creates a pair with the <tt>-n</tt> option and defines the name of the sysconfig file and a name of the file with templates. By default (that is, when the <tt>-n</tt> option is not used), the package name is used instead. So the template <tt>/var/adm/fillup-templates/sysconfig.%name</tt> is filled up to <tt>/etc/sysconfig/%name</tt>.<br />
* ''<tt>sysconfig_template_filename_suffix</tt>'' creates a pair with the <tt>-s</tt> option and defines a suffix of the filename with templates.<br />
* ''<tt>sysconfig_subdir</tt>'' creates a pair with the <tt>-d</tt> option and defines a subdirectory of <tt>/etc/sysconfig</tt> where the synconfig file is located.<br />
<br />
Example from the ''tetex'' package:<br />
<br />
Requires(post): %fillup_prereq<br />
<br />
%post<br />
%fillup_only<br />
<br />
It fills up the config file <tt>/etc/sysconfig/tetex</tt> from the template <tt>/var/adm/fillup-templates/sysconfig.tetex</tt>.<br />
<br />
Example from the ''man'' package:<br />
<br />
%{fillup_only -an cron}<br />
<br />
It fills the config file <tt>/etc/sysconfig/cron</tt> from the template <tt>/var/adm/fillup-templates/sysconfig.cron-man</tt>.<br />
<br />
Example from the ''dhcp'' package:<br />
<br />
%{fillup_only -ans syslog dhcpd}<br />
<br />
It fills the config file <tt>/etc/sysconfig/syslog</tt> from the template <tt>/var/adm/fillup-templates/sysconfig.syslog-dhcpd</tt>.<br />
<br />
Example from the ''samba'' package:<br />
<br />
%fillup_only -nsd dhcp samba-client network<br />
<br />
It fills the config file <tt>/etc/sysconfig/network/dhcp</tt> from the template <tt>/var/adm/fillup-templates/sysconfig.dhcp-samba-client</tt>.<br />
<br />
=== %find_lang ===<br />
<br />
This macro helps to mark locale-dependent files with the respective <code>%lang</code> tag in the file list.<br />
<br />
==== Synopsis ====<br />
<br />
%find_lang ''options'' ''name'' [''filelist'']<br />
<br />
The <tt>%find_lang</tt> macro searches the directories <tt>/usr/share/locale</tt> and <tt>locale/*/LC_MESSAGES</tt> for <tt>''name''.mo</tt> files. It also searches <tt>gnome/help/''name''</tt> and <tt>kde*/share/doc/HTML/*/''name''</tt> directories for a localized documentation. Then it creates the file ''filelist'' where the files are marked with the respective <tt>%lang(locale)</tt> and <tt>%doc</tt> tags. Such a file list can be then passed to the <tt>%files</tt> tag via the <tt>-f</tt> option. See below for an example.<br />
<br />
It is recommended to use this macro only if the [[openSUSE:Specfile_guidelines#Metadata_Tags|BuildRoot]] tag is defined as otherwise the entire system will be searched.<br />
<br />
%find_lang should be used in %install section.<br />
<br />
==== Options ====<br />
<br />
;--without-gnome<br />
: do not find GNOME help files.<br />
<br />
;--without-kde<br />
: do not find KDE help files.<br />
<br />
;--with-qt<br />
: find Qt translation files.<br />
<br />
;--with-man<br />
: find localized man pages.<br />
<br />
;--all-name<br />
: match all package/domain names.<br />
<br />
;--without-mo<br />
: do not find locale files.<br />
<br />
==== Parameters ====<br />
<br />
;''name''<br />
: defines the name of <tt>.mo</tt> files and the name of sub-directories where GNOME and KDE localized documentation is stored. It is also used for the ''filelist'' where the generated file list is stored if the parameter ''filelist'' is not given.<br />
<br />
;''filelist''<br />
: defines the name of the file where the generated list of files is stored. <tt>''name''.lang</tt> is used if not otherwise defined.<br />
<br />
Example from the package <tt>pan</tt>: <br />
<br />
%install<br />
make -i DESTDIR="%{buildroot}" install<br />
%find_lang %{name} # generate a special file list (macro can be used for different file names again)<br />
<br />
%files -f %{name}.lang # use the special file list (add more "-f" for each special file list)<br />
%defattr(-,root,root) # list the other files<br />
%doc README ChangeLog AUTHORS TODO COPYING CREDITS<br />
%attr(755,root,root) %prefix/bin/pan<br />
[&hellip;]<br />
<br />
=== %icon_theme_cache_post / %icon_theme_cache_postun ===<br />
<br />
This macro is used to update the icon theme cache for packages which install icons into hicolor or other icon themes.<br />
It is meant to be called in <tt>%post</tt> and <tt>%postun</tt> sections and takes an option argument which is the name of the updated icon theme where <tt>hicolor</tt> is the default.<br />
<br />
These macros are available from 11.4 on only!<br />
<br />
It requires the <tt>hicolor-icon-theme</tt> package. Example: see [[#.25desktop_database_post_.2F_.25desktop_database_postun|%desktop_database_post / %desktop_database_postun]].<br />
<br />
FIXME: Which tag is needed as Requires(post/postun)?<br />
<br />
=== %lang_package ===<br />
<br />
This macro is used to create a template for a <tt>lang</tt> subpackage.<br />
<br />
It accepts two optional parameters:<br />
<br />
* name: Alternative name for <tt>lang</tt> subpackage.<br />
* requires: Additional <tt>lang</tt> subpackage dependencies.<br />
<br />
Example from the ''k3b'' package:<br />
<br />
Recommends: %{name}-lang = %{version}<br />
...<br />
%package devel<br />
...<br />
%description devel<br />
This package contain files needed for development with k3b.<br />
<br />
%lang_package<br />
<br />
%prep<br />
%setup -q<br />
...<br />
<br />
This will create a <tt>k3b-lang</tt> subpackage. Do not forget to add the<br />
<tt>Recommends</tt> tag to the main package.<br />
<br />
=== %insserv_cleanup ===<br />
<br />
This macro is used to run `<code>insserv</code>` after a package is removed. Each package providing an init script should call this macro in the <tt>%postun</tt> section.<br />
<br />
Example from the ''openldap2'' package:<br />
<br />
%postun<br />
%restart_on_update ldap slurpd<br />
%insserv_cleanup<br />
<br />
=== %insserv_force_if_yast ===<br />
<br />
This macro is a plain call of the `<code>insserv</code>` if the package is not installed by YaST. When YaST is used, it calls `<code>insserv -f</code>` instead. This helps to avoid errors on "out-of-sequence" package installations.<br />
<br />
The macro is used in the <tt>%post</tt> script of packages that install an init script and which want to enable it by default. It is also used if the init script existed prior to SL 8.0 when the START variables were used. See [[openSUSE:Packaging_init_scripts#Installation]], “Installation” for more details. Do not forget to mention the used utilities in the <tt>PreReq</tt> tag. There are the macros <code>%insserv_prereq</code> and <code>%fillup_prereq</code> for this purpose.<br />
<br />
Example from the ''glibc'' package, ''nscd'' subpackage:<br />
<br />
%package -n nscd<br />
PreReq: %insserv_prereq<br />
<br />
%post -n nscd<br />
%{insserv_force_if_yast nscd}<br />
<br />
=== %install_info ===<br />
<br />
This macro updates dir entries for info files.<br />
<br />
Synopsis:<br />
<br />
<code>'''%install_info'''</code> ''<code>install_info_options</code>''<br />
<br />
The '''%install_info''' macro runs `<code>bin/install-info</code>` with some additional tests. It accepts any option from the <tt>install-info</tt> utility. See `<code>man install-info</code>` for more details.<br />
<br />
Each package providing info pages should call this macro in the <tt>%post</tt> section. Do not forget to mention all the used utilities in the <tt>PreReq</tt> tag. The <code>%install_info_prereq</code> macro exists for this purpose.<br />
<br />
Examples:<br />
<br />
Example from the ''zsh'' package:<br />
<br />
Requires(post): %install_info_prereq<br />
Requires(preun): %install_info_prereq<br />
<br />
%post<br />
%install_info --info-dir=%_infodir %_infodir/%name.info.gz<br />
<br />
Example from the ''rplay'' package (a package with multiple info pages):<br />
<br />
Requires(post): %install_info_prereq<br />
Requires(preun): %install_info_prereq<br />
<br />
%post<br />
%install_info --info-dir=%_infodir %_infodir/%name.info.gz<br />
%install_info --info-dir=%_infodir %_infodir/RPLAY.info.gz<br />
%install_info --info-dir=%_infodir %_infodir/RPTP.info.gz<br />
%install_info --info-dir=%_infodir %_infodir/librplay.info.gz<br />
<br />
=== %install_info_delete ===<br />
<br />
This macro removes dir entries for info files.<br />
<br />
Synopsis:<br />
<br />
<code>'''%install_info_delete'''</code> ''<code>install_info_options</code>''<br />
<br />
The macro <span>'''%install_info_delete'''</span> is a complement to the macro <span>'''%install_info'''</span>. It runs <span>'''sbin/install-info --quiet –delete'''</span> with some additional tests. It accepts any option from the <span>'''install-info'''</span> utility. See <span>'''man install-info'''</span> for more details.<br />
<br />
Each package providing info pages should call this macro in <code class="systemitem">%postun</code> script. Do not forget to mention all the utilities used in the <code class="systemitem">PreReq</code> tag. The macro <code class="systemitem">%install_info_prereq</code> is intended for this purpose.<br />
<br />
Examples:<br />
<br />
# This example is taken from the package <code class="systemitem">zsh</code> (also shows the related <code class="systemitem">PreReq</code> tag):<br />
Requires(post): %install_info_prereq<br />
Requires(preun): %install_info_prereq<br />
[...]<br />
%preun<br />
%install_info_delete --info-dir=%_infodir %_infodir/%name.info.gz<br />
# This example is taken from the package <code class="systemitem">rplay</code> (a package with multiple info pages). The example also shows the related <code class="systemitem">PreReq</code> tag):<br />
Requires(post): %install_info_prereq<br />
Requires(preun): %install_info_prereq<br />
<br />
[...]<br />
%preun<br />
for infoname in %name RPLAY RPTP librplay; do<br />
%install_info_delete --info-dir=%_infodir %_infodir/$infoname.info.gz<br />
done<br />
<br />
=== %perl_archlib ===<br />
<br />
This macro is substituted by the path where architecture-specific parts of Perl are installed, for example, <code class="filename">/usr/lib/perl5/5.8.5/i586-linux-thread-multi</code>.<br />
<br />
It is normally only used by the <code class="systemitem">perl</code> package itself and by the macro <code class="systemitem">%perl_process_packlist</code>. See below.<br />
<br />
=== %perl_gen_filelist ===<br />
<br />
Generates an rpmlint happy filelist of your installed files.<br />
<br />
In most cases you only need to check the %doc part<br />
sometimes there is a "Changes" or "ChangeLog",....<br />
<br />
You have to define following parts inside your spec file<br />
<br />
Example:<br />
<br />
%install<br />
%perl_make_install<br />
%perl_process_packlist<br />
%perl_gen_filelist<br />
<br />
%files -f %{name}.files<br />
%defattr(-,root,root)<br />
%doc Changes README<br />
<br />
And here an Example of the generated filelist:<br />
<br />
%dir /usr/lib/perl5/vendor_perl/5.8.8/Algorithm<br />
/usr/lib/perl5/vendor_perl/5.8.8/Algorithm/DiffOld.pm<br />
/usr/lib/perl5/vendor_perl/5.8.8/Algorithm/diff.pl<br />
/usr/lib/perl5/vendor_perl/5.8.8/Algorithm/Diff.pm<br />
/usr/lib/perl5/vendor_perl/5.8.8/Algorithm/diffnew.pl<br />
/usr/lib/perl5/vendor_perl/5.8.8/Algorithm/cdiff.pl<br />
/usr/lib/perl5/vendor_perl/5.8.8/Algorithm/htmldiff.pl<br />
%dir /usr/lib/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/auto/Algorithm<br />
%dir /usr/lib/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/auto/Algorithm/Diff<br />
/usr/lib/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/auto/Algorithm/Diff/.packlist<br />
/usr/share/man/man?/*<br />
/var/adm/perl-modules/perl-Algorithm-Diff<br />
<br />
=== %perl_make_install ===<br />
<br />
This macro does the <span>'''make install'''</span> call correctly on various products. Before SL 9.0, the normal way to invoke it was:<br />
<br />
make PREFIX="%buildroot/%_prefix" \<br />
INSTALLMAN1DIR="%buildroot/%_mandir/man1" \<br />
INSTALLMAN3DIR="%buildroot/%_mandir/man3" \<br />
install<br />
<br />
For 9.0 and later versions:<br />
<br />
make DESTDIR="%buildroot" install_vendor<br />
<br />
With the macro <code class="systemitem">%perl_make_install</code>, this is done correctly according to the version.<br />
<br />
This example comes from the package <code class="systemitem">perl-URI</code><nowiki>:</nowiki><br />
<br />
%install<br />
%perl_make_install<br />
<br />
=== %perl_process_packlist ===<br />
<br />
This macro prepares some files, related to perl modules, for the final package. It does the following actions:<br />
<br />
Each package including a perl module should call this macro in the section <code class="systemitem">%install</code>.<br />
<br />
==== for 0%{?suse_version} >= 1140 ====<br />
<br />
* Searches for the installed <code class="filename">.packlist</code> files and removes them from <code class="filename">%buildroot/%perl_vendorarch/auto</code>.<br />
If <code class="filename">%_target_cpu == noarch</code> then empty directories are removed from <code class="filename">%buildroot/%perl_vendorarch/auto</code>.<br />
* Removes the <code class="filename">%buildroot/%perl_archlib/perllocal.pod</code> file.<br />
<br />
This example is taken from the package <code class="systemitem">perl-HTML-Parser</code><nowiki>:</nowiki><br />
<br />
%install<br />
%perl_make_install<br />
%perl_process_packlist<br />
%perl_gen_filelist<br />
<br />
%files -f %name.files<br />
%doc Changes mkhctype mkpfunc README TODO eg<br />
<br />
%changelog<br />
<br />
==== for 0%{?suse_version} <= 1130 ====<br />
<br />
* Removes <code class="filename">%buildroot</code> from <code class="filename">%perl_archlib/perllocal.pod</code> and renames the file to a package-specific file. See below for more details.<br />
* Searches for the installed <code class="filename">.packlist</code> files and removes <code class="filename">%buildroot</code> from them.<br />
<br />
The file <code class="filename">%perl_archlib/perllocal.pod</code> must be renamed because it contains information about additional installed perl modules and evidently cannot be installed at the same place from multiple packages. Therefore, it is renamed and a special SuSEconfig module, <code class="filename">/sbin/conf.d/SuSEconfig.perl</code>, adds this information to the system <code class="filename">%perl_archlib/perllocal.pod</code> after the package is installed.<br />
<br />
This example is taken from the package <code class="systemitem">perl-URI</code><nowiki>:</nowiki><br />
<br />
%install<br />
%perl_make_install<br />
%perl_process_packlist<br />
<br />
%files<br />
[...]<br />
/var/adm/perl-modules/%name<br />
<br />
=== %perl_sitearch ===<br />
<br />
This macro is substituted by the path where architecture-specific parts of Perl modules are installed by a local administrator (<code class="filename">/usr/lib/perl5/site_perl/5.8.5/i586-linux-thread-multi</code>). The packages distributed within SUSE Linux use the path defined by <code class="systemitem">%perl_vendorarch</code> instead. See below.<br />
<br />
=== %perl_sitelib ===<br />
<br />
This macro is substituted by the path where architecture-independent parts of Perl modules are installed by a local administrator (<code class="filename">/usr/lib/perl5/site_perl/5.8.5</code>). The packages distributed within SUSE Linux use the path defined by <code class="systemitem">%perl_vendorlib</code> instead (see below).<br />
<br />
=== %perl_vendorarch ===<br />
<br />
This macro is substituted by the path where architecture-specific parts of Perl modules are installed by a Linux vendor (<code class="filename">/usr/lib/perl5/vendor_perl/5.8.5/i586-linux-thread-multi</code>). The macro is typically used in the file list. This example comes from the package <code class="systemitem">perl-URI</code><nowiki>:</nowiki><br />
<br />
%files<br />
[...]<br />
%perl_vendorarch/auto/URI<br />
<br />
This path has been used since SL 9.0. Until then, the Perl modules were installed below <code class="filename">/usr/lib/perl5/site_perl</code> using the macro <code class="systemitem">%perl_sitearch</code>. The directory <code class="filename">site_perl</code> is now intended for modules installed by a local administrator (see above at <code class="systemitem">%perl_sitearch</code>).<br />
<br />
=== %perl_vendorlib ===<br />
<br />
This macro substitutes for the path where architecture-independent parts of Perl modules are installed by a Linux vendor (<code class="filename">/usr/lib/perl5/vendor_perl/5.8.5</code>). The macro is typically used in the file list. This example comes from the package <code class="systemitem">perl-URI</code><nowiki>:</nowiki><br />
<br />
%files<br />
[...]<br />
%perl_vendorlib/URI.pm<br />
%perl_vendorlib/URI<br />
<br />
This path has been used since SL 9.0. Until then, the Perl modules were installed below <code class="filename">/usr/lib/perl5/site_perl</code> using the macro <code class="systemitem">%perl_sitearch</code>. The directory <code class="filename">site_perl</code> is now intended for modules installed by a local administrator (see above at <code class="systemitem">%perl_sitelib</code>).<br />
<br />
=== %perl_version ===<br />
<br />
This macro is substituted by the version of Perl used for building the package, such as <code class="literal">5.8.5</code>. It is used in packages providing a perl module to define the dependency on Perl.<br />
<br />
It is typically used the following way. This example is taken from the package <code class="systemitem">perl-URI</code><nowiki>:</nowiki><br />
<br />
%perl_requires<br />
<br />
and is expanded this way <nowiki>:</nowiki><br />
<br />
%perl_requires() \<br />
%if 0%{?suse_version} > 0 && 0%{?suse_version} < 1700 \<br />
Requires: perl = %perl_version \<br />
%endif<br />
<br />
=== %py_incdir ===<br />
<br />
This macro substituted by the path where Python header files are installed, such as <code class="filename">/usr/include/python2.3</code>. See [[openSUSE:Packaging_Python]], “Python Modules” for an example.<br />
<br />
=== %py_libdir ===<br />
<br />
This macro is substituted by the path where Python modules are installed, such as <code class="filename">/usr/lib/python2.3</code>. See [[openSUSE:Packaging_Python]], “Python Modules” for an example.<br />
<br />
=== %py_requires ===<br />
<br />
This macro is substituted by <code class="systemitem">PreReq</code> and <code class="systemitem">BuildRequires</code> tags. This defines dependency on the same python major version as is used during build. See [[openSUSE:Packaging_Python]], “Python Modules” for an example.<br />
<br />
=== %py_sitedir ===<br />
<br />
This macro is substituted by the path where all extra Python modules all installed, such as <code class="filename">/usr/lib/python2.3/site-packages</code>. See [[openSUSE:Packaging_Python|“Python Modules”]] for an example.<br />
<br />
=== %py_ver ===<br />
<br />
This macro is substituted by the Python major version, such as <code class="literal">2.3</code>. See [[openSUSE:Packaging_Python]], “Python Modules” for an example.<br />
<br />
=== %remove_and_set ===<br />
<br />
This macro is used to remove obsolete sysconfig variables.<br />
<br />
Synopsis:<br />
<br />
<span>'''%remove_and_set'''</span> [<code class="option">-ny</code>] [''<code>sysconfig_filename</code>''] ''<code>variable</code>''...<br />
<br />
The macro <span>'''%remove_and_set'''</span> removes variables from <code class="filename">/etc/rc.config</code> and <code class="filename">/etc/sysconfig/sysconfig_filename</code> and sets them in the actual environment for further handling. If a variable is not found, it is set to <code class="literal">"no"</code> by default or it is set to <code class="literal">“yes”</code> if the option <code class="option">-y</code> is used.<br />
<br />
Options:<br />
<br />
* <code class="option">-n</code> defines that the parameter ''<code>sysconfig_filename</code>'' is used (see below).<br />
* <code class="option">-y</code> sets the default value to <code class="literal">“yes”.</code><br />
<br />
Parameters:<br />
<br />
* ''<code>sysconfig_filename</code>'' creates a pair with the option <code class="option">-n</code> and defines the syconfig filename. The package name (<span>'''%name'''</span>) is used as the sysconfig filename otherwise.<br />
* ''<code>variable</code>'' defines the name of a variable to remove. Multiple variables can be defined.<br />
<br />
Examples:<br />
<br />
# This example is taken from the package <code class="systemitem">postfix</code><nowiki>:</nowiki><br />
%{fillup_and_insserv -y postfix}<br />
if [ -f etc/sysconfig/mail ]; then<br />
. etc/sysconfig/mail<br />
if [ -n "$NULLCLIENT" ]; then<br />
RCTMP="etc/sysconfig/postfix.$$"<br />
sed "s/^POSTFIX_NULLCLIENT.*/POSTFIX_NULLCLIENT=\"$ \"/" \<br />
etc/sysconfig/postfix &gt;"$RCTMP"<br />
mv "$RCTMP" etc/sysconfig/postfix<br />
fi<br />
fi<br />
%{remove_and_set -n mail NULLCLIENT}<br />
This code sets the variable <code class="systemitem">POSTFIX_NULLCLIENT</code> from <code class="filename">etc/sysconfig/postfix</code> to the value of the obsolete variable <code class="systemitem">NULLCLIENT</code> from <code class="filename">etc/sysconfig/mail</code>. Then the obsolete variable is removed.<br />
# This example is taken from the package <code class="systemitem">autofs</code><nowiki>:</nowiki><br />
<nowiki>%post<br />
%{fillup_and_insserv autofs}<br />
# needed for update from 7.3 and before<br />
%{remove_and_set USE_NIS_FOR_AUTOFS USE_NISPLUS_FOR_AUTOFS}<br />
if [ $USE_NIS_FOR_AUTOFS == "yes" ] ; then<br />
if `grep "^automount:" etc/nsswitch.conf | \<br />
grep -vqw nis` ; then<br />
sed "s/^automount:.*/&amp; nis/" &lt; etc/nsswitch.conf \<br />
&gt;etc/nsswitch.conf.new<br />
mv etc/nsswitch.conf.new etc/nsswitch.conf<br />
fi<br />
fi<br />
if [ $USE_NISPLUS_FOR_AUTOFS == "yes" ] ; then<br />
if `grep "^automount:" etc/nsswitch.conf | \<br />
grep -vqw nisplus` ; then<br />
sed "s/^automount:.*/&amp; nisplus/" &lt; etc/nsswitch.conf \<br />
&gt; etc/nsswitch.conf<br />
mv etc/nsswitch.conf.new etc/nsswitch.conf<br />
fi<br />
fi</nowiki><br />
The obsolete variables <code class="systemitem">USE_NIS_FOR_AUTOFS</code>, <code class="systemitem">USE_NISPLUS_FOR_AUTOFS</code> are removed from <code class="filename">/etc/rc_config</code> and <code class="filename">/etc/sysconfig/autofs</code> and the removed values are used to modify an actual configuration.<br />
The detected values cannot be used in the previous example because the macro <span>'''%remove_and_set'''</span> is able to set only values <code class="literal">“yes”</code> or <code class="literal">“no”</code> in the environment.<br />
<br />
=== %restart_on_update ===<br />
<br />
This macro restarts a service after an update.<br />
<br />
Synopsis:<br />
<br />
<span>'''%restart_on_update'''</span> ''<code>service</code>''...<br />
<br />
The macro <span>'''%restart_on_update'''</span> runs <span>'''systemctl try-restart'''</span> if not running under YaST in the <code class="systemitem">instsys</code> mode. Multiple services can be defined.<br />
<br />
This macro is usually used in the <code class="systemitem">%postun</code> script of packages providing a service. However, it cannot be used if it cannot be guaranteed that the service will work after an update.<br />
<br />
Examples:<br />
<br />
# This example is taken from the package <code class="systemitem">rsync</code><nowiki>:</nowiki><br />
%postun<br />
%restart_on_update rsyncd<br />
%insserv_cleanup<br />
# This example is taken from the package <code class="systemitem">samba</code> (restarts two services):<br />
%postun<br />
%restart_on_update nmb smb<br />
%insserv_cleanup<br />
<br />
=== %run_ldconfig (<span style="font-weight:bold; color:red">deprecated</span>) ===<br />
<br />
This macro runs <span>'''ldconfig'''</span> if not running from YaST. YaST runs <span>'''ldconfig'''</span> itself after all selected packages are installed.<br />
<br />
It was used in both <code class="systemitem">%post</code> and <code class="systemitem">%postun</code> scripts of packages providing a library. <span style="font-weight:bold; color:red">The macro is deprecated and should not be used anymore</span>. Instead, <span>'''/sbin/ldconfig'''</span> should be called directly both scripts, even from YaST, to keep from breaking other <code class="systemitem">%post</code> scripts. It could be done the following way:<br />
<br />
%post -p /sbin/ldconfig<br />
%postun -p /sbin/ldconfig<br />
<br />
If <span>'''ldconfig'''</span> is not the only command, the <code class="option">-p</code> option is not usable. For example, the <code class="systemitem">%post</code> script could look like:<br />
<br />
%post<br />
/sbin/ldconfig<br />
[...]<br />
<br />
(Keep in mind that RPM will interpret "[...]" to include any comments, which might be a surprise if they were intended for the next section of the spec file!)<br />
<br />
=== %run_permissions (<span style="font-weight:bold; color:red">deprecated</span>) ===<br />
<br />
This macro runs ''SuSEconfig --module permissions'' to adjust file permissions<br />
according to the system's security setting.<br />
<br />
Note: Running SuSEconfig has the disadvantage that permissions of<br />
all installed files are adjusted, not just the ones that belong to<br />
the package. Therefore this macro is <span style="font-weight:bold; color:red">deprecated</span> since openSUSE 11.4, use [[#%set_permissions|%set_permissions]] instead.<br />
<br />
''%run_permissions'' needs to be called in the ''%post'' script of packages<br />
that install files handled by ''/etc/permissions.*''. The ''permissions''<br />
package needs to be in ''PreReq'' so ''SuSEconfig.permissions'' is guaranteed<br />
to be available at install time.<br />
<br />
In addition the macro<br />
[[#%verify_permissions|%verify_permissions]]<br />
needs to be called as ''%verifyscript''<br />
<br />
Example:<br />
<br />
PreReq: permissions<br />
[...]<br />
%post<br />
%run_permissions<br />
<br />
=== %service_add_pre ===<br />
<br />
Needs to be called in %pre section of packages that install systemd<br />
service. Pass the list of service files as parameters.<br />
<br />
%pre<br />
%service_add_pre demo.service demo1.service<br />
<br />
=== service_add_post ===<br />
<br />
Needs to be called in %post section of packages that install systemd<br />
service. Pass the list of service files as parameters.<br />
<br />
%post<br />
%service_add_post demo.service demo1.service<br />
<br />
=== service_del_preun ===<br />
<br />
Needs to be called in %preun section of packages that install systemd<br />
service. Pass the list of service files as parameters.<br />
<br />
%preun<br />
%service_del_preun demo.service<br />
<br />
=== %service_del_postun ===<br />
<br />
Needs to be called in %postun section of packages that install systemd<br />
service. Pass the list of service files as parameters.<br />
<br />
%postun<br />
%service_del_postun demo.service<br />
<br />
=== %set_permissions ===<br />
<br />
This macro adjusts permissions of the specified files according to the system's security setting.<br />
<br />
Available since openSUSE 11.4<br />
<br />
''%set_permissions'' needs to be called in the ''%post'' script of packages<br />
that install files handled by ''/etc/permissions.*''. The ''permissions''<br />
package needs to be in ''PreReq'' so ''chkstat'' is guaranteed to be available<br />
at install time. The parameter is the name of the permissions config file of<br />
the package (usually identical to the package name).<br />
<br />
In addition the macro<br />
[[#%verify_permissions|%verify_permissions]]<br />
needs to be called as ''%verifyscript''<br />
<br />
Example:<br />
<br />
PreReq: permissions<br />
[...]<br />
%post<br />
%set_permissions /bin/ping<br />
<br />
=== %sles_version ===<br />
<br />
This macro expands to the version of SLES where the package is built. It is <code class="literal">”7”</code> for SLES7, <code class="literal">”8”</code> for SLES8, etc. It is <code class="literal">”0”</code> when not building on SLES.<br />
<br />
See also <code class="systemitem">%suse_version</code> and <code class="systemitem">%ul_version</code>.<br><br />
And [[openSUSE:Build Service cross distribution howto#Detect_a_distribution_flavor_for_special_code]]<br />
<br />
This example is taken from the package <code class="systemitem">pam-modules</code><nowiki>:</nowiki><br />
<br />
<nowiki>%install<br />
[...]<br />
# On UL or SLES, we have other defaults<br />
%if %sles_version &gt;= 8<br />
cp %_sourcedir/pam_pwcheck.conf.sles \<br />
%buildroot/etc/security/pam_pwcheck.conf<br />
%endif</nowiki><br />
<br />
=== %stop_on_removal ===<br />
<br />
This macro stops a service after a package is removed.<br />
<br />
Synopsis:<br />
<br />
<span>'''%stop_on_removal'''</span> ''<code>service</code>''...<br />
<br />
The macro <span>'''%stop_on_removal'''</span> runs <span>'''/etc/init.d/service stop'''</span> if not running from YaST in the instsys mode. Multiple services can be defined.<br />
<br />
Each package providing a service that can be stopped should call this macro on all services in the <code class="systemitem">%preun</code> script.<br />
<br />
Examples:<br />
<br />
# This example is taken from the package <code class="systemitem">rsync</code><nowiki>:</nowiki><br />
%preun<br />
%stop_on_removal rsyncd<br />
# This example is taken from the package <code class="systemitem">samba</code> (stops two services):<br />
%preun<br />
%stop_on_removal smb nmb<br />
<br />
=== %suse_update_config ===<br />
<br />
This macro updates some auto-stuff related files.<br />
<br />
Usage:<br />
<br />
<span>'''%suse_update_config'''</span> [<code class="option">-fcl</code>] [''<code>dir</code>'' ...]<br />
<br />
This macro takes the following actions for the current directory and all directories given as parameters:<br />
<br />
* <code class="filename">config.guess</code> and <code class="filename">config.sub</code> are overwritten by their most current versions from <code class="filename">/usr/share/automake*/</code>.<br />
* <code class="filename">depcomp</code> and <code class="filename">missing</code> are added if not present in the processed directory but present in <code class="filename">/usr/share/automake*/</code>.<br />
* <code class="filename">ltconfig</code> and <code class="filename">ltmain.sh</code> are patched to accept both <code class="literal">linux-gnu</code> and <code class="literal">linux</code>.<br />
* <code class="filename">/lib</code> is replaced by <code class="filename">/%_lib</code> in some occurrences in both <code class="filename">ltconfig</code> and <code class="filename">ltmain.sh</code>.<br />
<br />
This macro should be called in all packages using the problematic files. However, it is not needed when <span>'''autoreconf'''</span> or <span>'''aclocal'''</span>, <span>'''libtoolize'''</span>, <span>'''automake'''</span>, and <span>'''autoconf'''</span> is used, because they are able to update the needed things.<br />
<br />
This macro should be tested for existence when used in the section <code class="systemitem">%prep</code>. This allows running this section on other distributions where the macro is not available. See the examples below.<br />
<br />
Options:<br />
<br />
* <code class="option">-c</code> — do not update <code class="filename">config.guess</code>, <code class="filename">config.sub</code>, <code class="filename">depcomp</code> and <code class="filename">missing</code><br />
* <code class="option">-f</code> — force, ignore time stamps<br />
* <code class="option">-l</code> — do not update <code class="filename">ltconfig</code> and <code class="filename">ltmain.sh</code><br />
<br />
Parameters:<br />
<br />
* ''<code>dir</code>'' defines an additional directory where the files should be updated. Multiple directories can be defined.<br />
<br />
Examples:<br />
<br />
# This example is taken from the package <code class="systemitem">libunicode</code><nowiki>:</nowiki><br />
%prep<br />
%setup<br />
%patch -P 1 -p1<br />
<br />
%build<br />
%{?suse_update_config:%{suse_update_config -f}}<br />
%configure<br />
make %{?_smp_mflags}<br />
# This example is taken from the package <code class="systemitem">xosview</code> (updates files in both <code class="filename">./</code> and <code class="filename">./config</code> directories):<br />
%prep<br />
%setup -q<br />
%patch -P 1 -p0 -b ".serial"<br />
[...]<br />
%{?suse_update_config:%{suse_update_config -f config}}<br />
<br />
%build<br />
%ifarch ppc<br />
export SYSTEM=powerpc-suse-linux<br />
%else<br />
export SYSTEM=%_target_cpu-suse-linux<br />
%endif<br />
(cd config/; autoconf; cp configure ../)<br />
./configure $SYSTEM \<br />
--with-x \<br />
--enable-auto-depend \<br />
--enable-linux-syscalls \<br />
--prefix=/usr/X11R6 \<br />
--disable-linux-memstat<br />
make clean<br />
<br />
=== %suse_update_desktop_file ===<br />
<br />
This macro updates .desktop files.<br />
<br />
Synopsis:<br />
<br />
<span>'''%suse_update_desktop_file'''</span> <code class="option">-c</code> ''<code>filename</code>'' ''<code>name</code>'' ''<code>generic-name</code>'' ''<code>exec</code>'' ''<code>icon</code>'' [''<code>category</code>'']...<br />
<br />
<span>'''%suse_update_desktop_file'''</span> [<code class="option">-inru</code>] [<code class="option">-D</code> ''<code>docpath</code>''] [<code class="option">-N</code> ''<code>name</code>''] [<code class="option">-G</code> ''<code>genericname</code>''] ''<code>filename</code>'' [''<code>category</code>'']...<br />
<br />
The macro <span>'''%suse_update_desktop_file'''</span> updates translations, adds categories (needed to sort menus), and does some sanity checks in the given .desktop file. It requires the package <code class="systemitem">update-desktop-files</code>.<br />
<br />
Each package providing a .desktop file should call this macro for all basenames of .desktop files (without .desktop suffix) in the section <code class="systemitem">%install</code> after the desktop-files have been installed under <code>/usr/share/applications</code> or <code>/etc/xdg/autostart</code>. Do not forget to mention the package <code class="systemitem">update-desktop-files</code> in the [[openSUSE:Specfile_guidelines#BuildRequires|BuildRequires]] tag. It is included in the meta packages:<br />
<br />
* <code class="systemitem">gnome2-devel-packages</code><br />
* <code class="systemitem">gtk2-devel-packages</code><br />
* <code class="systemitem">kde3-devel-packages</code><br />
* <code class="systemitem">qt3-devel-packages</code><br />
* <code class="systemitem">yast2-core-devel-packages</code><br />
* <code class="systemitem">yast2-devel-packages</code><br />
<br />
The package <code class="systemitem">update-desktop-files</code> need not be explicitly mentioned in the <code class="systemitem">BuildRequires</code> tag if any of these meta packages is already there.<br />
<br />
Options:<br />
<br />
* <code class="option">-c</code> ''<code>filename</code>'' ''<code>name</code>'' ''<code>comment</code>'' ''<code>exec</code>'' ''<code>icon</code>'' [''<code>category</code>''] — Create a new .desktop file initialized by the parameters ''<code>filename</code>'', ''<code>name</code>'', ''<code>comment</code>'', ''<code>exec</code>'', ''<code>icon</code>'', and ''<code>category</code>'' the following way:<br />
[Desktop Entry]<br />
Name=name<br />
GenericName=comment<br />
Type=Application<br />
Exec=exec<br />
Icon=icon<br />
Categories=category;....<br />
and install it as <code class="filename">%buildroot/usr/share/applications/filename.desktop</code>.<br />
* <code class="option">-i</code> — Search <code class="filename">%_sourcedir</code> and <code class="filename">/usr/share/update-desktop-files/templates</code> for the template <code class="filename">filename.desktop</code> and install it as <code class="filename">%buildroot/usr/share/applications/filename.desktop</code>.<br />
* <code class="option">-n</code> — Do not update translations. It is useful if the lines <code class="literal">Name=</code> and <code class="literal">GenericName=</code> contain a string that cannot be translated.<br />
* <code class="option">-r</code> — Replace categories defined in the .desktop file with the new one defined by the parameter category. By default, the new categories are only added after the already included categories.<br />
* <code class="option">-u</code> — Add the line <code class="literal">X-SuSE-Unimportant=true</code> to the .desktop file.<br />
* <code class="option">-D</code>''<code>docpath</code>'' Sets the .desktop file DocPath entry.<br />
* <code class="option">-N</code>''<code>name</code>'' Sets the .desktop file Name entry.<br />
* <code class="option">-G</code>''<code>genericname</code>'' Sets the .desktop file GenericName entry.<br />
<br />
Parameters:<br />
<br />
* ''<code>filename</code>'' defines a filename of the .desktop file. The value is the filename without the suffix <code class="filename">.desktop</code>.<br />
* ''<code>category</code>'' is used to add or modify the line <code class="literal">Categories=</code> in the .desktop file. This line is used to sort entries into submenus.<br />
<br />
Examples:<br />
<br />
# This example is taken from the package <code class="systemitem">kvim</code> (also shows the related parts of <code class="systemitem">BuildRequires</code> tag and <code class="systemitem">%files</code> section):<br />
<br />
BuildRequires: ... update-desktop-files ...<br />
<br />
%install<br />
[...]<br />
%suse_update_desktop_file KVim TextEditor<br />
<br />
%files<br />
[...]<br />
/opt/kde3/share/applnk/*/*.desktop<br />
This code updates translations in the already installed <code class="filename">/opt/kde3/share/applnk/Editors/KVim.desktop</code>. As the original .desktop file does not contain the line <code class="literal">Categories=</code>, it is initialized to <code class="literal">Categories=TextEditor;</code>.<br />
# This example is from the package <code class="systemitem">crack-atack</code><nowiki>: (also shows the related parts of </nowiki><code class="systemitem">BuildRequires</code> tag, <code class="systemitem">Source</code> tags and <code class="systemitem">%files</code> section):<br />
<br />
BuildRequires: ... update-desktop-files ...<br />
<br />
Source1: %name.desktop<br />
Source2: %name-xtreme.desktop<br />
[...]<br />
<br />
%install<br />
[...]<br />
%suse_update_desktop_file -i %name Game ArcadeGame<br />
%suse_update_desktop_file -i %name-xtreme Game ArcadeGame<br />
<br />
%files<br />
[...]<br />
/usr/share/applications/%name.desktop<br />
/usr/share/applications/%name-xtreme.desktop<br />
This code finds the two templates in <code class="filename">%_sourcedir</code> and installs them into <code class="filename">/usr/share/applications</code>. See the section <code class="systemitem">%files</code> for the final path. It also updates translations. As the templates do not contain the line <code class="literal">Categories=</code>, it is initialized to <code class="literal">Categories=Game;ArcadeGame;</code>.<br />
# This example is taken from the package <code class="systemitem">koffice</code><nowiki>:</nowiki><br />
%install<br />
[...] <br />
%suse_update_desktop_file kugar Office Viewer<br />
%suse_update_desktop_file -r karbon Graphics VectorGraphics<br />
%suse_update_desktop_file kivio Office FlowChart<br />
%suse_update_desktop_file kpresenter Office Presentation<br />
%suse_update_desktop_file kchart Office FlowChart<br />
%suse_update_desktop_file kspread Office Spreadsheet<br />
%suse_update_desktop_file -u KThesaurus Office<br />
%suse_update_desktop_file -u kformula Office<br />
%suse_update_desktop_file kword Office WordProcessor<br />
%suse_update_desktop_file -u koshell Office Core-Office<br />
This code updates translations in the already installed desktop files. In addition, for example, <code class="filename">Kthesaurus.desktop</code> is marked as unimportant and the obsolete line <code class="literal">Categories=</code> is replaced with <code class="literal">Categories=VectorGraphics;</code> in <code class="filename">karbon.dekstop</code>.<br />
# This example is taken from the package <code class="systemitem">qbrew</code><nowiki>:</nowiki><br />
%suse_update_desktop_file -c qbrew QBrew \<br />
"A homebrewer's recipe calculator" \<br />
qbrew "" Science<br />
# This code creates a .desktop file:<br />
[Desktop Entry]<br />
Name=QBrew<br />
GenericName=A homebrewer's recipe calculator<br />
Type=Application<br />
Exec=qbrew<br />
Icon=<br />
Categories=Science;<br />
Then it adds available translations and installs it as <code class="filename">/usr/share/applications/qbrew.desktop</code>.<br />
<br />
==== Known issues ====<br />
# The setting<br />
Categories=Application;Office;<br />
is typical for Fedora packages, but yields to build failures in SUSE. The error message says '''No sufficient Category definition'''.<br />
You need to use the '-r' flag to remove the offending category 'Application' and replace it by only [[openSUSE:Packaging_desktop_menu_categories|allowed categories]]. The -r option must come before the name to be effective.<br />
%suse_update_desktop_file -u -r -G 'OCR Suite' %{name} Office Graphics Scanning OCR<br />
<br />
<br />
<br />
If this command leads to an error message '''/var/tmp/rpm-tmp.mkeCpx: line 54: fg: no job control''' please try adding<br />
BuildRequires: update-desktop-files<br />
<br />
# The setting<br />
Version=0.5<br />
is typical for Fedora packages, but yields a warning with SUSE. Manual patching is required to resolve this warning.<br />
<br />
=== %suse_version ===<br />
<br />
This macro expands to the version of SUSE Linux / openSUSE where the package is built. It is "1000" for SUSE Linux 10.0, "1020" for openSUSE 10.2 and so on.<br />
<br />
See also <code class="systemitem">%sles_version</code> and <code class="systemitem">%ul_version</code>.<br><br />
And [[openSUSE:Build Service cross distribution howto#Detect_a_distribution_flavor_for_special_code]]<br />
<br />
It can be used to used for version check<br />
..<br />
%if 0%{?suse_version} >= 1110<br />
BuildRequires: new-package-introduced-in-11.0<br />
%endif<br />
..<br />
<br />
Or to check if the package is being built for openSUSE<br />
<br />
..<br />
%if 0%{?suse_version}<br />
BuildRequires: libqt4-devel<br />
%else<br />
BuildRequires: qt4-devel<br />
%endif<br />
...<br />
<br />
=== %tcl_version ===<br />
<br />
This macro expands to the version of Tcl used on the product where the package is built. It is <code class="literal">"8.3"</code> for tcl-8.3, <code class="literal">“8.4”</code> for tcl-8.4, etc.<br />
<br />
This example is taken from the package <code class="systemitem">vkeybd</code><nowiki>:</nowiki><br />
<br />
%build<br />
make PREFIX="%_prefix" \<br />
TCL_VERSION="%tcl_version" \<br />
XLIB="-L/usr/X11R6/lib64 -L/usr/X11R6/lib -lX11" \<br />
USE_LADCCA=1<br />
<br />
=== %ul_version ===<br />
<br />
This macro expands to a version of United Linux where the package is built. It is <code class="literal">“1”</code> for UL 1.0 and <code class="literal">“0”</code> when not building on UL.<br />
<br />
See also <code class="systemitem">%sles_version</code> and <code class="systemitem">%suse_version</code>.<br />
<br />
This example is taken from the package <code class="systemitem">installation-images</code><nowiki>:</nowiki><br />
<br />
%build<br />
[...]<br />
%ifarch %ix86<br />
themes="SuSE Home"<br />
%else<br />
themes=SuSE<br />
%endif<br />
%if %ul_version &gt; 0<br />
themes=UnitedLinux<br />
%else<br />
%if %sles_version &gt; 0<br />
themes="SuSE-SLES"<br />
%endif<br />
<br />
=== %verify_permissions ===<br />
<br />
This macro verifies permissions of files handled via<br />
''/etc/permissions.*'' according to the system's security settings.<br />
<br />
Permissions attributes in the package should reflect the setting of<br />
the ''secure'' level (/etc/permissions.secure).<br />
<br />
To prevent rpm from complaining about the packaged permission<br />
settings affected files need to be tagged accordingly with e.g.<br />
''%verify(not mode)''.<br />
<br />
Usage:<br />
<br />
'''%verify_permissions''' [<code class="option">-f</code> ''<code>filelist</code>''] [<code class="option">-e</code> ''<code>file</code>''] ...<br />
<br />
''%verify_permissions'' needs to be used together with<br />
[[#%run_permissions|%run_permissions]] or [[#%set_permissions|%set_permissions]]<br />
<br />
<br />
Options:<br />
<br />
* <code class="option">-e</code> file — specifies which file to check<br />
* <code class="option">-f</code> filelist — specifies a file with a list of files to check (useful if there are many).<br />
<br />
Both options can be repeated.<br />
<br />
Example 1, files with variable mode:<br />
<br />
%verifyscript<br />
%verify_permissions -e /usr/bin/foo -e /bin/bar<br />
[...]<br />
%files<br />
%defattr(-,root,root)<br />
%verify(not mode) %attr(0755,root,root) /usr/bin/foo<br />
%verify(not mode) %attr(0755,root,root) /bin/bar<br />
<br />
<br />
Example 2, file with variable mode and user:<br />
<br />
%verifyscript<br />
%verify_permissions -e /etc/foo<br />
[...]<br />
%files<br />
%defattr(-,root,root)<br />
%verify(not mode user) %attr(0600,joe,root) /etc/foo<br />
<br />
Example 3, file with support for fscaps or setuid<br />
<br />
%verifyscript<br />
%verify_permissions -e /bin/foo<br />
[...]<br />
%files<br />
%defattr(-,root,root)<br />
%verify(not mode caps) %attr(4755,root,root) /bin/foo<br />
<br />
=== %create_subdir_filelist / %create_exclude_filelist ===<br />
<code>%create_subdir_filelist</code> macro helps to create sub-packages by looking at what's installed from a specified sub-directory (and a matching doc/ directory) of the source. It requires a parameter <code class="option">-d <directory></code> and creates a file list called filelists/<directory> unless a parameter <code class="option">-f <filelistname></code> is given which then let it appends to filelists/<filelistname>. If a <code class="option">-v <develfilelistname></code> parameter is given, development files like headers, cmake definitions and .so symlinks will be written to filelists/<develfilelistname> instead. <br />
<br />
<code>%create_exclude_filelist</code> creates an exclude file list from all file lists that were created by <code>%create_subdir_filelist</code>. It is intended to be used for the main package, to ensure that files that were moved into a subpackage are not packaged twice.<br />
<br />
Usage in ''koffice2.spec'' (shortened):<br />
<br />
..<br />
%install<br />
cd build<br />
%make_install<br />
%create_subdir_filelist -d kplato -v devel<br />
%create_subdir_filelist -d kword -v devel<br />
%create_subdir_filelist -d filters/kword -f kword -v devel<br />
..<br />
cd ..<br />
sed -ri s,.*/usr/share/doc/kde/HTML/en/.*,, filelists/*<br />
%create_exclude_filelist<br />
rm -rf $RPM_BUILD_ROOT/usr/share/doc/kde/HTML/en<br />
..<br />
%files devel -f filelists/devel<br />
..<br />
%files kplato -f filelists/kplato<br />
..<br />
%files kword -f filelists/kword<br />
..<br />
%files -f filelists/exclude<br />
<br />
This example also shows how it's optionally possible to merge/change the automatically created file lists.<br />
<br />
=== %make_jobs ===<br />
This is just a macro that calls <code>%make</code> with the right jobs parameter, if icecream is in use. This is for local test builds on a multiprocessor machine and/or the Factory builds, which use distributed buildpower to speed up compilation.<br />
<br />
=== %glib2_gsettings_schema ===<br />
Some applications might add configuration files to <code>%{_datadir}/glib-2.0/schemas/</code>. You need to not ship them in compiled form, but rather compile after installation and uninstallation. If the Makefile has no switch you need to manually remove them: <code>rm %{buildroot}%{_datadir}/glib-2.0/schemas/gschemas.compiled</code>.<br />
<br />
Put<br />
<pre><br />
%glib2_gsettings_schema_requires<br />
</pre><br />
near the <code>BuildRequires:</code> section and<br />
<br />
<pre><br />
%post<br />
%glib2_gsettings_schema_post<br />
<br />
%postun<br />
%glib2_gsettings_schema_postun<br />
</pre><br />
<br />
below <code>%install</code><br />
<br />
[[Category:Packaging]]<br />
[[Category:Packaging documentation]]<br />
<br />
[[de:openSUSE:Paketbauvereinbarungen zu RPM-Makros]]<br />
[[ru:Сборка пакетов/Соглашение по стилю RPM-пакетов/Макросы RPM]]<br />
[[zh:openSUSE:Packaging_Conventions_RPM_Macros]]</div>Kfreitaghttps://en.opensuse.org/index.php?title=Portal:Hackweek/Intro&diff=119067Portal:Hackweek/Intro2017-03-03T10:15:44Z<p>Kfreitag: </p>
<hr />
<div>One of the ways SUSE and its developers contribute to openSUSE is through Hackweek: – a week long sprint permitting developers to work on something entirely of their own design or wishes as long as it is [[Free_and_Open_Source_Software|<abbr title="Free and Open Source Software">FOSS</abbr>]]-related. Started in 2007, it has become a regular part of SUSE’s development.<br />
<br />
See the [https://hackweek.suse.com/ Hack Week site].<br />
<br />
'''Hack Week 15'''<br />
<br />
Hackweek 15 happened from February 21st to 27th, 2017. Check the [https://hackweek.suse.com/15/projects List of projects] people were working on.<br />
<br />
'''Hack Week 14'''<br />
<br />
This Hack Week kicked off at the openSUSE Conference on June 24. It run through the week June 27 - July 1, 2016. <br />
<br />
<br />
'''Hack Week 13'''<br />
<br />
Dec. 7-11, 2015: <br />
<br />
'''Hack Week 12'''<br />
<br />
April 13-17, 2015: https://news.opensuse.org/2015/04/10/next-week-is-hack-week/<br />
<br />
<br />
'''Hack Week 11'''<br />
<br />
Oct. 20-24 2014, at SUSE offices around the world, with other developers participating remotely: https://www.suse.com/company/press/2014/10/suse-to-host-hackweek-11.html<br />
<br />
<br />
'''Hack Week 10'''<br />
<br />
[[File:Hackweek10.png]]<br />
<br />
[http://hackweek.suse.com Hack Week 10] took place:<br />
<br />
* from October 7th to 11th 2013 in Nuremberg and Prague,<br />
* on October 3rd and 4th and from 7th to 9th in Provo and Taipei, and<br />
* from October 8th to 12th in Beijing<br />
<br />
'''Hack Week 9'''<br />
<br />
[[File:Hackweek9.jpg]]<br />
<br />
Hack Week 9 took place from April 8th to 12th 2013.<br />
<br />
* [http://hackweek.suse.com Official Website]<br />
* Press release by SUSE: https://www.suse.com/company/press/2013/3/suse-hack-week-nine-begins-april-eight.html<br />
* Hack Week announcement in openSUSE News: https://news.opensuse.org/2013/03/26/hackweek-9-is-coming/<br />
<br />
The Prague SUSE office held a Hack Week kickoff meeting combined with an openSUSE 12.3 Release Party on March 28th 2013, see these announcements for details:<br />
* http://michal.hrusecky.net/2013/03/opensuse-12-3-release-party-v-praze/ (in Czech)<br />
* http://michal.hrusecky.net/2013/03/plan-opensuse-12-3-release-party/ (in Czech)<br />
<br />
'''Hackweek VIII'''<br />
<br />
[[File:Logo_hackweek8_blue_white.png]]<br />
<br />
Hackweek VIII took place from July 23rd to 27th 2012.<br />
<br />
Jos Poortvliet wrote a [https://news.opensuse.org/2012/08/24/hackweek-8-at-suse/ blog post summarising the week].<br />
<br />
<br/><br />
<br />
'''Hackweek VII'''<br />
<br />
[[File:Hackweek-7-logo.png|thumb|200px|right]]<br />
<br />
Hackweek VII took place September 26th to 30th 2011. As usual, SUSE extended the invitation to openSUSE Community contributors.<br />
<br />
Unlike in the previous years, this year's motto was: "No Motto, do what you want, but do it!"<br />
<br />
[http://blip.tv/opensuse Hackweek VII on blip.tv]<br />
<br />
Like in previous years, we used [http://features.opensuse.org/hackweek openFATE] to track your ideas and coordinate with others that might want to join a project. Make sure to check out the ideas listed in the Hackweek VII product category (as well as some good ones left over from Hackweek VI).<br />
<br />
During the week, we had a good-morning-catering in all participating locations. Enjoy!<br />
<br />
Browse for [https://features.opensuse.org/query/run?search_string=&tag=&search_products%5B%5D=hackweek_6&search_products%5B%5D=hackweek_7&type=find existing hackweek projects]<br><br />
<br />
Create a [https://features.opensuse.org/feature/new?products%5b%5d=hackweek_7 new hackweek project]<br />
<br />
<br />
<br />
'''Hackweek VI'''<br />
<br />
[[File:Hackweek6Logo.png|thumb|200px|right]]<br />
<br />
Hackweek VI took place January 24.-28., 2011. As usual, Novell extended the invitation to openSUSE Community contributors. Hackweek VI featured the theme "Engineering Cloud" and allows developers to get their hands on related projects. In order to support that approach, we are providing access to a few select cloud providers and a setup where you can deploy cloud infrastructure software (e.g. Eucalyptus). Your favorite hack-project may or may not relate to that theme, it may well be experimental, as long as it is Linux- or SUSE-related.<br />
<br />
Like in previous years, we used [http://features.opensuse.org/hackweek openFATE] to track your ideas and coordinate with others that might want to join a project. Make sure to check out all ideas listed in the Hack Week VI product category.<br />
<br />
We also plan to nominate the 3 best projects that relates to the "Engineering Cloud" theme and hand out Amazon gift vouchers. For your project to be considered we ask you to:<br />
# submit your idea until Fri, Jan 21st at [http://features.opensuse.org/hackweek openFATE] (opens Jan, 13)<br />
# provide a introductory video of your project on Mo, Jan, 24th<br />
# wrap up and do a final video submission no later than Fri, Feb 4th <br />
<br />
Participating Novell locations also try to provide a "hackspace", some comfy place to meet, work together and snack.<br />
<br />
Finally, we are trying to spread the word via [http://twitter.com/#!/search?q=%23hackweek6 #hackweek6] on twitter and look forward to hear about your updates there.<br />
<br />
Following people will be at your assistance in the various locations:<br />
* Nuernberg / Prague: Holger Sickenberg<br />
* Beijing: Charles Wei<br />
* Taiwan: Joey Lee<br />
* USA: Olli Ries<br />
* India: Nirav Kumar<br />
<br />
Please check in with us for all questions related to Hack Week VI, e.g. how to get a video of you and your project done or where to submit your project to be considered for an award.<br />
<br />
For those who are busy during this week, the suggested backup slot is Hackweek VI b) February 21.-25.<br />
<br />
<br />
<br />
'''Welcome to Hackweek V (June 7.-11, 2010)'''<br />
from [http://news.opensuse.org news.opensuse.org]:<br />
<br />
Novell is once again sponsoring a Hack Week. This is an opportunity for Novell’s Open Platform Solutions developers to use their Innovation Time Off and hunker down and work on the projects that catch their fancy.<br />
<br />
Hack Week projects can be new features, new applications, or improvements to existing services and applications. Previous Hack Weeks have generated projects like Tasque, Giver, Debian package support in the openSUSE Build Service, and many others. Hack Week is also a chance for Novell employees to work with the openSUSE Community contributors if they wish on projects that help improve openSUSE.<br />
<br />
You don’t have to be a Novell employee to participate! If you’d like to hack on something cool and useful, you’re welcome to join in!<br />
<br />
We’ll be collecting ideas in [http://features.opensuse.org/hackweek openFATE] for Hack Week, so if you’d like to contribute an idea, just go to openFATE and log in with your openSUSE account. Then select “Create” and add your feature, as well as any test or use cases.<br />
<br />
If you’d like to help implement one of the ideas, check out the features that are already in openFATE for Hack Week V. Go to “Browse” and select Hack Week V as the Product, and you’ll see all of the proposed features for Hack Week.<br />
<br />
Have questions about Hack Week? Email Klaas or ask in #opensuse-project on Freenode.</div>Kfreitaghttps://en.opensuse.org/index.php?title=Archive:OpenSUSE:Connect&diff=71248Archive:OpenSUSE:Connect2015-06-16T07:46:21Z<p>Kfreitag: Minor updates to adopt to current state.</p>
<hr />
<div>{{Connect navbar}}<br />
<br />
__NOTOC__{{Info|[http://connect.opensuse.org Connect] is the framework we are currently testing to manage users and group memberships in the openSUSE project}}<br />
<br />
== About ==<br />
<br />
* is based on Elgg (an open source social networking platform - http://elgg.org/)<br />
* replaces the former users.opensuse.org <br />
* adds a social aspect to the project infrastructure (users, groups, events, etc.)<br />
* used to handle memberships and elections<br />
<br />
== How to ... ==<br />
* [[openSUSE:Connect installation|Install Connect on your development machine]]<br />
* [[openSUSE:Connect API|Using Connect REST API]]<br />
* [http://docs.elgg.org/wiki/Plugin_development Create plugins]<br />
* [http://docs.elgg.org/wiki/Views Work with Views]<br />
* [http://docs.elgg.org/wiki/Views/Creating_a_new_site_theme Create new theme]<br />
* [http://docs.elgg.org/wiki/Tutorials/HelloWorld Create widget]<br />
<br />
== Features ==<br />
<br />
Elgg already provides a large subset of features we want, some of them provided by [http://community.elgg.org/pg/plugins/all/ plugins/mods] from a very large repository.<br />
<br />
We need to make sure that the following is available and working in Connect:<br />
*Login: <br />
** Other possible Login methods (would need to bind to an opensuse account after first login):<br />
** OAuth support ([http://community.elgg.org/pg/plugins/jricher/read/385119/oauth OAuth] mod)<br />
** OpenID support ([http://community.elgg.org/pg/plugins/kevin/read/433999/openid-client OpenID] mod)<br />
** LDAP support ([http://community.elgg.org/pg/plugins/bruno/read/384363/ldap-authentication-plugin LDAP] mod)<br />
* global and group events (maybe [http://community.elgg.org/pg/plugins/kevin/read/384926/event-calendar Event calendar] mod)<br />
* CalDAV support for above (TBD)<br />
* geotagging ([http://community.elgg.org/pg/plugins/vazco/read/384618/geotagging-and-geolocation-maps-for-elgg-vazco-gmap vazco_gmap] mod or [http://community.elgg.org/pg/plugins/pedroprez/read/399848/geolocation geolocation] mod)<br />
* user awards/recognition (TBD, maybe [http://community.elgg.org/pg/plugins/vazco/read/384905/vazco_karma vazco_karma] mod, maybe something else, see bellow)<br />
* ribbons/banners/wordpress plugin/facebook plugin - showing username, contributions, etc., linking to the profile on connect (TBD)<br />
<br />
=== Already done ===<br />
<br />
* Bento theme (our theme_bento mod)<br />
* user profile (internal profile mod)<br />
* groups (internal groups mod)<br />
* friends (internal friends mod)<br />
* search (internal search mod)<br />
* custom fields to profile and groups (our connect_fields mod)<br />
* gravatar ([http://community.elgg.org/pg/plugins/marcus/read/384308/simple-gravatar-plugin gravatar] mod)<br />
* generate business cards and vcards from profile (our profile_cards mod)<br />
* voting/polls ([http://community.elgg.org/pg/plugins/kevin/read/515853/polls polls] mod + our modifications)<br />
* group moderators ([http://community.elgg.org/pg/plugins/caedes/read/493281/group-operators group operators] mod)<br />
* bugzilla widget (our mod)<br />
* openfate widget (our mod)<br />
* rss integration (maybe [http://community.elgg.org/pg/plugins/costelloc/read/384545/simplepie-rss-feed-integrator rss plugin])<br />
** iChain Plugin (our mod)<br />
<br />
== User ==<br />
<br />
attributes:<br />
<br />
* Current country, Timezone, Website, Blog, XMPP Contact, Freenode IRC nickname, Freenode IRC cloak<br />
* Telephone, Skype, GPG key, SSH key, Twitter, Identi.ca, Facebook, Linkedin, Xing, ohloh, Gitorious, Github<br />
* openid login, spoken languages, computer languages, opensuse.org email alias, description<br />
* RSS feed for aggregated API calls<br />
* mailing lists subscriptions, company blog URL<br />
* some attributes should be changed to lists (irc, openid, ssh-key, gpg-key, ...)<br />
<br />
== Groups ==<br />
<br />
* there are two types of groups:<br />
** roles - group membership means that user has this role (eg. board, member, security team)<br />
** projects - group membership that user is somehow participating in this (upstream) project <br />
<br />
* groups can be moderated (join requests have to be approved by group moderator)<br />
* user can gain experience in certain groups (XP points, levels, ____ hero of the week/month)<br />
<br />
<br />
Missing group attributes:<br />
* website/blog, IRC channel/network, identi.ca/twitter/facebook, ohloh, OBS project, upstream bugtracker<br />
<br />
== Related features ==<br />
<br />
* https://features.opensuse.org/306343 (pkgstars)<br />
* https://features.opensuse.org/306625 (cloaks)<br />
* https://features.opensuse.org/307498 (improve+integrate)<br />
* [https://features.opensuse.org/312001 312001: Add email related functionality]<br />
* [https://features.opensuse.org/312079 312079: page that shows all group members]<br />
* [https://features.opensuse.org/312080 312080: add a 'connect' group]<br />
<br />
== Very far future / ideas ==<br />
<br />
* store user data files on the server<br />
* teamgeist (shared zeitgeist) integration<br />
<br />
== Concepts ==<br />
<br />
=== Karma ===<br />
<br />
* we probably want to write our own karma plugin<br />
** we need integration with bugzilla<br />
** we need integration with wiki<br />
** we need integration with buildservice<br />
** ...<br />
* people will recieve points and badges/awards in particular arrea<br />
* leader of the area of the interest can add extra points to the people for hard tasks and remove few points in case of cheating<br />
* people will have widget on their dashboard with their awards/badges<br />
** this will include things like '5 x KDE hero of the week, 3 x Gnome hero of the month, ...'<br />
* people will get image on openSUSE website stating their awards so they can link against it on other pages (their blog, forum signature, etc)<br />
* each area of interest will have widget with:<br />
** top ten contributors of all times<br />
** hero of the week<br />
** hero of the month<br />
<br />
Other crazy ideas about openSUSE Connect Karma can be found on [http://michal.hrusecky.net/2010/08/ideas-about-karma-in-opensuse-connect/ Miska's blog]</div>Kfreitaghttps://en.opensuse.org/index.php?title=openSUSE:Membership_officials&diff=70867openSUSE:Membership officials2015-06-03T15:37:00Z<p>Kfreitag: Removed myself from the list of officials - have never been active on it.</p>
<hr />
<div>__NOTOC__<br />
<br />
<center>[[Image:Membership-officials.png]]</center><br />
<div style="background-color:#E5E5E6;text-align:center;color:#000000"><br />
=== Introduction ===<br />
</div><br />
<br />
This team processes the [[openSUSE:Members|openSUSE membership]] requests and accepts or rejects them after review. Membership officials are appointed by the [[openSUSE:Board|openSUSE Board]].<br />
<br />
<div style="background-color:#E5E5E6;text-align:center;color:#000000"><br />
<br />
=== Communicate ===<br />
</div><br />
<br />
* '''membership-officials@opensuse.org''' - This is a closed mailing list so the team can discuss privately applications that might require a debate (unclear contributions, for example).<br />
<br />
{{Warning|'''Please DO NOT contact the membership team about individual candidates!'''}}<br />
<br />
<div style="background-color:#E5E5E6;text-align:center;color:#0b5147"><br />
<br />
=== Members ===<br />
</div><br />
<br />
Currently the team consists of the following members (usernames in brackets):<br />
<br />
* Andrew Wafaa (awafaa)<br />
* Chuck Payne (terrorpup)<br />
* Wolfgang Rosenauer (wolfir)<br />
* Dominique Leuenberger (dimstar)<br />
* Peter Nixon (nix)<br />
* Thomas Schmidt (digitaltomm)<br />
* Raymond Wooninck (tittiatcoke)<br />
* Jean-Daniel Dodin (jdd)<br />
* Sascha Manns (saigkill)<br />
* Jaromir Cervenka (cervajz)<br />
* Michal Hrusecky (miska)<br />
* Jan Weber (TheCode)<br />
* Andrea Florio (anubisg1)<br />
* Richard Brown (Ilmehtar)<br />
* Athanasios-Ilias Rousinopoulos (zoumpis)<br />
<br />
Previous members of the team include:<br />
<br />
* Vincent Untz (vuntz)<br />
<br />
<div style="background-color:#E5E5E6;text-align:center;color:#0b5147"><br />
<br />
=== Process ===<br />
</div><br />
<br />
==== Vote membership requests ====<br />
# login to connect.o.o<br />
# go to the [https://connect.opensuse.org/mod/groups/membershipreq.php?group_guid=111 following link] (Manage join requests for Members group) - also shortened as [http://is.gd/newmembers http://is.gd/newmembers]<br />
# clicking on the +/- numbers shows a popup with the comments, clicking on 'validation links' shows a popup with helpful links for evaluation<br />
# to vote for applications, provide your reasons in the text field and give a +1 or -1 votes<br />
#to remove your vote click on [x] next to your comment in the popup<br />
# if applications gets 4x +1 or 4x -1 then you can hit Accept or Reject button. <br/>After deciding whether to accept or to reject the application, you can modify the notification message the user will receive, and set his email alias on acceptance.<br />
<br />
==== Administrate @opensuse.org email aliases ====<br />
<br />
To change the email alias or target of a user, set the corresponding field(alias, target) in <br />
his profile. This can only be done by connect admins, please send requests to admin@opensuse.org .<br />
<br />
==== Administrate irc cloaks ====<br />
<br />
When requesting membership, the users should add their desired freenode cloak and irc username in the contributions field. Upon accepting the user as member, the membership admins will set these values in the users profile. <br />
<br />
To get the cloak active on freenode, our irc admins download the [https://connect.opensuse.org/pg/membersadmin/txt/ cloak export] from the connect admin page, do a diff <br />
with the existing cloaks on freenode, and request the new ones. <br />
(TODO: Add reference to the script doing this)<br />
<br />
After the new cloaks are registered with freenode, the irc admins paste the list of nicknames to the [https://connect.opensuse.org/pg/membersadmin/ membership admin page], which triggers a notification mail to the new members, and sets their cloak state to done. <br />
<br />
Please send requests regarding your cloak to admin@opensuse.org.<br />
<br />
[[Category:Team pages|{{PAGENAME}}]]</div>Kfreitaghttps://en.opensuse.org/index.php?title=User:Kfreitag&diff=55411User:Kfreitag2012-10-18T19:41:08Z<p>Kfreitag: </p>
<hr />
<div><div style="width:70%; float:left"><br />
{{Box-header|About Klaas Freitag|{{FULLPAGENAME}}|}}<br />
While I did some packaging in the beginning of my time at SUSE I switched to work on internal infrastructure pretty soon. For example, the SUSE Bugzilla was done by me, later by my colleague [[User:cwh|Christopher]] and me, and finally by the '''Inttools Team''' which was part of SUSE R&D.<br />
<br />
Well, bugzilla.suse.de has vanished from us and went to the Novell servers. All Novell bugtracking is now done with [http://www.bugzilla.org Bugzilla] so the [http://bugzilla.novell.com Novell Bugzilla] needs a very much bigger mind than the SUSE Bugzilla ever had... And a bigger team for maintenance and development...<br />
<br />
The SUSE Inttools Team have found interesting things to move forward: For example [http://swamp.sourceforge.net SWAMP], our workflow management and administration tool which is in production to manage all the maintenance update s for SLE and openSUSE. Another topic for the tools team was feature tracking for the SUSE products with our tool [[openSUSE:openFate|Fate]]. <br />
<br />
I am one of the fathers of the open(SUSE) [[openSUSE:Build_Service|Buildservice]] and maintain [[openSUSE:Hermes|Hermes]], the Open Buildservice notification system.<br />
<br />
In summer 2007 I changed my role and became the architect of the SUSE department RD OPS/IPD. In that role I worked on a higher level on infrastructure such as the internal and external Buildservice, our tools and more.<br />
<br />
Later on in summer of 2009 I became the teamlead of the [[openSUSE:Boosters|openSUSE Boosters Team]] - something I was very happy about. We were working to make openSUSE more attractive for contributors.<br />
<br />
In early 2012 I left SUSE as a company and joined the starup [http://www.owncloud.com ownCloud Inc.] where I work as a developer on the [http://owncloud.org/sync-clients ownCloud Desktop Client] and enjoy the fun and excitement with a small and agile company.<br />
<br />
In the spare time I am contributing to [http://www.kde.org KDE] and I am <br />
active member of the KDE e.V. In july 2007 I was elected to the board of the [http://ev.kde.org KDE e.V] in which I served until summer 2009.<br />
<br />
My current spare time project is a tool called [http://volle-kraft-voraus.de/pmwiki.php/Main/Kraft Kraft] which helps people to create documents like invoices for their little business.<br />
<br />
{{Box-footer|}}<br />
</div><br />
<div style="width:30%; float:right"><br />
{{Box-header|Imagination|{{FULLPAGENAME}}|}}<br />
[[Image:Klaas_freitag.jpg|140px|center|Klaas Freitag]]<br />
{{Box-footer|}}<br />
</div><br />
<br />
<div style="width:30%; float:right"><br />
{{Box-header|Contact|{{FULLPAGENAME}}|}}<br />
Blog: [http://dragotin.wordpress.com Free Software]<br/><br />
Email: [mailto:freitag@opensuse.org freitag@opensuse.org]<br/><br />
[irc://irc.freenode.net/opensuse-project irc]: dragotin<br/><br />
{{Box-footer|}}<br />
</div></div>Kfreitaghttps://en.opensuse.org/index.php?title=User:Kfreitag&diff=55410User:Kfreitag2012-10-18T19:40:12Z<p>Kfreitag: </p>
<hr />
<div><div style="width:70%; float:left"><br />
{{Box-header|About Klaas Freitag|{{FULLPAGENAME}}|}}<br />
While I did some packaging in the beginning of my time at SUSE I switched to work on internal infrastructure pretty soon. For example, the SUSE Bugzilla was done by me, later by my colleague [[User:cwh|Christopher]] and me, and finally by the '''Inttools Team''' which was part of SUSE R&D.<br />
<br />
Well, bugzilla.suse.de has vanished from us and went to the Novell servers. All Novell bugtracking is now done with [http://www.bugzilla.org Bugzilla] so the [http://bugzilla.novell.com Novell Bugzilla] needs a very much bigger mind than the SUSE Bugzilla ever had... And a bigger team for maintenance and development...<br />
<br />
The SUSE Inttools Team have found interesting things to move forward: For example [http://swamp.sourceforge.net SWAMP], our workflow management and administration tool which is in production to manage all the maintenance update s for SLE and openSUSE. Another topic for the tools team was feature tracking for the SUSE products with our tool [[openSUSE:openFate|Fate]]. <br />
<br />
I am one of the fathers of the open(SUSE) [[openSUSE:Build_Service|Buildservice]] and maintain [[openSUSE:Hermes|Hermes]], the Open Buildservice notification system.<br />
<br />
In summer 2007 I changed my role and became the architect of the SUSE department RD OPS/IPD. In that role I worked on a higher level on infrastructure such as the internal and external Buildservice, our tools and more.<br />
<br />
Later on in summer of 2009 I became the teamlead of the [[openSUSE:Boosters|openSUSE Boosters Team]] - something I was very happy about. We were working to make openSUSE more attractive for contributors.<br />
<br />
In early 2012 I left SUSE as a company and joined the starup [http://www.owncloud.com ownCloud Inc.] where I work as a developer on the [http://owncloud.org/sync-clients ownCloud Desktop Client] and enjoy the fun and excitement with a small and agile company.<br />
<br />
In the spare time I am contributing to [http://www.kde.org KDE] and I am <br />
active member of the KDE e.V. In july 2007 I was elected to the board of the [http://ev.kde.org KDE e.V] in which I served until summer 2009.<br />
<br />
My current project in KDE is a project called [http://volle-kraft-voraus.de/pmwiki.php/Main/Kraft Kraft] which helps people to create documents like invoices for their little business.<br />
<br />
{{Box-footer|}}<br />
</div><br />
<div style="width:30%; float:right"><br />
{{Box-header|Imagination|{{FULLPAGENAME}}|}}<br />
[[Image:Klaas_freitag.jpg|140px|center|Klaas Freitag]]<br />
{{Box-footer|}}<br />
</div><br />
<br />
<div style="width:30%; float:right"><br />
{{Box-header|Contact|{{FULLPAGENAME}}|}}<br />
Blog: [http://dragotin.wordpress.com Free Software]<br/><br />
Email: [mailto:freitag@opensuse.org freitag@opensuse.org]<br/><br />
[irc://irc.freenode.net/opensuse-project irc]: dragotin<br/><br />
{{Box-footer|}}<br />
</div></div>Kfreitaghttps://en.opensuse.org/index.php?title=Archive:GSOC_ideas_2014&diff=50671Archive:GSOC ideas 20142012-04-03T14:57:56Z<p>Kfreitag: /* ownCloud Related Ideas */</p>
<hr />
<div>{{Template:GSOC_navbar}}<br />
<br />
==GSOC 2012 Idea list==<br />
<br />
This is a list of ideas for projects which could be done for openSUSE as part of the Google Summer of Code program. If you have an idea and want to mentor it, please add it it to the list. You might also find inspiration on the [[Archive:GSOC_ideas_2011|GSoC 2011 Ideas]] page. The openSUSE GSOC 2012 page is [[openSUSE:GSOC|here]]<br />
<br />
If you are a student and want to work on an idea, please submit a proposal. You are not limited to the ideas listed here. If you have an own idea or want to approach an idea in a completely different way, feel free to submit this as proposal as well. Sometimes these are the best projects. Creativity and initiative are highly appreciated.<br />
<br />
A great source for openSUSE related ideas is [https://features.opensuse.org/ openFATE].<br />
<br />
There have been a [[openSUSE:Derivate_Ideas|couple of ideas]] about more [[Derivates|openSUSE derivates]] but it was decided that they are not good GSOC ideas as the coding part is not primal.<br />
<br />
{{GSOC new task|pagename=openSUSE:GSOC_2012_Ideas}}<br />
<br />
----<br />
<br />
== General ideas==<br />
* Limited GUI support in text mode for multimedia & browsers.<br />
* develop a way for GTK apps to use a KDE file dialog in a Plasma Desktop<br />
* develop a way for KDE apps to use a GTK filedialog in a GTK desktop (GNOME, XFCE, LXDE)<br />
* Zypper to be able to talk to the 'osc' world so we can do zypper se on osc packages and trivially add repos, and install packages.<br />
* [http://en.opensuse.org/openSUSE:Easy-LTSP_GSoC_ideas LTSP-GSOC Ideas]<br />
* GRUB2 yast module<br />
* Remastersys or mylivecd for openSUSE<br />
* WebPin<br />
* owncloud<br />
** Integration in GNOME Online Acconts with automatic configuration of Evolution and Nautilus to use ownCloud<br />
** Integration in Dolphin to access sharing and version of files from within the context menu.<br />
** Integration of ownCloud Gallery with Digikam<br />
** Integration of ownCloud Apps into GNOME as GNOME Web Apps<br />
* Integrate Ksplice for reboot less kernel upgrades<br />
* FATE: Work on the KDE 4 client<br />
FATE is the feature tracking framework of Novell/openSUSE. The user visible part of this is [http://features.opensuse.org openFATE], the place where different projects of openSUSE track their feature requests. There also exists a KDE3 client, which should get ported to QT4.<br />
<br />
----<br />
<br />
===Ideas coming from openFATE===<br />
<br />
Overview: [https://features.opensuse.org/query/tag?tag=gsoc_2011 Features on openFATE tagged with 'gsoc_2011']<br />
<br />
* [https://features.opensuse.org/308314 better wine integration]<br />
* [https://features.opensuse.org/310232 kde addressbook integration in openoffice/libreoffice via akonadi connector]<br />
* [https://features.opensuse.org/310913 Add YAST module to set up multiseat installations]<br />
* [https://features.opensuse.org/307254 Use POSIX capabilities instead of suid]<br />
* [https://features.opensuse.org/310516 YaST2 DNSSEC]<br />
<br />
----<br />
<br />
== [[openSUSE:Connect|openSUSE Connect]] ==<br />
<br />
=== openSUSE Karma plugin for openSUSE Connect ===<br />
<br />
Implement Karma concept in openSUSE Connect that will collect points from wiki edits, bugzilla entries, planet.opensuse.org posts, distribution changelogs and possibly other sources and store them in the Connect. Also implement some UI to make it possible to send points. Create per group badget that will grow according of the number of skilled members automatically. Karma points should have some categorie - developer karma/marketing karma/... And it it would be also great to make it accessible though connect API (to trustworthy external applications (log transactions so in case of security breach it can be reverted)).<br />
<br />
'''Required knowledge:''' PHP basics<br />
<br />
'''Skill level:''' Basic<br />
<br />
'''Mentor:''' [[User:-miska-|Michal Hrušecký]]<br />
<br />
'''Student:''' 2 candidates available<br />
<br />
[http://michal.hrusecky.net/2010/08/ideas-about-karma-in-opensuse-connect/ Blog post about karma idea]<br />
<br />
[http://michal.hrusecky.net/2011/03/gsoc-2011-ideas-karma-plugin-for-opensuse-connect/ GSoC blog post about karma idea]<br />
<br />
----<br />
<br />
=== Ambassador/Event plugin for openSUSE Connect ===<br />
openSUSE Connect is the social network of the project. It is based on [http://elgg.org Elgg], a social networking platform based on php/sql. Elgg has an event calender plugin that is used by various groups to organize meetings. The ambassadors use this too, but for their planing of events they attend they have to use the wiki which is too much for many of them. In this project you either adapt the event plugin of Elgg or create a new one that allows planing of events in connect.<br />
<br />
<br />
'''Required knowledge:''' PHP, HTML, CSS<br />
<br />
'''Skill level:''' Medium<br />
<br />
'''Mentor:''' [[User:hennevogel|Henne Vogelsang]]<br />
<br />
'''Student:''' <br />
<br />
[https://features.opensuse.org/312178 Related Features in openFATE]<br />
<br />
----<br />
=== Make openSUSE Connect more engaging ===<br />
openSUSE Connect is the social network of the project. It is based on [http://elgg.org Elgg], a social networking platform based on php/sql. There are various features people miss about the network to have it more engaging. In this project you will work on connect to implement these missing features.<br />
<br />
* [https://features.opensuse.org/312001 Email notifications for more actions]<br />
* [https://features.opensuse.org/312931 RSS feed permissions]<br />
* [https://features.opensuse.org/312158 Comments on user pages]<br />
* [https://features.opensuse.org/312180 Add emoticons/paste plugins]<br />
* [https://features.opensuse.org/312328 Activity stream from openfate]<br />
* [https://features.opensuse.org/312757 Add some language packs]<br />
* [https://features.opensuse.org/312833 Add an image sharing plugin]<br />
<br />
<br />
'''Required knowledge:''' PHP, HTML, CSS<br />
<br />
'''Skill level:''' Medium<br />
<br />
'''Mentor:''' [[User:hennevogel|Henne Vogelsang]]<br />
<br />
'''Student:''' <br />
<br />
----<br />
<br />
== [[Portal:Build_Service|openSUSE Build Service ]] ==<br />
<br />
=== Support for [http://bitbake.berlios.de/manual/ Bitbake] in OBS ===<br />
[http://bitbake.berlios.de/manual/ Bitbake] is class based build system. It uses <tt>.bb</tt> recipes and it is able to create rpm, deb and other formats. All from one recipe. openSUSE Build Service supports building packages on variety of distributions. Support for Bitbake would make it easier to package software and hopefully later to make it possible to build it for all distributions from one recipe. Among other tasks student would need to add support for <tt>.bb</tt> in obs, get list of dependencies from Bitbake to provide it to Build Service and create staging tree using binary packages provided by obs.<br />
<br />
'''Required knowledge:'''<br />
* Python (Bitbake is written in it)<br />
* Shell, Perl (obs use these)<br />
* Basic packaging knowledge<br />
* Good orientation in ugly code<br />
* Ability to create creative hacks<br />
<br />
'''Skill level:''' Advanced<br />
<br />
'''Mentor:''' [[User:-miska-|Michal Hrušecký]] (feel free to replace me)<br />
<br />
'''Student:''' 2 candidates available<br />
<br />
[https://michal.hrusecky.net/2011/03/gsoc-2011-ideas-support-for-bitbake-in-obs/ Blog post about this idea]<br />
<br />
=== End user oriented obs web interface ===<br />
<br />
The web interface of the Build Service is currently focused on developers. End users could benefit from exposing the work of individuals more. Displaying recent changes, a global history, activity and rating overview. Also a new user home page (similar to what Facebook or GitHub has) are ideas worth thinking about. Currently the ability to visually inspect the work of others is limited (mostly) to user's membership in projects/groups, their recent requests and what info they provide about themselves. The user's home page could be expanded by interests, external URL links (to an ohloh.net profile or blog). <br />
<br />
<!-- <br />
Mentor name and/or link with contact information <br />
--><br />
*'''Mentor:''' [[User:saschpe|Sascha Peilicke]], Adrian Schröter, Markus Rückert, [[User:digitaltomm|Thomas Schmidt]]<br />
<br />
* '''Required skills:''' Ruby and Ruby on Rails, to integrate the new features into the web user interface<br />
<br />
* '''Student:''' one candidate available <br />
<br />
=== Capability-based build scheduling ===<br />
<br />
In particular ARM devices often have limited RAM whereas some packages fail to build without adequate memory. So far we have refrained from adding low-end boards to the build farm. It would be nice to add more build nodes to the farm by being able to manage scheduling more fine-grained on criteria such as RAM size, storage size, CPU features, network access, virtualization capabilities. With regards to ARM it might be an option to build certain packages under QEMU system emulation on x86/ppc rather than QEMU linux-user emulation or native. Individual packages would need to be able to specify required build node capabilities, and these would need to be evaluated and matched to available nodes by the build scheduler.<br />
<br />
<!-- <br />
Mentor name and/or link with contact information <br />
--><br />
*'''Mentor:''' Adrian Schröter<br />
<br />
----<br />
<br />
== [[Portal:SUSE_Studio|Appliances/SUSE Studio]] ==<br />
<br />
=== SUSE Studio Command Line Client (ssc) ===<br />
<br />
With [http://www.susestudio.com SUSE Studio] users can easily create openSUSE based systems in their web browser. But when running such a system, there is still missing a convenient way how to feed back changes in the system to Studio, so that with the next build on the Studio web site these changes are incorporated.<br />
<br />
The idea of this project is to extend the Studio command line client [http://github.com/susestudio/ssc ssc] by this functionality. This could be modeled similar to how the openSUSE Build Service command line client osc works, with commands to list packages, and overlay files, to show diffs, and to commit changes back to Studio. Think git for [http://www.susestudio.com SUSE Studio]. You checkout an appliance, make some changes for it (locally) and once you are happy with the appliance you commit the changes to [http://www.susestudio.com SUSE Studio].<br />
<br />
Example use case<br />
<source lang="bash" style="overflow:auto"><br />
$ ssc appliance create web_server --source-id=SOURCE_APPLIANCE_ID --username=USERNAME --password=PASSWORD<br />
$ cd web_server<br />
$ ssc package list<br />
$ ssc package add apache<br />
$ ssc file add /etc/apache2/apache2.conf<br />
$ ssc commit<br />
</source><br />
<br />
<br />
Goal: get some workflow going, which can be used to track changes within an appliance and selectively apply them back to Studio.<br />
<br />
Essential: Community involvement, introduce yourself on the opensuse-project mailing list. (this probably applies to all other projects as well)<br />
<br />
Find more details on the [[openSUSE:SUSE Studio command line client|SUSE Studio command line client]] page.<br />
<br />
'''Required knowledge:''' Ruby<br />
<br />
'''Skill level:''' intermediate<br />
<br />
'''Mentor:''' [[User:mess110|Cristian Mircea Messel]]<br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
=== SUSE Studio Java Client SDK ===<br />
<br />
[https://github.com/susestudio/susestudio-lib-java SUSE Studio Java Client] is a Java based library to interact with the [http://susestudio.com SUSE Studio] image store and appliances toolkit. The library is supposed to enable developers to easily implement SUSE Studio client applications in Java, even for mobile platforms like Android. The implementation however is at the moment still a work in progress and only very basic parts of the [http://susestudio.com/help/api/v2 REST API] are currently covered.<br />
<br />
The project goal is therefore to bring on the development of this library as much as possible, while ideally the whole API functionality should be covered by the implementation. The interface should be designed in a way so that developers will be able to write beautiful code using this library. Further it would be nice to have a suite of unit tests, so we can automatically ensure the overall functionality of the code and data model at any time using continuous integration tools like Jenkins.<br />
<br />
It would be a big plus for your application, if you propose to implement new software based on this SDK instead of just working on the library itself. This might be a mobile app for Android, a new web application or anything else, as far as it makes sense. Feel free to come up with your own ideas!<br />
<br />
Please find the existing code and documentation [https://github.com/susestudio/susestudio-lib-java here] and the SUSE Studio API documentation [http://susestudio.com/help/api/v2 here].<br />
<br />
'''Required knowledge:''' Java, HTTP and REST, unit testing and continuous integration<br />
<br />
'''Skill level:''' beginner - intermediate<br />
<br />
'''Mentor:''' [[User:J_renner|Johannes Renner]]<br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
=== SUSE Studio Amazon EC2 scripts ===<br />
<br />
SUSE Studio allows you to easily build customized Amazon EC2 AMIs (Amazon Machine Images). While you can directly push and launch them from Studio to Amazon EC2, it is sometimes preferred to download the raw images and do this yourself. For example, you can automate a deployment workflow with Studio's WebHook API to download a new AMI when it is available, and then automatically push it to all EC2 regions, launch, test and swap them out for production use.<br />
<br />
The project at https://github.com/susestudio/susestudio-ec2 allows one to easily upload and create these AMIs from the downloaded Studio images. This project is to extend the existing code.<br />
<br />
'''Required knowledge:''' Bash/Shell scripting, Amazon EC2 knowledge preferred.<br />
<br />
'''Skill level:''' beginner - intermediate<br />
<br />
'''Mentor:''' [[User:jatan11|James Tan]]<br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
=== SUSE StudioCheck ===<br />
<br />
[[http://en.opensuse.org/openSUSE:GSOC_ideas#SUSE_Studio:_StudioCheck_automated_test_framework | See entry in section QA]]<br />
----<br />
<br />
==Cross-distribution topics==<br />
The openSUSE project is proudly pushing cross-distribution collaboration.<br />
<br />
===AppStream: Reviews in software center===<br />
[http://distributions.freedesktop.org/wiki/AppStream AppStream] aims to solve the topic of how to deal with installing applications in a cross-distribution way.<br />
<br />
A core part of the Software Center story we want to build in AppStream is the social features: ratings, comments, etc. Ubuntu is using the https://reviews.ubuntu.com/reviews/ server (investigation needed: is the code for this free? If yes, this project is already fixed). We need a similar server that each distribution can install and, if possible, that could talk to other instances to use the data from other distributions.<br />
<br />
'''Required knowledge:''' web services, python<br />
<br />
'''Skill level:''' intermediate<br />
<br />
'''Mentor:''' [[User:vuntz|Vincent Untz]]<br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
===Upstream/downstream tracker===<br />
Many distributions have some custom tools to track upstream, and to help determine, for example, what is the latest version of an application. However, all those tools have some limitations and none is available as a service that everybody could use.<br />
<br />
The goal of this project is to bootstrap a common tracker that could be then used to know the status of a module upstream, but also in various distributions. Information about the versions, but also what patches distro use and opened bugs are the first metadata we'd want to cover.<br />
<br />
Examples:<br />
* Debian: http://dehs.alioth.debian.org/<br />
* openSUSE: http://tmp.vuntz.net/opensuse-packages/obs<br />
<br />
'''Required knowledge:''' preferably python<br />
<br />
'''Skill level:''' advanced<br />
<br />
'''Mentor:''' [[User:vuntz|Vincent Untz]]<br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
===Popularity contest for RPM (popcorn)===<br />
[https://build.opensuse.org/ OBS] has a lot of repositories and a lot of packages. People continually contribute new packages and maintain them for the greater good. But who uses these packages?<br />
<br />
It would be great to have a way for people to tell us (voluntarily) what packages/repos they use. This way we could have a way of knowing what to concentrate on and what's not needed.<br />
<br />
Popcorn aims to track the collection of packages and repositories that users have installed on their systems in a central place. The aim of the project is to be distribution neutral, but we will start with RPM (and openSUSE) first.<br />
<br />
You can learn: python, [http://flask.pocoo.org/ Flask], [http://sqlalchemy.org SQLAlchemy], [http://postgresql.org PostgreSQL], [http://rpm.org/ rpm], [http://en.opensuse.org/Portal:YaST YaST] ([http://doc.opensuse.org/projects/YaST/SLES10/tdg/Book-YCPLanguage.html YCP]) and others.<br />
<br />
You can see the WIP popcorn sources at [https://github.com/mapleoin/popcorn github]. Check out the [https://github.com/mapleoin/popcorn/wiki/TODO TODO] and don't hesitate to come up with your own ideas!<br />
<br />
'''Required knowledge:''' python, beautiful code<br />
<br />
'''Skill level:''' intermediate<br />
<br />
'''Mentor:''' [[User:mapleoin|Ionuț Arțăriși]]<br />
<br />
'''Potential students:''' Akshit Khurana, Gaurav Sood.<br />
<br />
=== Compositor Colour Management ===<br />
Colour Management has to be easy for casual developers and automatic for users. To get there it is an good idea to have all applications colour corrected inside the window manager. On the other side graphics applications, want to do own colour management and should be able to say a window shall not be colour managed. To do so easily exists the [http://www.freedesktop.org/wiki/OpenIcc#X_Color_Management_spec X Color Management] spec and the implementation of this protocol in libXcm.<br />
<br />
The ICC based colour correction is easy for compositing window managers, as they support mostly shaders. Shaders run on the GPU and allow for a very fast and efficient colour correction.<br />
<br />
The project targets at providing colour management inside a compositing window manager of your choice. The protocol part to be implemented is the Baseline spec with _ICC_COLOR_OUTPUTS and additional the _ICC_COLOR_PROFILES atom.<br />
<br />
This implementation prepared a easy transition into Wayland compositor colour management, which will as well be window based.<br />
<br />
A good and very fast start is the update the [http://compicc.sf.net CompICC] plug for Compiz-0.8, to use the _ICC_COLOR_OUTPUTS atom.<br />
<br />
'''Required knowledge:''' OpenGL, GPU shaders, Oyranos, C<br />
<br />
'''Skill level:''' intermediate<br />
<br />
'''Mentor:''' [[User:bekun|Kai-Uwe Behrmann]]<br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
=== Gtk Front End to Oyranos ===<br />
The [http://www.oyranos.org Oyranos project] is a cross desktop and cross OS colour management system (CMS) to provide easy to use and while robust colour management services to applications. The main goal of Oyranos is to provide colour management without user interaction. But in some situations and especially experts might want to configure and tweak the various settings manually.<br />
<br />
Front ends exist in Qt and for KDE. For Gtk based Desktop Environments it is currently only possible to use the Qt front end. For a better appearance and integration it makes sense to provide a native Gtk GUI for settings and configuration.<br />
<br />
'''Required knowledge:''' Gtk, Oyranos, C, good communication<br />
<br />
'''Skill level:''' intermediate<br />
<br />
'''Mentor:''' [[User:bekun|Kai-Uwe Behrmann]]<br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
=== OpenICC Colour Configuration Data Base ===<br />
Users, who configure their colour management system (CMS) behaviour and devices, want to share these settings on one host without any intervention among installed CMSes. The project will introduce the OpenICC data base into CMSes like ArgyllCMS, Oyranos and colord and replaces existing own DB access code.<br />
<br />
device DB example: http://www.freedesktop.org/wiki/Specifications/icc_meta_tag_for_monitor_profiles<br />
<br />
existing code: http://openicc.git.sourceforge.net/git/gitweb.cgi?p=openicc/openicc;a=tree<br />
<br />
'''Required knowledge:''' C, good communication<br />
<br />
'''Skill level:''' intermediate<br />
<br />
'''Mentor:''' [[User:bekun|Kai-Uwe Behrmann]]<br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
'''Links:'''<br />
<br />
=== Redesign fdisk to be more extensible and implement GPT support ===<br />
<br />
The fdisk (and family) partitioning utility is a popular and widely used tool<br />
in Linux, among other operating systems. The current code, dating from 20<br />
years ago - since 1992, is messy, without standards, and a result of years of<br />
hacky patching. The util-linux project has been developing traditional Linux<br />
tools and updating them for the 21st century, in an organized and unified<br />
way.<br />
<br />
Cleaning up the fdisk-family tools will allow refactoring, unification, clarity<br />
and abstraction across all fdisk-like programs (fdisk, sfdisk and cfdisk). This<br />
makes bug fixing and future contributions easier, with clearer, better<br />
organized code. A longer time goal, which comes naturally afterwards is to<br />
implement a libfdisk library - something like what libmount is to mount/umount.<br />
<br />
This work should include, at least:<br />
* move all label-specific code to separate files<br />
* add GPT (GUID Partition Table) support<br />
* remove obsolete code - for example, around CHS addressing<br />
* use libblkid for partition tables parsing<br />
* create any interface for dialogs (fdisk is about dialogs)<br />
* write regression tests<br />
* data type standardization (ie: off_t instead of long long)<br />
* documentation<br />
<br />
<br />
'''Required knowledge:''' C, partitioning, writing clean code, autotools, git<br />
<br />
'''Skill level:''' intermediate<br />
<br />
'''Mentor:''' [[User:Puzel|Petr Uzel]]<br />
<br />
'''Student:''' Davidlohr Bueso<br />
<br />
=== On-demand Symbolic Memory ===<br />
<br />
There are free symbolic execution tools like klee which perform symbolic execution on a code to find bugs. The problem is that often the input to a program (or its part) is unknown in advance. So checkers use a hack that they pass large symbolic buffer as input and hope that it is large enough.<br />
<br />
This is slow, inconvenient and does not help in cases where the buffer is a structure or an array of them. The members of the structure, especially pointers, are uninitialized and point to NULL.<br />
<br />
Instead, an on-demand symbolic buffer should be created. That ensures that NULL members are allocated on-the-fly and input arrays extended as needed. This was described in a paper called "Practical, low-effort equivalence verification of real code". Unfortunately the source code is not available. So the task of the student here is to implement this to klee, present that it works on examples provided by the mentor (parts of the Linux kernel code) and make the tool available to wide public.<br />
<br />
'''Required knowledge:''' C, static analysis (symbolic execution), writing clean code<br />
<br />
'''Skill level:''' advanced<br />
<br />
'''Mentor:''' [[User:Jirislaby|Jiri Slaby]]<br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
=== Concolic Symbolic Execution ===<br />
<br />
There are free symbolic execution tools like klee which perform symbolic execution on a code to find bugs. The problem with symbolic execution is that it gets lost very early if the code uses non-linear computations like comparing integers to hashes of other inputs or finding a number 'x' where x^3 == ~0.<br />
<br />
The cure for this is a parallel symbolic and concrete execution. If the symbolic execution cannot reason about some input, it asks the concrete one and vice versa. It is well-described in some papers.<br />
<br />
The student should implement this technique to klee and demonstrate how it improves performance of the symbolic execution.<br />
<br />
'''Required knowledge:''' C, static analysis (symbolic execution), writing clean code<br />
<br />
'''Skill level:''' advanced<br />
<br />
'''Mentor:''' [[User:Jirislaby|Jiri Slaby]]<br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
=== Scanny — Ruby on Rails Security Scanner ===<br />
<br />
Web developers working with Ruby on Rails framework often write insecure code — either by mistake or because thay don't know better. However many of the insecure code patterns can be detected statically and could be easily avoided. [https://github.com/openSUSE/scanny Scanny] is a tool in early stage of development that parses Ruby files and aims to report such insecure patterns.<br />
<br />
The goal of this project is to develop Scanny further so it would become a usesful tool for all Ruby on Rails developers. This consists of:<br />
<br />
* Porting all useful checks from an older [http://gitorious.org/code-scanner/ror-sec-scanner/ Perl-based tool] with a similar purpose.<br />
* Researching what other checks would be useful (based on common Ruby on Rails security problems) and adding them to the tool.<br />
* Ensuring that Scanny is usable with production-level Rails applications. This mainly means testing on real-world code and improving usability and performance of the tool as necessary.<br />
<br />
Note that Scanny is based on a code pattern-matching library [https://github.com/openSUSE/machete Machete]. Work on Scanny will probably also involve improving it.<br />
<br />
'''Required knowledge:''' Ruby, Ruby on Rails, web security basics, idea how parsing works<br />
<br />
'''Skill level:''' intermediate<br />
<br />
'''Mentor:''' [[User:Dmajda|David Majda]]<br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
=== MirrorBrain: buffer-cache-friendly mirror selection ===<br />
<br />
MirrorBrain is the framework that openSUSE uses to redirect downloads to mirror servers. <br />
<br />
It would be possible to select mirrors intelligently with the purpose of optimizing the usage of the buffer caches of the mirrors. Right now, if openSUSE is released, all CD/DVD images are downloaded from all mirror servers. It would need many GB of buffer cache on the mirrors to keep the images in memory, usually more than physically available. Now, it would be very clever if the redirector could send redirects for DVD 1 to a certain mirror (group of mirrors), and send requests to DVD 2 to another mirror (group of mirrors). The question is how to recognize situations where this is possible, and how make this happen without administrative effort. A solution has been proposed (http://postr.poeml.de/a-buffer-cache-friendly-mirror-selection-algo) and it seems to work by proof-of-concept testing. <br />
<br />
To implement this, some hacking on mod_mirrorbrain.c is needed. A prerequisite is to understand how the current mirror selection works and how to add the further algorithm to it.<br />
<br />
Mirrors (and thereby, indirectly, its users, i.e. all of us) should benefit from this selection algorithm, because they would need to read less data from their disks.<br />
<br />
'''Required knowledge:''' C programming, HTTP and networking<br />
<br />
'''Skill level:''' intermediate (high?)<br />
<br />
'''Mentor:''' [[User:poeml|Peter Poeml]]<br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
[[Category:Google Summer of Code]]<br />
<br />
== QA ==<br />
=== SUSE Studio: StudioCheck automated test framework ===<br />
<br />
This project is a abstraction of the Studio API to have the ability of creating test cases using a gherkin syntax. A prototype of the core system was created and is working, now the remaining items are the creation of abstraction steps and some reporting interface to get more than just a list of results for easier consumption.<br />
<br />
'''Required knowledge:''' Ruby, Rails, gherkin/BDL based tests<br />
<br />
'''Skill level:''' Depending on task Easy to Intermediate<br />
<br />
'''Mentor:''' [[User:bkutil|Balazs Kutil]] / [[User:chuller|Christian Hueller]]<br />
<br />
'''Student:''' [[User:SShyukriev|Shyukri Shyukriev]]<br />
<br />
=== LTP:Fix/Implement automated kernel/glibc tests ===<br />
<br />
The [http://sourceforge.net/projects/ltp/ Linux Test Project] is huge collection of testcases aiming to test stability and correctness of kernel/glibc implementation and as the time goes by, some of the testcases needs polishing and testcases for newly introduced features should be written.<br />
<br />
'''Required knowledge:''' C, low level Linux/POSIX interface<br />
<br />
'''Skill level:''' Intermediate<br />
<br />
'''Mentor:''' [[User:metan|Cyril Hrubis]]<br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
=== openQA:Implement alternative backends ===<br />
<br />
The [http://openqa.opensuse.org/ openQA/OS-autoinst testing framework] provides reliable continuous quality feedback about current openSUSE-Factory, Debian (and potentially other distributions).<br />
Currently the service relies on kvm for the testing (an alternative VirtualBox backend exists), but to test things, that need real hardware such as NVidia/ATI drivers, it needs a different backend. One idea is to use Net::VNC to interact with the machine-under-test and another is to use HDMI-capturing hardware (e.g. from Blackmagic for 200€) and hardware that can generate keystrokes to emulate user-input.<br />
<br />
'''Required knowledge:''' perl<br />
<br />
'''Skill level:''' Intermediate<br />
<br />
'''Mentor:''' [[User:bmwiedemann|Bernhard M. Wiedemann]] / [[User:dheidler|Dominik Heidler]]<br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
=== openQA:Implement web-based test creator ===<br />
(for description of openQA see above)<br />
Creating/modifying test modules currently requires people to use a text-editor to create/change perl module files.<br />
Having an interactive web-based test-module editor/creator (could be similar to a user-input recorder) would allow easier creation of test-modules.<br />
<br />
'''Required knowledge:''' perl, AJAX<br />
<br />
'''Skill level:''' Advanced<br />
<br />
'''Mentor:''' [[User:bmwiedemann|Bernhard M. Wiedemann]] / [[User:dheidler|Dominik Heidler]]<br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
== openSUSE System Management ==<br />
=== Automatic resizing of LVM volumes and filesystems ===<br />
<br />
openSUSE currently provides good support for creating LVM volumes and installing the OS<br />
on these volumes. However, if the filesystem becomes full, the user/administrator has to increase the volume size and contained filesystem capacity manually.<br />
<br />
The goal of this project would be to implement automatic resizing of LVM <br />
volumes and contained filesystems. This resizing would be triggered e.g.<br />
by the package manager before installing the packages, if the free space drops<br />
before certain threshold etc. The installer should be modified to compute the <br />
necessary space needed for installing the selected set of packages and allocate<br />
the LVM volumes 'just big enough' for the installation. With future automatic<br />
resizing of the LVM/FS, this would save storage capacity in the volume group<br />
which would otherwise be unnecessarily allocated for /, /usr etc.<br />
<br />
'''Required knowledge:''' At least basic experience with C/C++, RPM, scripting<br />
(Python, bash). Understanding of LVM is a plus, but not necessary. Willingness to learn and investigate is a must.<br />
<br />
'''Skill level:''' Intermediate<br />
<br />
'''Mentor:''' [[User:Puzel|Petr Uzel]]<br />
<br />
'''Student:''' Praful Johari<br />
<br />
== ownCloud Related Ideas==<br />
<!-- <br />
Problem description short enough to catch attention.<br />
--><br />
* ''ownCloud Apps as GNOME Web Apps''<br />
<!-- <br />
General background information, as much as needed, but not more. <br />
--><br />
* ''Background: ownCloud can show Apps as standalone Web Apps. They should automatically appear in GNOME when you connect ownCloud with GNOME via the Online Accounts Panel.'''<br />
<!-- <br />
Mentor name and/or link with contact information <br />
--><br />
* '''Mentor: Frank Karlitschek'''<br />
<!-- <br />
Easy, Medium<br />
--><br />
* '''Skill Level: Medium '''<br />
<!-- <br />
Student name goes here<br />
--><br />
* '''Student:'''<br />
<br />
<br />
<br />
<!-- <br />
Problem description short enough to catch attention.<br />
--><br />
* ''Project Title: ownCloud Dolphin integration''<br />
<!-- <br />
General background information, as much as needed, but not more. <br />
--><br />
* '''Background: Integration in Dolphin to access sharing and version of files from within the context menu.'''<br />
<br />
The idea is that users can click on a folder with right mouse button and get a possibility to add that directory as syncing directory to ownCloud or "desync" it. Another idea is to display a special icon in dolphin if a folder is a synced folder. <br />
<br />
Together with ownClouds versioning feature, it moreover would be great if the user could have access to previous versions of the file. <br />
<!-- <br />
Mentor name and/or link with contact information <br />
--><br />
* '''Mentor: Frank Karlitschek'''<br />
<!-- <br />
Medium<br />
--><br />
* '''Skill Level:'''<br />
<!-- <br />
Student name goes here<br />
--><br />
* '''Student:'''<br />
<br />
== Beautiful one-click-install ==<br />
<br />
<!-- <br />
Problem description short enough to catch attention.<br />
--><br />
* ''Project Title:'' Beautiful one-click-install <br />
<!-- <br />
General background information, as much as needed, but not more. <br />
--><br />
* '''Background:''' Garrett made a [http://ux.suse.de/~garrett/public/hackweek/oneclick/mockups/oneclick-mockup-disable%20widgets.png great mockup] for a much more beautiful one click installer some time ago. It would be great to get this implemented. I think it could be done with a small Qt application which uses libzypp or PackageKit or something like that as the backend to do the actual installation. Some more information in [https://features.opensuse.org/309503 FATE #309503].<br />
<br />
<!-- <br />
Mentor name and/or link with contact information <br />
--><br />
* '''Mentor:''' [[User:cschum|Cornelius Schumacher]]<br />
<!-- <br />
Easy, Medium, Hard<br />
--><br />
* '''Skill Level:''' Intermediate<br />
<!-- <br />
Student name goes here<br />
--><br />
* '''Student:''' Student Needed<br />
<br />
== Implementing Accurate XML Code Formatting ==<br />
<br />
<!-- <br />
Problem description short enough to catch attention.<br />
--><br />
* ''Create Readable Source Code Formatting for XML''<br />
<br />
<!-- <br />
General background information, as much as needed, but not more. <br />
--><br />
* '''Background:'''<br />
There are some tools which can format XML/HTML sourcecode (tidy, xmlformat, ...). <br />
For example, xmlformat splits elements in an inline, block, and verbatim (=code) category. In most cases this works fine, but sometimes it fails.<br />
<br />
This tool could be improved by, for example using XPath expressions or by<br />
reading schemas (DTD, RNG, ...) to know more about the structure<br />
and how to format it. This would (hopefully) lead to a more exact<br />
formatting (think of mixed contents)<br />
<br />
<br />
<!-- <br />
Mentor name and/or link with contact information <br />
--><br />
* '''Mentor:''' [[User:Thomas-schraitle|Thomas Schraitle]], [[User:rjschwei|Robert Schweikert]]<br />
<br />
<!-- <br />
Easy, Medium, Hard<br />
--><br />
* '''Skill Level:''' Intermediate<br />
<br />
Perl or C experience. Knowledge of XML and/or XPath is desirable. Depending on the project plan, DTD would also be useful.<br />
<br />
<!-- <br />
Student name goes here<br />
--><br />
* '''Student:''' STUDENT NEEDED<br />
<br />
== Virtualization ==<br />
<br />
<!-- <br />
Problem description short enough to catch attention.<br />
--><br />
===Upstream Xen Support for Libvirt===<br />
<br />
<!-- <br />
General background information, as much as needed, but not more. <br />
--><br />
The libvirt project provide a common and stable layer for different virtualization technology, including Xen, KVM, qemu and other hypervisors. Xen is one of the most important virtualization technology supported by openSUSE. But there are lots of changes from Xen-unstable, which lead to libvirt unused in lots of occasion. <br />
<br />
The gual of this project is to update libvirt for the xen-unstable. Most of the work may be update for the latest xenlight driver in libvirt. <br />
<br />
<!-- <br />
Mentor name and/or link with contact information <br />
--><br />
'''Mentor:''' [[User:Bjzhang|Bamvor Jian Zhang]]<br />
<br />
'''Required knowledge:''' C<br />
<br />
<!-- <br />
Easy, Medium, Hard<br />
--><br />
'''Skill Level:''' Intermediate<br />
<br />
<!-- <br />
Student name goes here<br />
--><br />
'''Student:''' STUDENT NEEDED<br />
<br />
<br />
== Code review for projects on GitHub ==<br />
<br />
<!-- <br />
Problem description short enough to catch attention.<br />
--><br />
The goal of this project is to extend [https://github.com/b4mboo/git-review git-review] to make code review from the command line interface even simpler.<br />
<br />
<!-- <br />
General background information, as much as needed, but not more. <br />
--><br />
A lot of our projects have moved their code to [https://github.com GitHub]. Using pull requests is a comfortable way to collaborate on projects hosted there and if done in a browser there is also a nice UI for it. <br />
However, since most developers use the command line for all of their git operations anyways, git-review was created to add some commands to git and thus enable developers to handle code review from the command line, too.<br />
<br />
For productive use git-review needs code coverage and added functionality that allows developers to work on different forks of a project.<br />
For further information please take a look at the project's list of open [https://github.com/b4mboo/git-review/issues issues].<br />
<br />
<!-- <br />
Mentor name and/or link with contact information <br />
--><br />
'''Mentor:''' [mailto:bamboo@suse.com Dominik Bamberger]<br />
<br />
'''Required knowledge:''' Ruby, Git, RSpec<br />
<br />
<!-- <br />
Easy, Medium, Hard<br />
--><br />
'''Skill Level:''' Medium<br />
<br />
<!-- <br />
Student name goes here<br />
--><br />
'''Student:''' STUDENT NEEDED<br />
<br />
== syslog-ng ==<br />
<br />
=== Improve the MongoDB destination of syslog-ng ===<br />
<br />
syslog-ng, the leading logging platform has had support for storing messages in MongoDB for a good while now, but the technical details of how this is accomplished are a bit arcane, and the functionality and speed suffers because of this.<br />
<br />
The idea behind this project is to enhance the driver, to make it more robust, scalable and performant.<br />
<br />
There are already plans on how this can be accomplished, touching multiple parts of syslog-ng, deep in its core. These plans need to be explored further, and a suitable implementation needs to be developed.<br />
<br />
Basically - for those who are a bit familiar with mongodb - we want to go from using dot-notation and upserts to building structured BSON objects and using (bulk) inserts instead.<br />
<br />
'''Mentor'''<br />
<br />
* Confirmed Mentor: Gergely Nagy, who is available at [mailto:algernon@balabit.hu algernon@balabit.hu], or algernon on IRC (irc.oftc.net or irc.freenode.org)<br />
* Co-mentor: Viktor Juhasz, who is available at [mailto:jviktor@balabit.hu jviktor@balabit.hu]<br />
<br />
'''Deliverables of the project'''<br />
<br />
* Modify syslog-ng's internal value pairs subsystem to be able to emit a tree of values, not just a flat name=value list.<br />
* Teach the mongodb driver to walk the tree, and construct BSON objects out of it, and use insert instead of upsert.<br />
* Add support for inserting messages into a MongoDB database in batches, instead of inserting one by one.<br />
<br />
'''Desirable skills'''<br />
<br />
* A reasonable knowledge of the C programming language. glib experience is a great help, but not strictly neccessary.<br />
* Interest in working with a modern non-relational database, and hacking on a mature code-base.<br />
* Interested students who wish to apply should attach a log of a successful syslog-ng 3.3 compilation from source.<br />
<br />
'''What the student will learn'''<br />
<br />
* The student will learn about the MongoDB wire protocol, and the BSON serialization format.<br />
* The student will be able to learn how to refactor code, and make it much more efficient.<br />
* The student can learn about lex and yacc, and see and modify a complex parser built using these.<br />
<br />
'''Student:''' STUDENT NEEDED<br />
<br />
=== libdbi-less SQL destination for syslog-ng ===<br />
<br />
syslog-ng has long supported storing log messages in various SQL databases, through the libdbi library. However, development of that library has stalled, and the code is old, inefficient and generally not suitable for high performance situations.<br />
<br />
For this reason, the goal of this project would be to develop a destination driver for syslog-ng that is able to store logs in selected SQL databases (mysql or postgres at first, with the promise that it'll be reasonably easy to add support for others) without using libdbi, and directly using the libraries or protocols provided by the databases.<br />
<br />
With this, not only would the performance of storing logs in SQL increase, but we'd be able to add features that are not possible with libdbi.<br />
<br />
'''Mentor'''<br />
<br />
* Confirmed Mentor: Viktor Juhasz, who is available at jviktor@balabit.hu<br />
* Co-mentor: Gergely Nagy, who is available at: algernon@balabit.hu, or algernon on IRC (irc.oftc.net or irc.freenode.org)<br />
<br />
'''Deliverables of the project'''<br />
<br />
* A working destination driver, able to store messages in an SQL database of the student's choice, without the use of libdbi.<br />
* The driver should support using prepared statements<br />
* The driver should be mostly backwards compatible with the existing SQL driver, if possible.<br />
* The result should be faster than the existing solution.<br />
<br />
'''Desirable skills'''<br />
<br />
* A reasonable knowledge of the C programming language<br />
* Basic SQL knowledge (INSERT, transactions, prepared statements, etc..)<br />
* Experience with, or willingness to learn to use the native libraries provided by the database.<br />
* Interested students who wish to apply should attach a log of a successful syslog-ng 3.3 compilation from source.<br />
<br />
'''What the student will learn'''<br />
<br />
* The student will be able to learn communicating with an SQL database from C.<br />
* The student will be able to learn how to make database access fast, and still robust.<br />
* The student will be able to learn from past mistakes of other developers, and improve upon their design.<br />
<br />
'''Student:''' STUDENT NEEDED<br />
<br />
=== Asynchronous communication support for libmongo-client ===<br />
<br />
In order to talk to the MongoDB server, syslog-ng uses the libmongo-client library developed at BalaBit. This library uses synchronous communication with the server, meaning that it will block<br />
until an operation is in progress.<br />
<br />
We would like to change that, and for performance and other reasons, make it asynchronous. This demands a lot of internal changes within the library, that have been started, but isn't complete yet.<br />
<br />
The goal of this project is to finish the low-level transition that have been started, then design and implement asynchronous, non-blocking communication with the MongoDB server.<br />
<br />
'''Mentor'''<br />
<br />
* Confirmed Mentor: Gergely Nagy, who is available at algernon@balabit.hu, or algernon on IRC (irc.oftc.net or irc.freenode.org)<br />
* Co-mentor: Viktor Tusa, who is available at tusa@balabit.hu<br />
<br />
'''Deliverables of the project:'''<br />
<br />
* The libmongo-client library split into two: a small one to work with BSON, and another to work with MongoDB.<br />
* A workable design of how to communicate with MongoDB in a non-blocking way, while still preserving most - if not all - of the convenience features the library now provides (such as safe-mode, automatic failover and replica-set support).<br />
* An implementation of said design, with test coverage.<br />
<br />
'''Desired skills:'''<br />
<br />
* A good knowledge of the C programming language<br />
* A reasonable amount of experience and knowledge about writing network programs or libraries.<br />
* Familiarity with the BSON format, and the MongoDB wire protocol (both of which can be picked up in a single afternoon).<br />
* The applicant is expected to show his knowledge of either the BSON format, or the MongoDB wire protocol in his application, or shortly after (the exact method of that is left up to the student).<br />
<br />
'''What the student will learn:'''<br />
<br />
* Best practices while developing a library<br />
* Test-driver development, with periodic reviews<br />
* Unit testing a network library written in C<br />
* How to write portable, efficient C code<br />
<br />
'''Student:''' STUDENT NEEDED<br />
<br />
== Zorp ==<br />
<br />
=== MongoDB proxy for the Zorp application level firewall ===<br />
<br />
Zorp is an application level firewall: something that sees inside protocols, can understand and modify them.<br />
<br />
The goal of this project is to write a completely new proxy module for it, that is able to parse and reassemble the MongoDB wire protocol, and provide hooks for the firewall user to influence the traffic (by, for example, restricting access to read-only operations).<br />
<br />
'''Mentor'''<br />
<br />
* Confirmed Mentor: Szilard Pfeiffer, who is available at coroner@balabit.hu<br />
* Co-mentor: Gergely Nagy, who is available at: algernon@balabit.hu, or algernon on IRC (irc.oftc.net or irc.freenode.org)<br />
<br />
'''Deliverables of the project'''<br />
<br />
* A functional proxy, that is able to parse and reassemble the MongoDB wire protocol.<br />
* Ability to hook into the protocol, and influence it, by restricting the usable set of commands to read-only operation only (or to a selected list of commands).<br />
<br />
'''Desirable skills'''<br />
<br />
* A reasonable knowledge of the C and Python programming languages<br />
* Basic knowledge of network protocols<br />
* Interested students who wish to apply should attach a log of a successful Zorp 3.9.5 compilation from source. An even more interesting thing would be if applicants already tried the Zorp virtual machines in advance, to get familiar with the software.<br />
<br />
'''What the student will learn'''<br />
<br />
* The student will learn about the MongoDB wire protocol, and the BSON serialization format.<br />
* The student will be able to learn how to call Python from C, and vice versa.<br />
* The student will learn how to influence network traffic using an application level firewall<br />
<br />
'''Student:''' STUDENT NEEDED<br />
<br />
=== XMPP proxy for the Zorp application level firewall ===<br />
<br />
Zorp, being an application level firewall, that sees inside protocols, and can even modify the traffic between peers is the perfect place to audit or filter instant-messaging protocols, such as XMPP (used by, among other things, Jabber and Google Talk).<br />
<br />
The goal of this project would be to implement an XMPP proxy, that is not only able to parse and reassemble the protocol, but also suitable to disable parts of it, such as file transfer or video chat, or restrict the traffic in any other way the student finds interesting or useful.<br />
<br />
'''Mentor'''<br />
<br />
* Confirmed Mentor: Szilard Pfeiffer, who is available at coroner@balabit.hu<br />
* Co-mentor: Attila Szalay, who is available at: sasa@balabit.hu<br />
<br />
'''Deliverables of the project:'''<br />
<br />
* A functional proxy, that can parse and reassemble XMPP traffic<br />
* Ability to hook into the protocol, and disable parts of it (such as file transfer or video chat)<br />
* Ability to restrict XMPP to certain users, or to user-specifiable time-frames (thus making it possible to disable XMPP during the day, but enable it outside of working hours).<br />
<br />
'''Desirable skills:'''<br />
<br />
* A reasonable knowledge of the C and Python programming languages<br />
* A solid knowledge of instant messaging protocols, XMPP in particular.<br />
* Interested students who wish to apply should attach a log of a successful Zorp 3.9.5 compilation from source. An even more interesting thing would be if applicants already tried the Zorp virtual machines in advance, to get familiar with the software.<br />
<br />
'''What the student will learn:'''<br />
<br />
* The student will be able to learn a lot about application level firewalls.<br />
* The student will be able to learn how to call Python from C, and vice versa.<br />
<br />
'''Student:''' STUDENT NEEDED<br />
<br />
=== Facebook chat restrictions with Zorp ===<br />
<br />
<br />
The goal of the project would be to figure out a way to either enhance the existing HTTP proxy, or write a new one, that can be stacked inside it, to be able to restrict Facebook chat.<br />
<br />
This involves a reasonable amount of research along with the coding. The expected outcome is a way to enable users to use facebook, but forbid chatting during work hours (where work hours are, of course, configurable).<br />
<br />
'''Mentor'''<br />
<br />
* Confirmed Mentor: Attila Szalay, who is available at sasa@balabit.hu<br />
* Co-mentor: Szilard Pfeiffer, who is available at coroner@balabit.hu<br />
<br />
'''Deliverables of the project:'''<br />
<br />
* An analysis of how one could restrict facebook chat.<br />
* Either an enhancement of the existing HTTP proxy, or a new one, that can be stacked inside it that makes the restriction possible.<br />
<br />
'''Desirable skills'''<br />
<br />
* A reasonable knowledge of the C and Python programming languages<br />
* A solid knowledge of the HTTP protocol and HTML.<br />
* A reasonable knowledge of JavaScript, and debugging tools.<br />
* Interested students who wish to apply should attach a log of a successful Zorp 3.9.5 compilation from source. An even more interesting thing would be if applicants already tried the Zorp virtual machines in advance, to get familiar with the software.<br />
<br />
'''What the student will learn:'''<br />
<br />
* The student will be able to learn a lot about application level firewalls.<br />
* The student will be able to learn how to call Python from C, and vice versa.<br />
<br />
<br />
'''Student:''' STUDENT NEEDED</div>Kfreitaghttps://en.opensuse.org/index.php?title=openSUSE:Build_Service_Tutorial&diff=49544openSUSE:Build Service Tutorial2012-02-23T12:05:38Z<p>Kfreitag: /* Perform the local build */</p>
<hr />
<div>{{Buildservice_navbar}}<br />
{{Intro|This document should give an overview of the Build Service and a tutorial on how to build packages for different distributions using this great tool. We will try to show all actions on an example application so you can follow the steps to produce your own packages. }}<br />
<br />
== Prerequisites ==<br />
<br />
You should have a general understanding about [http://en.wikipedia.org/wiki/RPM_Package_Manager RPMs] and how they are created. See the [[openSUSE:Packaging_guidelines|packaging guidelines]] for openSUSE or a similar document of another supported packaging system such as [http://en.wikipedia.org/wiki/Dpkg dpkg]. This document is not meant to be a replacement for packaging documentation, which can be found at the above links.<br />
<br />
You should be familiar with the source code environment your project is using for your package. The Build Service can work around some common mistakes and will try to guide you in case of failures. We have a [http://lists.opensuse.org/archive/opensuse-buildservice/ buildservice-mailinglist] which can be a source of help and advice. However, decisions on which patches to apply, what compiler flags to use, etc. are ultimately up to you.<br />
<br />
== Requirements ==<br />
<br />
To make full use of the [http://build.opensuse.org Build Service], you need '''to login with your openSUSE/SUSE account''' (same as wiki, bugzilla...). If you have no account yet, click on the "[https://build.opensuse.org/ICSLogin/?%22https://build.opensuse.org/%22 sign up]" link at the top of the page to create one. Keep in mind that if you change your password someday that you also need to change <tt>~/.oscrc</tt>, and if you fail to do so and run osc commands that involve the server nevertheless, the user account may be blocked after repeated tries with an incorrect password.<br />
<br />
== Terminology ==<br />
<br />
The Build Service contains '''projects''' (you can [https://build.opensuse.org/project/list_all view a list of them]). Each project contains the resources needed to build one or more '''packages''' (i.e. RPMs/DEBs/etc.). These resources include source archives, patch files, spec files, etc. The output of a project is one or more '''repositories'''. A repository is an old familiar concept: simply a bunch of RPMs organized in a directory hierarchy along with some index/meta-data files that make it easy for tools like '''zypper''' to search and resolve dependencies. The repositories a project outputs correspond to the different operating system versions such as openSUSE 11.2, etc.<br />
<br />
As far as the projects that exist, there are "official" openSUSE projects that build the RPMs provided in the standard openSUSE distributions. The "factory" project is the work-in-progress project that will become the next version of openSUSE. There are also lots of area-specific projects such as [https://build.opensuse.org/project/show?project=Apache Apache] and [https://build.opensuse.org/project/show?project=network%3Atelephony network:telephony]. Finally, each user has his own "playground" project named '''home:''username'''''.<br />
<br />
RPMs tend to have lots of dependencies on other RPMs, and often these RPMs come from different projects within the Build Service. This has two important implications.<br />
<br />
First, if your package depends on some other package at runtime ("Requires"), it will often also depend on it at build time (i.e., "BuildRequires"). The Build Service does not automatically go search and find build dependencies for you (other than what is included in the standard distribution you are building for). So somehow you have to tell the Build Service where to get the required package.<br />
<br />
Secondly, a nice goal is for a repository to be '''transitively closed''', i.e. any dependency of any package in the repository is also in the repository (packages in the standard distribution excepted). This makes life easier for people installing the RPMs your project provides. But this is not required: users can always find these dependencies manually using the [http://software.opensuse.org/search search interface].<br />
<br />
The Build Service provides a few different ways to facilitate handling of these dependencies.<br />
<br />
First, you can directly add the required package(s) to your repository. This is<br />
certainly the approach you must take if no other project builds the required<br />
packages. Typically though, those packages are already being built by some<br />
other project. Consider re-using their work.<br />
<br />
The second option is to link the other project's repository to your repository.<br />
This is called '''layering'''. It is done by editing the meta-data of your<br />
project. Add the other project/repository as an additional path. This simply<br />
adds to the list of repositories in which the Build Service will search for<br />
"BuildRequires" dependencies at build time. This will allow your package's<br />
build to succeed, addressing the first problem, but it does not address the<br />
"transitively closed" goal at all: users will have to go fetch the required<br />
package themselves. However, this is a good choice when there are several<br />
dependencies from your project into another project and/or users are likely to<br />
be pulling from both repositories anyway.<br />
<br />
The third option is called '''linking''' and is a way to allow your project to<br />
re-use a package that already exists in another project. When you link a<br />
package into your project, dependent packages will be able to build, and the<br />
package will also appear your project's repository, therefore solving both<br />
problems without duplicating any work.<br />
<br />
There are two types of linking: '''link''' and '''aggregate'''. When you<br />
'''link''', you can optionally modify the way the package is built. You can add patches, and enable the build for additional repositories. Your build<br />
of the package's RPM will have a different build number from the original<br />
project's build of it. Note, this could cause confusion for users. Really, you<br />
are building a different version of a package with the same name.<br />
<br />
Unless you need to modify the required package, you should '''aggregate'''<br />
instead of '''link'''. When you '''aggregate''', you are performing a<br />
"read-only" link. The package is not built within your project; instead, the<br />
already-built package is copied into your project from the original project. So<br />
the same RPM (with the same build number) will appear in both projects. For the<br />
user, there is less confusion because the RPMs are identical. <br />
<br />
The Build Service automatically detects changes in linked packages and triggers rebuilds of any packages depending on them.<br />
<br />
== Workflow ==<br />
<br />
The following steps outline a normal workflow to create a project and add packages to it. Of course, in a real world example you might fail at some steps and have to repeat it until it does not fail anymore. This outline is just to give you a feeling about what we are trying to achieve. <br />
<br />
We will show you two different ways if possible: <br />
* the '''[http://build.opensuse.org Web client]''' way<br />
* the '''[[openSUSE:OSC|Command line]]''' client way <br />
* An alternate method is the '''MonoOSC''' client way, a tutorial already exist [[openSUSE:MonoOSC_guide|here]], so no need to duplicate.<br />
<br />
=== Step One – Login and one time Local Project setup ===<br />
<br />
If you already have an openSUSE Account, this is the easiest step.<br />
<br />
* '''Web client''': Open http://build.opensuse.org/ and use the login link on the upper right to login. After that, your home project is available by clicking on your username.<br />
<br />
* '''Command line''': <br />
<br />
At first, you have to install the command-line client on your machine. You can find osc packages for different distributions in the [http://download.opensuse.org/repositories/openSUSE:/Tools/ openSUSE-Tools] software download repository (yes: this is also a Build Service Project). Use your favorite package manager to install the osc package.<br />
<br />
Afterwards, "cd" into the directory you want to use for your project files. Now everybody familiar with [[wikipedia:en:Apache_Subversion|SVN]] will feel "at home": try to checkout your home project using <br />
cd <directory_to_contain_project_root><br />
osc checkout home:&lt;username&gt;<br />
cd home:&lt;username&gt; <br />
: (please replace &lt;username&gt; with your login). You will be prompted for '''your username and password''' — afterwards, osc will try to checkout packages in your home project and create a new directory called home:&lt;username&gt;. You can edit your settings in the file <tt>~/.oscrc</tt>.<br />
<br />
=== Step Two – Create & Upload packages ===<br />
<br />
You can use your home project as a "playground" to test packages which will be transferred to other, more visible projects if everything is alright.<br />
<br />
* '''Web client''': Click on your username to open your home project, then click on "create new package" in the packages tab. You should fill out the following three textfields: "Name" (mandatory), "Title" and "Description". Just use the package name as "Name", the package summary as "Title" and the package description as "Description". <br />
<br />
After the package is created, go to the "Sources" tab to add the files for your package. You need to upload the source code of your package and at least a spec file (see also [[openSUSE:Packaging_guidelines]]).<br />
<br />
* '''Command line''':<br />
osc meta pkg -e home:&lt;username&gt; &lt;packagename&gt;<br />
<br />
osc will open a template xml file in your favorite editor (based on the <tt>EDITOR</tt> environment variable) and you can just add the same things (Name, Title and Description) as described above. <br />
<br />
Now call<br />
osc up<br />
and you will get a new directory with the name of your new package. To add files via the command line, just cd into the new directory, copy the relevant files (typically a .tar.xz and support files).<br />
<br />
openSUSE RPM packages have their build instructions in a specfile.<br />
See the [[openSUSE:Packaging_guidelines|packaging guidelines]] how to create this. An easier approach is to copy and adapt a specfile from a similar package, or from within the tar-ball, if available.<br />
When the files are ready call<br />
osc add *<br />
this will mark the files in the directory for the next submit. To submit the files, call<br />
osc commit<br />
A commit automatically triggers the build process. You may want to delay the commit, until after you successfully built the package locally, see below.<br />
<br />
=== Step Three – Choose build targets ===<br />
<br />
Now you have to select for which distributions (e.g. openSUSE 11.3, Ubuntu 10.04 etc.) your packages should get built. <br />
<br />
* '''Web client''': Go to the "Repositories" tab on your project, and click on ''add repositories'' and choose one of the available distributions and architectures.<br />
<br />
* '''Command line''': first get a list of available repositories<br />
osc ls<br />
then edit your project metadata:<br />
osc meta prj -e home:&lt;username&gt;<br />
and add the repository like:<br />
<br />
<repository name="openSUSE_Factory"><br />
<path project="openSUSE:Factory" repository="standard" /><br />
<arch>x86_64</arch><br />
<arch>i586</arch><br />
</repository><br />
<br />
'''project''' can be openSUSE:Factory, openSUSE:11.3, SUSE:SLE-11:SP1 and the like. The ''repository="standard"'' is just for future extensions (forks of a repository).<br />
<br />
=== Step Four – Build your package ===<br />
<br />
Your package is scheduled for build automatically after it is committed or some files have changed. If a required package is rebuilt, your package will automatically be rebuilt, too. <br />
<br />
You can also manually trigger a rebuild if you need: <br />
osc rebuildpac <project> <package> [<repo> [<arch>]]<br />
With the optional <repo> and <arch> arguments, the rebuild can be limited to a certain repository or architecture.<br />
<br />
If your project is named home:username, you can now find your project at http://download.opensuse.org/repositories/home:/username/<br />
<br />
==== Build your package locally ====<br />
<br />
Sometimes, it can be faster to build your package on your local machine instead of waiting for the results from the Build Service. <br />
osc supports local builds of your package if your local hardware supports it (on x86_64 you can build for i586 and x86_64, on i586 only for i586). <br />
<br />
===== Ensure you have the latest sources =====<br />
<br />
Use osc checkout (osc co) or osc up to ensure you have the latest version of the source.<br />
<br />
If it is project you don't have checkout at all:<br />
<br />
cd <your_obs_working_dir>;<br />
osc co <project> <package><br />
<br />
or<br />
<br />
cd <your_obs_working_dir>/<project>;<br />
osc co <package><br />
<br />
or<br />
<br />
cd <your_obs_working_dir>/<project>/<package>;<br />
osc up<br />
<br />
===== Perform the local build =====<br />
<br />
osc build <platform> <arch> <specfile> [--clean|--noinit]<br />
for example<br />
~/obs/home:user/project # osc build openSUSE_11.4 x86_64 project.spec<br />
<br />
If you start the build as normal user (good idea!), you will be asked for the root password of your local machine. You can avoid that if you add your user to <tt>/etc/sudoers</tt> and edit your <tt>~/.oscrc</tt>:<br />
su-wrapper = sudo<br />
and with `<tt>visudo</tt>`, add the line (as root):<br />
<your login name> ALL = NOPASSWD: /usr/bin/build<br />
to the sudo configuration (of course without '<' and '>').<br />
<br />
osc will connect to the OBS repository server and download all needed RPMs to <tt>/var/tmp/osbuild-packagecache/''plattform''/''repository''/''arch''</tt> as cache directory. If you want to avoid network traffic, its possible to fill the cache beforehand with rpms from a DVD or iso. For that, copy the rpms from the DVD to the cache dir. <br />
<br />
For example, for openSUSE_12.1 repository you can use a DVD iso as below:<br />
<br />
mount openSUSE-12.1.iso /mnt/ -o loop<br />
mkdir -p /var/tmp/osbuild-packagecache/openSUSE\:12.1/standard<br />
cp -r /mnt/suse/* /var/tmp/osbuild-packagecache/openSUSE:12.1/standard<br />
<br />
Now fix the permissions as the DVD is not writeable, but osc will need to write data into the cache:<br />
<br />
find /var/tmp/osbuild-packagecache/openSUSE:12.1 -type d -exec chmod 755 {} \;<br />
find /var/tmp/osbuild-packagecache/openSUSE:12.1 -type f -exec chmod 644 {} \;<br />
<br />
Packages can be now built locally like this:<br />
<br />
osc build openSUSE_12.1 i586 <some-package-name>.spec<br />
<br />
<TT >osc</TT > will create a chroot environment in <TT >/var/tmp/build-root/</TT > and start the build of your package. If you only have minor changes, you can avoid the re-creation of the build environment with the option <TT >--noinit</TT >. If you suspect that your chroot environment is broken, you can trigger a complete rebuild with the option <TT >--clean</TT >. You can configure the chroot directory; see the comments in your <TT >~/.oscrc</TT > file.<br />
<br />
: <TT >osc</TT > will refuse to install packages from projects your system does not trust. This may happen when your package is linked to a development project and your system is not configured to use that repository. You can get the necessary GPG key by executing:<br />
<br />
sudo rpm --import - <<_END_KEY<br />
$(osc signkey <VAR >offending-project</VAR >)<br />
_END_KEY<br />
<br />
After your packages are built in this chroot environment, you can find the resulting packages in <tt>/var/tmp/build-root/home/abuild/rpmbuild/RPMS/</tt> (older versions of rpmbuild use <tt>/usr/src/packages/RPMS/</tt>.<br />
<br />
If your package uses a URL download service, you may have to execute the following command first:<br />
<br />
zypper ar -r http://download.opensuse.org/repositories/openSUSE:/Tools/openSUSE_11.3/openSUSE:Tools.repo<br />
<br />
The complete log file of your local build is stored in ''/var/tmp/build-root/.build.log''.<br />
<br />
===== Correct Errors in the Local Build Process =====<br />
<br />
The main reason why you would need to compile a new package for openSUSE or any other distro is to assert compatibility if your package has not yet been compiled for your operating system version and release. <br />
However, that way you may encounter new errors in the build process which need to be fixed.<br />
The easiest way to fix errors is to chroot to the build environment and create a fix there. You may want to use [http://www.elstel.com/openroot openroot] instead of chroot in order to get X11 access and all the other necessary directories mounted.<br />
<br />
osc chroot openSUSE_12.1 x86_64<br />
<br />
or old-fashioned and cumbersome<br />
<br />
chroot /var/tmp/build-root/<br />
cd /home/abuild/rpmbuild/BUILD/your-package-dir<br />
ls<br />
or:<br />
openroot /var/tmp/build-root/ 'cd /home/abuild/rpmbuild/ILD/your-package-dir; ls; bash'<br />
...<br />
exit<br />
<br />
===== Dependencies =====<br />
If you get a dependency error during your build, add a line containing the build dependencies, like:<br />
BuildRequires: cmake libkde4-devel<br />
In this case, cmake and libkde4-devel will be installed before your package is built.<br />
<br />
===== Install extra packages to build root =====<br />
For debugging purposes, you might need to install extra packages to your local build root to debug and fix build related problems. This can be done through the '''~/.oscrc''' file and variable '''extra-pkgs'''. For example:<br />
<br />
extra-pkgs = vim gdb strace valgrind<br />
<br />
===== install privileges =====<br />
If you get an error message like this:<br />
error: Bad exit status from /var/tmp/rpm-tmp.qrRAn2 (%install)<br />
this means that your %install step has failed (and all others before went well). This can be because of missing write privileges if you try to install to the wrong place. In this case add the following make install command to your spec file:<br />
make install DESTDIR=%buildroot<br />
<br />
===== submit your work back to OBS =====<br />
Once you have your <package> directory the way you want it, use the below commands to submit your work back to OBS.<br />
<br />
add a new file to the package<br />
osc add <br />
<br />
remove a file from the package<br />
osc rm <br />
<br />
update the change log (ie. *.changes)<br />
osc vc <br />
<br />
submit your updated files back to OBS<br />
osc commit <br />
<br />
==== Patches ====<br />
If you plan to patch a file copy it before editing to .orig, retry the desired step in the build process until it succeeds and then create a patch for it. <br />
To make the build more verbose you may want to insert a "set -x" in your specfile making bash recite all executed commands (set +x disables reciting afterwards).<br />
diff -Pdpru /var/tmp/build-root/home/abuild/rpmbuild/BUILD/your-package-dir/Makefile.orig \<br />
/var/tmp/build-root/home/abuild/rpmbuild/BUILD/your-package-dir/Makefile \<br />
>/osc/home:user/your-package-dir/my.patch<br />
<br />
Now add the patch to the .spec-file by listing "Patch67: my.patch" in the header and then let it be applied at the appropriate position (usually %setup) in the build process by "%patch67 -p7" (-p7 strips seven directory levels if you have not manually edited the file directories in the header of the patch file.).<br />
You may find it easier to use a special program for automatic patch generation like [http://nordisch.org/2009/3/20/quilt-a-really-quick-howto Quilt].<br />
<br />
=== Step Five: Check the logfiles ===<br />
<br />
The buildservice produces one big logfile for each build of a package.<br />
<br />
* '''Web client''': Just click on the link ''[Build Log]'' in the package view.<br />
<br />
* '''Command line''': You have a few choices depending on your needs (<code>packagedir</code> is optional if you are in the package directory):<br />
<br />
osc prjresults [packagedir]<br />
<br />
Shows the aggregated build results of an entire project. Or you can do:<br />
<br />
osc results [packagedir]<br />
<br />
Shows the build results of a single package.<br />
<br />
osc buildlog <platform> <arch><br />
<br />
Shows the log file from a package (you need to be inside a package directory).<br />
<br />
===Create Patterns===<br />
<br />
Patterns are files which contain a list of packages together with a description of what they are useful for. Additionally the Build Service creates .ymp files for each generated repository pattern. These .ymp files can be used for a [[openSUSE:One_Click_Install_specification|One Click Install]] by the user. <br />
<br />
In short, patterns are useful for installing a set of software for a typical need without creating dependencies between packages.<br />
<br />
Submitting patterns is possible using the api directly, or using osc:<br />
<br />
* to open a pattern in $EDITOR (creating it if it doesn't exist yet)<br />
osc meta pattern -e <project> <pattern><br />
* to list existing patterns<br />
osc meta pattern <project><br />
* get an existing pattern<br />
osc meta pattern <project> <pattern><br />
* You can also submit an existing file as below:<br />
osc meta pattern --file <local_file> <project> <pattern><br />
<br />
To test: clicking on the .ymp in konqueror should launch the installer, if you do not have konqueror installed, you can try launching from shell as normal user:<br />
/sbin/yast2 MetaPackageHandler http://download.opensuse.org/repositories/<project>/<SUSE_Factory or openSUSE_10.2>/<pattern>.ymp<br />
<br />
The following file is an example pattern file from the KDE:KDE4 project. You can see the generated .ymp file from it [http://download.opensuse.org/repositories/KDE:/KDE4:/Factory:/Desktop/openSUSE_Factory/KDE4-GAMES.ymp here].<br />
<pre><br />
<pattern<br />
xmlns="http://novell.com/package/metadata/suse/pattern"<br />
xmlns:rpm="http://linux.duke.edu/metadata/rpm"<br />
><br />
<name>KDE 4 Games</name><br />
<summary>KDE 4 Games</summary><br />
<description>A number of games for KDE 4.</description><br />
<uservisible/><br />
<category lang="en">Desktop Functions</category><br />
<rpm:recommends><br />
<rpm:entry name="kde4-kpat"/><br />
<rpm:entry name="kde4-kmahjongg"/><br />
<rpm:entry name="kde4-kmines"/><br />
<rpm:entry name="kde4-kreversi"/><br />
<rpm:entry name="kde4-ksudoku"/><br />
</rpm:recommends><br />
<rpm:suggests><br />
<rpm:entry name="kde4-katomic"/><br />
<rpm:entry name="kde4-kbattleship"/><br />
<rpm:entry name="kde4-ksquares"/><br />
<rpm:entry name="kde4-bovo"/><br />
<rpm:entry name="kde4-kiriki"/><br />
<rpm:entry name="kde4-kwin4"/><br />
<rpm:entry name="kde4-kolf"/><br />
<rpm:entry name="kde4-klines"/><br />
<rpm:entry name="kde4-ksame"/><br />
<rpm:entry name="kde4-lskat"/><br />
<rpm:entry name="kde4-kgoldrunner"/><br />
<rpm:entry name="kde4-kblackbox"/><br />
<rpm:entry name="kde4-kbounce"/><br />
<rpm:entry name="kde4-ktuberling"/><br />
<rpm:entry name="kde4-knetwalk"/><br />
<rpm:entry name="kde4-kjumpingcube"/><br />
<rpm:entry name="kde4-kspaceduel"/><br />
<rpm:entry name="kde4-konquest"/><br />
<rpm:entry name="kde4-kshisen"/><br />
</rpm:suggests><br />
</pattern><br />
</pre><br />
<br />
Some Tag descriptions:<br />
{| border="1" cellpadding="5" cellspacing="0"<br />
! Tag !! Description<br />
|-<br />
| <pre><rpm:requires><br />
<rpm:entry name="example" /><br />
</rpm:requires></pre> || '''Requires''' RPM ''example'': this package must be installed - otherwise the pattern is not fulfilled.<br />
|-<br />
| <pre><rpm:recommends><br />
<rpm:entry name="example" /><br />
</rpm:recommends></pre> || '''Recommends''' RPM ''example'': if available and all dependencies of this package are fulfilled, the package would be installed. If the package is not available, there are not error messages. If the package dependencies are not met, the package would be visible but not installed. <br />
|-<br />
| <pre><rpm:suggests><br />
<rpm:entry name="example" /><br />
</rpm:suggests></pre> || '''Suggests''' RPM ''example'': would be shown in the pattern but not installed per default<br />
|}<br />
<br />
== See also ==<br />
<br />
* [[openSUSE:Build_Service_Tips_and_Tricks|General Tips and Tricks for the buildservice]]<br />
* [[openSUSE:Build_Service_Collaboration|How to contribute to a package maintained by someone else]]<br />
* [[openSUSE:Build_Service_cross_distribution_howto|Cross distribution package how to]]<br />
* [[openSUSE:OSC_plugins|Writing osc plugins]]<br />
* [[openSUSE:Build_Service_Debian_builds|Sharing Debian packages]]<br />
<br />
[[Category:Build Service|Tutorial]]<br />
[[Category:Packaging]]<br />
[[el:openSUSE:Build Service Tutorial]]<br />
[[ru:Build Service|Уроки]]<br />
[[de:Build Service/Anleitung]]<br />
[[es:Build Service/Guía_básica]]<br />
[[fr:Build Service/Tutoriel]]<br />
[[it:Build Service/Tutorial]]<br />
[[zh:SDB:编译服务教程]]</div>Kfreitaghttps://en.opensuse.org/index.php?title=openSUSE:Build_Service_Tutorial&diff=49543openSUSE:Build Service Tutorial2012-02-23T12:05:04Z<p>Kfreitag: /* Perform the local build */</p>
<hr />
<div>{{Buildservice_navbar}}<br />
{{Intro|This document should give an overview of the Build Service and a tutorial on how to build packages for different distributions using this great tool. We will try to show all actions on an example application so you can follow the steps to produce your own packages. }}<br />
<br />
== Prerequisites ==<br />
<br />
You should have a general understanding about [http://en.wikipedia.org/wiki/RPM_Package_Manager RPMs] and how they are created. See the [[openSUSE:Packaging_guidelines|packaging guidelines]] for openSUSE or a similar document of another supported packaging system such as [http://en.wikipedia.org/wiki/Dpkg dpkg]. This document is not meant to be a replacement for packaging documentation, which can be found at the above links.<br />
<br />
You should be familiar with the source code environment your project is using for your package. The Build Service can work around some common mistakes and will try to guide you in case of failures. We have a [http://lists.opensuse.org/archive/opensuse-buildservice/ buildservice-mailinglist] which can be a source of help and advice. However, decisions on which patches to apply, what compiler flags to use, etc. are ultimately up to you.<br />
<br />
== Requirements ==<br />
<br />
To make full use of the [http://build.opensuse.org Build Service], you need '''to login with your openSUSE/SUSE account''' (same as wiki, bugzilla...). If you have no account yet, click on the "[https://build.opensuse.org/ICSLogin/?%22https://build.opensuse.org/%22 sign up]" link at the top of the page to create one. Keep in mind that if you change your password someday that you also need to change <tt>~/.oscrc</tt>, and if you fail to do so and run osc commands that involve the server nevertheless, the user account may be blocked after repeated tries with an incorrect password.<br />
<br />
== Terminology ==<br />
<br />
The Build Service contains '''projects''' (you can [https://build.opensuse.org/project/list_all view a list of them]). Each project contains the resources needed to build one or more '''packages''' (i.e. RPMs/DEBs/etc.). These resources include source archives, patch files, spec files, etc. The output of a project is one or more '''repositories'''. A repository is an old familiar concept: simply a bunch of RPMs organized in a directory hierarchy along with some index/meta-data files that make it easy for tools like '''zypper''' to search and resolve dependencies. The repositories a project outputs correspond to the different operating system versions such as openSUSE 11.2, etc.<br />
<br />
As far as the projects that exist, there are "official" openSUSE projects that build the RPMs provided in the standard openSUSE distributions. The "factory" project is the work-in-progress project that will become the next version of openSUSE. There are also lots of area-specific projects such as [https://build.opensuse.org/project/show?project=Apache Apache] and [https://build.opensuse.org/project/show?project=network%3Atelephony network:telephony]. Finally, each user has his own "playground" project named '''home:''username'''''.<br />
<br />
RPMs tend to have lots of dependencies on other RPMs, and often these RPMs come from different projects within the Build Service. This has two important implications.<br />
<br />
First, if your package depends on some other package at runtime ("Requires"), it will often also depend on it at build time (i.e., "BuildRequires"). The Build Service does not automatically go search and find build dependencies for you (other than what is included in the standard distribution you are building for). So somehow you have to tell the Build Service where to get the required package.<br />
<br />
Secondly, a nice goal is for a repository to be '''transitively closed''', i.e. any dependency of any package in the repository is also in the repository (packages in the standard distribution excepted). This makes life easier for people installing the RPMs your project provides. But this is not required: users can always find these dependencies manually using the [http://software.opensuse.org/search search interface].<br />
<br />
The Build Service provides a few different ways to facilitate handling of these dependencies.<br />
<br />
First, you can directly add the required package(s) to your repository. This is<br />
certainly the approach you must take if no other project builds the required<br />
packages. Typically though, those packages are already being built by some<br />
other project. Consider re-using their work.<br />
<br />
The second option is to link the other project's repository to your repository.<br />
This is called '''layering'''. It is done by editing the meta-data of your<br />
project. Add the other project/repository as an additional path. This simply<br />
adds to the list of repositories in which the Build Service will search for<br />
"BuildRequires" dependencies at build time. This will allow your package's<br />
build to succeed, addressing the first problem, but it does not address the<br />
"transitively closed" goal at all: users will have to go fetch the required<br />
package themselves. However, this is a good choice when there are several<br />
dependencies from your project into another project and/or users are likely to<br />
be pulling from both repositories anyway.<br />
<br />
The third option is called '''linking''' and is a way to allow your project to<br />
re-use a package that already exists in another project. When you link a<br />
package into your project, dependent packages will be able to build, and the<br />
package will also appear your project's repository, therefore solving both<br />
problems without duplicating any work.<br />
<br />
There are two types of linking: '''link''' and '''aggregate'''. When you<br />
'''link''', you can optionally modify the way the package is built. You can add patches, and enable the build for additional repositories. Your build<br />
of the package's RPM will have a different build number from the original<br />
project's build of it. Note, this could cause confusion for users. Really, you<br />
are building a different version of a package with the same name.<br />
<br />
Unless you need to modify the required package, you should '''aggregate'''<br />
instead of '''link'''. When you '''aggregate''', you are performing a<br />
"read-only" link. The package is not built within your project; instead, the<br />
already-built package is copied into your project from the original project. So<br />
the same RPM (with the same build number) will appear in both projects. For the<br />
user, there is less confusion because the RPMs are identical. <br />
<br />
The Build Service automatically detects changes in linked packages and triggers rebuilds of any packages depending on them.<br />
<br />
== Workflow ==<br />
<br />
The following steps outline a normal workflow to create a project and add packages to it. Of course, in a real world example you might fail at some steps and have to repeat it until it does not fail anymore. This outline is just to give you a feeling about what we are trying to achieve. <br />
<br />
We will show you two different ways if possible: <br />
* the '''[http://build.opensuse.org Web client]''' way<br />
* the '''[[openSUSE:OSC|Command line]]''' client way <br />
* An alternate method is the '''MonoOSC''' client way, a tutorial already exist [[openSUSE:MonoOSC_guide|here]], so no need to duplicate.<br />
<br />
=== Step One – Login and one time Local Project setup ===<br />
<br />
If you already have an openSUSE Account, this is the easiest step.<br />
<br />
* '''Web client''': Open http://build.opensuse.org/ and use the login link on the upper right to login. After that, your home project is available by clicking on your username.<br />
<br />
* '''Command line''': <br />
<br />
At first, you have to install the command-line client on your machine. You can find osc packages for different distributions in the [http://download.opensuse.org/repositories/openSUSE:/Tools/ openSUSE-Tools] software download repository (yes: this is also a Build Service Project). Use your favorite package manager to install the osc package.<br />
<br />
Afterwards, "cd" into the directory you want to use for your project files. Now everybody familiar with [[wikipedia:en:Apache_Subversion|SVN]] will feel "at home": try to checkout your home project using <br />
cd <directory_to_contain_project_root><br />
osc checkout home:&lt;username&gt;<br />
cd home:&lt;username&gt; <br />
: (please replace &lt;username&gt; with your login). You will be prompted for '''your username and password''' — afterwards, osc will try to checkout packages in your home project and create a new directory called home:&lt;username&gt;. You can edit your settings in the file <tt>~/.oscrc</tt>.<br />
<br />
=== Step Two – Create & Upload packages ===<br />
<br />
You can use your home project as a "playground" to test packages which will be transferred to other, more visible projects if everything is alright.<br />
<br />
* '''Web client''': Click on your username to open your home project, then click on "create new package" in the packages tab. You should fill out the following three textfields: "Name" (mandatory), "Title" and "Description". Just use the package name as "Name", the package summary as "Title" and the package description as "Description". <br />
<br />
After the package is created, go to the "Sources" tab to add the files for your package. You need to upload the source code of your package and at least a spec file (see also [[openSUSE:Packaging_guidelines]]).<br />
<br />
* '''Command line''':<br />
osc meta pkg -e home:&lt;username&gt; &lt;packagename&gt;<br />
<br />
osc will open a template xml file in your favorite editor (based on the <tt>EDITOR</tt> environment variable) and you can just add the same things (Name, Title and Description) as described above. <br />
<br />
Now call<br />
osc up<br />
and you will get a new directory with the name of your new package. To add files via the command line, just cd into the new directory, copy the relevant files (typically a .tar.xz and support files).<br />
<br />
openSUSE RPM packages have their build instructions in a specfile.<br />
See the [[openSUSE:Packaging_guidelines|packaging guidelines]] how to create this. An easier approach is to copy and adapt a specfile from a similar package, or from within the tar-ball, if available.<br />
When the files are ready call<br />
osc add *<br />
this will mark the files in the directory for the next submit. To submit the files, call<br />
osc commit<br />
A commit automatically triggers the build process. You may want to delay the commit, until after you successfully built the package locally, see below.<br />
<br />
=== Step Three – Choose build targets ===<br />
<br />
Now you have to select for which distributions (e.g. openSUSE 11.3, Ubuntu 10.04 etc.) your packages should get built. <br />
<br />
* '''Web client''': Go to the "Repositories" tab on your project, and click on ''add repositories'' and choose one of the available distributions and architectures.<br />
<br />
* '''Command line''': first get a list of available repositories<br />
osc ls<br />
then edit your project metadata:<br />
osc meta prj -e home:&lt;username&gt;<br />
and add the repository like:<br />
<br />
<repository name="openSUSE_Factory"><br />
<path project="openSUSE:Factory" repository="standard" /><br />
<arch>x86_64</arch><br />
<arch>i586</arch><br />
</repository><br />
<br />
'''project''' can be openSUSE:Factory, openSUSE:11.3, SUSE:SLE-11:SP1 and the like. The ''repository="standard"'' is just for future extensions (forks of a repository).<br />
<br />
=== Step Four – Build your package ===<br />
<br />
Your package is scheduled for build automatically after it is committed or some files have changed. If a required package is rebuilt, your package will automatically be rebuilt, too. <br />
<br />
You can also manually trigger a rebuild if you need: <br />
osc rebuildpac <project> <package> [<repo> [<arch>]]<br />
With the optional <repo> and <arch> arguments, the rebuild can be limited to a certain repository or architecture.<br />
<br />
If your project is named home:username, you can now find your project at http://download.opensuse.org/repositories/home:/username/<br />
<br />
==== Build your package locally ====<br />
<br />
Sometimes, it can be faster to build your package on your local machine instead of waiting for the results from the Build Service. <br />
osc supports local builds of your package if your local hardware supports it (on x86_64 you can build for i586 and x86_64, on i586 only for i586). <br />
<br />
===== Ensure you have the latest sources =====<br />
<br />
Use osc checkout (osc co) or osc up to ensure you have the latest version of the source.<br />
<br />
If it is project you don't have checkout at all:<br />
<br />
cd <your_obs_working_dir>;<br />
osc co <project> <package><br />
<br />
or<br />
<br />
cd <your_obs_working_dir>/<project>;<br />
osc co <package><br />
<br />
or<br />
<br />
cd <your_obs_working_dir>/<project>/<package>;<br />
osc up<br />
<br />
===== Perform the local build =====<br />
<br />
osc build <platform> <arch> <specfile> [--clean|--noinit]<br />
for example<br />
~/obs/home:user/project # osc build openSUSE_11.4 x86_64 project.spec<br />
<br />
If you start the build as normal user (good idea!), you will be asked for the root password of your local machine. You can avoid that if you add your user to <tt>/etc/sudoers</tt> and edit your <tt>~/.oscrc</tt>:<br />
su-wrapper = sudo<br />
and with `<tt>visudo</tt>`, add the line (as root):<br />
<your login name> ALL = NOPASSWD: /usr/bin/build<br />
to the sudo configuration (of course without '<' and '>').<br />
<br />
osc will connect to the OBS repository server and download all needed RPMs to <tt>/var/tmp/osbuild-packagecache/''plattform''/''repository''/''arch''</tt> as cache directory. If you want to avoid network traffic, its possible to fill the cache beforehand with rpms from a DVD or iso. For that, copy the rpms from the DVD to the cache dir. <br />
<br />
For example, for openSUSE_12.1 repository you can use a DVD iso as below:<br />
<br />
mount openSUSE-12.1.iso /mnt/ -o loop<br />
mkdir -p /var/tmp/osbuild-packagecache/openSUSE\:12.1/standard<br />
cp -r /mnt/suse/* /var/tmp/osbuild-packagecache/openSUSE:12.1<br />
<br />
Now fix the permissions as the DVD is not writeable, but osc will need to write data into the cache:<br />
<br />
find /var/tmp/osbuild-packagecache/openSUSE:12.1 -type d -exec chmod 755 {} \;<br />
find /var/tmp/osbuild-packagecache/openSUSE:12.1 -type f -exec chmod 644 {} \;<br />
<br />
Packages can be now built locally like this:<br />
<br />
osc build openSUSE_12.1 i586 <some-package-name>.spec<br />
<br />
<TT >osc</TT > will create a chroot environment in <TT >/var/tmp/build-root/</TT > and start the build of your package. If you only have minor changes, you can avoid the re-creation of the build environment with the option <TT >--noinit</TT >. If you suspect that your chroot environment is broken, you can trigger a complete rebuild with the option <TT >--clean</TT >. You can configure the chroot directory; see the comments in your <TT >~/.oscrc</TT > file.<br />
<br />
: <TT >osc</TT > will refuse to install packages from projects your system does not trust. This may happen when your package is linked to a development project and your system is not configured to use that repository. You can get the necessary GPG key by executing:<br />
<br />
sudo rpm --import - <<_END_KEY<br />
$(osc signkey <VAR >offending-project</VAR >)<br />
_END_KEY<br />
<br />
After your packages are built in this chroot environment, you can find the resulting packages in <tt>/var/tmp/build-root/home/abuild/rpmbuild/RPMS/</tt> (older versions of rpmbuild use <tt>/usr/src/packages/RPMS/</tt>.<br />
<br />
If your package uses a URL download service, you may have to execute the following command first:<br />
<br />
zypper ar -r http://download.opensuse.org/repositories/openSUSE:/Tools/openSUSE_11.3/openSUSE:Tools.repo<br />
<br />
The complete log file of your local build is stored in ''/var/tmp/build-root/.build.log''.<br />
<br />
===== Correct Errors in the Local Build Process =====<br />
<br />
The main reason why you would need to compile a new package for openSUSE or any other distro is to assert compatibility if your package has not yet been compiled for your operating system version and release. <br />
However, that way you may encounter new errors in the build process which need to be fixed.<br />
The easiest way to fix errors is to chroot to the build environment and create a fix there. You may want to use [http://www.elstel.com/openroot openroot] instead of chroot in order to get X11 access and all the other necessary directories mounted.<br />
<br />
osc chroot openSUSE_12.1 x86_64<br />
<br />
or old-fashioned and cumbersome<br />
<br />
chroot /var/tmp/build-root/<br />
cd /home/abuild/rpmbuild/BUILD/your-package-dir<br />
ls<br />
or:<br />
openroot /var/tmp/build-root/ 'cd /home/abuild/rpmbuild/ILD/your-package-dir; ls; bash'<br />
...<br />
exit<br />
<br />
===== Dependencies =====<br />
If you get a dependency error during your build, add a line containing the build dependencies, like:<br />
BuildRequires: cmake libkde4-devel<br />
In this case, cmake and libkde4-devel will be installed before your package is built.<br />
<br />
===== Install extra packages to build root =====<br />
For debugging purposes, you might need to install extra packages to your local build root to debug and fix build related problems. This can be done through the '''~/.oscrc''' file and variable '''extra-pkgs'''. For example:<br />
<br />
extra-pkgs = vim gdb strace valgrind<br />
<br />
===== install privileges =====<br />
If you get an error message like this:<br />
error: Bad exit status from /var/tmp/rpm-tmp.qrRAn2 (%install)<br />
this means that your %install step has failed (and all others before went well). This can be because of missing write privileges if you try to install to the wrong place. In this case add the following make install command to your spec file:<br />
make install DESTDIR=%buildroot<br />
<br />
===== submit your work back to OBS =====<br />
Once you have your <package> directory the way you want it, use the below commands to submit your work back to OBS.<br />
<br />
add a new file to the package<br />
osc add <br />
<br />
remove a file from the package<br />
osc rm <br />
<br />
update the change log (ie. *.changes)<br />
osc vc <br />
<br />
submit your updated files back to OBS<br />
osc commit <br />
<br />
==== Patches ====<br />
If you plan to patch a file copy it before editing to .orig, retry the desired step in the build process until it succeeds and then create a patch for it. <br />
To make the build more verbose you may want to insert a "set -x" in your specfile making bash recite all executed commands (set +x disables reciting afterwards).<br />
diff -Pdpru /var/tmp/build-root/home/abuild/rpmbuild/BUILD/your-package-dir/Makefile.orig \<br />
/var/tmp/build-root/home/abuild/rpmbuild/BUILD/your-package-dir/Makefile \<br />
>/osc/home:user/your-package-dir/my.patch<br />
<br />
Now add the patch to the .spec-file by listing "Patch67: my.patch" in the header and then let it be applied at the appropriate position (usually %setup) in the build process by "%patch67 -p7" (-p7 strips seven directory levels if you have not manually edited the file directories in the header of the patch file.).<br />
You may find it easier to use a special program for automatic patch generation like [http://nordisch.org/2009/3/20/quilt-a-really-quick-howto Quilt].<br />
<br />
=== Step Five: Check the logfiles ===<br />
<br />
The buildservice produces one big logfile for each build of a package.<br />
<br />
* '''Web client''': Just click on the link ''[Build Log]'' in the package view.<br />
<br />
* '''Command line''': You have a few choices depending on your needs (<code>packagedir</code> is optional if you are in the package directory):<br />
<br />
osc prjresults [packagedir]<br />
<br />
Shows the aggregated build results of an entire project. Or you can do:<br />
<br />
osc results [packagedir]<br />
<br />
Shows the build results of a single package.<br />
<br />
osc buildlog <platform> <arch><br />
<br />
Shows the log file from a package (you need to be inside a package directory).<br />
<br />
===Create Patterns===<br />
<br />
Patterns are files which contain a list of packages together with a description of what they are useful for. Additionally the Build Service creates .ymp files for each generated repository pattern. These .ymp files can be used for a [[openSUSE:One_Click_Install_specification|One Click Install]] by the user. <br />
<br />
In short, patterns are useful for installing a set of software for a typical need without creating dependencies between packages.<br />
<br />
Submitting patterns is possible using the api directly, or using osc:<br />
<br />
* to open a pattern in $EDITOR (creating it if it doesn't exist yet)<br />
osc meta pattern -e <project> <pattern><br />
* to list existing patterns<br />
osc meta pattern <project><br />
* get an existing pattern<br />
osc meta pattern <project> <pattern><br />
* You can also submit an existing file as below:<br />
osc meta pattern --file <local_file> <project> <pattern><br />
<br />
To test: clicking on the .ymp in konqueror should launch the installer, if you do not have konqueror installed, you can try launching from shell as normal user:<br />
/sbin/yast2 MetaPackageHandler http://download.opensuse.org/repositories/<project>/<SUSE_Factory or openSUSE_10.2>/<pattern>.ymp<br />
<br />
The following file is an example pattern file from the KDE:KDE4 project. You can see the generated .ymp file from it [http://download.opensuse.org/repositories/KDE:/KDE4:/Factory:/Desktop/openSUSE_Factory/KDE4-GAMES.ymp here].<br />
<pre><br />
<pattern<br />
xmlns="http://novell.com/package/metadata/suse/pattern"<br />
xmlns:rpm="http://linux.duke.edu/metadata/rpm"<br />
><br />
<name>KDE 4 Games</name><br />
<summary>KDE 4 Games</summary><br />
<description>A number of games for KDE 4.</description><br />
<uservisible/><br />
<category lang="en">Desktop Functions</category><br />
<rpm:recommends><br />
<rpm:entry name="kde4-kpat"/><br />
<rpm:entry name="kde4-kmahjongg"/><br />
<rpm:entry name="kde4-kmines"/><br />
<rpm:entry name="kde4-kreversi"/><br />
<rpm:entry name="kde4-ksudoku"/><br />
</rpm:recommends><br />
<rpm:suggests><br />
<rpm:entry name="kde4-katomic"/><br />
<rpm:entry name="kde4-kbattleship"/><br />
<rpm:entry name="kde4-ksquares"/><br />
<rpm:entry name="kde4-bovo"/><br />
<rpm:entry name="kde4-kiriki"/><br />
<rpm:entry name="kde4-kwin4"/><br />
<rpm:entry name="kde4-kolf"/><br />
<rpm:entry name="kde4-klines"/><br />
<rpm:entry name="kde4-ksame"/><br />
<rpm:entry name="kde4-lskat"/><br />
<rpm:entry name="kde4-kgoldrunner"/><br />
<rpm:entry name="kde4-kblackbox"/><br />
<rpm:entry name="kde4-kbounce"/><br />
<rpm:entry name="kde4-ktuberling"/><br />
<rpm:entry name="kde4-knetwalk"/><br />
<rpm:entry name="kde4-kjumpingcube"/><br />
<rpm:entry name="kde4-kspaceduel"/><br />
<rpm:entry name="kde4-konquest"/><br />
<rpm:entry name="kde4-kshisen"/><br />
</rpm:suggests><br />
</pattern><br />
</pre><br />
<br />
Some Tag descriptions:<br />
{| border="1" cellpadding="5" cellspacing="0"<br />
! Tag !! Description<br />
|-<br />
| <pre><rpm:requires><br />
<rpm:entry name="example" /><br />
</rpm:requires></pre> || '''Requires''' RPM ''example'': this package must be installed - otherwise the pattern is not fulfilled.<br />
|-<br />
| <pre><rpm:recommends><br />
<rpm:entry name="example" /><br />
</rpm:recommends></pre> || '''Recommends''' RPM ''example'': if available and all dependencies of this package are fulfilled, the package would be installed. If the package is not available, there are not error messages. If the package dependencies are not met, the package would be visible but not installed. <br />
|-<br />
| <pre><rpm:suggests><br />
<rpm:entry name="example" /><br />
</rpm:suggests></pre> || '''Suggests''' RPM ''example'': would be shown in the pattern but not installed per default<br />
|}<br />
<br />
== See also ==<br />
<br />
* [[openSUSE:Build_Service_Tips_and_Tricks|General Tips and Tricks for the buildservice]]<br />
* [[openSUSE:Build_Service_Collaboration|How to contribute to a package maintained by someone else]]<br />
* [[openSUSE:Build_Service_cross_distribution_howto|Cross distribution package how to]]<br />
* [[openSUSE:OSC_plugins|Writing osc plugins]]<br />
* [[openSUSE:Build_Service_Debian_builds|Sharing Debian packages]]<br />
<br />
[[Category:Build Service|Tutorial]]<br />
[[Category:Packaging]]<br />
[[el:openSUSE:Build Service Tutorial]]<br />
[[ru:Build Service|Уроки]]<br />
[[de:Build Service/Anleitung]]<br />
[[es:Build Service/Guía_básica]]<br />
[[fr:Build Service/Tutoriel]]<br />
[[it:Build Service/Tutorial]]<br />
[[zh:SDB:编译服务教程]]</div>Kfreitaghttps://en.opensuse.org/index.php?title=Mirall&diff=47449Mirall2011-12-17T12:02:08Z<p>Kfreitag: /* Features */</p>
<hr />
<div><!-- This page was created using Template:Application template --><br />
{{Infobox|<br />
name=mirall|<br />
packagename=mirall|<br />
developer=[[User:Dmacvicar|Duncan Mac Vicar]], [[User:kfreitag|Klaas Freitag]], [[User:Cschum|Cornelius Schumacher]]|<br />
image=[[File:Creating_a_new_ownCloud.png|200px]]|<br />
description=mirall configuration dialog|<br />
vendor=ownCloud Project|<br />
license=GPL|<br />
website=http://owncloud.org|<br />
}}<br />
<br />
==About==<br />
<!-- Describe the application to a novice user --><br />
Mirall is a system tray application running on your desktop. It helps you to install [http://owncloud.org ownCloud], your own private file hosting service in the cloud. <br />
<br />
In addition to that it allows you to set up express upload folders which mirror all data from local to your ownCloud.<br />
<br />
----<br />
<br />
==Features==<br />
<!-- Describe the features of the application as a bullet list --><br />
* Install ownCloud locally on your computer if apache is already there<br />
* Install ownCloud on a webspace that is accessible via ftp<br />
* Creates a local folder from which is mirrored to your ownCloud<br />
* connect to an already existing ownCloud<br />
----<br />
<br />
==See also==<br />
<!-- Other applications that provide similar functionality --><br />
* [[SpiderOak]]<br />
* [[Unison]]<br />
* [[SDB:OwnCloud|Setting up]] ownCloud and Mirall<br />
----<br />
<br />
==External links==<br />
<!-- Links to external documentation resources and the like --><br />
* [http://owncloud.org ownCloud website]<br />
* [http://en.wikipedia.org/wiki/File_hosting_service File hosting service on wikipedia]<br />
<br />
<!-- Find a suitable category on Category:Applications and add it below --><br />
[[Category:Applications:Backup]]<br />
<br />
[[it:Mirall]]</div>Kfreitaghttps://en.opensuse.org/index.php?title=Mirall&diff=47448Mirall2011-12-17T12:00:08Z<p>Kfreitag: /* About */</p>
<hr />
<div><!-- This page was created using Template:Application template --><br />
{{Infobox|<br />
name=mirall|<br />
packagename=mirall|<br />
developer=[[User:Dmacvicar|Duncan Mac Vicar]], [[User:kfreitag|Klaas Freitag]], [[User:Cschum|Cornelius Schumacher]]|<br />
image=[[File:Creating_a_new_ownCloud.png|200px]]|<br />
description=mirall configuration dialog|<br />
vendor=ownCloud Project|<br />
license=GPL|<br />
website=http://owncloud.org|<br />
}}<br />
<br />
==About==<br />
<!-- Describe the application to a novice user --><br />
Mirall is a system tray application running on your desktop. It helps you to install [http://owncloud.org ownCloud], your own private file hosting service in the cloud. <br />
<br />
In addition to that it allows you to set up express upload folders which mirror all data from local to your ownCloud.<br />
<br />
----<br />
<br />
==Features==<br />
<!-- Describe the features of the application as a bullet list --><br />
* Install ownCloud locally on your computer<br />
* Install ownCloud on a webspace that is accessible via ftp<br />
* Creates a local folder from which is mirrored to your ownCloud<br />
<br />
----<br />
==See also==<br />
<!-- Other applications that provide similar functionality --><br />
* [[SpiderOak]]<br />
* [[Unison]]<br />
* [[SDB:OwnCloud|Setting up]] ownCloud and Mirall<br />
----<br />
<br />
==External links==<br />
<!-- Links to external documentation resources and the like --><br />
* [http://owncloud.org ownCloud website]<br />
* [http://en.wikipedia.org/wiki/File_hosting_service File hosting service on wikipedia]<br />
<br />
<!-- Find a suitable category on Category:Applications and add it below --><br />
[[Category:Applications:Backup]]<br />
<br />
[[it:Mirall]]</div>Kfreitaghttps://en.opensuse.org/index.php?title=Archive:In_the_press_12.1&diff=47272Archive:In the press 12.12011-12-10T19:22:01Z<p>Kfreitag: </p>
<hr />
<div>{{Current distribution navbar|12.1}}<br />
{{Intro|A list of media articles about the openSUSE 12.1 release.}}<br />
<br />
__TOC__<br />
<br />
{| style="vertical-align:top;" border="1" cellpadding="2" cellspacing="0"<br />
! bgcolor="#efeeee" style="width:20%;vertical-align:top;text-align:left" | <br />
==Press News==<br />
|<br />
* [http://www.h-online.com/open/news/item/openSUSE-12-1-arrives-with-systemd-and-Btrfs-1380033.html openSUSE 12 1 arrives with systemd and Btrfs] - The H<br />
* [https://www.linux.com/learn/tutorials/510731-opensuse-121-arrives-whats-new-and-what-happened-to-120 openSUSE 12.1 arrives. What's new and what happened to 12.0?]- Linux.com <br />
* [http://www.zdnet.com/blog/open-source/opensuses-new-linux-distribution-is-for-the-clouds/9908 openSUSEs new linux distribution for the clouds] - ZDnet<br />
* [http://www.zdnet.com/blog/open-source/opensuse-121-debuts-cloud-virtualization-google-go-support/9899 openSUSE 12.1 debuts cloud, virtualization, Google Go support] - ZDnet<br />
* [http://techcrunch.com/2011/11/16/opensuse-12-1-released/ openSUSE 12.1 released] - TechCrunch<br />
* [http://www.networkworld.com/community/node/79200 OpenSUSE 12.1 bulks up on features for cloud, servers, desktops] - Network World<br />
* [http://www.linuxfordevices.com/c/a/News/OpenSUSE-121/ OpenSUSE 12.1 ships with GNOME 3.2, SystemD, Snapper, Go tools] - eWeek<br />
* [http://www.serverwatch.com/server-news/opensuse-12.1-gets-snappy-release.html OpenSUSE 12.1 Gets Snappy Release] - Serverwatch<br />
* [http://www.linuxfordevices.com/c/a/News/OpenSUSE-121/?kc=rss OpenSUSE 12.1 ships with GNOME 3.2, SystemD, Snapper, Go tools] - Linuxfordevices<br />
* [http://www.golem.de/1111/87786.html Opensuse 12.1 bereit für Experimente] - Golem<br />
* [http://www.phoronix.com/scan.php?page=article&item=opensuse_121_release&num=1 OpenSUSE 12.1 Is Set For Release Today, Here Are Benchmarks] Phoronix<br />
* [http://ostatic.com/blog/opensuse-12-1-gone-gold-release-wednesday openSUSE 12.1 Gone Gold, Release Wednesday] - Ostatic<br />
* [http://searchenterpriselinux.techtarget.com/news/2240110774/New-openSUSE-Linux-leaders-call-for-secure-boot-fix-News-in-brief New openSUSE, Linux leaders call for secure boot fix: News in brief] -SearchEnterpriseLinux<br />
* [http://www.muktware.com/bitsnbytes/2956 openSuse 12.1 Released, Comes With OwnCloud] - Muktware<br />
* [http://www.zdnet.co.uk/blogs/jamies-mostly-linux-stuff-10006480/opensuse-121-released-10024817/ OpenSUSE 12.1 released] - ZDNet UK<br />
* [http://www.theregister.co.uk/2011/11/17/opensuse_cloud_virtual/ New openSUSE heads for cloud, virtual markets] - The Register<br />
* [http://www.pcadvisor.co.uk/opinion/software/3318876/try-opensuse-linux-121-for-stability-flexibility/ Try OpenSUSE Linux 12.1 for Stability and Flexibility] - PC Advisor<br />
* [http://www.noticiaslinux.com.br/nl1321488235.html openSUSE 12.1 chega com systemd e Btrfs] - Noticias Linux Brazil<br />
|-<br />
!bgcolor="#efeeee" style="width:20%;vertical-align:top;text-align:left"| <br />
==Press Reviews==<br />
|<br />
* [http://www.h-online.com/open/features/What-s-new-in-openSUSE-12-1-1380131.html What's new in openSUSE 12.1] - The H<br />
* [http://www.linuxidentity.com/index.php?name=News&file=article&sid=102 openSUSE 12.1] Linux Identity (FR)<br />
* [http://distrowatch.com/weekly.php?issue=20111128#feature Boot up, little SUSE] DistroWatch.com<br />
|-<br />
!bgcolor="#efeeee" style="width:20%;vertical-align:top;;text-align:left"| <br />
==Blogs==<br />
|<br />
* [http://seife.kernalert.de/blog/2011/11/18/121-update-no-problems-and-systemd-rocks/ 12.1 update -no problems and systemd rocks] - Stefan Seyfried<br />
|-<br />
! bgcolor="#efeeee" style="width:20%;vertical-align:top;text-align:left"| <br />
==Screenshots==<br />
|<br />
|-<br />
! bgcolor="#efeeee" style="width:20%;vertical-align:top;;text-align:left"| <br />
==Videos==<br />
|<br />
* [http://www.youtube.com/watch?v=v3qdfAlWFxo Gnome 3.2, YaST]<br />
* [http://www.youtube.com/watch?v=aRneBJ5Uqwc Overview]<br />
* [http://www.youtube.com/watch?v=I7Lz9k1Hxp8 KDE]<br />
* [http://www.youtube.com/watch?v=U7LJZ6EXmzw The Linux Action Show] "this release spanks every distribution out there"<br />
* And many, many more...<br />
|-<br />
! bgcolor="#efeeee" style="width:20%;vertical-align:top;;text-align:left"| <br />
==Social Media==<br />
|<br />
|-<br />
! bgcolor="#efeeee" style="width:20%;vertical-align:top;;text-align:left"| <br />
==Other==<br />
|<br />
|}<br />
<br />
__NOEDITSECTION__<br />
<br style="clear: both;" /><br />
<br />
[[Category:In the press]]<br />
<br />
[[de:In_der_Presse]]<br />
[[ru:In_the_press]]</div>Kfreitaghttps://en.opensuse.org/index.php?title=SDB:OwnCloud&diff=45677SDB:OwnCloud2011-11-11T16:26:47Z<p>Kfreitag: /* Calendaring and Contact Management */</p>
<hr />
<div>{{SDB_navbar}}<br />
{{Knowledge|<br />
*[[Portal:12.1|12.1]]<br />
*[[Portal:11.4|11.4]]<br />
|<br />
|<br />
*[[SDB:One_click_install]]<br />
}}<br />
<br />
This article describes how to use [[http://owncloud.org ownCloud]] with openSUSE: Setup and configuration.<br />
<br />
== Situation ==<br />
<br />
Today computer work is not limited to a single machine any more. People<br />
have the urgent need to share their data over various computers, ie. desktop <br />
computers, laptops and such. For that a so called cloud-solution is very helpful.<br />
<br />
The freedom of software and data is very valueable to the openSUSE Project and that is why we want to push for a complete free cloud solution for users - free as in code and free as in content.<br />
<br />
ownCloud is a slim yet powerful private cloud software. It runs on your computer in your home network or on your web space with minimal requirements. First and formost it allows you to store files on it and access it from everywhere where you have access to the web. <br />
<br />
But there are more features: ownCloud provides you with a media player, calendaring and contact management and with a desktop client you can automate your file synchronisation.<br />
<br />
----<br />
<br />
== ownCloud Setup ==<br />
<br />
There are several options to easily set up and integrate ownCloud with openSUSE distributions.<br />
<br />
=== Install the ownCloud package ===<br />
<br />
The first option is to install an ownCloud rpm package. There is one available in the openSUSE Build Service in the project [https://build.opensuse.org/project/show?project=server%3Aphp%3Aapplications server:php:applicatons]. An easy [http://software.opensuse.org/ymp/server:php:applications/openSUSE_12.1/owncloud.ymp?base=openSUSE%3A12.1&query=owncloud One-Click-Install for openSUSE 12.1] is available and its use is recommended. <br />
<br />
For other distributions please use the [http://software.opensuse.org/search?q=owncloud software search page] to find a suitable package.<br />
<br />
The downside is that you need root access to install rpm packages on the machine which might not be the case for a web space.<br />
<br />
=== Install from Source ===<br />
<br />
On the homepage of the [http://www.owncloud.org ownCloud Project] there are tarballs of the latest stable version available for [http://owncloud.org/releases/owncloud-2.tar.bz2 download]. Basically they must be extracted in a directory that is accessible for the web server. Please refer to the [http://owncloud.org/install upstream install instructions] for detailed information about installation and configuration. <br />
<br />
=== Install through Mirall ===<br />
<br />
Mirall can install ownCloud either locally on the computer its running on or on a webspace that is accessible via ftp. That is what most cheap, ie. non root or virtual server hostings offer.<br />
<br />
Refer to the next chapter about details. <br />
<br />
== Mirall Desktop Client ==<br />
<br />
Mirall was started by Duncan Mac Vicar and was later extended by Klaas Freitag in a SUSE hackweeks to implement the described vision. The first and foremost target with mirall is to provide a very easy to use tool for unexperienced users. It should be fun to use and hide the complex client/server issues from its users completely.<br />
[[File:miralltray.png|frame|Mirall in the system tray]]<br />
<br />
Mirall starts in the system tray on your desktop and if you click on it, it checks if your system is already connected to an ownCloud. If not, it offers you to either connect to an existing ownCloud install a new one.<br />
<br />
=== Mirall Installation ===<br />
<br />
Mirall is available as rpm package for your openSUSE installation from the project [https://build.opensuse.org/project/show?project=network network].<br />
<br />
Please install it from there picking a suitable version for your distribution setup. AI: Add one-click-install....<br />
<br />
After installation start mirall from the start menue. A new icon will appear in your system tray. <br />
<br />
=== Connect to an ownCloud ===<br />
[[File:new_oc_connect.png|frame]]<br />
If you click on the tray icon and have no ownCloud configured yet, a dialog wizard will show up and offer you two options: <br />
# connect my ownCloud<br />
# create a new ownCloud<br />
<br />
If you pick the first option, ''connect my owncloud'' you have to enter the valid ownCloud url into the text field and hit Next. The next dialog asks you for username and password to connect to the ownCloud. After hitting on ''Next'' again, a summary page displays the result of the operation.<br />
<br />
=== ownCloud Installation ===<br />
<br />
If you choose to ''create a new ownCloud'' on the first dialog page, the next wizard page asks you if you want to create it on the local computer or on an internet domain you control. In both cases mirall downloads latest stable sources of ownCloud from the [http://owncloud.org ownCloud project page], extracts it on the local machine and copies it to the target system.<br />
<br />
If you go for the installation on the local machine, mirall will ask you for the root password to be able to copy files into the webservers application directory. <br />
<br />
If you choose to install on your ftp accessible site, enter a domain name into the text field. On the next wizard page, a FTP-Url and credentials for FTP need to be provided.<br />
<br />
Mirall uses FTP to access the webspace and creates a directory called <tt>owncloud</tt> on the ftp site and copies the files there.<br />
<br />
On the next wizard page, you need to provide credentials for the admin user of your new ownCloud instance. During installation the user is created automatically and after the installation finished you can use the credentials to log in.<br />
<br />
Finally the ownCloud is configured as your connected cloud. After a successful installation, mirall tries to create an express upload folder in your home directory named <tt>mirall</tt>. It is automatically mirrored to the cloud. This step is skipped for security reasons if the folder already exists in your home dir.<br />
<br />
=== Express Upload Directories ===<br />
<br />
Mirall can create so called Express Upload Directories for you.<br />
<br />
They basically connect a local directory with a directory <br />
on the ownCloud. Whatever changes you do in the local directory, either<br />
connected to a network or not, is going to be mirrored to the ownCloud<br />
right away or as soon as you go online again. No matter if change, add <br />
or delete files or directories, the changes go into the cloud.<br />
<br />
'''The local directory is the master'''. <br />
Always keep that in mind!<br />
<br />
What happens if changes are made to one of your Epress Upload Directories on <br />
the ownCloud? Well, the local directory is the master. That means, the changes<br />
to files on the cloud are going to be overwritten with the next syncing mirall <br />
performs. <br />
<br />
If new files are added on the ownCloud, mirall disables the Express Upload Folder for you in order to not delete files on the cloud, because, remember, local is the master, and if remote are more files than local, following the logic, they need to be deleted. However, mirall tries to avoid that and disables the folder and you have the chance to fetch from the cloud directory, ie. get the contents of the remote dir to local.<br />
<br />
{{Warning|This contains a risk: If you use the same ownCloud with more than one user or from more than one device at the same time, make sure to not loose data.}}<br />
<br />
Taking this into consideration, mirall already solves a lot of the "where are <br />
my files" problems people have when they move around a lot...<br />
<br />
=== Check the Status ===<br />
[[File:statusdialog.png|frame]]<br />
mirall opens a status dialog if you click on the tray icon and if there are express upload directories configured. The dialog gives information if the directories are in good status, ie. synced correctly, or they are disabled.<br />
<br />
If they are disabled, the button ''fetch'' lets you pull the data from the ownCloud to your local directory. With that, local files can be deleted!<br />
<br />
== Calendaring and Contact Management ==<br />
<br />
... TODO ...<br />
<br />
===External links===<br />
* [http://www.owncloud.org ownCloud Homepage]<br />
<br />
{{DEFAULTSORT:{{PAGENAME}}}}<br />
<br />
[[Category:SDB:Network]]<br />
[[Category:SDB:12.1]]<br />
<br />
<noinclude><br />
[[Category:Article templates]]<br />
</noinclude></div>Kfreitaghttps://en.opensuse.org/index.php?title=SDB:OwnCloud&diff=45676SDB:OwnCloud2011-11-11T16:26:22Z<p>Kfreitag: </p>
<hr />
<div>{{SDB_navbar}}<br />
{{Knowledge|<br />
*[[Portal:12.1|12.1]]<br />
*[[Portal:11.4|11.4]]<br />
|<br />
|<br />
*[[SDB:One_click_install]]<br />
}}<br />
<br />
This article describes how to use [[http://owncloud.org ownCloud]] with openSUSE: Setup and configuration.<br />
<br />
== Situation ==<br />
<br />
Today computer work is not limited to a single machine any more. People<br />
have the urgent need to share their data over various computers, ie. desktop <br />
computers, laptops and such. For that a so called cloud-solution is very helpful.<br />
<br />
The freedom of software and data is very valueable to the openSUSE Project and that is why we want to push for a complete free cloud solution for users - free as in code and free as in content.<br />
<br />
ownCloud is a slim yet powerful private cloud software. It runs on your computer in your home network or on your web space with minimal requirements. First and formost it allows you to store files on it and access it from everywhere where you have access to the web. <br />
<br />
But there are more features: ownCloud provides you with a media player, calendaring and contact management and with a desktop client you can automate your file synchronisation.<br />
<br />
----<br />
<br />
== ownCloud Setup ==<br />
<br />
There are several options to easily set up and integrate ownCloud with openSUSE distributions.<br />
<br />
=== Install the ownCloud package ===<br />
<br />
The first option is to install an ownCloud rpm package. There is one available in the openSUSE Build Service in the project [https://build.opensuse.org/project/show?project=server%3Aphp%3Aapplications server:php:applicatons]. An easy [http://software.opensuse.org/ymp/server:php:applications/openSUSE_12.1/owncloud.ymp?base=openSUSE%3A12.1&query=owncloud One-Click-Install for openSUSE 12.1] is available and its use is recommended. <br />
<br />
For other distributions please use the [http://software.opensuse.org/search?q=owncloud software search page] to find a suitable package.<br />
<br />
The downside is that you need root access to install rpm packages on the machine which might not be the case for a web space.<br />
<br />
=== Install from Source ===<br />
<br />
On the homepage of the [http://www.owncloud.org ownCloud Project] there are tarballs of the latest stable version available for [http://owncloud.org/releases/owncloud-2.tar.bz2 download]. Basically they must be extracted in a directory that is accessible for the web server. Please refer to the [http://owncloud.org/install upstream install instructions] for detailed information about installation and configuration. <br />
<br />
=== Install through Mirall ===<br />
<br />
Mirall can install ownCloud either locally on the computer its running on or on a webspace that is accessible via ftp. That is what most cheap, ie. non root or virtual server hostings offer.<br />
<br />
Refer to the next chapter about details. <br />
<br />
== Mirall Desktop Client ==<br />
<br />
Mirall was started by Duncan Mac Vicar and was later extended by Klaas Freitag in a SUSE hackweeks to implement the described vision. The first and foremost target with mirall is to provide a very easy to use tool for unexperienced users. It should be fun to use and hide the complex client/server issues from its users completely.<br />
[[File:miralltray.png|frame|Mirall in the system tray]]<br />
<br />
Mirall starts in the system tray on your desktop and if you click on it, it checks if your system is already connected to an ownCloud. If not, it offers you to either connect to an existing ownCloud install a new one.<br />
<br />
=== Mirall Installation ===<br />
<br />
Mirall is available as rpm package for your openSUSE installation from the project [https://build.opensuse.org/project/show?project=network network].<br />
<br />
Please install it from there picking a suitable version for your distribution setup. AI: Add one-click-install....<br />
<br />
After installation start mirall from the start menue. A new icon will appear in your system tray. <br />
<br />
=== Connect to an ownCloud ===<br />
[[File:new_oc_connect.png|frame]]<br />
If you click on the tray icon and have no ownCloud configured yet, a dialog wizard will show up and offer you two options: <br />
# connect my ownCloud<br />
# create a new ownCloud<br />
<br />
If you pick the first option, ''connect my owncloud'' you have to enter the valid ownCloud url into the text field and hit Next. The next dialog asks you for username and password to connect to the ownCloud. After hitting on ''Next'' again, a summary page displays the result of the operation.<br />
<br />
=== ownCloud Installation ===<br />
<br />
If you choose to ''create a new ownCloud'' on the first dialog page, the next wizard page asks you if you want to create it on the local computer or on an internet domain you control. In both cases mirall downloads latest stable sources of ownCloud from the [http://owncloud.org ownCloud project page], extracts it on the local machine and copies it to the target system.<br />
<br />
If you go for the installation on the local machine, mirall will ask you for the root password to be able to copy files into the webservers application directory. <br />
<br />
If you choose to install on your ftp accessible site, enter a domain name into the text field. On the next wizard page, a FTP-Url and credentials for FTP need to be provided.<br />
<br />
Mirall uses FTP to access the webspace and creates a directory called <tt>owncloud</tt> on the ftp site and copies the files there.<br />
<br />
On the next wizard page, you need to provide credentials for the admin user of your new ownCloud instance. During installation the user is created automatically and after the installation finished you can use the credentials to log in.<br />
<br />
Finally the ownCloud is configured as your connected cloud. After a successful installation, mirall tries to create an express upload folder in your home directory named <tt>mirall</tt>. It is automatically mirrored to the cloud. This step is skipped for security reasons if the folder already exists in your home dir.<br />
<br />
=== Express Upload Directories ===<br />
<br />
Mirall can create so called Express Upload Directories for you.<br />
<br />
They basically connect a local directory with a directory <br />
on the ownCloud. Whatever changes you do in the local directory, either<br />
connected to a network or not, is going to be mirrored to the ownCloud<br />
right away or as soon as you go online again. No matter if change, add <br />
or delete files or directories, the changes go into the cloud.<br />
<br />
'''The local directory is the master'''. <br />
Always keep that in mind!<br />
<br />
What happens if changes are made to one of your Epress Upload Directories on <br />
the ownCloud? Well, the local directory is the master. That means, the changes<br />
to files on the cloud are going to be overwritten with the next syncing mirall <br />
performs. <br />
<br />
If new files are added on the ownCloud, mirall disables the Express Upload Folder for you in order to not delete files on the cloud, because, remember, local is the master, and if remote are more files than local, following the logic, they need to be deleted. However, mirall tries to avoid that and disables the folder and you have the chance to fetch from the cloud directory, ie. get the contents of the remote dir to local.<br />
<br />
{{Warning|This contains a risk: If you use the same ownCloud with more than one user or from more than one device at the same time, make sure to not loose data.}}<br />
<br />
Taking this into consideration, mirall already solves a lot of the "where are <br />
my files" problems people have when they move around a lot...<br />
<br />
=== Check the Status ===<br />
[[File:statusdialog.png|frame]]<br />
mirall opens a status dialog if you click on the tray icon and if there are express upload directories configured. The dialog gives information if the directories are in good status, ie. synced correctly, or they are disabled.<br />
<br />
If they are disabled, the button ''fetch'' lets you pull the data from the ownCloud to your local directory. With that, local files can be deleted!<br />
<br />
== Calendaring and Contact Management ==<br />
<br />
===External links===<br />
* [http://www.owncloud.org ownCloud Homepage]<br />
<br />
{{DEFAULTSORT:{{PAGENAME}}}}<br />
<br />
[[Category:SDB:Network]]<br />
[[Category:SDB:12.1]]<br />
<br />
<noinclude><br />
[[Category:Article templates]]<br />
</noinclude></div>Kfreitaghttps://en.opensuse.org/index.php?title=SDB:OwnCloud&diff=45674SDB:OwnCloud2011-11-11T16:23:05Z<p>Kfreitag: /* Check the Status */</p>
<hr />
<div>{{SDB_navbar}}<br />
{{Knowledge|<br />
*[[Portal:11.4|11.4]]<br />
*[[Portal:11.3|11.3]]<br />
*[[Portal:11.2|11.2]]<br />
|<br />
*[[Info page]]<br />
*[[Info page]]<br />
*[[Info page]]<br />
|<br />
*[[Related article]]<br />
*[[Related article]]<br />
*[[Related article]]<br />
}}<br />
<br />
This article describes how to use [[http://owncloud.org ownCloud]] with openSUSE: Setup and configuration.<br />
<br />
== Situation ==<br />
<br />
Today computer work is not limited to a single machine any more. People<br />
have the urgent need to share their data over various computers, ie. desktop <br />
computers, laptops and such. For that a so called cloud-solution is very helpful.<br />
<br />
The freedom of software and data is very valueable to the openSUSE Project and that is why we want to push for a complete free cloud solution for users - free as in code and free as in content.<br />
<br />
ownCloud is a slim yet powerful private cloud software. It runs on your computer in your home network or on your web space with minimal requirements. First and formost it allows you to store files on it and access it from everywhere where you have access to the web. <br />
<br />
But there are more features: ownCloud provides you with a media player, calendaring and contact management and with a desktop client you can automate your file synchronisation.<br />
<br />
----<br />
<br />
== ownCloud Setup ==<br />
<br />
There are several options to easily set up and integrate ownCloud with openSUSE distributions.<br />
<br />
=== Install the ownCloud package ===<br />
<br />
The first option is to install an ownCloud rpm package. There is one available in the openSUSE Build Service in the project [https://build.opensuse.org/project/show?project=server%3Aphp%3Aapplications server:php:applicatons]. An easy [http://software.opensuse.org/ymp/server:php:applications/openSUSE_12.1/owncloud.ymp?base=openSUSE%3A12.1&query=owncloud One-Click-Install for openSUSE 12.1] is available and its use is recommended. <br />
<br />
For other distributions please use the [http://software.opensuse.org/search?q=owncloud software search page] to find a suitable package.<br />
<br />
The downside is that you need root access to install rpm packages on the machine which might not be the case for a web space.<br />
<br />
=== Install from Source ===<br />
<br />
On the homepage of the [http://www.owncloud.org ownCloud Project] there are tarballs of the latest stable version available for [http://owncloud.org/releases/owncloud-2.tar.bz2 download]. Basically they must be extracted in a directory that is accessible for the web server. Please refer to the [http://owncloud.org/install upstream install instructions] for detailed information about installation and configuration. <br />
<br />
=== Install through Mirall ===<br />
<br />
Mirall can install ownCloud either locally on the computer its running on or on a webspace that is accessible via ftp. That is what most cheap, ie. non root or virtual server hostings offer.<br />
<br />
Refer to the next chapter about details. <br />
<br />
== Mirall Desktop Client ==<br />
<br />
Mirall was started by Duncan Mac Vicar and was later extended by Klaas Freitag in a SUSE hackweeks to implement the described vision. The first and foremost target with mirall is to provide a very easy to use tool for unexperienced users. It should be fun to use and hide the complex client/server issues from its users completely.<br />
[[File:miralltray.png|frame|Mirall in the system tray]]<br />
<br />
Mirall starts in the system tray on your desktop and if you click on it, it checks if your system is already connected to an ownCloud. If not, it offers you to either connect to an existing ownCloud install a new one.<br />
<br />
=== Mirall Installation ===<br />
<br />
Mirall is available as rpm package for your openSUSE installation from the project [https://build.opensuse.org/project/show?project=network network].<br />
<br />
Please install it from there picking a suitable version for your distribution setup. AI: Add one-click-install....<br />
<br />
After installation start mirall from the start menue. A new icon will appear in your system tray. <br />
<br />
=== Connect to an ownCloud ===<br />
[[File:new_oc_connect.png|frame]]<br />
If you click on the tray icon and have no ownCloud configured yet, a dialog wizard will show up and offer you two options: <br />
# connect my ownCloud<br />
# create a new ownCloud<br />
<br />
If you pick the first option, ''connect my owncloud'' you have to enter the valid ownCloud url into the text field and hit Next. The next dialog asks you for username and password to connect to the ownCloud. After hitting on ''Next'' again, a summary page displays the result of the operation.<br />
<br />
=== ownCloud Installation ===<br />
<br />
If you choose to ''create a new ownCloud'' on the first dialog page, the next wizard page asks you if you want to create it on the local computer or on an internet domain you control. In both cases mirall downloads latest stable sources of ownCloud from the [http://owncloud.org ownCloud project page], extracts it on the local machine and copies it to the target system.<br />
<br />
If you go for the installation on the local machine, mirall will ask you for the root password to be able to copy files into the webservers application directory. <br />
<br />
If you choose to install on your ftp accessible site, enter a domain name into the text field. On the next wizard page, a FTP-Url and credentials for FTP need to be provided.<br />
<br />
Mirall uses FTP to access the webspace and creates a directory called <tt>owncloud</tt> on the ftp site and copies the files there.<br />
<br />
On the next wizard page, you need to provide credentials for the admin user of your new ownCloud instance. During installation the user is created automatically and after the installation finished you can use the credentials to log in.<br />
<br />
Finally the ownCloud is configured as your connected cloud. After a successful installation, mirall tries to create an express upload folder in your home directory named <tt>mirall</tt>. It is automatically mirrored to the cloud. This step is skipped for security reasons if the folder already exists in your home dir.<br />
<br />
=== Express Upload Directories ===<br />
<br />
Mirall can create so called Express Upload Directories for you.<br />
<br />
They basically connect a local directory with a directory <br />
on the ownCloud. Whatever changes you do in the local directory, either<br />
connected to a network or not, is going to be mirrored to the ownCloud<br />
right away or as soon as you go online again. No matter if change, add <br />
or delete files or directories, the changes go into the cloud.<br />
<br />
'''The local directory is the master'''. <br />
Always keep that in mind!<br />
<br />
What happens if changes are made to one of your Epress Upload Directories on <br />
the ownCloud? Well, the local directory is the master. That means, the changes<br />
to files on the cloud are going to be overwritten with the next syncing mirall <br />
performs. <br />
<br />
If new files are added on the ownCloud, mirall disables the Express Upload Folder for you in order to not delete files on the cloud, because, remember, local is the master, and if remote are more files than local, following the logic, they need to be deleted. However, mirall tries to avoid that and disables the folder and you have the chance to fetch from the cloud directory, ie. get the contents of the remote dir to local.<br />
<br />
{{Warning|This contains a risk: If you use the same ownCloud with more than one user or from more than one device at the same time, make sure to not loose data.}}<br />
<br />
Taking this into consideration, mirall already solves a lot of the "where are <br />
my files" problems people have when they move around a lot...<br />
<br />
=== Check the Status ===<br />
[[File:statusdialog.png|frame]]<br />
mirall opens a status dialog if you click on the tray icon and if there are express upload directories configured. The dialog gives information if the directories are in good status, ie. synced correctly, or they are disabled.<br />
<br />
If they are disabled, the button ''fetch'' lets you pull the data from the ownCloud to your local directory. With that, local files can be deleted!<br />
<br />
== Calendaring and Contact Management ==<br />
<br />
<br />
==See also==<br />
=== Related articles ===<br />
*[[Main Page]]<br />
*[[Main Page]]<br />
*[[Main Page]]<br />
*[[Main Page]]<br />
<br />
===External links===<br />
* [http://www.owncloud.org ownCloud Homepage]<br />
<br />
{{DEFAULTSORT:{{PAGENAME}}}}<br />
<br />
[[Category:SDB:Network]]<br />
[[Category:SDB:12.1]]<br />
<br />
<noinclude><br />
[[Category:Article templates]]<br />
</noinclude></div>Kfreitaghttps://en.opensuse.org/index.php?title=File:Statusdialog.png&diff=45673File:Statusdialog.png2011-11-11T16:20:11Z<p>Kfreitag: </p>
<hr />
<div></div>Kfreitaghttps://en.opensuse.org/index.php?title=SDB:OwnCloud&diff=45672SDB:OwnCloud2011-11-11T16:19:24Z<p>Kfreitag: /* Express Upload Directories */</p>
<hr />
<div>{{SDB_navbar}}<br />
{{Knowledge|<br />
*[[Portal:11.4|11.4]]<br />
*[[Portal:11.3|11.3]]<br />
*[[Portal:11.2|11.2]]<br />
|<br />
*[[Info page]]<br />
*[[Info page]]<br />
*[[Info page]]<br />
|<br />
*[[Related article]]<br />
*[[Related article]]<br />
*[[Related article]]<br />
}}<br />
<br />
This article describes how to use [[http://owncloud.org ownCloud]] with openSUSE: Setup and configuration.<br />
<br />
== Situation ==<br />
<br />
Today computer work is not limited to a single machine any more. People<br />
have the urgent need to share their data over various computers, ie. desktop <br />
computers, laptops and such. For that a so called cloud-solution is very helpful.<br />
<br />
The freedom of software and data is very valueable to the openSUSE Project and that is why we want to push for a complete free cloud solution for users - free as in code and free as in content.<br />
<br />
ownCloud is a slim yet powerful private cloud software. It runs on your computer in your home network or on your web space with minimal requirements. First and formost it allows you to store files on it and access it from everywhere where you have access to the web. <br />
<br />
But there are more features: ownCloud provides you with a media player, calendaring and contact management and with a desktop client you can automate your file synchronisation.<br />
<br />
----<br />
<br />
== ownCloud Setup ==<br />
<br />
There are several options to easily set up and integrate ownCloud with openSUSE distributions.<br />
<br />
=== Install the ownCloud package ===<br />
<br />
The first option is to install an ownCloud rpm package. There is one available in the openSUSE Build Service in the project [https://build.opensuse.org/project/show?project=server%3Aphp%3Aapplications server:php:applicatons]. An easy [http://software.opensuse.org/ymp/server:php:applications/openSUSE_12.1/owncloud.ymp?base=openSUSE%3A12.1&query=owncloud One-Click-Install for openSUSE 12.1] is available and its use is recommended. <br />
<br />
For other distributions please use the [http://software.opensuse.org/search?q=owncloud software search page] to find a suitable package.<br />
<br />
The downside is that you need root access to install rpm packages on the machine which might not be the case for a web space.<br />
<br />
=== Install from Source ===<br />
<br />
On the homepage of the [http://www.owncloud.org ownCloud Project] there are tarballs of the latest stable version available for [http://owncloud.org/releases/owncloud-2.tar.bz2 download]. Basically they must be extracted in a directory that is accessible for the web server. Please refer to the [http://owncloud.org/install upstream install instructions] for detailed information about installation and configuration. <br />
<br />
=== Install through Mirall ===<br />
<br />
Mirall can install ownCloud either locally on the computer its running on or on a webspace that is accessible via ftp. That is what most cheap, ie. non root or virtual server hostings offer.<br />
<br />
Refer to the next chapter about details. <br />
<br />
== Mirall Desktop Client ==<br />
<br />
Mirall was started by Duncan Mac Vicar and was later extended by Klaas Freitag in a SUSE hackweeks to implement the described vision. The first and foremost target with mirall is to provide a very easy to use tool for unexperienced users. It should be fun to use and hide the complex client/server issues from its users completely.<br />
[[File:miralltray.png|frame|Mirall in the system tray]]<br />
<br />
Mirall starts in the system tray on your desktop and if you click on it, it checks if your system is already connected to an ownCloud. If not, it offers you to either connect to an existing ownCloud install a new one.<br />
<br />
=== Mirall Installation ===<br />
<br />
Mirall is available as rpm package for your openSUSE installation from the project [https://build.opensuse.org/project/show?project=network network].<br />
<br />
Please install it from there picking a suitable version for your distribution setup. AI: Add one-click-install....<br />
<br />
After installation start mirall from the start menue. A new icon will appear in your system tray. <br />
<br />
=== Connect to an ownCloud ===<br />
[[File:new_oc_connect.png|frame]]<br />
If you click on the tray icon and have no ownCloud configured yet, a dialog wizard will show up and offer you two options: <br />
# connect my ownCloud<br />
# create a new ownCloud<br />
<br />
If you pick the first option, ''connect my owncloud'' you have to enter the valid ownCloud url into the text field and hit Next. The next dialog asks you for username and password to connect to the ownCloud. After hitting on ''Next'' again, a summary page displays the result of the operation.<br />
<br />
=== ownCloud Installation ===<br />
<br />
If you choose to ''create a new ownCloud'' on the first dialog page, the next wizard page asks you if you want to create it on the local computer or on an internet domain you control. In both cases mirall downloads latest stable sources of ownCloud from the [http://owncloud.org ownCloud project page], extracts it on the local machine and copies it to the target system.<br />
<br />
If you go for the installation on the local machine, mirall will ask you for the root password to be able to copy files into the webservers application directory. <br />
<br />
If you choose to install on your ftp accessible site, enter a domain name into the text field. On the next wizard page, a FTP-Url and credentials for FTP need to be provided.<br />
<br />
Mirall uses FTP to access the webspace and creates a directory called <tt>owncloud</tt> on the ftp site and copies the files there.<br />
<br />
On the next wizard page, you need to provide credentials for the admin user of your new ownCloud instance. During installation the user is created automatically and after the installation finished you can use the credentials to log in.<br />
<br />
Finally the ownCloud is configured as your connected cloud. After a successful installation, mirall tries to create an express upload folder in your home directory named <tt>mirall</tt>. It is automatically mirrored to the cloud. This step is skipped for security reasons if the folder already exists in your home dir.<br />
<br />
=== Express Upload Directories ===<br />
<br />
Mirall can create so called Express Upload Directories for you.<br />
<br />
They basically connect a local directory with a directory <br />
on the ownCloud. Whatever changes you do in the local directory, either<br />
connected to a network or not, is going to be mirrored to the ownCloud<br />
right away or as soon as you go online again. No matter if change, add <br />
or delete files or directories, the changes go into the cloud.<br />
<br />
'''The local directory is the master'''. <br />
Always keep that in mind!<br />
<br />
What happens if changes are made to one of your Epress Upload Directories on <br />
the ownCloud? Well, the local directory is the master. That means, the changes<br />
to files on the cloud are going to be overwritten with the next syncing mirall <br />
performs. <br />
<br />
If new files are added on the ownCloud, mirall disables the Express Upload Folder for you in order to not delete files on the cloud, because, remember, local is the master, and if remote are more files than local, following the logic, they need to be deleted. However, mirall tries to avoid that and disables the folder and you have the chance to fetch from the cloud directory, ie. get the contents of the remote dir to local.<br />
<br />
{{Warning|This contains a risk: If you use the same ownCloud with more than one user or from more than one device at the same time, make sure to not loose data.}}<br />
<br />
Taking this into consideration, mirall already solves a lot of the "where are <br />
my files" problems people have when they move around a lot...<br />
<br />
=== Check the Status ===<br />
<br />
== Calendaring and Contact Management ==<br />
<br />
<br />
==See also==<br />
=== Related articles ===<br />
*[[Main Page]]<br />
*[[Main Page]]<br />
*[[Main Page]]<br />
*[[Main Page]]<br />
<br />
===External links===<br />
* [http://www.owncloud.org ownCloud Homepage]<br />
<br />
{{DEFAULTSORT:{{PAGENAME}}}}<br />
<br />
[[Category:SDB:Network]]<br />
[[Category:SDB:12.1]]<br />
<br />
<noinclude><br />
[[Category:Article templates]]<br />
</noinclude></div>Kfreitaghttps://en.opensuse.org/index.php?title=SDB:OwnCloud&diff=45671SDB:OwnCloud2011-11-11T16:18:59Z<p>Kfreitag: /* Connect to an ownCloud */</p>
<hr />
<div>{{SDB_navbar}}<br />
{{Knowledge|<br />
*[[Portal:11.4|11.4]]<br />
*[[Portal:11.3|11.3]]<br />
*[[Portal:11.2|11.2]]<br />
|<br />
*[[Info page]]<br />
*[[Info page]]<br />
*[[Info page]]<br />
|<br />
*[[Related article]]<br />
*[[Related article]]<br />
*[[Related article]]<br />
}}<br />
<br />
This article describes how to use [[http://owncloud.org ownCloud]] with openSUSE: Setup and configuration.<br />
<br />
== Situation ==<br />
<br />
Today computer work is not limited to a single machine any more. People<br />
have the urgent need to share their data over various computers, ie. desktop <br />
computers, laptops and such. For that a so called cloud-solution is very helpful.<br />
<br />
The freedom of software and data is very valueable to the openSUSE Project and that is why we want to push for a complete free cloud solution for users - free as in code and free as in content.<br />
<br />
ownCloud is a slim yet powerful private cloud software. It runs on your computer in your home network or on your web space with minimal requirements. First and formost it allows you to store files on it and access it from everywhere where you have access to the web. <br />
<br />
But there are more features: ownCloud provides you with a media player, calendaring and contact management and with a desktop client you can automate your file synchronisation.<br />
<br />
----<br />
<br />
== ownCloud Setup ==<br />
<br />
There are several options to easily set up and integrate ownCloud with openSUSE distributions.<br />
<br />
=== Install the ownCloud package ===<br />
<br />
The first option is to install an ownCloud rpm package. There is one available in the openSUSE Build Service in the project [https://build.opensuse.org/project/show?project=server%3Aphp%3Aapplications server:php:applicatons]. An easy [http://software.opensuse.org/ymp/server:php:applications/openSUSE_12.1/owncloud.ymp?base=openSUSE%3A12.1&query=owncloud One-Click-Install for openSUSE 12.1] is available and its use is recommended. <br />
<br />
For other distributions please use the [http://software.opensuse.org/search?q=owncloud software search page] to find a suitable package.<br />
<br />
The downside is that you need root access to install rpm packages on the machine which might not be the case for a web space.<br />
<br />
=== Install from Source ===<br />
<br />
On the homepage of the [http://www.owncloud.org ownCloud Project] there are tarballs of the latest stable version available for [http://owncloud.org/releases/owncloud-2.tar.bz2 download]. Basically they must be extracted in a directory that is accessible for the web server. Please refer to the [http://owncloud.org/install upstream install instructions] for detailed information about installation and configuration. <br />
<br />
=== Install through Mirall ===<br />
<br />
Mirall can install ownCloud either locally on the computer its running on or on a webspace that is accessible via ftp. That is what most cheap, ie. non root or virtual server hostings offer.<br />
<br />
Refer to the next chapter about details. <br />
<br />
== Mirall Desktop Client ==<br />
<br />
Mirall was started by Duncan Mac Vicar and was later extended by Klaas Freitag in a SUSE hackweeks to implement the described vision. The first and foremost target with mirall is to provide a very easy to use tool for unexperienced users. It should be fun to use and hide the complex client/server issues from its users completely.<br />
[[File:miralltray.png|frame|Mirall in the system tray]]<br />
<br />
Mirall starts in the system tray on your desktop and if you click on it, it checks if your system is already connected to an ownCloud. If not, it offers you to either connect to an existing ownCloud install a new one.<br />
<br />
=== Mirall Installation ===<br />
<br />
Mirall is available as rpm package for your openSUSE installation from the project [https://build.opensuse.org/project/show?project=network network].<br />
<br />
Please install it from there picking a suitable version for your distribution setup. AI: Add one-click-install....<br />
<br />
After installation start mirall from the start menue. A new icon will appear in your system tray. <br />
<br />
=== Connect to an ownCloud ===<br />
[[File:new_oc_connect.png|frame]]<br />
If you click on the tray icon and have no ownCloud configured yet, a dialog wizard will show up and offer you two options: <br />
# connect my ownCloud<br />
# create a new ownCloud<br />
<br />
If you pick the first option, ''connect my owncloud'' you have to enter the valid ownCloud url into the text field and hit Next. The next dialog asks you for username and password to connect to the ownCloud. After hitting on ''Next'' again, a summary page displays the result of the operation.<br />
<br />
=== ownCloud Installation ===<br />
<br />
If you choose to ''create a new ownCloud'' on the first dialog page, the next wizard page asks you if you want to create it on the local computer or on an internet domain you control. In both cases mirall downloads latest stable sources of ownCloud from the [http://owncloud.org ownCloud project page], extracts it on the local machine and copies it to the target system.<br />
<br />
If you go for the installation on the local machine, mirall will ask you for the root password to be able to copy files into the webservers application directory. <br />
<br />
If you choose to install on your ftp accessible site, enter a domain name into the text field. On the next wizard page, a FTP-Url and credentials for FTP need to be provided.<br />
<br />
Mirall uses FTP to access the webspace and creates a directory called <tt>owncloud</tt> on the ftp site and copies the files there.<br />
<br />
On the next wizard page, you need to provide credentials for the admin user of your new ownCloud instance. During installation the user is created automatically and after the installation finished you can use the credentials to log in.<br />
<br />
Finally the ownCloud is configured as your connected cloud. After a successful installation, mirall tries to create an express upload folder in your home directory named <tt>mirall</tt>. It is automatically mirrored to the cloud. This step is skipped for security reasons if the folder already exists in your home dir.<br />
<br />
=== Express Upload Directories ===<br />
<br />
Mirall can create so called Express Upload Directories for you.<br />
<br />
They basically connect a local directory with a directory <br />
on the ownCloud. Whatever changes you do in the local directory, either<br />
connected to a network or not, is going to be mirrored to the ownCloud<br />
right away or as soon as you go online again. No matter if change, add <br />
or delete files or directories, the changes go into the cloud.<br />
<br />
'''The local directory is the master'''. <br />
Always keep that in mind!<br />
<br />
What happens if changes are made to one of your Epress Upload Directories on <br />
the ownCloud? Well, the local directory is the master. That means, the changes<br />
to files on the cloud are going to be overwritten with the next syncing mirall <br />
performs. <br />
<br />
If new files are added on the ownCloud, mirall disables the Express Upload Folder for you in order to not delete files on the cloud, because, remember, local is the master, and if remote are more files than local, following the logic, they need to be deleted. However, mirall tries to avoid that and disables the folder and you have the chance to fetch from the cloud directory, ie. get the contents of the remote dir to local.<br />
<br />
{{Warning|This contains a risk: If you use the same ownCloud with more than one user or from more than one device at the same time, make sure to not loose data.}}<br />
<br />
Taking this into consideration, mirall already solves a lot of the "where are <br />
my files" problems people have when they move around a lot...<br />
<br />
<br />
=== Check the Status ===<br />
<br />
== Calendaring and Contact Management ==<br />
<br />
<br />
==See also==<br />
=== Related articles ===<br />
*[[Main Page]]<br />
*[[Main Page]]<br />
*[[Main Page]]<br />
*[[Main Page]]<br />
<br />
===External links===<br />
* [http://www.owncloud.org ownCloud Homepage]<br />
<br />
{{DEFAULTSORT:{{PAGENAME}}}}<br />
<br />
[[Category:SDB:Network]]<br />
[[Category:SDB:12.1]]<br />
<br />
<noinclude><br />
[[Category:Article templates]]<br />
</noinclude></div>Kfreitaghttps://en.opensuse.org/index.php?title=File:New_oc_connect.png&diff=45670File:New oc connect.png2011-11-11T16:17:46Z<p>Kfreitag: </p>
<hr />
<div></div>Kfreitaghttps://en.opensuse.org/index.php?title=SDB:OwnCloud&diff=45669SDB:OwnCloud2011-11-11T16:16:37Z<p>Kfreitag: </p>
<hr />
<div>{{SDB_navbar}}<br />
{{Knowledge|<br />
*[[Portal:11.4|11.4]]<br />
*[[Portal:11.3|11.3]]<br />
*[[Portal:11.2|11.2]]<br />
|<br />
*[[Info page]]<br />
*[[Info page]]<br />
*[[Info page]]<br />
|<br />
*[[Related article]]<br />
*[[Related article]]<br />
*[[Related article]]<br />
}}<br />
<br />
This article describes how to use [[http://owncloud.org ownCloud]] with openSUSE: Setup and configuration.<br />
<br />
== Situation ==<br />
<br />
Today computer work is not limited to a single machine any more. People<br />
have the urgent need to share their data over various computers, ie. desktop <br />
computers, laptops and such. For that a so called cloud-solution is very helpful.<br />
<br />
The freedom of software and data is very valueable to the openSUSE Project and that is why we want to push for a complete free cloud solution for users - free as in code and free as in content.<br />
<br />
ownCloud is a slim yet powerful private cloud software. It runs on your computer in your home network or on your web space with minimal requirements. First and formost it allows you to store files on it and access it from everywhere where you have access to the web. <br />
<br />
But there are more features: ownCloud provides you with a media player, calendaring and contact management and with a desktop client you can automate your file synchronisation.<br />
<br />
----<br />
<br />
== ownCloud Setup ==<br />
<br />
There are several options to easily set up and integrate ownCloud with openSUSE distributions.<br />
<br />
=== Install the ownCloud package ===<br />
<br />
The first option is to install an ownCloud rpm package. There is one available in the openSUSE Build Service in the project [https://build.opensuse.org/project/show?project=server%3Aphp%3Aapplications server:php:applicatons]. An easy [http://software.opensuse.org/ymp/server:php:applications/openSUSE_12.1/owncloud.ymp?base=openSUSE%3A12.1&query=owncloud One-Click-Install for openSUSE 12.1] is available and its use is recommended. <br />
<br />
For other distributions please use the [http://software.opensuse.org/search?q=owncloud software search page] to find a suitable package.<br />
<br />
The downside is that you need root access to install rpm packages on the machine which might not be the case for a web space.<br />
<br />
=== Install from Source ===<br />
<br />
On the homepage of the [http://www.owncloud.org ownCloud Project] there are tarballs of the latest stable version available for [http://owncloud.org/releases/owncloud-2.tar.bz2 download]. Basically they must be extracted in a directory that is accessible for the web server. Please refer to the [http://owncloud.org/install upstream install instructions] for detailed information about installation and configuration. <br />
<br />
=== Install through Mirall ===<br />
<br />
Mirall can install ownCloud either locally on the computer its running on or on a webspace that is accessible via ftp. That is what most cheap, ie. non root or virtual server hostings offer.<br />
<br />
Refer to the next chapter about details. <br />
<br />
== Mirall Desktop Client ==<br />
<br />
Mirall was started by Duncan Mac Vicar and was later extended by Klaas Freitag in a SUSE hackweeks to implement the described vision. The first and foremost target with mirall is to provide a very easy to use tool for unexperienced users. It should be fun to use and hide the complex client/server issues from its users completely.<br />
[[File:miralltray.png|frame|Mirall in the system tray]]<br />
<br />
Mirall starts in the system tray on your desktop and if you click on it, it checks if your system is already connected to an ownCloud. If not, it offers you to either connect to an existing ownCloud install a new one.<br />
<br />
=== Mirall Installation ===<br />
<br />
Mirall is available as rpm package for your openSUSE installation from the project [https://build.opensuse.org/project/show?project=network network].<br />
<br />
Please install it from there picking a suitable version for your distribution setup. AI: Add one-click-install....<br />
<br />
After installation start mirall from the start menue. A new icon will appear in your system tray. <br />
<br />
=== Connect to an ownCloud ===<br />
<br />
If you click on the tray icon and have no ownCloud configured yet, a dialog wizard will show up and offer you two options: <br />
# connect my ownCloud<br />
# create a new ownCloud<br />
<br />
If you pick the first option, ''connect my owncloud'' you have to enter the valid ownCloud url into the text field and hit Next. The next dialog asks you for username and password to connect to the ownCloud. After hitting on ''Next'' again, a summary page displays the result of the operation.<br />
<br />
=== ownCloud Installation ===<br />
<br />
If you choose to ''create a new ownCloud'' on the first dialog page, the next wizard page asks you if you want to create it on the local computer or on an internet domain you control. In both cases mirall downloads latest stable sources of ownCloud from the [http://owncloud.org ownCloud project page], extracts it on the local machine and copies it to the target system.<br />
<br />
If you go for the installation on the local machine, mirall will ask you for the root password to be able to copy files into the webservers application directory. <br />
<br />
If you choose to install on your ftp accessible site, enter a domain name into the text field. On the next wizard page, a FTP-Url and credentials for FTP need to be provided.<br />
<br />
Mirall uses FTP to access the webspace and creates a directory called <tt>owncloud</tt> on the ftp site and copies the files there.<br />
<br />
On the next wizard page, you need to provide credentials for the admin user of your new ownCloud instance. During installation the user is created automatically and after the installation finished you can use the credentials to log in.<br />
<br />
Finally the ownCloud is configured as your connected cloud. After a successful installation, mirall tries to create an express upload folder in your home directory named <tt>mirall</tt>. It is automatically mirrored to the cloud. This step is skipped for security reasons if the folder already exists in your home dir.<br />
<br />
=== Express Upload Directories ===<br />
<br />
Mirall can create so called Express Upload Directories for you.<br />
<br />
They basically connect a local directory with a directory <br />
on the ownCloud. Whatever changes you do in the local directory, either<br />
connected to a network or not, is going to be mirrored to the ownCloud<br />
right away or as soon as you go online again. No matter if change, add <br />
or delete files or directories, the changes go into the cloud.<br />
<br />
'''The local directory is the master'''. <br />
Always keep that in mind!<br />
<br />
What happens if changes are made to one of your Epress Upload Directories on <br />
the ownCloud? Well, the local directory is the master. That means, the changes<br />
to files on the cloud are going to be overwritten with the next syncing mirall <br />
performs. <br />
<br />
If new files are added on the ownCloud, mirall disables the Express Upload Folder for you in order to not delete files on the cloud, because, remember, local is the master, and if remote are more files than local, following the logic, they need to be deleted. However, mirall tries to avoid that and disables the folder and you have the chance to fetch from the cloud directory, ie. get the contents of the remote dir to local.<br />
<br />
{{Warning|This contains a risk: If you use the same ownCloud with more than one user or from more than one device at the same time, make sure to not loose data.}}<br />
<br />
Taking this into consideration, mirall already solves a lot of the "where are <br />
my files" problems people have when they move around a lot...<br />
<br />
<br />
=== Check the Status ===<br />
<br />
== Calendaring and Contact Management ==<br />
<br />
<br />
==See also==<br />
=== Related articles ===<br />
*[[Main Page]]<br />
*[[Main Page]]<br />
*[[Main Page]]<br />
*[[Main Page]]<br />
<br />
===External links===<br />
* [http://www.owncloud.org ownCloud Homepage]<br />
<br />
{{DEFAULTSORT:{{PAGENAME}}}}<br />
<br />
[[Category:SDB:Network]]<br />
[[Category:SDB:12.1]]<br />
<br />
<noinclude><br />
[[Category:Article templates]]<br />
</noinclude></div>Kfreitaghttps://en.opensuse.org/index.php?title=File:Miralltray.png&diff=45668File:Miralltray.png2011-11-11T16:11:32Z<p>Kfreitag: </p>
<hr />
<div></div>Kfreitaghttps://en.opensuse.org/index.php?title=SDB:OwnCloud&diff=45662SDB:OwnCloud2011-11-11T15:27:21Z<p>Kfreitag: ownCloud and Mirall on openSUSE</p>
<hr />
<div>{{SDB_navbar}}<br />
{{Knowledge|<br />
*[[Portal:11.4|11.4]]<br />
*[[Portal:11.3|11.3]]<br />
*[[Portal:11.2|11.2]]<br />
|<br />
*[[Info page]]<br />
*[[Info page]]<br />
*[[Info page]]<br />
|<br />
*[[Related article]]<br />
*[[Related article]]<br />
*[[Related article]]<br />
}}<br />
<br />
This article describes how to use [[http://owncloud.org ownCloud]] with openSUSE: Setup and configuration.<br />
<br />
== Situation ==<br />
<br />
Today computer work is not limited to a single machine any more. People<br />
have the urgent need to share their data over various computers, ie. desktop <br />
computers, laptops and such. For that a so called cloud-solution is very helpful.<br />
<br />
The freedom of software and data is very valueable to the openSUSE Project and that is why we want to push for a complete free cloud solution for users - free as in code and free as in content.<br />
<br />
ownCloud is a slim yet powerful private cloud software. It runs on your computer in your home network or on your web space with minimal requirements. First and formost it allows you to store files on it and access it from everywhere where you have access to the web. <br />
<br />
But there are more features: ownCloud provides you with a media player, calendaring and contact management and with a desktop client you can automate your file synchronisation.<br />
<br />
----<br />
<br />
== ownCloud Setup ==<br />
<br />
There are several options to easily set up and integrate ownCloud with openSUSE distributions.<br />
<br />
=== Install the ownCloud package ===<br />
<br />
The first option is to install an ownCloud rpm package. There is one available in the openSUSE Build Service in the project [https://build.opensuse.org/project/show?project=server%3Aphp%3Aapplications server:php:applicatons]. An easy [http://software.opensuse.org/ymp/server:php:applications/openSUSE_12.1/owncloud.ymp?base=openSUSE%3A12.1&query=owncloud One-Click-Install for openSUSE 12.1] is available and its use is recommended. <br />
<br />
For other distributions please use the [http://software.opensuse.org/search?q=owncloud software search page] to find a suitable package.<br />
<br />
The downside is that you need root access to install rpm packages on the machine which might not be the case for a web space.<br />
<br />
=== Install from Source ===<br />
<br />
On the homepage of the [http://www.owncloud.org ownCloud Project] there are tarballs of the latest stable version available for [http://owncloud.org/releases/owncloud-2.tar.bz2 download]. Basically they must be extracted in a directory that is accessible for the web server. Please refer to the [http://owncloud.org/install upstream install instructions] for detailed information about installation and configuration. <br />
<br />
=== Install through Mirall ===<br />
<br />
Mirall can install ownCloud either locally on the computer its running on or on a webspace that is accessible via ftp. That is what most cheap, ie. non root or virtual server hostings offer.<br />
<br />
Refer to the next chapter about details. <br />
<br />
== Mirall Desktop Client ==<br />
<br />
Mirall was started by Duncan Mac Vicar and was later extended by Klaas Freitag in a SUSE hackweeks to implement the described vision. The first and foremost target with mirall is to provide a very easy to use tool for unexperienced users. It should be fun to use and hide the complex client/server issues from its users completely.<br />
<br />
Mirall starts in the system tray on your desktop and if you click on it, it checks if your system is already connected to an ownCloud. If not, it offers you to either connect to an existing ownCloud install a new one.<br />
<br />
=== Mirall Installation ===<br />
<br />
Mirall is available as rpm package for your openSUSE installation from the project [https://build.opensuse.org/project/show?project=network network].<br />
<br />
Please install it from there picking a suitable version for your distribution setup. AI: Add one-click-install....<br />
<br />
After installation start mirall from the start menue. A new icon will appear in your system tray. <br />
<br />
=== Connect to an ownCloud ===<br />
<br />
If you click on the tray icon and have no ownCloud configured yet, a dialog wizard will show up and offer you two options: <br />
# connect my ownCloud<br />
# create a new ownCloud<br />
<br />
If you pick the first option, ''connect my owncloud'' you have to enter the valid ownCloud url into the text field and hit Next. The next dialog asks you for username and password to connect to the ownCloud. After hitting on ''Next'' again, a summary page displays the result of the operation.<br />
<br />
=== ownCloud Installation ===<br />
<br />
If you choose to ''create a new ownCloud'' on the first dialog page, the next wizard page asks you if you want to create it on the local computer or on an internet domain you control. In both cases mirall downloads latest stable sources of ownCloud from the [http://owncloud.org ownCloud project page], extracts it on the local machine and copies it to the target system.<br />
<br />
If you go for the installation on the local machine, mirall will ask you for the root password to be able to copy files into the webservers application directory. <br />
<br />
If you choose to install on your ftp accessible site, enter a domain name into the text field. On the next wizard page, a FTP-Url and credentials for FTP need to be provided.<br />
<br />
Mirall uses FTP to access the webspace and creates a directory called <tt>owncloud</tt> on the ftp site and copies the files there.<br />
<br />
On the next wizard page, you need to provide credentials for the admin user of your new ownCloud instance. During installation the user is created automatically and after the installation finished you can use the credentials to log in.<br />
<br />
Finally the ownCloud is configured as your connected cloud. After a successful installation, mirall tries to create an express upload folder in your home directory named <tt>mirall</tt>. It is automatically mirrored to the cloud. This step is skipped for security reasons if the folder already exists in your home dir.<br />
<br />
=== Express Upload Directories ===<br />
<br />
Mirall can create so called Express Upload Directories for you.<br />
<br />
They basically connect a local directory with a directory <br />
on the ownCloud. Whatever changes you do in the local directory, either<br />
connected to a network or not, is going to be mirrored to the ownCloud<br />
right away or as soon as you go online again. No matter if change, add <br />
or delete files or directories, the changes go into the cloud.<br />
<br />
'''The local directory is the master'''. <br />
Always keep that in mind!<br />
<br />
What happens if changes are made to one of your Epress Upload Directories on <br />
the ownCloud? Well, the local directory is the master. That means, the changes<br />
to files on the cloud are going to be overwritten with the next syncing mirall <br />
performs. <br />
<br />
If new files are added on the ownCloud, mirall disables the Express Upload Folder for you in order to not delete files on the cloud, because, remember, local is the master, and if remote are more files than local, following the logic, they need to be deleted. However, mirall tries to avoid that and disables the folder and you have the chance to fetch from the cloud directory, ie. get the contents of the remote dir to local.<br />
<br />
{{Warning|This contains a risk: If you use the same ownCloud with more than one user or from more than one device at the same time, make sure to not loose data.}}<br />
<br />
Taking this into consideration, mirall already solves a lot of the "where are <br />
my files" problems people have when they move around a lot...<br />
<br />
<br />
=== Check the Status ===<br />
<br />
== Calendaring and Contact Management ==<br />
<br />
<br />
==See also==<br />
=== Related articles ===<br />
*[[Main Page]]<br />
*[[Main Page]]<br />
*[[Main Page]]<br />
*[[Main Page]]<br />
<br />
===External links===<br />
* [http://www.owncloud.org ownCloud Homepage]<br />
<br />
{{DEFAULTSORT:{{PAGENAME}}}}<br />
<br />
[[Category:SDB:Network]]<br />
[[Category:SDB:12.1]]<br />
<br />
<noinclude><br />
[[Category:Article templates]]<br />
</noinclude></div>Kfreitaghttps://en.opensuse.org/index.php?title=Archive:Product_highlights_12.1&diff=45610Archive:Product highlights 12.12011-11-11T10:09:41Z<p>Kfreitag: /* Virtualization, Cloud and web applications */</p>
<hr />
<div>{{Current_distribution_navbar|12.1}}<br />
<br />
{{info|the product highlights are not ready yet! help is appreciated with adding screenshots and fixing mistakes. Please edit sections to make sure you do not clash with others who might also be editing. See [[Archive:Product_highlights_11.4|the 11.4 highlights for how this should look like]]}}<br />
<div style="text-align:justify;float:left;"><br />
==openSUSE 12.1 – the Latest Free Software in a Stable and Easy Manner==<br />
Dear users, contributors, fans and friends. We are proud to present to you the latest openSUSE release! It is the result of 8 months of hard work by the openSUSE community and allows you to enjoy the latest that Free Software has to offer, with the unique openSUSE touch — stable, friendly, fun.<br />
<br />
{{Portal:12.1/Features}}<br />
<br />
==More details on openSUSE 12.1==<br />
The following pages go into more detail on what is new in this openSUSE release.<br />
<br />
===Under the hood===<br />
Although the most obvious improvements to openSUSE 12.1 may be on the surface, we have made a slew of improvements under the hood as well to improve booting, hardware management, and system configuration. The boot procedure of openSUSE is now handled by systemd (with sysvinit still available as backup); the new Snapper tool automatically tracks system configuration and other file changes (and lets you roll them back); YaST received a variety of improvements crushing the demons of setups past; SAX makes its return in the form of SAX3, an openSUSE GSOC project; and of course we are supporting the freshest versions of every core system component, such as the Linux 3.1 Kernel, syslog-ng 3.3, GCC 4.6 and LLVM v3. Also notable is the fact that openSUSE is the first major Linux distribution to ship [http://golang.org Google's new Go programming language].<br />
<br />
====openSUSE Technology improvements====<br />
openSUSE, as a Linux Distribution, does more than package third party software. We have our own tools to configure your system, manage software and more.<br />
<br />
=====Snapper=====<br />
[[Image:openSUSE_12.1_Snapper.png|thumb|250px||Snapper YaST GUI in action]]<br />
openSUSE 12.1 is the first Linux distribution taking advantage of the snapshot functionality in the upcoming Linux filesystem, btrfs. These snapshots of the file system are using copy-on-write, making them very space efficient. openSUSE 12.1 debuts [[Portal:Snapper|Snapper]], which allows the user to interface with this technology.<br />
<br />
The command line and GUI Snapper tools allow users to view older versions of files and revert changes. The unique integration in the zypper package manager of openSUSE allows users to roll back entire upgrades or software installations with the accompanying configuration changes.<br />
<br />
Note that Snapper and the rollback functionality currently is only available for the btrfs filesystem! Work is going on to enable it for the older ext4 filesystem as well, but this will not be possible before the next openSUSE release.<br />
<br />
You can read [http://lizards.opensuse.org/2011/04/01/introducing-snapper/ an introduction to snapper here].<br />
<br />
<videoflash type="youtube">9H7e6BcI5Fo</videoflash><br />
<br />
[http://www.youtube.com/susevideo#p/a/u/0/9H7e6BcI5Fo Greg K-H demoing Snapper at Brainshare].<br />
<br />
=====SAX3=====<br />
When Xorg evolved beyond <tt>xorg.conf</tt>, to the new <tt>xorg.conf.d</tt> structure, our beloved X configuration tool, SAX2, went away as well. Thanks to the efforts of Manu Gupta [http://news.opensuse.org/2011/07/05/people-of-opensuse-manu-gupta/ during Google's Summer of Code], openSUSE again has an elegant GUI for customizing your X configuration: SAX3. Now, openSUSE users may once again easily tweak their keyboard, mouse, monitor, and touchpad settings in one convenient interface. Do not worry if you are having trouble with your X configuration: as is usual for YaST modules, SAX3 solves that chicken-and-egg problem by including an ncurses text interface as well as GTK and QT graphical interfaces. Please note that sax3 on the oss repo does not work properly for 12.1, but an update is already available at [https://build.opensuse.org/project/show?project=X11%3Asax X11:sax repo].<br />
<br />
=====YaST=====<br />
Aside from the new Snapper support, and the return of SAX3, openSUSE's YaST2 received a number of bugfixes and small improvements. The YaST maintainers are happy to report that after the last few fixes they are now confident that YaST will not accidentally overwrite user modified configuration files like it used to in "the early days". And together with the zypp package management performance improvements in the openSUSE 11 series, the myth that YaST is slow and overwrites files can be finally put to rest now. A more visible change is the new style, which is possible thanks to the new [http://lizards.opensuse.org/2011/10/24/new-style-for-yast2/ CSS based themes available for YaST]. WebYaST continues to evolve as well, including more modules than ever to aid in web-based administration of your openSUSE machines.<br />
<br />
=====OBS, openQA and other tools=====<br />
openSUSE has developed a number of powerful tools which we use to build our distribution and which are also available for others to build packages or test software with. These tools include the cross-platform [http://openbuildservice.org Open Build Service], the omnipotent [http://openqa.opensuse.org openQA], the flexible [[Portal:KIWI|KIWI]] and much more. Each of those has seen releases with improvements in the last 8 months. This includes the [http://news.opensuse.org/2011/10/11/opensuse-announces-first-public-release-of-openqa/ first release of openQA] and the [http://news.opensuse.org/2010/10/19/the-opensuse-build-service-2-1-released/2.1 release of the Open Build Service] which has [https://build.opensuse.org/project/show?project=openSUSE%3ATools packages available for openSUSE 12.1].<br />
<br />
====Linux kernel 3.1====<br />
The new Linux 3.1 kernel is a substantial improvement over the 2.6.38 kernel which was part of openSUSE 11.4. Not only have filesystems like ext4 and btrfs been improved, the Linux 3.1 kernel specifically brings a number of performance improvements to memory management and data handling. Of course, there is the usual slab of new hardware support including external devices like Microsoft's Kinect, Apple iSight webcam and the Nintendo Wii controller, as well as internal hardware like the new AMD Llano Fusion APUs and Intel's Ivy Bridge and Cedar Trail CPUs, a variety of wireless and graphics cards and much more. Find more details about what is new in the openSUSE kernel on the [http://kernelnewbies.org/Linux_2_6_39 Linux 2.6.39], [http://kernelnewbies.org/Linux_3.0 Linux 3.0] and [http://kernelnewbies.org/Linux_3.1 Linux 3.1] KernelNewbies pages.<br />
<br />
====systemd and other system-wide changes====<br />
System boot is now handled by the new '''systemd''' init tool, controlling and speeding up the boot process. Developed in close cooperation with fellow Linux distribution Fedora, systemd is especially interesting for system administrators due to its powerful socket- and bus-activated service system, which improves parallelization and resource usage. It also works closely with Linux's cgroups, providing better security and control over the processes.<br />
<br />
If for some reason, systemd does not work for you, you can still '''use the old sysV-init''' by pressing F5 in the bootloader. If you want to permanently use the old init, just do `<tt>zypper rm systemd-sysvinit</tt>`.<br />
We also again provide '''grub2''' as an optional bootloader. While we are still not satisfied with GRUB2 as a replacement for the current GRUB, we encourage users to try it out, and want to make sure it is available for developers.<br />
<br />
A number of smaller changes includes:<br />
*the '''util-linux''' tool version 2.20 introduces the first major changes to the dmesg logging tool in 18 years, bringing a number of options to bring human readable prefixes and timestamps to the output or clean it up, only showing important messages or messages coming from either kernel or userspace.<br />
*'''LightDM 1.0''' is the first stable release of this faster, extensible Display Manager. LightDM aims to replace the myriad of different DMs with a single [http://xkcd.com/927/ new standard].<br />
*the '''syslog-ng 3.3''' release adds multithreading, JSON and mongodb output to this system logging tool.<br />
*The [http://www.rpm.org/wiki/Releases/4.9.0 rpm 4.9] release brings a number of stability and performance improvements to this package manager.<br />
<br />
==== First to ship Google Go, LLVM v3 and CLANG v3 ====<br />
openSUSE is proud to be the first major distribution to ship [http://golang.org/ '''Google's new Go programming language'''] as part of our release. Go is a fast, statically typed, compiled language that feels like a dynamically typed, interpreted language. Go makes it easy to work with multi-core and networked machines and offers flexible and modular program construction mechanisms. While it compiles (quickly) to machine code, it has the convenience of garbage collection and the power of run-time reflection. Learn more on the [http://golang.org/ Go language website].<br />
<br />
openSUSE 12.1 also comes with the just-released [http://llvm.org/ '''LLVM3 compiler tool'''] and [http://clang.llvm.org/ clang], the C/C++ compiler building upon LLVM. LLVM, a set of flexible and performant compiler tools, offers powerful code generation which is used by Mesa for its software based OpenGL "Gallium" graphics driver architecture. It is also employed by the open source ATI and NVIDIA accelerated graphics drivers and thus forms an integral part of a high-performance graphics stack on Linux.<br />
<br />
[http://clang.llvm.org/ '''Clang'''] takes advantage of LLVM to provide an fast and memory-efficient GCC-compatible C/C++ code compiler. Clang in openSUSE 12.1 comes with enabled ARM code generation support, in the spirit of the recently started [http://opensuse.org/opensuse:ARMopenSUSE ARMs project]!<br />
Aside from Go and LLVM, openSUSE offers a large number of the latest compilers and tools. openSUSE 12.1 is built with [http://gcc.gnu.org '''GCC 4.6.2'''], which has [http://www.phoronix.com/scan.php?page=article&item=amd_fx4100_gcc&num=1 shown to offer significant performance improvements] over the previous 4.5 version. This release also introduces initial support for the Ada 2012 programming language, as well as experimental support for the latest C++11 standard (status can be found [http://gcc.gnu.org/gcc-4.6/cxx0x_status.html here]).<br />
<br />
This release of GCC, combined with the latest '''binutils 2.21.1''', has allowed us to enable [http://en.wikipedia.org/wiki/Link-time_optimization '''link-time optimization'''] in a number of packages, bringing an additional performance improvement.<br />
<br />
=== Localization ===<br />
{{Point here|[[Image:Icon-localize.png|64px|link=|Features]]|<br />
openSUSE 12.1 has been [http://i18n.opensuse.org translated into many languages] — currently about 30 are over 90% complete and no less than 66 languages are in the process of being finished. This openSUSE release has added five Cyrillic fonts. Two of them (PT Sans and PT Serif), beside standard Western, Central European and Cyrillic code pages, contain characters of all title languages of Russian Federation that make them unique and a very important tool of modern digital communications.}}<br />
<br />
===Repository changes and third party support for openSUSE 12.1===<br />
Via the [http://build.opensuse.org Open Build Service installation on build.opensuse.org], openSUSE hosts over 160,000 packages created by more than 30,000 individual contributors. These are available to openSUSE users as well as users from other Linux Distributions. But outside of this infrastructure, other projects like VLC and Packman offer their own OBS instance with packages for openSUSE! We highlight a few important projects from build.opensuse.org and third parties.<br />
<br />
====Tumbleweed====<br />
'''Tumbleweed''', the unique [[openSUSE:Tumbleweed|rolling release repository for openSUSE]], can be considered "complete" at the time of this release. Covering almost all of the openSUSE 12.1 packages, Tumbleweed offers newer versions as soon as they are deemed stable. Instead of making you wait for a new release of openSUSE, Tumbleweed lessens the significance and change impact of major releases by updating systems continuously. By enabling Tumbleweed, you are always up to date with the '''latest software'''. And you will not have to install newer versions of openSUSE as you will be running them already by the time they get released!<br />
<br />
Tumbleweed will require its current users to make one manual change to the repositories upon the 12.1 release. Besides the Tumbleweed repository, users are required to have the latest stable openSUSE repositories enabled, currently for most users set at openSUSE 11.4. With the 12.1 release, these will thus have to change. The openSUSE sysadmins have ensured however that this will be the first and last time this has to be changed. From now on, there will be a link to the latest stable release, for the convenience of Tumbleweed users. Upon a new release, the openSUSE servers will automatically handle the required changes, transparent to the users. For instructions to make these changes, [[openSUSE:Tumbleweed_12.1change|please see here]].<br />
<br />
Find more information [[Tumbleweed|about Tumbleweed here]].<br />
<br />
====Packman====<br />
{{Text and image|<br />
|text=[http://packman.links2linux.de/ Packman] repositories for openSUSE already offer openSUSE 12.1 support. '''Packman''' provides four different repositories each offering a targeted selection of software, in addition to the larger common repository. Additional to packages for openSUSE 11.3, 11.4, 12.1, Factory and SLE 11, an essential set of Packman packages is provided for Tumbleweed. Find more information on the [http://packman.links2linux.de/ Packman website] and [[Additional_package_repositories#Packman| find out how to get software from Packman on the openSUSE wiki]].|<br />
|image=Packman.png|<br />
|link=http://packman.links2linux.de |<br />
}}<br />
<br />
====SUSE Studio====<br />
{{Text and image|<br />
|text='''SUSE Studio''' is a project from openSUSE sponsor SUSE™ which builds upon the Free and Open Source openSUSE tools like '''KIWI''' and offers a convenient web interface for easy building of openSUSE and SLE based custom operating systems (appliances).<br />
<br />
[http://susestudio.com SUSE Studio] users can expect availability of openSUSE 12.1 right from the release date, and support for upgrading existing appliances shortly after. This means it will be possible to easily create your own versions of openSUSE 12.1 with '''custom package selections''', '''artwork''', '''scripts''' and any other properties and download them as USB or disk images, Live CDs and a variety of popular virtual formats. You can share your appliance or also browse other’s shared appliances on [http://susestudio.com/browse SUSE Gallery].|<br />
|image=SUSE_Studio_Cloning.png|<br />
|link= |<br />
}}<br />
<br />
====Contrib retired====<br />
The [[openSUSE:Contrib|Contrib]] repository for third-party packages was once a community-driven extension of the main repository. The vast majority of these packages have since been integrated in the main repository or in one of the central additional repositories like the official [[KDE_repositories|KDE]] and [[GNOME_repositories|GNOME]] repositories. These provide newer versions of the software in the main repositories, as well as new or experimental software not yet available in openSUSE 12.1.<br />
<br />
====Packages on the Open Build Service====<br />
If you can not find an application in openSUSE 12.1, you can use the search functionality on [http://software.opensuse.org software.opensuse.org]. If you enable searching in users home projects (under advanced), you can choose from the 160,000 packages provided by our 30,000 packagers using the [http://build.opensuse.org Open Build Service instance on build.opensuse.org].<br />
<br />
====VLC====<br />
The VideoLAN organization continues their robust support for openSUSE, with a 1-click install of the VLC universal media player already available for openSUSE 12.1 at [http://www.videolan.org/vlc/download-suse.html this page].<br />
<br />
=== Latest Free Desktops ===<br />
openSUSE offers both major Free Software desktops as well as a number of community-supported desktops, all with a high level of polish and support. openSUSE 12.1 is the first release to introduce the new '''GNOME Shell''' user interface, part of GNOME 3.2. GNOME Shell brings a vastly refined user experience with a smooth, natural workflow. The default openSUSE desktop, the '''KDE Plasma Desktop''', brings color management and much improved performance as well as the new "Akonadi"-based Kontact2 groupware solution. Current releases of both XFCE and LXDE include minor improvements on the road to their next big releases.<br />
For the first time, the openSUSE community openly selected artwork for openSUSE 12.1; the preferred "upwind" theme reflects in our new splash, boot and background images. GNOME users will notice that the art team has maintained the trend of providing a time-sensitive set of themed wallpapers.<br />
<br />
==== KDE Plasma Workspaces and applications 4.7 ====<br />
{{Text and image|<br />
|text=openSUSE 12.1 ships the [http://kde.org/workspaces KDE Plasma Workspaces] 4.7 and is the first major Linux distribution to ship the new [http://www.oyranos.org/2011/11/colour-management-in-opensuse-12-1/ KolorManager + Oyranos Color Management Service]. Oyranos and its associated tools add [http://en.wikipedia.org/wiki/Color_management color management] to KDE applications, making sure graphics and video look uniform between input and output devices like screens. Another major new addition is Apper, an easy to use software management tool replacing KPackageKit. There are also improvements to network management, the Nepomuk Semantic Desktop tool and Activities. In total, this release fixed over 12,000 bugs and contains hundreds of smaller and larger performance improvements. |<br />
|image=OpenSUSE114Ksysguard.png |<br />
|link= |<br />
}}<br />
{{Text and image|<br />
|text=The innovative new Tablet project from the KDE community, Plasma Active, is not an integral part of the openSUSE 12.1 release, as it depends on functionality not available in the released KDE Platform yet and conflicts with the Desktop and Netbook workspaces. However, tablet users can install Plasma Active in openSUSE 12.1 and we work on integrating it in the next openSUSE release.<br />
Read on for a more extensive view on what is new in the Desktop, Netbook and application area as well as to learn more about Plasma Active One! |<br />
|image=OpenSUSE114KWin.png |<br />
|link= |<br />
}}<br />
=====Plasma Workspaces bring improved visuals with Oyranos CMS=====<br />
openSUSE is the '''first major Linux distribution to ship [http://www.oyranos.org/about/ Oyranos CMS]''' integrated in the KDE applications and workspaces. Oyranos is is an operating system level [http://en.wikipedia.org/wiki/Color_management Color Management System], matching input device colors to output device colors across supported applications. Oyranos makes use of the ICC color management standard and is integrated in the KDE Workspaces and applications through the new KolorManager application. The KolorManager application makes sure graphics and video look uniform between input and output devices like screens.<br />
<br />
Users can now configure their ICC profiles and settings in one central place. It brings as well a set of command line tools like <tt>oyranos-policy</tt> for handling policy configuration files and <tt>oyranos-profiles</tt> for installation of ICC profiles. KDE users can install the <tt>KolorManager</tt> package. This Oyranos front-end adds a system settings control panel for individual settings adaption. Most systems will run fine with the Oyranos defaults. [http://www.oyranos.org/2011/11/colour-management-in-opensuse-12-1/ read more about color management in openSUSE 12.1 on the oyranos website]<br />
<br />
'''Visual improvements'''<br />
On the visual side, KDE's Plasma workspaces provides '''better integration with GTK/GNOME applications''' with a port of KDE's Oxygen style to GTK. The Oxygen icons have been improved and the Plasma panel offers a more consistent look with changes to the icons and the clock. The new Shadow support in window manager '''KWin''' gives a better look on older hardware and performs better all around. KWin also can now disable compositing when a full-screen application calls for it, increasing performance for OpenGL games and GPU accelerated video playback.<br />
<br />
Plasma's Activities have seen many improvements. The '''Activity Manager''' now takes a more prominent place in the default panel in Plasma Desktop. Activities enhance the user's workflows by providing smart ways of grouping applications, widgets and documents.<br />
<br />
Navigating through applications and recent files is easier with the '''addition of breadcrumbs''' to the Kickoff application launcher, helping users to see where they are and quickly back up to higher menu levels. Many other usability and functionality improvements have been made to the Workspaces. For example, '''Konsole''' no longer blocks the removal of USB storage devices and '''KMix''' has improved PulseAudio support. <br />
<br />
'''Network management, multimedia and Nepomuk'''<br />
The Plasma Workspaces now also offer '''much improved network management''', including support for NetworkManager 0.9 as well as Bluetooth tethering, 3G, VPN, MAC spoofing and other advanced networking options.<br />
<br />
Thanks to [http://dot.kde.org/2011/09/21/nepomuk-stability-and-performance generous donations from the community], the Semantic Desktop technology '''Nepomuk has seen extensive bugfixing''', improving stability and performance as well as making it easier to use. Strigi analyzers now read meta-data in their own process, resolving over 35 crash-related bugs in Dolphin and Konqueror.<br />
<br />
The latest version of '''Phonon''', our media framework, has seen work on the backends. The VLC-based back-end is now considered stable and is the preferred back-end for multiplatform use, while the back-end based on GStreamer is now also considered stable on Linux platforms. The xine back-end is no longer maintained.<br />
<br />
=====KDE Applications suite 4.7 features many refinements=====<br />
The latest version of KPackageKit — now renamed '''Apper''' — (developed by [http://dantti.wordpress.com Daniel Nicoletti]) is now included with Plasma Desktop. This brings significant improvements to the KDE's PackageKit front-end and makes it possible to list Applications instead of listing only Packages. This makes openSUSE a lot more user-friendly and closer to be "grandma-compatible".<br />
<br />
'''Dolphin''', KDE’s file manager, has a cleaner default appearance. The menu bar is hidden, but easy to reach and restore. The file searching interface has been improved. In addition, Dolphin now has much deeper integration with source code management systems, including the ability to create and clone repositories, push and pull changes, view diffs and much more.<br />
<br />
Dolphin and Konqueror both benefit from a new plugin that provides a '''rating and an annotation menu action''' for files and folders, leveraging Nepomuk capabilities. <br />
<br />
Image management has become easier with '''Gwenview''', the KDE image viewer, now offering the ability to compare two or more pictures side by side. From the browse mode, select two or more pictures, and then switch to the view mode or to the full-screen mode. In the view mode, you can add more pictures from the thumbnail bar.<br />
<br />
Comic fans will be pleased that Okular, the universal file viewer, gains support for reading a directory as a comicbook.<br />
<br />
'''KStars''', the essential KDE application for stargazers around the world, has gained a feature to predict a star hopping route and dynamic switching between its OpenGL and native rendering backends. Labels can now be assigned to points on celestial lines; comet trails are rendered in OpenGL mode. Mathematicians and scientists can now explore higher order functions in Kalgebra and get information on oxidation states for elements in Kalzium. <br />
<br />
'''KDM''', the display manager, has gained ''GRUB2'' support. A user with multiple operating systems in their GRUB2 menu can now choose which one to reboot to in the shutdown dialog by holding down the mouse button on their reboot choice. <br />
<br />
'''Marble''', the virtual globe application, has gained many improvements over the past eight months. It now has voice navigation support, a map creation wizard, and new plug-ins. Following the Voice of Marble contest, '''voice navigation''' is now available in several languages, with voices provided by the KDE community. For more details, see Marble's [http://edu.kde.org/marble/current_1.2.php visual changelog]. <br />
<br />
Other applications such as Kate, Kalzium, KAlgebra, KStars, and KDevelop have also been updated in this release. Changes and improvements to some other major applications from the KDE community can be found in the [[Product_highlights#New_and_updated_applications|applications section]].<br />
<br />
Find more information on what is new in the Plasma Workspaces, the KDE Applications and the KDE Platform in the [http://www.kde.org/announcements/4.7/ announcement by KDE].<br />
<br />
{|<br />
|[[Image:OpenSUSE114KDENetbookPages.png|thumb|250px|alt=KDE Netbook features scrollable widget pages|Plasma Netbook widgets]]<br />
|[[Image:OpenSUSE114kdeNetbookSAL.png|thumb|250px|alt=Search and Launch interface in Plasma Netbook|Plasma Netbook search and launch interface]]<br />
|}<br />
<br />
=====Plasma Active One is optionally available=====<br />
The fresh and innovative [http://community.kde.org/Plasma/Active Plasma Active] interface for tablets and mobile devices is available for openSUSE 12.1. It is not an integral part of this release, as it still depends on a number of unreleased technologies but we plan to have Plasma Active as part of openSUSE 12.2.<br />
<br />
'''Plasma Active'''<br />
Plasma Active aims at creating a cross-device user experience for emerging devices such as tablet computers, media centers, smartphones, and more. It builds on the Linux stack with X11, Qt and the KDE libraries. The user interface is designed using Plasma Quick, a declarative markup language allowing for organic user interface design based on Qt Quick.<br />
<br />
The first release, [http://kde.org/announcements/plasma-active-one/ Plasma Active One] fully focuses on tablet computers. Plasma Active Tablet's user experience is designed around the web, social networks and multimedia content. Packages for openSUSE are offered in the [https://build.opensuse.org/project/show?project=KDE%3AActive Plasma Active] repository.<br />
<br />
==== GNOME 3.2 ====<br />
After shipping a technical preview of [http://www.gnome.org/gnome-3/ GNOME 3] with 11.4, openSUSE 12.1 replaces the GNOME 2.x series with the latest GNOME 3.2 desktop for the openSUSE GNOME users. With many improvements based on the feedback of the openSUSE community and the wider Free Software community, numerous usability and application changes have been incorporated.<br />
<br />
'''GNOME Shell''' brings a fresh user interface that is designed from the scratch to satisfy the needs of today's users. The interface focuses on getting out of the way and providing unobtrusive yet powerful notifications and deep integration of calendar, chat and other technologies. The UI elements and workflows are designed to be touch-friendly for use on tablets or desktops with a touch screen. By using the 3D acceleration capabilities provided by most of the computers these days, pleasing animations are used to give users an aesthetic look and feel and a much easier way of switching between applications. Read on for more details on what is new in GNOME 3.2.<br />
<br />
===== What is new in GNOME Shell 3.2 =====<br />
Various minor tweaks and major features are incorporated into this release based on user feedback. openSUSE 12.1 ships the alt-status-menu extension to make various computer operations easily accessible. Some examples:<br />
*It is now easier to resize windows and titlebars, buttons and other controls are a bit less tall, making GNOME easier to use on small screens.<br />
* Notifications now include a counter so you can see how many mails or chats messages are waiting for you and Shell now also shows media device notifications.<br />
* The focus-follows-mouse feature has been improved and while it is not perfect yet, it will suffice for most usecases.<br />
* The System Settings have been improved, showing links to other relevant settings and has integrated color management<br />
* GNOME Shell battery power status now shows how much power you have left<br />
<br />
===== Communication in GNOME Shell =====<br />
Compared to any prior release of GNOME, the instant messaging workflow is much improved in GNOME Shell 3.2. You can receive chats, reply to messages, approve / deny friendship requests, call requests, all without having to launch the IM application explicitly. You can change the status of your machine from a centralized place so that all the IM accounts reflect the status change. Error and new message notifications are so well integrated in GNOME shell so that you will not have focus stealing popups but only unobtrusive animations notifying you what is going on.<br />
<br />
A new "Online Accounts" feature enables users to create online accounts. Accounts created will be seamlessly available for various applications throughout the desktop experience. For example, if you create a Google Account, your Google Docs documents will be available in the new Document browser, your Google contacts will be available in empathy for IM, and the calendar shows your appointments. http://library.gnome.org/misc/release-notes/3.2/figures/gnome-documents-google.png.en<br />
<br />
[[Image:114_screenshots_gnome_desktop_generic.png|thumb|250px||The GNOME 2.32 Desktop]]<br />
[http://library.gnome.org/misc/release-notes/3.2/ GNOME 3.2] <br />
<br />
===== What is new in the GNOME 3.2 Applications =====<br />
The new GNOME 3 libraries bring many improvements to GNOME 3 applications. Some examples:<br />
* File open dialogs in applications now show a list of recent files and directories<br />
* Better performance and a new theme<br />
* A redesigned Font chooser dialog<br />
* A new on-screen keyboard and a number of other accessibility enhancements<br />
<br />
Moreover, the individual applications have seen many features and bugfixes, read on for a quick overview.<br />
A new people-focused '''Contacts"' application is shipped which can work with Evolution and Empathy in the background, providing you with a unified addressbook for your desktop. <br />
<br />
'''Empathy''', the GNOME IM application has got a lot of improvements. You can easily search your logs visually filtering on various parameters such as Who, When.<br />
<br />
http://library.gnome.org/misc/release-notes/3.2/figures/empathy-log.png.en NetworkManager-gnome version 0.9 provides fast user switching, improved WiFi roaming, WiMAX support, flexible permissions and centralized storage of network connection information.<br />
<br />
Not to be left out of the party, GNOME 3.2 includes robust color management support as well, including the new GNOME Color Manager wizard for calibrating displays using either ICC profiles or a Huey hardware colorimeter. [http://projects.gnome.org/gnome-color-manager/screenshots.html]<br />
<br />
File manager '''Nautilus''' has seen a major overhaul for GNOME 3, with an improved Places sidebar, a new ''Connect to server'' dialog and a quick preview function which can be triggered by 'space'.<br />
<br />
Many smaller improvements include new and configurable effects in the Webcam application '''Cheese''', bookmark support in PDF viewer '''Evince''', plugins for image viewer '''Eye of GNOME''' and improved streaming support for video and audio in media player Totem.<br />
<br />
Read more about [http://library.gnome.org/misc/release-notes/3.2/ GNOME 3.2 in the official announcement] and find more GNOME applications in the sections below.<br />
<br />
<gallery><br />
File:OpenSUSE 12.1 GNOME desktop.png|Desktop<br />
File:OpenSUSE 12.1 GNOME activities.png|Activities<br />
File:OpenSUSE 12.1 GNOME eog.png|Picture Viewer<br />
File:OpenSUSE_12.1_GNOME_nautilus.png|File Manager<br />
File:OpenSUSE_12.1_GNOME_shotwell.png|Photo Manager<br />
File:OpenSUSE_12.1_GNOME_totem.png|Video Player<br />
File:OpenSUSE_12.1_GNOME_totem2.png|Video Player (FullScreen)<br />
</gallery><br />
<br />
==== LXDE 0.5 ====<br />
This release of openSUSE comes with LXDE 0.5. There have been no major updates to this lightweight desktop for a while but minor improvements and bugfixes have been integrated.<br />
{|<br />
|[[Image:114_screenshots_lxde_menu.png|thumb|200px|LXDE Menu]]<br />
|[[Image:114_screenshots_lxde_filemanager_configuration.png|thumb|200px|LXDE File Manager & Configuration]]<br />
|}<br />
==== Xfce 4.8 ====<br />
openSUSE 12.1 ships ''''Xfce 4.8''''. All Xfce components have been updated to the latest bugfix releases. The desktop has been polished further in terms of integration and branding. LightDM is now the default display manager reducing the dependencies on core GNOME components. The functionality provided in the default install should now be on par with GNOME/KDE desktops.<br />
<br />
<br />
<gallery><br />
File:openSUSE_12.1_Xfce_Login_Manager.png|Login Manager<br />
File:openSUSE_12.1_Xfce_Desktop.png|Desktop<br />
File:openSUSE_12.1_Xfce_Main_Menu.png|Main Menu<br />
File:openSUSE_12.1_Xfce_Update_Notifier.png|New Update Notifier<br />
</gallery><br />
<br />
==== KDE 3 ====<br />
KDE 3 is again available for openSUSE after a gap of four releases. While it does not ship with the default DVD, it is available for installation from the official repository. This became possible due to unique features of the Open Build Service which greatly simplifies maintenance.<br />
<br />
Besides this, an additional community-supported repository KDE:KDE3 currently provides more KDE 3 related software than was ever available for any KDE 3-based distribution.<br />
<br />
KDE 3 received a number of security patches and bug fixes since its last release, contributed by enthusiasts from different projects which aim at continuation of KDE 3, such as Chakra and Trinity as well as openSUSE KDE3 team itself. One of the changes is a rewritten mediamanager which does not depend on HAL any longer.<br />
<br />
<gallery><br />
File:openSUSE_12.1_KDE3_Desktop.png|Desktop<br />
File:openSUSE_12.1_KDE3_Kickoff.png|Kickoff menu<br />
</gallery><br />
<br />
=== New and updated applications ===<br />
On top of the kernel and other low-level tools, openSUSE provides a huge variety of console and graphical applications. These applications have been updated to the latest versions bringing many improvements in terms of features and bugfixes.<br />
<br />
====Web browsers====<br />
The web is important for modern computer users, and openSUSE has you covered with a selection of browsers Free Software has to offer. We ship a much faster Firefox, an innovative Opera, a well integrated Epiphany and a more stable Rekonq. New is Chromium, the fast and easy to use browser from Google. These browsers provide a wide range of rendering engines supporting the latest web standards. Read on to find out what is new in these browsers since we brought to you in openSUSE 11.4!<br />
<br />
'''Firefox 7'''<br /><br />
Since Firefox 4.0 in openSUSE 11.4, the project has moved to a more rapid release schedule and thus we present you with Mozilla's latest Firefox 7.0.1. Firefox has introduced support for new privacy features like do-not-track and much improved developer tools in the new "web developer" menu. End users will appreciate the many smaller and larger usability improvements like the URL bar highlighting the website domain and hiding the prefix. Last but not least, each subsequent Firefox release brought better performance, from faster loading of tabs to the large memory management improvements in Firefox 7 and of course support for the latest web standards.<br />
<br />
'''Chromium 16'''<br /><br />
Chromium, meet openSUSE 12.1 users. Users, meet Chromium. This venerable WebKit based web browser from Google is quickly gaining popularity and thus had to become part of the openSUSE distribution. With its simplified interface, great integration with Google services, separate processes so a crashing site can not take down the browser and the fastest JavaScript engine in the world, it will impress you with its speed and ease of use. The rapid release cycle of Chromium is hard to track — we ensure the latest is always available on your system so you do not have to worry about security or not being able to work with the latest websites.<br />
<br />
'''Opera 11.52'''<br /><br />
Opera 11.52 brings much improved Opera Link to sync your passwords between system and a better Speed Dial which now supports extensions, small webpages embedded in your Speed Dial. Another new feature is the Location support on websites like Google Maps. Opera also uses far less memory now and became a fair bit more stable. Of course, this release supports the latest HTML 5 and CSS 3 standards and features a faster JavaScript engine and smoother graphics.<br />
<br />
'''Rekonq 0.8'''<br /><br />
With Rekonq 0.8, openSUSE ships a second WebKit based browser. Built on Qt and the KDE Platform, this new release takes advantage of the many improvements in QtWebKit 2.2, bringing better stability and performance. New features include the Do-Not-Track feature, availability of history in restored tabs, and Third Party rule support in AdBlock. Usability has been given attention with much improved drag'n'drop support, an new SSL UI, optional VI-style navigation and improved URL bar handling.<br />
<br />
'''Epiphany from GNOME 3.2'''<br /><br />
The third WebKit based browser, this time from the GNOME community, Epiphany, allows you to create Web Application links. These Web Applications show up in the application view of GNOME Shell and acts very much like real applications, opening links in new web browser windows and not showing a navigation bar or tabs. They also run in a process separate from the browser, so that crashes of Epiphany do not affect your web applications.<br />
<br />
====Office and desktop publishing applications====<br />
openSUSE helps you get work done by providing a stable base and up to date productivity tools. The latest LibreOffice brings new features in most components as well as speed and stability improvements to this enterprise ready office suite. While Abiword, Gnumeric and KOffice are still at their latest stable versions, our additional repositories offer the innovative Calligra application suite as a choice.<br />
<br />
'''Libreoffice 3.4.3'''<br /><br />
The latest [http://libreoffice.org '''Libreoffice'''] release brings a large number of small additions and improvements like the ability to add and remove color charts, a named range as data source and supporting an unlimited number of fields in the DataPilot (now named Pivot Table), Greek Character mode for numbering in Writer and much more. As usual, much performance work was done decreasing the size of LibreOffice and improving startup speed. Text rendering and theming have received a major overhaul, making LibreOffice fitting better in your desktop.<br />
<br />
'''Scribus 1.4'''<br /><br />
[http://www.scribus.net '''Scribus'''] is the major Open Source Desktop Publishing tool available for Linux. Underneath a modern and user-friendly interface, Scribus supports professional publishing features, such as color separations, CMYK and Spot Color support, ICC color management, and versatile PDF creation. openSUSE ships a release candidate of Scribus 1.4 which has a large number of stability fixes over the release in openSUSE 11.4.<br />
<br />
'''Calligra 2.4 beta 3'''<br /><br />
The new [http://www.calligra-suite.org/ Calligra Suite], the successor of KOffice in openSUSE, is not yet part of this release. However, most users report the current betas to be of '''better quality than the latest KOffice release''' and the openSUSE packagers have thus committed to provide a repository which will offer the latest Calligra releases.<br />
<br />
Specifically '''targeting students and academic users''' with the productivity part, Calligra brings much improved text handling and rendering, state of the art '''import support for the Microsoft XML formats''' and many stability and usability improvements to all applications. Words introduces handling of citations and bibliographies and an automatically updating Table of Content, better text tables, footer and header support and much more. Presentation application Stage has a new slide sorter and easier editing of notes with slides. Project Management application Plan introduces many new chart printing options and improved import from external data sources. Tables has improved support for large tables, rotated text, many new formulas, improved Microsoft Excel file support and much faster loading.<br />
<br />
Calligra also introduces two new applications: <br />
<br />
*Flow is a diagramming and flowcharting application in the spirit of Visio.<br />
*Braindump is a note taking application that builds on the Calligra core and uses the full power of the openDocument Format to allow for text, images and even multimedia in the notes.<br />
<br />
Find a [http://www.calligra-suite.org/news/calligra-2-4-snapshot-1-tour/ Calligra Tour here].<br />
<br />
You can find the latest Calligra in the KDE teams [http://en.opensuse.org/KDE_repositories#Updated_applications_only updated applications repository under Unstable]. Note that these applications are NOT up to the usual openSUSE standards yet!<br />
<br />
====Communication and groupware====<br />
Of course, openSUSE ships a wide variety of groupware and Personal Information Management (PIM) solutions like email clients, chat applications, calendar tools and more.<br />
<br />
'''KDE PIM'''<br /><br />
Kontact, KDE’s groupware solution, has most components now ported to Akonadi. Once the initial bugs are ironed out, this will offer increased stability and performance, better connection to new services and sharing of communication information between more applications. The biggest change is the introduction of KMail 2. This application has the familiar interface, while under the surface, all mail storage and retrieval has been ported to use the powerful Akonadi cache.<br />
<br />
The openSUSE KDE team has put '''significant efforts''' in ensuring a smooth upgrade to KMail 2, but this is a significant change and the team will keep an eye out for further issues. Bugfixes will be provided through updates and users are encouraged to report problems and update their systems frequently.<br />
<br />
It should be noted that the move from KMail1 to KMail2 requires the '''import/conversion of email data to Akonadi'''. This process can take considerable time, measuring up to a day on slow systems with multiple gigabyte-sized mailboxes. It is possible to, instead of doing a migration, doing a clean start by moving the current data from the <tt>~/.kde4/share/apps/kmail</tt> directory to a backup location. If you have your data stored on a server and it is only cached locally, this should not cause you to loose data. In case of a downloading POP mail account, however, you will have to use the conversion process or import your mail separately.<br />
<br />
Also note that '''Akonadi is a cache''', not a permanent storage system. This means that your mail should remain where it is — be it on a server or in a local directory. Akonadi will store a '''copy''' in its database, as well as extra information like ratings and the like, for fast search and retrieval. This essentially replaces the internal cache KMail1 employed for this purpose. Due to this design, Akonadi is very unlikely to lose user data, as it normally operates on a copy of it. Of course, actions like moving or removing mails are synced back to the original mail storage!<br />
<br />
'''Evolution 3.2.1'''<br /><br />
Evolution provides integrated mail, address book and calendaring functionality to users of the GNOME desktop. Version 3.2.1 has been ported over to the GNOME 3 infrastructure and offers a number of small improvements and bugfixes over the previous release. Also new in the openSUSE 12.1 Evolution is the Exchange Connector for Evolution, compatible with Exchange 2007 and later, allowing Evolution to work with Microsoft Exchange 2007 and 2010. Evolution also works with the Google contacts, calendar and mail services.<br />
<br />
'''Thunderbird 7.0.1'''<br /><br />
The latest [http://www.mozilla.org/thunderbird Mozilla Thunderbird] email client shipped with openSUSE brings delivers faster performance, safer email experience, and a new add-ons manager. With over 390 improvements and performance enhancements, Thunderbird is more responsive, starts faster and is easier to use than ever.<br />
<br />
For example, the interface improvements like the improved RSS feeds and better Attachment management make handling your news and mail easier. Tabs can now be re-ordered or dragged into a new window and Thunderbird gives you control over the look and functionality of your email client with a gallery of hundreds of add-ons. The new Add-ons manager allows you to search the gallery in Thunderbird to install, remove, and manage the Add-ons. This release also adds support for technologies that make it easier for developers to build some of these amazing Add-ons, such as the Lightning Calendar, Conversation View, and Open Search.<br />
<br />
====Multimedia====<br />
openSUSE comes with a number of prominent multimedia applications like the Amarok, Banshee and Rythmbox music players, DigiKam and Shotwell photo managers and the Marble virtual globe. Each of those has seen new releases with new features and bugfixes.<br />
<br />
=====Music Players=====<br />
openSUSE comes with a large number of music players, from the well known Rythmbox, Banshee and Amarok to the less prominent like Juk, Totem, KMplayer, Dragon and Bangarang.<br />
<br />
'''Banshee 2.2'''<br /><br />
The new [http://banshee.fm '''Banshee'''] comes with with lots of new extensions like an alarmclock, albumart writer, ampache, duplicated sound detector, jamendo, karaoke, live radio, lyrics and more. Other improvements include the ability to not only queue songs but also artists and albums and having the ability to play a queued song immediately after the current. There has been a number of UI improvements like putting the search next to the volume button, smaller icons in the source list, hidden counts for the libraries, named group separators and a resizable seek slider and search entry. Podcasts episodes are now shown in a grid, with several lines of description shown to help you find an appealing episode to enjoy.<br />
<br />
'''Amarok 2.4.3 and Clementine 0.7.3'''<br /><br />
[http://amarok.kde.org '''Amarok'''] introduces improved Dynamic Playlists and Internet Services including integration with Gpodder.net. The user interface has been improved with better drag and drop, automatic scrolling in the lyrics applet and the ability to scrobble the composer as artist to last.fm. Other than that, many bugs have been crushed and performance has improved a bit. For those not fond of the direction Amarok took with the 2.0 release, openSUSE ships [http://www.clementine-player.org '''Clementine 0.7.3''']. In this version, Clementine brings a new edit tag dialog which offers autocompletion and automatic music identification and missing-tag-fetching. CUE sheets are now supported, detected automatically and tracks will show up separately. Album covers are shown in the Library tab, deleted songs greyed out and much more.<br />
<br />
=====Photo managers, editors and painting applications=====<br />
openSUSE ships with a large number of graphics and painting applications. There have been major versions of DigiKam and Blender as well as minor improvements to most of the other applications. openSUSE 12.1 also comes with lots of ICC color management Profiles ready to go.<br />
<br />
'''DigiKam 2.2'''<br />
openSUSE 12.1 features the release of '''DigiKam''', the result of more than a year of hard work since the DigiKam version in openSUSE 11.4. This version features long awaited technologies like face detection and recognition, image versioning support, XMP metadata sidecar files support, big improvements in tagging and marking photos, reversed geotagging and many other improvements, including a total of 258 fixed bugs.<br />
<br />
Close companion Kipi-plugins is released along with DigiKam 2.2. This release features new export tools to three web services — Yandex.Fotki, MediaWiki and Rajce. The GPSSync plugin now has the ability to do reverse geocoding. Also new is a plugin which is dedicated to creating photo album-like layouts. Finally, there has been extensive bugfixing.<br />
Find out more about DigiKam and read articles with tips and tricks [http://www.digikam.org/ on the DigiKam website].<br />
<br />
'''Inkscape 4.8.2'''<br />
[http://inkscape.org Inkscape] is a powerful vector graphics editor using the W3C standard Scalable Vector Graphics (SVG) file format. It supports many advanced SVG features (markers, clones, alpha blending, etc.) and great care is taken in designing a streamlined interface. It is very easy to edit nodes, perform complex path operations, trace bitmaps and much more. The latest stable 4.8.2 version introduces a number of critical bugfixes and improvements to openSUSE 12.1.<br />
<br />
'''Blender'''<br />
This release is feature complete, offering the powerful UI, animation tools, rigging, modeling, shading, physics and particle tools and everything else Blender is known for.<br />
<br />
'''Shotwell 0.11.5'''<br />
The [http://yorba.org/shotwell/ '''Shotwell'' photo organizer handles pictures based on a timeline. It also offers tagging and rating features and a host of image editing functions like rotating, cropping and adjustment of exposure, saturation and more. It can import photos from most cameras and from directories and publish photos and videos to Facebook, Flickr, Picasa Web Albums, and YouTube. The latest release introduces hierarchical trees for the tags, a new plugin framework, improved printing, a new crop tool and a new search bar as well as many smaller improvements to the user interface. New is also support for paired JPEG and RAW images, BMP, TIFF and other formats, and improved rendering of RAW files. This release also does automatic backups of the database and allows you to save searches.<br />
<br />
'''F-spot 0.8.2-14'''<br />
The easy to use '''F-spot''' photo manager features a very simple interface combined with powerful search, import, browse and edit functionality. Advanced capabilities are exporting EXIF and XMP metadata to your images, versioning of changes in the image editor and quite complete import functionality. This release does not introduce major new features or improvements.<br />
<br />
'''GIMP 2.6.11'''<br />
[http://www.gimp.org/ '''GIMP'''] is a versatile graphics manipulation package offering a customizable interface and a large number of plugins to modify and improve photos. It can work with a huge variety of fileformats. 2.6.11 brings bugfixes for this popular photo manipulation program as well as some minor usability and performance improvements.<br />
<br />
'''Krita and Karbon 2.4 Beta3'''<br />
Two applications, part of the upcoming [http://www.calligra-suite.org Calligra 2.4] release, should not be missed in this overview. While they are not included in the standard openSUSE repositories, they offer some unique benefits many people will apreciate.<br />
<br />
[http://krita.org '''Krita'''] is a sketching and painting tool, offering an end-to-end solution for creating digital painting files from scratch by masters. Fields of painting that Krita explicitly supports are concept art, creation of comics and textures for rendering. Modelled on existing real-world painting materials and workflows, Krita supports creative working by getting out of the way and with snappy response. Developed in close collaboration with a number of artists Krita 2.4 brings many user interface improvements as well as much better performance. New functionality like the ability to share patterns, gradients and brushes over the web and the huge number of unique brushes solidify Krita's position as the '''premier Free Software sketching and drawing application'''.<br />
<br />
The Karbon vector graphics application, also part of [http://www.calligra-suite.org Calligra 2.4], has much better '''support for the SVG standard''' and introduces many new filters and effects while improving on its stability.<br />
You can find the latest Calligra in the KDE teams [http://en.opensuse.org/KDE_repositories#Updated_applications_only updated applications repository under Unstable]. Note that these applications are NOT up to the usual openSUSE standards yet!<br />
<br />
=====Video editors and 3D modelling=====<br />
Out of the box, openSUSE does not ship multimedia support due to legal and patent worries in a number of countries. However, if it is legal for you to play your music and videos, you can find information on the [http://opensuse-community.org/Multimedia openSUSE-community Multimedia] and [http://opensuse-community.org/Restricted_Formats Restricted formats] pages on how to obtain the needed codecs. The [http://packman.links2linux.de/ Packman] project offers the codecs and also packages a number of related applications like the excellent [http://www.kdenlive.org/ Kdenlive] and [http://www.openshotvideo.com/ openshot] video editors.<br />
<br />
'''Kdenlive 0.8.2'''<br />
'''Kdenlive''' claims to be the most advanced video editor available on Linux today. It supports virtually any camera and codec thanks to the [http://www.ffmpeg.org/ FFMPEG] and [http://www.mltframework.org/ MLT] frameworks it builds upon. It is a multitrack editor with a timeline and an unlimited number of video and audio tracks. Thanks to the [http://www.piksel.org/frei0r Frei0r] framework, Kdenlive offers a large number of effects and transitions and lets you add your own. It renders videos in a separate thread while you keep working and allows you to pause, stop and restart rendering. The latest 0.8.2 version fixes over 140 stability issues and introduces an automated backup feature to avoid the loss of any data. Check the [http://www.kdenlive.org/users/j-b-m/kdenlive-082-released announcement] for more information.<br />
<br />
'''OpenShot 1.4'''<br />
The '''OpenShot''' video editor has a more easy to use interface and offers features like 3D animations, HD video support, as well as Clip resizing, scaling, trimming, snapping, and cutting, Video transitions with real-time previews, Compositing, image overlays, watermarks, Title templates, title creation, sub-titles and support for Rotoscoping / Image sequences. [http://vimeo.com/29465427 watch the video of the 1.4 release] or [http://www.openshot.org/features/ check out the openshot features] online.<br />
<br />
'''Audacity 1.3.13'''<br />
For audio editing, '''Audacity''' offers a powerful set of features. Audacity lets you record live audio or convert existing music into digital data. It can also edit files, mixing the music or changing it with a variety of effects. These include echo, a phase changer, equalization, normalization and a number of effects to clean up hiss, noise and other mess. Additional plugins are availble with the VST and LADSPA plug-ins compatibility. Recording up to 96 kHz and 32 bit is available with high-quality sample rate conversion and there is a number of spectrum analysis tools for your viewing pleasure.<br />
<br />
This release, while part of the beta series, is quite stable. Compared to the 1.3.12 version in the previous openSUSE release, there has been a number of improvements to the effects, a new Device Toolbar showing all input and output devices has been introduced and the new "Sync-lock Tracks" feature allows groups of audio and/or label tracks to retain synchronisation when the track length changes. There has also been a fair number of bugfixes and some other smaller improvements.<br />
<br />
'''PiTiVi 0.15'''<br />
openSUSE does ship the simple [http://www.pitivi.org/ '''PiTiVi''' video editor in the main repositories. PiTiVi is more intuitive and easy to use video editor compared to OpenShot and Kdenlive, but does not offer the depth of input and output formats, camera support and effects the others do.<br />
<br />
'''Blender 2.59'''<br />
The well known [http://www.blender.org Blender] 3D content creation suite (3D modeller and video editor) is also part of openSUSE 12.1 with the stable 2.59 version. This third stable release in the 2.5 series brings big improvements in stability with many hundreds of bugs fixed. There is also a number of new features, including 3D mouse support and many UI improvements like the custom keymaps support and the camera locking. Sculpting, the warp modifier and the node editor have also been heavily improved.<br />
The biggest changes in the addons include:<br />
*the new Ivy Generator can grow curves over an existing mesh, <br />
*the Sapling addon generates trees<br />
*Mesh inset can inset individual faces or a selected region.<br />
*Grease scatter can scatter objects along predefined lines<br />
*much, much more. <br />
<br />
openSUSE of course delivers far more multimedia applications to you, from the GStreamer framework to less known music players and a myriad of tools.<br />
<br />
====Security and administration tools====<br />
openSUSE has always been a powertool for system adminstrators around the world and openSUSE 12.1 builds on this strong foundation. It is not only the powerful YaST which is appreciated, but also the many tools available with openSUSE. This release brings major improvements to AppArmor, the new Shorewall gateway/firewall configuration application, a big update to the Performance Co-Pilot tool, an extended WebYaST and much more.<br />
<br />
'''AppArmor 2.7 rc1'''<br /><br />
openSUSE 12.1 ships with the latest available [http://apparmor.net AppArmor] to ensure sys admins can easily secure their servers. [http://www.suse.com/support/security/apparmor/ Initially developed by SUSE], AppArmor is part of the Linux kernel now and openSUSE has the userspace components available. It is only in these userspace components that AppArmor ships changes compared to the previous release in openSUSE 11.4. Major features since AppArmor 2.5 include a working desktop notifier and automatic profile update for samba shares. And of course many other profile updates, bugfixes and better performance.<br />
<br />
'''Shorewall 4.4.24'''<br /><br />
New in openSUSE from the Open Build Service is the [http://shorewall.net/Introduction.html Shoreline Firewall configuration tool]. This application offers a very powerful but still rather high-level interface to configure Netfilter through editing a series of configuration files. Upon starting Shorewall, it will read the files and with help of the iptables and other security utils configure Netfilter/Xtables and the Linux networking subsystem to match your requirements, building a firewal, router or gateway. Find a list of [http://www.shorewall.net/4.4/shorewall_features.htm features of Shorewall here].<br />
<br />
[[Image:WebYaST_Screenshot.png|thumb|250px||WebYast in action]]<br />
<br />
'''Performance Co-Pilot (PCP) 3.5.8 and the PCP GUI charting tools.'''<br /><br />
The [http://oss.sgi.com/projects/pcp/ performance co-pilot] is a heavy-duty performance monitoring tool. It is specifically built to find the harder type of system-level performance problems. It is capable of correlating end-user quality of service with platform activity and diagnosing complex interactions between resource demands on single or multiple systems in dynamic environments. This release is a significant upgrade over what was shipped in openSUSE 11.4, bringing a host of new features and improvements like support for distributed event tracing, transparent support for compressed archives in the client tools, Integrated pmieconf and pmlogconf utilities for automating management of pmie/pmlogger configuration files, Linux kernel control group metrics, per-node CPU metrics, XFS btree metrics and some Postfix updates.<br />
<br />
'''WebYaST'''<br /><br />
The latest version of WebYaST has many improvements regarding speed, memory usage, usability and developing environment. Due a new caching mechanism the startup time of each module has been decreased to a maximum of 1–2 seconds. Former versions of WebYaST were split into a service and into an UI part. Each part ran in its own HTTP server. We have decided to bring these parts together in order to save one HTTP server, which halves the memory usage.<br />
<br />
====Virtualization, Cloud and web applications====<br />
openSUSE is an excellent guest OS for the cloud, as anyone who ever uses [http://susestudio.com SUSE Studio] can agree with. Nowhere is it as easy to build a cloud solution and openSUSE is now ready for the '''Amazon EC2 cloud''' by having a special EC2 kernel and suse-ami-tools in the default repositories.<br />
<br />
But openSUSE can also be an excellent host and contains a fair number of virtualization and cloud tools. Most prominent is OwnCloud, which is shipped with unique desktop integration in openSUSE. What is not available in the default repositories can be found in the special [https://build.opensuse.org/project/show?project=Virtualization%3ACloud openSUSE Virtualization and Cloud repository], where openSUSE contributors package and maintain '''Eucalyptus''', '''OpenNebula''' and '''OpenStack''' for openSUSE 12.1. <br />
<br />
'''ownCloud 2'''<br /><br />
openSUSE 12.1 supports ownCloud, the web-based storage application. ownCloud is different from solutions like Google Docs, Dropbox or Ubuntu One in that it lets '''you own the data'''. With version 2, the ownCloud team has improved the basic service and added valuable features:<br />
* Secure file sharing<br />
* Improved web access including the ability to play music<br />
* Synchronization with other web application tools<br />
* calendaring and contact management, also as Akonadi backend for desktop PIM apps<br />
<br />
openSUSE maintains a tool called mirall which is an unique system tray based tool which can:<br />
* Install a new ownCloud locally or in a webspace<br />
* Connect your system to an existing ownCloud<br />
* give you assistance to set up mirrored folders<br />
<br />
'''virtualization technologies'''<br /><br />
The new '''Xen 4.1''' release brings support for large systems (>255 processors and 1GB/2MB hugepage support), CPU Pools for advanced partitioning, the prototype credit2 scheduler designed for latency-sensitive workloads and very large systems, a re-architected XL toolstack that is functionally nearly equivalent to XM/XEND, support for x86 Advanced Vector Extension (AVX), new Memory Access API enabling integration of 3rd party security solutions into Xen virtualized environments and even better stability through the new automated regression tests.<br />
<br />
The lastest version of '''KVM''' provides live migration from one host to another, guest swapping, paravirtualized networking and block devices and PCI Express passthrough.<br />
<br />
The new 4.1 series '''VirtualBox''' release brings new features like VM cloning, enhanced wizard for creating and copying virtual disks, raised memory limit to 1TB for 64-bit hosts and a couple of experimental featuers like PCI passthrough or SATA hard disk hot-plugging.<br />
<br />
'''Virtualization tools'''<br /><br />
The latest release of '''virt-manager''' (supported by libvirt) brings new VM features including new VM wizard support for LCX guests, remote serial console access and remote URL guest installs.<br />
<br />
The recent version of '''open-vm-tools''' provides integration (shared folders, drag and drop, clipboard sharing, automatic guest resolution resizing, etc.) with the VMware tools.<br />
<br />
'''Horde 4.0.8'''<br /><br />
openSUSE 12.1 ships the latest Horde 4 groupware server and framework! Horde 4 is the first release in over 6 years and brings major improvements to all applications of the suite as well as to the framework itself. <br />
Some of the more significant changes from Horde 3 to 4 include a requirement for PHP 5.2 or higher, a new Ajax interface and a new test suite. The complete framework has been modernized and cleaned up and the libraries are better separated and Unit tested.<br />
<br />
The most important things users will notice are the e improved setup and upgrade processes, an Ajax interface for the calendar, and an improved interface for the complete application stack.<br />
<br />
Horde offers a large number of web applications including a webmail tool (part of the Horde Groupware Webmail Edition) complete with WYSIWYG HTML editor, IMAP and POP3 support, message search and filtering, spell check, attachment viewer, encryption and signing, keyboard navigation, threaded view and previews, downloading of attachments in a ZIP file and much more.<br />
<br />
There is now basic social media support with Facebook and Twitter integration and there is an Active Sync server component which can synchronize with iPhones and Android devices. The existing SyncML support already took care of most Nokia phones. The last missing piece is CalDAV support for calendar sharing, which is planned for the future.<br />
<br />
== Development tools and platforms (GNOME/GTK, KDE/Qt,..., etc) ==<br />
<br />
===IDEs and toolchain===<br />
openSUSE offers a complete and productive environment for developers and packagers. With stable tools and updated libraries available through [http://build.opensuse.org OBS], developers can easily develop using multiple programming languages and create packages for multiple distributions.<br />
<br />
====KDevelop====<br />
For software developers, KDevelop has gained support for predefined indentation styles and a Python interpreter using Kross. Improved Python auto-completion and support for lex/yacc file extensions are also included in this release.<br />
<br />
====Kate====<br />
KDE’s Advanced Text Editor, Kate has seen quite a number of improvements, including:<br />
* New Search Plugin with the ability to search in files on disk or opened files <br />
* Plugin improvements: Build Plugin, GDB Plugin<br />
* Kate’s tab bar plugins gained several new features<br />
* Swap files: If lost data is found, documents are marked as read-only<br />
* Further noteworthy changes: Improved printing, change of line ending triggers modified flag, fixed shortcut issues, fixed auto completion popup, and more.<br />
For more information, see [http://kate-editor.org/2011/07/09/kate-in-kde-4-7/ this blog].<br />
<br />
===KDE Platform===<br />
openSUSE 12.1 ships with the latest stable '''Qt 4.7.4''' and the '''KDE Platform 4.7.2''', giving developers the best from these powerful cross-platform development libraries.<br />
<br />
'''KDE Platform 4.7 '''<br /><br />
This release of KDE's development platform is an incremental release, bringing many bugfixes and small improvements to technologies like the build-in WebKit browser engine, system wide proxy support and the Phonon Multimedia engine. Developer-visible changes include:<br />
* Improvements to the Semantic Desktop components offering a richer API for applications<br />
* The option to suspend compositing in KWin whenever an application calls for it to improve performance in OpenGL games and GPU-accelerated video playback.<br />
<br />
For details on the KDE Platform 4.7 release see [http://kde.org/announcements/4.7/platform.php the KDE platform release notes].<br />
<br />
'''Qt 4.7 introduces QtQuick'''<br /><br />
Qt 4.7.4 is a '''bugfix release''' over the release shipped with openSUSE 11.4. <br />
<br />
However, it does introduce some powerful features including the official release of [http://blog.qt.nokia.com/2011/03/01/qt-quick-is-here QtQuick], a new feature within Qt that makes it easy to create light-weight apps and UIs. It contains the new QML language, a simple to learn declarative language for building dynamic and fluid interfaces, the Qt Declarative module and new tooling in Qt Creator to easily build apps.<br />
<br />
QtQuick 1.1 brings Right-to-Left support, improved caching and text input and a declarative API for handling touch input. There is also the new QML Sharders plugin which allows developers to embed OpenGL sharder effects in QML apps.<br />
<br />
=== GNOME platform improvements ===<br />
For further details, seee [http://library.gnome.org/misc/release-notes/3.2/ the GNOME 3.2 release notes].<br />
<br />
==== New features and functionality ====<br />
Included in openSUSE 12.1 is the latest release of the GNOME Developer Platform. This consists of a set of API- and ABI-stable libraries available under the GNU LGPL that can be used for the development of cross-platform applications.<br />
<br />
For information on developing with GNOME please visit the [http://developer.gnome.org GNOME Developer Center].<br />
<br />
'''GLib 2.30'''<br /><br />
GNOME's low-level software utility library GLib has seen various improvements, some of which are:<br />
* GApplication can now be used for non-unique applications.<br />
* GDBus supports the 'object manager' pattern with a number of new interfaces and has a code generator: gdbus-codegen.<br />
* An interface for certificate and key lookup has been added: GTlsDatabase. An implementation is provided by glib-networking.<br />
<br />
'''GTK+ 3.2'''<br /><br />
GTK+ 3.2 is the latest release of the GTK+ toolkit, which is at the heart of GNOME. GTK+ 3.2 includes new features for developers, as well as extensive bug fixes. <br />
* Many more widgets support height-for-width geometry management. It is important to set reasonable sizes on labels and check window sizes.<br />
* New widgets include GtkLockButton for privileged operations, GtkOverlay for floating controls over a content area, the new GtkFontChooserDialog and more.<br />
* There is also improved CSS theming support and the HTML backend Broadway, which renders a GTK3 application in a browser. It is still experimental and requires compiling with <tt>--enable-broadway-backend</tt> and environment varialbe <tt>GDK_BACKEND</tt> at runtime.<br />
<br />
'''Clutter 1.8'''<br /><br />
GNOME's graphics library for hardware-accelerated user interfaces Clutter provides, among other things, the following improvements: <br />
* New actions including Gesture and swipe detection, creating drop actors and long-press support for ClutterClickAction. <br />
* ClutterState transitions can be bound to object signals when creating a scene in ClutterScript. <br />
* Cogl, the GPU programming interface used by Clutter, is exposed as a separate library. <br />
<br />
'''Use of Deprecated Libraries'''<br /><br />
Further progress has been made in the continuous work of replacing outdated technologies with superior facilities. Some examples:<br />
* GConf now uses D-Bus. As a consequence, the deprecated libraries ORBit2 and libIDL have been removed from GNOME. Many applications using GConf have been ported to gsettings.<br />
* GNOME core modules now only depend on introspection-based Python bindings (pygobject-3) and hence pygtk, gnome-python and gnome-python-desktop are not required anymore.<br />
* Several packages, such as the Epiphany web browser, have been converted from using dbus-glib to GDBus and from libunique to G(tk)Application.<br />
<br />
'''Miscellaneous Developer Updates'''<br /><br />
Other GNOME Platform improvements in GNOME 3.2 include: <br />
* GNOME's build tool JHBuild does not build a module anymore if the version installed on your system is recent enough. If you start to build GNOME from scratch with a recent distribution, this can easily drop 50 modules from the list of modules to compile.<br />
* Tracker version 0.12 provides support for Firefox ≥ 4.0, Thunderbird ≥ 5.0, MeeGoTouch, several additional SPARQL parameters, extracting information from EPub files, and local XDG directories for desktop files. <br />
* NetworkManager version 0.9 provides introspection support and a simplified D-Bus API. Information how to port applications from NetworkManager 0.8 to 0.9 is available.<br />
* GtkSourceView now supports syntax highlighting of Markdown and Standard ML files.<br />
* libfolks now includes an Evolution-Data-Server backend, which is used by the new Contacts application.<br />
<br />
== And more ==<br />
The above selection of changes and improvements in openSUSE 12.1 is still far from complete but gives a taste of what is new. We hope you enjoyed reading it!<br />
</div></div>Kfreitaghttps://en.opensuse.org/index.php?title=openSUSE:Build_Service_Tools&diff=45594openSUSE:Build Service Tools2011-11-11T08:45:46Z<p>Kfreitag: /* Hermes */</p>
<hr />
<div>{{Buildservice navbar}}<br />
=OBS Server and Tools=<br />
This page provides a brief overview about all known OBS components and clients.<br />
If you write also one, please add a link to your resources here.<br />
<br />
==Official OBS components==<br />
===Build Script===<br />
The build script is used by server and client to do the actual build process. It can build in chroot or in secure XEN or KVM enviroment.<br />
<br />
Source: https://github.com/openSUSE/obs-build<br />
<br />
===Command Line Client===<br />
The command line client is used by power packagers, to solve merge conflicts and do local builds.<br />
<br />
Source: https://github.com/openSUSE/osc<br />
<br />
===OSC source validator===<br />
An extension for osc to find common mistakes before committing source. These checks are enforced for official openSUSE packages.<br />
<br />
Source: https://github.com/openSUSE/obs-service-source_validator<br />
<br />
===OBS Server===<br />
The OBS server code to setup an own instance of OBS.<br />
<br />
Source: https://github.com/openSUSE/open-build-service<br />
<br />
It needs also the Bento theming libs from<br />
<br />
Source: http://github.com/openSUSE/themes<br />
<br />
It can be installed easily as appliance:<br />
<br />
Appliance: http://en.opensuse.org/openSUSE:Build_Service_Appliance<br />
<br />
===OBS signing daemon===<br />
The signing daemon can be used for signing packages on the server. It is part of the OBS appliance.<br />
<br />
Source: https://github.com/openSUSE/obs-sign<br />
<br />
===Hermes===<br />
Hermes is an optional extra component for OBS. <br />
<br />
It is an extremely flexible solution to distribute events from OBS as notifications to users. It supports various ways of notification such as email, RSS or twitter posts. Users also can choose when the notification should happen: For each event individually or as digests posts after a given time span.<br />
<br />
Hermes comes with a decent configuration app for users and an admin application.<br />
<br />
Hermes Information portal: http://en.opensuse.org/openSUSE:Hermes<br />
<br />
Source: https://github.com/openSUSE/hermes<br />
<br />
===Software.o.o===<br />
software-o-o is an optional extra component for OBS end users. It is not yet<br />
modularized for general purpose use.<br />
<br />
Source: http://www.gitorious.org/opensuse/software-o-o<br />
<br />
==Unofficial OBS components==<br />
===osc extensions===<br />
====PyQT UI client====<br />
A simple GUI client for OBS written in PyQt. It is using osc python library as base.<br />
<br />
Source: http://www.gitorious.org/opensuse/yabsc<br />
<br />
====osc contrib====<br />
An osc plugin for working with the openSUSE:Factory:Contrib project.<br />
<br />
Source: http://www.gitorious.org/opensuse/osc-contrib<br />
<br />
====osc collaboration plugin====<br />
An osc plugin for taging patches to improve upstream collaboration. Used by the Gnome people, it needs an additional server.<br />
<br />
Source: http://www.gitorious.org/opensuse/osc-plugin-collab<br />
<br />
===Mono OSC===<br />
an OBS GUI written in Mono.<br />
<br />
Source: http://sourceforge.net/projects/monoosc/<br />
<br />
===spec file cleaner===<br />
A script to standarise a spec file.<br />
<br />
Source: http://www.gitorious.org/opensuse/spec-cleaner<br />
<br />
===OBS git===<br />
A tool to checkout OBS sources and replicate them as a git repo.<br />
<br />
Source: http://www.gitorious.org/opensuse/obs-git<br />
<br />
===FUSE file system to access OBS===<br />
To be able to mount an obs server as file system, you can use this fuse plugin.<br />
<br />
Source: https://github.com/uli/obsfs<br />
<br />
===OBS client for Android===<br />
Check your build states from your Android phone.<br />
<br />
Source: http://www.gitorious.org/opensuse/obs-client-android<br />
<br />
===OBS client lib for Qt===<br />
A first stub to connect to an OBS server from a Qt appliacation.<br />
<br />
Source: http://www.gitorious.org/opensuse/qtobs<br />
<br />
===Sofware Auto Test Enviroment===<br />
This code is using OBS to rebuild code and test automatically the resulting appliance. This is used by YaST people to test their stack based on their git code, building packages and appliance in OBS.<br />
<br />
Source: http://www.gitorious.org/opensuse/obs-autotest</div>Kfreitaghttps://en.opensuse.org/index.php?title=User:Kfreitag&diff=43737User:Kfreitag2011-10-04T19:23:57Z<p>Kfreitag: </p>
<hr />
<div><div style="width:70%; float:left"><br />
{{Box-header|About Klaas Freitag|{{FULLPAGENAME}}|}}<br />
While I did some packaging in the beginning of my time at SUSE I switched to work on internal infrastructure pretty soon. For example, the SUSE Bugzilla was done by me, later by my colleague [[User:cwh|Christopher]] and me, and finally by the '''Inttools Team''' which was part of SUSE R&D.<br />
<br />
Well, bugzilla.suse.de has vanished from us and went to the Novell servers. All Novell bugtracking is now done with [http://www.bugzilla.org Bugzilla] so the [http://bugzilla.novell.com Novell Bugzilla] needs a very much bigger mind than the SUSE Bugzilla ever had... And a bigger team for maintenance and development...<br />
<br />
The SUSE Inttools Team have found interesting things to move forward: For example [http://swamp.sourceforge.net SWAMP], our workflow management and administration tool which is in production to manage all the maintenance update s for SLE and openSUSE. Another topic for the tools team was feature tracking for the SUSE products with our tool [[openSUSE:openFate|Fate]]. <br />
<br />
I am one of the fathers of the open(SUSE) [[openSUSE:Build_Service|Buildservice]] and maintain [[openSUSE:Hermes|Hermes]], the Open Buildservice notification system.<br />
<br />
In summer 2007 I changed my role and became the architect of the SUSE department RD OPS/IPD. In that role I worked on a higher level on infrastructure such as the internal and external Buildservice, our tools and more.<br />
<br />
Later on in summer of 2009 I became the teamlead of the [[openSUSE:Boosters|openSUSE Boosters Team]] - something I am very happy about. We're working towards to make openSUSE more attractive for contributors. <br />
<br />
In the spare time I am contributing to [http://www.kde.org KDE] and I am <br />
active member of the KDE e.V. In july 2007 I was elected to the board of the [http://ev.kde.org KDE e.V] in which I served until summer 2009.<br />
<br />
My current project in KDE is a project called [http://volle-kraft-voraus.de/pmwiki.php/Main/Kraft Kraft] which helps people to create documents like invoices for their little business.<br />
<br />
{{Box-footer|}}<br />
</div><br />
<div style="width:30%; float:right"><br />
{{Box-header|Imagination|{{FULLPAGENAME}}|}}<br />
[[Image:Klaas_freitag.jpg|140px|center|Klaas Freitag]]<br />
{{Box-footer|}}<br />
</div><br />
<br />
<div style="width:30%; float:right"><br />
{{Box-header|Contact|{{FULLPAGENAME}}|}}<br />
new Blog: [http://kfreitag.tumblr.com Tumblr]<br/><br />
Blog: [http://lizards.opensuse.org/author/kfreitag Lizards]<br/><br />
Email: [mailto:freitag@opensuse.org freitag@opensuse.org]<br/><br />
[irc://irc.freenode.net/opensuse-project irc]: dragotin<br/><br />
{{Box-footer|}}<br />
</div></div>Kfreitaghttps://en.opensuse.org/index.php?title=Archive:Hermes_Architecture&diff=43087Archive:Hermes Architecture2011-09-07T15:52:20Z<p>Kfreitag: /* Architecture */</p>
<hr />
<div>{{Hermes_navbar}}<br />
__NOTOC__<br />
{{Special info|This page explains the architecture of the Hermes system.<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 />
==Architecture==<br />
<br />
To fulfill the requirements, the following logical functional blocks are needed:<br />
<br />
[[Image:hermes_arch_overview.png]]<br />
<br />
* The ''User Preferences Module'' stores the different choices of which notifications a user would like to receive how. With this part of the system, the user controls how the messages approach her. It feeds it's information in nearly all other blocks<br />
<br />
* The ''Storage'' represents the interface for incoming messages and stores them into the database or transfers it to the Relay if immediate sending is required.<br />
<br />
* A ''Database'' holds the messages until their delivery. Since the data is structured a relation database is used.<br />
<br />
* The ''Relay'' is triggered time based and checks if messages are due for delivery. If so it assembles messages if required (like digests) and proceeds them to the agents for delivery. <br />
<br />
* The ''Agents'' are specialized transport modules that deliver a message using a different technologies.<br />
<br />
These are the logical building blocks. For more details read [[openSUSE:Hermes_Subsystems|about Hermes' subsystems]].<br />
----<br />
<br />
==Interfaces==<br />
<br />
Basically there are four interaction points with the system:<br />
<br />
* Message Storage through a HTTP CGI (later REST) interface<br />
* User interaction for preference setting and message reading through a rails based web application<br />
* An admin web interface for administration tasks<br />
* Message delivery through the various agents<br />
<br />
Some details about each of them follow.<br />
<br />
===Message storage===<br />
<br />
Other applications which want to feed their notifications into Hermes can store notifications into the system via a HTTP based CGI interface<br />
<br />
===Concept: Hermes REST Interface===<br />
<br />
{{Info|The REST interface is not yet implemented but here's the concept.}}<br />
<br />
Clients can post notifications to Hermes sending a POST request to <br />
<pre><br />
http://hermes.opensuse.org/<username>/[<notificationtype>]<br />
</pre><br />
All parameters are added to the POST request.<br />
<br />
To query already existing notifications from the Hermes Storage a ''GET'' request to the following url returns the stored messages:<br />
<br />
<pre><br />
http://hermes.opensuse.org/<username>/[<notificationtype>]<br />
</pre><br />
<br />
====Notification type====<br />
<br />
The notification type is a special element used to qualify the kind of notification. It need to be one parameter of the CGI POST request. Basically the message type is a string freely choseable from the posting client. The poster does not have to worry about whether the notification type exists or was used before. If a notification type is not known to Hermes, the notification time schedule and the delivery type is handled by a user configurable default.<br />
<br />
In later releases of Hermes it might give sub message types that inherit<br />
the settings of their parents.<br />
<br />
----<br />
<br />
==Agents==<br />
<br />
There are different agents that deliver the messages according to<br />
the time constraints defined for the message type by the user. The kind of<br />
delivery (by mail, as Jabber message etc.) is also subject to<br />
configuration done through Starship, the User Preferences Module. The Agents get<br />
triggered by the Relay to do message delivery.<br />
<br />
----<br />
<br />
==The User Web Application Starship==<br />
<br />
The Hermes web application called Starship fulfills two purposes: Managing user<br />
preferences and showing lists of messages.<br />
For the openSUSE Hermes installation Starship is hosted at [http://hermes.opensuse.org http://hermes.opensuse.org].<br />
<br />
This module lets the user edit his/her personal settings. Basically<br />
that is how a message of a distinct type is to be delivered and under<br />
which time constraint. Furthermore, filters which narrow down the message delivery even more can be configured.<br />
<br />
See user documentation for Starship:<br />
[[openSUSE:Hermes_documentation|Hermes usage documentation]]<br />
<br />
Starship also shows lists of messages in a sortable, filterable<br />
and smooth way.</div>Kfreitaghttps://en.opensuse.org/index.php?title=File:Hermes_arch_overview.png&diff=43086File:Hermes arch overview.png2011-09-07T15:51:44Z<p>Kfreitag: uploaded a new version of &quot;File:Hermes arch overview.png&quot;</p>
<hr />
<div>Architecture overview image.</div>Kfreitaghttps://en.opensuse.org/index.php?title=File:Hermes_arch_overview.png&diff=43083File:Hermes arch overview.png2011-09-07T15:49:00Z<p>Kfreitag: Architecture overview image.</p>
<hr />
<div>Architecture overview image.</div>Kfreitaghttps://en.opensuse.org/index.php?title=openSUSE:Conference_todo_list&diff=42963openSUSE:Conference todo list2011-09-05T16:34:19Z<p>Kfreitag: /* Sponsoring */</p>
<hr />
<div>{{Conference organizing navbar}}<br />
{{Intro|The following is a list of tasks to be completed for the organization of the upcoming openSUSE 2011 Conference. Even if a task is assigned, you can still volunteer to assist. We encourage everyone to take something fun that they can enjoy and develop with.}}<br />
<br />
==How to handle this page==<br />
# If you do a task put it onto this list<br />
# If you take over a task add your name to it<br />
# If you finish a task remove it from this list<br />
# If you didn't do 1,2 or 3 don't touch this page! This is not a wishlist or collection of ideas!<br />
<br />
==Marketing==<br />
This is tracked on [[openSUSE:Conference_promotion_todo_list]]<br />
<br />
==Program==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
| Print the program that falls out of indico as A4 handouts and very large posters.<br />
| Robert<br />
|-<br />
| Print the [[openSUSE:Conference_code_of_conduct|conference code of conduct]] to be put into each bag<br />
| Robert<br />
|- <br />
| Organize a whiteboard for BoF scheduling for the registration desk<br />
| Henne<br />
|}<br />
<br />
==Sponsoring==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|}<br />
<br />
==Conference Bag==<br />
Track the contents of the conference bag with a person to talk to.<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Content<br />
!Contact person<br />
|-<br />
|}<br />
===Travel Sponsorship===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Pay the money to the accepted applicants<br />
|Jos, AJaeger, AlanClark<br />
|-<br />
|}<br />
<br />
==Venue==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Organize cleaning service for Wednesday the 7.<br />
|Olli<br/> ''Status: Meeting in the rooms in CW 35 with the chief of cleaning service''<br />
|-<br />
|Organize insurance for damage and theft of hardware<br />
|Ajaeger<br />
|-<br />
|Direction signs from the subway station to the venue<br />
|Jürgen Weigert<br />
|-<br />
|Direction signs inside the venue<br />
|Jürgen Weigert<br />
|-<br />
| Organize 40 flashy "organizers" t-shirt.<br />
| Henne<br />
|-<br />
| Check lighting in all rooms<br />
| Henne<br />
|- <br />
| Organize extension cords and plugstrips<br />
| Henne<br />
|-<br />
|Buy ducktape<br />
|Henne<br />
|-<br />
|Print Kantine Posters<br />
|Henne<br />
|- <br />
|}<br />
<br />
===Entry Area===<br />
<br />
====Lounge/Beergarden====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Buy flowers <br />
|<br />
|-<br />
|Organize old SUSE stuff for decoration<br />
|Olli<br/>''Status: Get from stock cw 35 to get an overview''<br />
|-<br />
|Get the SUSE sofas/tables to the venue<br />
|Klaas, Tom, Olli<br/>''Status: Will be done with rental car on thursday, sept. 8th.''<br />
|-<br />
|Organize waste bins<br />
|Klaas, Tom<br />
|-<br />
|Buy toys like a football, frisbee<br />
|Henne<br />
|}<br />
<br />
==== Snack Bar ([[openSUSE:Conference_snack_bar|details]]) ====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to <br />
|-<br />
|Organize a coffee machine and plastic coffee mugs<br />
|Olli<br/>''Status: 2 pump machines from SUSE plus coffee, filters. Mugs to be bought at Metro or so.''<br />
|-<br />
|Buy 2 buckets, clouts, soap, dish-washing stuff, sponge cloth, paper roll and a dish washing bowl as we only have water on the opposite of the main hall.<br />
|Ajaeger, Klaas<br />
|-<br />
|Bring servicing <br />
|Henne<br />
|-<br />
|Bring 2 Bar stools from SUSE (ask ofecher) <br />
|Tom<br />
|-<br />
|Buy coffee mugs<br />
|Henne<br />
|-<br />
|Bring coffee milk and cans from ebc (ask salva)<br />
|Tom<br />
|-<br />
|Bring small fridge from suse for barbecue stuff<br />
|Tom<br />
|-<br />
|Bring from SUSE: cutter, coffee powder, filter paper, beaker, small bowl<br />
|Tom<br />
|-<br />
|Organize a fruit basket<br/>''Status: Tom or Klaas will bring baskets.''<br />
|Klaas, Tom<br/>''Status: Tom or Klaas will bring baskets.''<br />
|- <br />
|}<br />
<br />
====Registration/Help Desk====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Create [http://www.flickr.com/photos/blogwiese/3185417530/ pin buttons] as badges with name<br />
|Henne, Robert<br />
|-<br />
|Organize openSUSE/Sponsor goodies<br />
|Jos, Ajaeger, Izabel<br />
|- <br />
|Organize Bags to put goodies in<br />
|Robert<br />
|-<br />
|Organize Nürnberg brochures from the tourist info<br />
|Henne<br />
|-<br />
| Extend http://conference.opensuse.org/map to include surroundings (parking, atm, ciggs, caffee, food, etc) and print it<br />
| Christopher/Henne/Izabel/Robert<br />
|-<br />
| Organize a emergencies contact list with all phone numbers and people who can help (find volunteers)<br />
| Henne<br />
|- <br />
| Organize "Keine Haftung" signs for the coat-hangers..<br />
| Henne<br />
|-<br />
|}<br />
<br />
===Main Room===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Bring the speaker desk from the all-hands area<br />
|Ajaeger<br />
|-<br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
===Ballroom===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
===Seminar Rooms===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Mark one of the small rooms upstairs as speaker room<br />
|Ajaeger<br />
|- <br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
==Social Events==<br />
<br />
===Party===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Tell Metzger Wolf how many people will attend by 2011-09-01<br />
|Henne, Olli<br />
|- <br />
|Buy red/white wine and organize enough glasses<br />
|Cboltz, Henne<br />
|-<br />
|Invite the companies at Zentrifuge to the party and inform them of the conference<br />
|Henne<br />
|- <br />
|Buy Whiskey<br />
|Henne<br />
|-<br />
|}<br />
<br />
===Speakers Dinner===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
| Notify the keynote speakers<br />
| AJaeger<br />
|-<br />
| Organize the speakers + sponsors + professional ticket holder dinners<br />
| Ajaeger<br />
|- <br />
|}<br />
<br />
[[Category:Conference]]</div>Kfreitaghttps://en.opensuse.org/index.php?title=Archive:Conference_speaker_information_2011&diff=42803Archive:Conference speaker information 20112011-08-30T12:54:16Z<p>Kfreitag: </p>
<hr />
<div>{{Conference speaker navbar}}<br />
<br />
We are happy that you will speak on the openSUSE Conference 2011 and we hope that it will be a pleasant and exciting experience for all attendees. <br />
<br />
We collected some information for the speakers. Please read it carefully. Let us know if something is missing or not accurate. We are happy to hear your feedback.<br />
<br />
===Preparation===<br />
<br />
Congratulations that you got your talk accepted by the Program Committee. We're very much looking forward to your contribution and you should be prepared for an interested audience that is really looking forward to your presentation. <br />
<br />
Before the conference, please make sure to check your contribution in [http://conference.opensuse.org/indico//myconference.py?confId=2 Indico] at the menu point "My conference".<br />
If there is something to change, please let the [mailto://cfp@opensuse.org Program Committee] know. They will change it for you.<br />
<br />
The contribution should consist of:<br />
<br />
* The proper talk-, workshop- or BOF '''title'''<br />
* A reasonable '''description''' of your activity. The description should be around 400 words describing what people can expect in the session. Note that an interesting description is the key for a large audience.<br />
* A '''short bio''' of the speaker. No need to tell people your mothers' birth name but its interesting what your relation to free software in general and to the specific topic in particular is. <br />
<br />
===Rooms and Technical Equipment===<br />
<br />
The conference venue has two large presentation rooms and some smaller rooms. All rooms have a projector displaying on a screen. The larger ones also have an audio system. Check the rooms and stuff on the [http://conference.opensuse.org/location/ map].<br />
<br />
The rooms are open during the talks so be prepared to people entering and leaving the room during your presentation. There will be a session chair person around to help you and introduce your talk.<br />
<br />
For your convenience, drinking water will be available during your talk.<br />
<br />
===Time===<br />
<br />
<br />
{{Special info|Usually presentations have a time slot of 60 minutes if not stated differently. This time includes 45 minutes of speaking time including questions and additional 15 minutes time for listeners to change rooms and for the presenter to set up the computer with the projector and get the audio thing going.}}<br />
<br />
To be fair to all presenters we will maintain the schedule in the hard way. Please make sure to finish the presentation in 45 minutes and give the attendees time to ask questions. Note that if your talk has another length on the timetable, you still should end 15 minutes before the end on the timetable to give people time to change.<br />
<br />
There will be a session chair in the room who can give you time hints if you want that. Please let the session chair know.<br />
<br />
===Slides===<br />
<br />
Since there are always problems with setting up projectors on notebooks we encourage every speaker to show up in time to set the stuff up.<br />
<br />
Please attach the slides or any important notes of a BoF session to the Indico system. That enables people to work after your contribution.<br />
<br />
===Photos and Videos===<br />
<br />
Depending on what technical equipment we have available we would like to record as many talks as possible, as well as we will have people taking photos. As common for free software events we would like to put them online. <br />
<br />
''Please actively inform the Program Committee if that is not ok with you.''<br />
<br />
[[Category:Conference]]</div>Kfreitaghttps://en.opensuse.org/index.php?title=Archive:Conference_speaker_information_2011&diff=42802Archive:Conference speaker information 20112011-08-30T12:19:18Z<p>Kfreitag: /* Rooms and Technical Equipment */</p>
<hr />
<div>{{Conference speaker navbar}}<br />
We are happy that you will speak on the openSUSE Conference 2011 and we hope that it will be a pleasant and exciting experience for all attendees. <br />
<br />
We collected some information for the speakers. Please read it carefully. Let us know if something is missing or not accurate. We are happy to hear your feedback.<br />
<br />
===Preparation===<br />
<br />
Congratulations that you got your talk accepted by the Program Committee. We're very much looking forward to your contribution and you should be prepared for an interested audience that is really looking forward to your presentation. <br />
<br />
Before the conference, please make sure to check your contribution in [http://conference.opensuse.org/indico//myconference.py?confId=2 Indico] at the menu point "My conference".<br />
If there is something to change, please let the [mailto://cfp@opensuse.org Program Committee] know. They will change it for you.<br />
<br />
The contribution should consist of:<br />
<br />
* The proper talk-, workshop- or BOF '''title'''<br />
* A reasonable '''description''' of your activity. The description should be around 400 words describing what people can expect in the session. Note that an interesting description is the key for a large audience.<br />
* A '''short bio''' of the speaker. No need to tell people your mothers' birth name but its interesting what your relation to free software in general and to the specific topic in particular is. <br />
<br />
===Rooms and Technical Equipment===<br />
<br />
The conference venue has two large presentation rooms and some smaller rooms. All rooms have a projector displaying on a screen. The larger ones also have an audio system. Check the rooms and stuff on the [http://conference.opensuse.org/location/ map].<br />
<br />
The rooms are open during the talks so be prepared to people entering and leaving the room during your presentation. There will be a session chair person around to help you and introduce your talk.<br />
<br />
For your convenience, drinking water will be available during your talk.<br />
<br />
===Time===<br />
<br />
Usually presentations have a time slot of 60 minutes if not stated differently. This time includes 45 minutes of speaking time including questions and additional 15 minutes time for listeners to change rooms and for the presenter to set up the computer with the projector and get the audio thing going.<br />
<br />
To be fair to all presenters we will maintain the schedule in the hard way. Please make sure to finish the presentation in 45 minutes and give the attendees time to ask questions. Note that if your talk has another length on the timetable, you still should end 15 minutes before the end on the timetable to give people time to change.<br />
<br />
There will be a session chair in the room who can give you time hints if you want that. Please let the session chair know.<br />
<br />
===Slides===<br />
<br />
Since there are always problems with setting up projectors on notebooks we encourage every speaker to show up in time to set the stuff up.<br />
<br />
Please attach the slides or any important notes of a BoF session to the Indico system. That enables people to work after your contribution.<br />
<br />
===Photos and Videos===<br />
<br />
Depending on what technical equipment we have available we would like to record as many talks as possible, as well as we will have people taking photos. As common for free software events we would like to put them online. <br />
<br />
''Please actively inform the Program Committee if that is not ok with you.''<br />
<br />
[[Category:Conference]]</div>Kfreitaghttps://en.opensuse.org/index.php?title=Archive:Conference_speaker_information_2011&diff=42801Archive:Conference speaker information 20112011-08-30T12:17:37Z<p>Kfreitag: </p>
<hr />
<div>{{Conference speaker navbar}}<br />
We are happy that you will speak on the openSUSE Conference 2011 and we hope that it will be a pleasant and exciting experience for all attendees. <br />
<br />
We collected some information for the speakers. Please read it carefully. Let us know if something is missing or not accurate. We are happy to hear your feedback.<br />
<br />
===Preparation===<br />
<br />
Congratulations that you got your talk accepted by the Program Committee. We're very much looking forward to your contribution and you should be prepared for an interested audience that is really looking forward to your presentation. <br />
<br />
Before the conference, please make sure to check your contribution in [http://conference.opensuse.org/indico//myconference.py?confId=2 Indico] at the menu point "My conference".<br />
If there is something to change, please let the [mailto://cfp@opensuse.org Program Committee] know. They will change it for you.<br />
<br />
The contribution should consist of:<br />
<br />
* The proper talk-, workshop- or BOF '''title'''<br />
* A reasonable '''description''' of your activity. The description should be around 400 words describing what people can expect in the session. Note that an interesting description is the key for a large audience.<br />
* A '''short bio''' of the speaker. No need to tell people your mothers' birth name but its interesting what your relation to free software in general and to the specific topic in particular is. <br />
<br />
===Rooms and Technical Equipment===<br />
<br />
The conference venue has two large presentation rooms and some smaller rooms. All rooms have a projector displaying on a screen. The larger ones also have an audio system.<br />
<br />
The rooms are open during the talks so be prepared to people entering and leaving the room during your presentation. There will be a session chair person around to help you and introduce your talk.<br />
<br />
For your convenience, drinking water will be available during your talk. <br />
<br />
===Time===<br />
<br />
Usually presentations have a time slot of 60 minutes if not stated differently. This time includes 45 minutes of speaking time including questions and additional 15 minutes time for listeners to change rooms and for the presenter to set up the computer with the projector and get the audio thing going.<br />
<br />
To be fair to all presenters we will maintain the schedule in the hard way. Please make sure to finish the presentation in 45 minutes and give the attendees time to ask questions. Note that if your talk has another length on the timetable, you still should end 15 minutes before the end on the timetable to give people time to change.<br />
<br />
There will be a session chair in the room who can give you time hints if you want that. Please let the session chair know.<br />
<br />
===Slides===<br />
<br />
Since there are always problems with setting up projectors on notebooks we encourage every speaker to show up in time to set the stuff up.<br />
<br />
Please attach the slides or any important notes of a BoF session to the Indico system. That enables people to work after your contribution.<br />
<br />
===Photos and Videos===<br />
<br />
Depending on what technical equipment we have available we would like to record as many talks as possible, as well as we will have people taking photos. As common for free software events we would like to put them online. <br />
<br />
''Please actively inform the Program Committee if that is not ok with you.''<br />
<br />
[[Category:Conference]]</div>Kfreitaghttps://en.opensuse.org/index.php?title=openSUSE:Conference_todo_list&diff=42737openSUSE:Conference todo list2011-08-29T15:13:00Z<p>Kfreitag: /* Snack Bar (details) */</p>
<hr />
<div>{{Conference organizing navbar}}<br />
{{Intro|The following is a list of tasks to be completed for the organization of the upcoming openSUSE 2011 Conference. Even if a task is assigned, you can still volunteer to assist. We encourage everyone to take something fun that they can enjoy and develop with.}}<br />
<br />
==How to handle this page==<br />
# If you do a task put it onto this list<br />
# If you take over a task add your name to it<br />
# If you finish a task remove it from this list<br />
# If you didn't do 1,2 or 3 don't touch this page! This is not a wishlist or collection of ideas!<br />
<br />
==Marketing==<br />
This is tracked on [[openSUSE:Conference_promotion_todo_list]]<br />
<br />
==Program==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
| Ask the speakers to blog about their submissions -CFP<br />
| <br />
|-<br />
| Print the program that falls out of indico as A4 handouts and very large posters.<br />
| Robert<br />
|-<br />
| Finish the [[openSUSE:Conference speaker guidelines|guidelines for speakers]]<br />
|<br />
|- <br />
| Write and announce the [[openSUSE:Conference_code_of_conduct|conference code of conduct]]<br />
|<br />
|- <br />
| Organize Lightning Talks<br />
| Bryen<br />
|- <br />
| Organize a whiteboard for BoF scheduling for the registration desk<br />
|<br />
|}<br />
<br />
==Sponsoring==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|}<br />
<br />
===Travel Sponsorship===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Pay the money to the accepted applicants<br />
|Jos, AJaeger, AlanClark<br />
|-<br />
|}<br />
<br />
==Venue==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Find volunteers to record the main hall talks with their own cameras.<br />
|Bryen, Jürgen Weigert<br />
|-<br />
|Organize cleaning service for Wednesday the 7.<br/> ''Status: Meeting in the rooms in CW 35 with the chief of cleaning service, cleaning happens in CW 36''<br />
|Olli<br />
|-<br />
|Organize insurance for damage and theft of hardware<br />
|Ajaeger<br />
|-<br />
|Direction signs from the subway station to the venue<br />
|Jürgen Weigert<br />
|-<br />
|Direction signs inside the venue<br />
|Jürgen Weigert<br />
|-<br />
|}<br />
<br />
===Entry Area===<br />
<br />
====Lounge/Beergarden====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Buy flowers <br />
|<br />
|-<br />
|Organize old SUSE stuff for decoration<br/>''Status: Get from stock cw 35 to get an overview''<br />
|Olli<br />
|-<br />
|Get the SUSE sofas/tables to the venue<br/>''Status: Will be done with rental car on thursday, sept. 8th.''<br />
|Klaas, Tom, Olli<br />
|-<br />
|Organize a wardrobe<br />
|Klaas, Tom, Olli<br/>''Status: Olli will bring a wardrobe from home''<br />
|-<br />
|Organize 20 sets of benches and tables for the beergarden:<br/>''Status: 80 crates of Old Toad and 20 benches and tables will be on friday, 9th directly to zentrifuge by the brewery. The stuff is picked up again on thursday, 15 th. september''<br />
|Klaas<br />
|-<br />
|Organize waste bins<br />
|Klaas, Tom<br />
|-<br />
|Buy toys like a football, frisbee<br />
|Henne<br />
|}<br />
<br />
==== Snack Bar ([[openSUSE:Conference_snack_bar|details]]) ====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to <br />
|-<br />
|Organize the Bar from Coca Cola<br/>''Status: Coca Cola delivers at sept. 8th.''<br />
|Olli<br />
|-<br />
|Organize the sandwiches/softdrinks/ice-cream<br/>''Status:''<br />
* ''softdrinks: Delivery on sept. 8th''<br />
* ''sandwiches: every day delivery in the morning by Metzger Wolf''<br />
* ''ice-cream: Wont happen, too much hassle''<br />
|Olli<br />
|-<br />
|Organize Beer - <br/>''Status: see above: 80 beer crates will be delivered to the conference venue on sept. 9th.''<br />
|Klaas<br />
|-<br />
|Organize fridges for the softdrinks/beer<br/>''Status: Delivery by Coca Cola on sept. 8th to Zentrifuge''<br />
|Olli<br />
|-<br />
|Organize a coffee machine and plastic coffee mugs<br/>''Status: 2 pump machines from SUSE plus coffee, filters. Mugs to be bought at Metro or so.''<br />
|Olli<br />
|-<br />
|Buy 2 buckets, clouts, soap and a dish washing bowl as we only have water on the opposite of the main hall.<br />
|Ajaeger, Klaas<br />
|-<br />
|Organize a fruit basket<br/>''Status: Tom or Klaas will bring baskets.''<br />
|Klaas, Tom<br />
|- <br />
|}<br />
<br />
====Registration/Help Desk====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Find volunteers to run the registration desk: ''done, see [[openSUSE:Conference_volunteers|the Volunteers Page]]''<br />
|Klaas, Tom<br />
|-<br />
|Create [http://www.flickr.com/photos/blogwiese/3185417530/ pin buttons] as badges with name<br />
|Henne, Robert<br />
|-<br />
|Organize openSUSE/Sponsor goodies<br />
|Jos, Ajaeger, Izabel<br />
|- <br />
|Organize Bags to put goodies in<br />
|Robert<br />
|-<br />
|Organize Nürnberg brochures from the tourist info<br />
|Henne<br />
|-<br />
|Organize a network printer<br/>''Status: done.''<br />
|Olli<br />
|-<br />
|}<br />
<br />
===Main Room===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Bring the speaker desk from the all-hands area<br />
|Ajaeger<br />
|-<br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
===Ballroom===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
===Seminar Rooms===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Mark one of the small rooms upstairs as speaker room<br />
|Ajaeger<br />
|-<br />
|Organize 4 projectors from SUSE<br/>''Status: one is at Henne to check. Three others to investigate.''<br />
|Olli<br />
|-<br />
|Organize 4 projector screens<br />
|Christopher<br />
|-<br />
|Organize 4 flip charts from SUSE<br/>''Status: Done.''<br />
|Olli<br />
|- <br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
==Social Events==<br />
<br />
===Party===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Organize barbecue food/grill/dishes<br/>''BBQ comes from Metzger Wolf, everything confirmned''<br />
|Henne, Olli<br />
|- <br />
|Buy red/white wine and organize enough glasses<br />
|Cboltz, Henne<br />
|-<br />
|Invite the companies at Zentrifuge to the party and inform them of the conference<br />
|Henne<br />
|- <br />
|}<br />
<br />
===Afternoon Program===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|}<br />
<br />
[[Category:Conference]]</div>Kfreitaghttps://en.opensuse.org/index.php?title=openSUSE:Conference_todo_list&diff=42736openSUSE:Conference todo list2011-08-29T15:11:01Z<p>Kfreitag: /* Party */</p>
<hr />
<div>{{Conference organizing navbar}}<br />
{{Intro|The following is a list of tasks to be completed for the organization of the upcoming openSUSE 2011 Conference. Even if a task is assigned, you can still volunteer to assist. We encourage everyone to take something fun that they can enjoy and develop with.}}<br />
<br />
==How to handle this page==<br />
# If you do a task put it onto this list<br />
# If you take over a task add your name to it<br />
# If you finish a task remove it from this list<br />
# If you didn't do 1,2 or 3 don't touch this page! This is not a wishlist or collection of ideas!<br />
<br />
==Marketing==<br />
This is tracked on [[openSUSE:Conference_promotion_todo_list]]<br />
<br />
==Program==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
| Ask the speakers to blog about their submissions -CFP<br />
| <br />
|-<br />
| Print the program that falls out of indico as A4 handouts and very large posters.<br />
| Robert<br />
|-<br />
| Finish the [[openSUSE:Conference speaker guidelines|guidelines for speakers]]<br />
|<br />
|- <br />
| Write and announce the [[openSUSE:Conference_code_of_conduct|conference code of conduct]]<br />
|<br />
|- <br />
| Organize Lightning Talks<br />
| Bryen<br />
|- <br />
| Organize a whiteboard for BoF scheduling for the registration desk<br />
|<br />
|}<br />
<br />
==Sponsoring==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|}<br />
<br />
===Travel Sponsorship===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Pay the money to the accepted applicants<br />
|Jos, AJaeger, AlanClark<br />
|-<br />
|}<br />
<br />
==Venue==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Find volunteers to record the main hall talks with their own cameras.<br />
|Bryen, Jürgen Weigert<br />
|-<br />
|Organize cleaning service for Wednesday the 7.<br/> ''Status: Meeting in the rooms in CW 35 with the chief of cleaning service, cleaning happens in CW 36''<br />
|Olli<br />
|-<br />
|Organize insurance for damage and theft of hardware<br />
|Ajaeger<br />
|-<br />
|Direction signs from the subway station to the venue<br />
|Jürgen Weigert<br />
|-<br />
|Direction signs inside the venue<br />
|Jürgen Weigert<br />
|-<br />
|}<br />
<br />
===Entry Area===<br />
<br />
====Lounge/Beergarden====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Buy flowers <br />
|<br />
|-<br />
|Organize old SUSE stuff for decoration<br/>''Status: Get from stock cw 35 to get an overview''<br />
|Olli<br />
|-<br />
|Get the SUSE sofas/tables to the venue<br/>''Status: Will be done with rental car on thursday, sept. 8th.''<br />
|Klaas, Tom, Olli<br />
|-<br />
|Organize a wardrobe<br />
|Klaas, Tom, Olli<br/>''Status: Olli will bring a wardrobe from home''<br />
|-<br />
|Organize 20 sets of benches and tables for the beergarden:<br/>''Status: 80 crates of Old Toad and 20 benches and tables will be on friday, 9th directly to zentrifuge by the brewery. The stuff is picked up again on thursday, 15 th. september''<br />
|Klaas<br />
|-<br />
|Organize waste bins<br />
|Klaas, Tom<br />
|-<br />
|Buy toys like a football, frisbee<br />
|Henne<br />
|}<br />
<br />
==== Snack Bar ([[openSUSE:Conference_snack_bar|details]]) ====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to <br />
|-<br />
|Organize the Bar from Coca Cola<br/>''Status: Coca Cola delivers at sept. 8th.''<br />
|Olli<br />
|-<br />
|Organize the sandwiches/softdrinks/ice-cream<br/>''Status:''<br />
* ''softdrinks: Delivery on sept. 8th''<br />
* ''sandwiches: every day delivery in the morning by Metzger Wolf''<br />
* ''ice-cream: Wont happen, too much hassle''<br />
|Olli<br />
|-<br />
|Organize Beer - <br/>''Status: see above: 80 beer crates will be delivered to the conference venue on sept. 9th.''<br />
|Klaas<br />
|-<br />
|Organize fridges for the softdrinks/beer<br/>''Status: Delivery by Coca Cola on sept. 8th to Zentrifuge''<br />
|Olli<br />
|-<br />
|Organize a coffee machine and plastic coffee mugs<br/>''Status: 2 pump machines from SUSE plus coffee, filters. Mugs to be bought at Metro or so.''<br />
|Olli<br />
|-<br />
|Buy 2 buckets, clouts, soap and a dish washing bowl as we only have water on the opposite of the main hall.<br />
|Ajaeger, Klaas<br />
|-<br />
|Organize a fruit basket<br />
|Klaas, Tom<br />
|- <br />
|}<br />
<br />
====Registration/Help Desk====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Find volunteers to run the registration desk: ''done, see [[openSUSE:Conference_volunteers|the Volunteers Page]]''<br />
|Klaas, Tom<br />
|-<br />
|Create [http://www.flickr.com/photos/blogwiese/3185417530/ pin buttons] as badges with name<br />
|Henne, Robert<br />
|-<br />
|Organize openSUSE/Sponsor goodies<br />
|Jos, Ajaeger, Izabel<br />
|- <br />
|Organize Bags to put goodies in<br />
|Robert<br />
|-<br />
|Organize Nürnberg brochures from the tourist info<br />
|Henne<br />
|-<br />
|Organize a network printer<br/>''Status: done.''<br />
|Olli<br />
|-<br />
|}<br />
<br />
===Main Room===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Bring the speaker desk from the all-hands area<br />
|Ajaeger<br />
|-<br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
===Ballroom===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
===Seminar Rooms===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Mark one of the small rooms upstairs as speaker room<br />
|Ajaeger<br />
|-<br />
|Organize 4 projectors from SUSE<br/>''Status: one is at Henne to check. Three others to investigate.''<br />
|Olli<br />
|-<br />
|Organize 4 projector screens<br />
|Christopher<br />
|-<br />
|Organize 4 flip charts from SUSE<br/>''Status: Done.''<br />
|Olli<br />
|- <br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
==Social Events==<br />
<br />
===Party===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Organize barbecue food/grill/dishes<br/>''BBQ comes from Metzger Wolf, everything confirmned''<br />
|Henne, Olli<br />
|- <br />
|Buy red/white wine and organize enough glasses<br />
|Cboltz, Henne<br />
|-<br />
|Invite the companies at Zentrifuge to the party and inform them of the conference<br />
|Henne<br />
|- <br />
|}<br />
<br />
===Afternoon Program===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|}<br />
<br />
[[Category:Conference]]</div>Kfreitaghttps://en.opensuse.org/index.php?title=openSUSE:Conference_todo_list&diff=42735openSUSE:Conference todo list2011-08-29T15:10:44Z<p>Kfreitag: /* Party */</p>
<hr />
<div>{{Conference organizing navbar}}<br />
{{Intro|The following is a list of tasks to be completed for the organization of the upcoming openSUSE 2011 Conference. Even if a task is assigned, you can still volunteer to assist. We encourage everyone to take something fun that they can enjoy and develop with.}}<br />
<br />
==How to handle this page==<br />
# If you do a task put it onto this list<br />
# If you take over a task add your name to it<br />
# If you finish a task remove it from this list<br />
# If you didn't do 1,2 or 3 don't touch this page! This is not a wishlist or collection of ideas!<br />
<br />
==Marketing==<br />
This is tracked on [[openSUSE:Conference_promotion_todo_list]]<br />
<br />
==Program==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
| Ask the speakers to blog about their submissions -CFP<br />
| <br />
|-<br />
| Print the program that falls out of indico as A4 handouts and very large posters.<br />
| Robert<br />
|-<br />
| Finish the [[openSUSE:Conference speaker guidelines|guidelines for speakers]]<br />
|<br />
|- <br />
| Write and announce the [[openSUSE:Conference_code_of_conduct|conference code of conduct]]<br />
|<br />
|- <br />
| Organize Lightning Talks<br />
| Bryen<br />
|- <br />
| Organize a whiteboard for BoF scheduling for the registration desk<br />
|<br />
|}<br />
<br />
==Sponsoring==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|}<br />
<br />
===Travel Sponsorship===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Pay the money to the accepted applicants<br />
|Jos, AJaeger, AlanClark<br />
|-<br />
|}<br />
<br />
==Venue==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Find volunteers to record the main hall talks with their own cameras.<br />
|Bryen, Jürgen Weigert<br />
|-<br />
|Organize cleaning service for Wednesday the 7.<br/> ''Status: Meeting in the rooms in CW 35 with the chief of cleaning service, cleaning happens in CW 36''<br />
|Olli<br />
|-<br />
|Organize insurance for damage and theft of hardware<br />
|Ajaeger<br />
|-<br />
|Direction signs from the subway station to the venue<br />
|Jürgen Weigert<br />
|-<br />
|Direction signs inside the venue<br />
|Jürgen Weigert<br />
|-<br />
|}<br />
<br />
===Entry Area===<br />
<br />
====Lounge/Beergarden====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Buy flowers <br />
|<br />
|-<br />
|Organize old SUSE stuff for decoration<br/>''Status: Get from stock cw 35 to get an overview''<br />
|Olli<br />
|-<br />
|Get the SUSE sofas/tables to the venue<br/>''Status: Will be done with rental car on thursday, sept. 8th.''<br />
|Klaas, Tom, Olli<br />
|-<br />
|Organize a wardrobe<br />
|Klaas, Tom, Olli<br/>''Status: Olli will bring a wardrobe from home''<br />
|-<br />
|Organize 20 sets of benches and tables for the beergarden:<br/>''Status: 80 crates of Old Toad and 20 benches and tables will be on friday, 9th directly to zentrifuge by the brewery. The stuff is picked up again on thursday, 15 th. september''<br />
|Klaas<br />
|-<br />
|Organize waste bins<br />
|Klaas, Tom<br />
|-<br />
|Buy toys like a football, frisbee<br />
|Henne<br />
|}<br />
<br />
==== Snack Bar ([[openSUSE:Conference_snack_bar|details]]) ====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to <br />
|-<br />
|Organize the Bar from Coca Cola<br/>''Status: Coca Cola delivers at sept. 8th.''<br />
|Olli<br />
|-<br />
|Organize the sandwiches/softdrinks/ice-cream<br/>''Status:''<br />
* ''softdrinks: Delivery on sept. 8th''<br />
* ''sandwiches: every day delivery in the morning by Metzger Wolf''<br />
* ''ice-cream: Wont happen, too much hassle''<br />
|Olli<br />
|-<br />
|Organize Beer - <br/>''Status: see above: 80 beer crates will be delivered to the conference venue on sept. 9th.''<br />
|Klaas<br />
|-<br />
|Organize fridges for the softdrinks/beer<br/>''Status: Delivery by Coca Cola on sept. 8th to Zentrifuge''<br />
|Olli<br />
|-<br />
|Organize a coffee machine and plastic coffee mugs<br/>''Status: 2 pump machines from SUSE plus coffee, filters. Mugs to be bought at Metro or so.''<br />
|Olli<br />
|-<br />
|Buy 2 buckets, clouts, soap and a dish washing bowl as we only have water on the opposite of the main hall.<br />
|Ajaeger, Klaas<br />
|-<br />
|Organize a fruit basket<br />
|Klaas, Tom<br />
|- <br />
|}<br />
<br />
====Registration/Help Desk====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Find volunteers to run the registration desk: ''done, see [[openSUSE:Conference_volunteers|the Volunteers Page]]''<br />
|Klaas, Tom<br />
|-<br />
|Create [http://www.flickr.com/photos/blogwiese/3185417530/ pin buttons] as badges with name<br />
|Henne, Robert<br />
|-<br />
|Organize openSUSE/Sponsor goodies<br />
|Jos, Ajaeger, Izabel<br />
|- <br />
|Organize Bags to put goodies in<br />
|Robert<br />
|-<br />
|Organize Nürnberg brochures from the tourist info<br />
|Henne<br />
|-<br />
|Organize a network printer<br/>''Status: done.''<br />
|Olli<br />
|-<br />
|}<br />
<br />
===Main Room===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Bring the speaker desk from the all-hands area<br />
|Ajaeger<br />
|-<br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
===Ballroom===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
===Seminar Rooms===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Mark one of the small rooms upstairs as speaker room<br />
|Ajaeger<br />
|-<br />
|Organize 4 projectors from SUSE<br/>''Status: one is at Henne to check. Three others to investigate.''<br />
|Olli<br />
|-<br />
|Organize 4 projector screens<br />
|Christopher<br />
|-<br />
|Organize 4 flip charts from SUSE<br/>''Status: Done.''<br />
|Olli<br />
|- <br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
==Social Events==<br />
<br />
===Party===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Organize barbecue food/grill/dishes<br/><br />
''BBQ comes from Metzger Wolf, everything confirmned''<br />
|Henne, Olli<br />
|- <br />
|Buy red/white wine and organize enough glasses<br />
|Cboltz, Henne<br />
|-<br />
|Invite the companies at Zentrifuge to the party and inform them of the conference<br />
|Henne<br />
|- <br />
|}<br />
<br />
===Afternoon Program===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|}<br />
<br />
[[Category:Conference]]</div>Kfreitaghttps://en.opensuse.org/index.php?title=openSUSE:Conference_todo_list&diff=42734openSUSE:Conference todo list2011-08-29T15:09:44Z<p>Kfreitag: /* Seminar Rooms */</p>
<hr />
<div>{{Conference organizing navbar}}<br />
{{Intro|The following is a list of tasks to be completed for the organization of the upcoming openSUSE 2011 Conference. Even if a task is assigned, you can still volunteer to assist. We encourage everyone to take something fun that they can enjoy and develop with.}}<br />
<br />
==How to handle this page==<br />
# If you do a task put it onto this list<br />
# If you take over a task add your name to it<br />
# If you finish a task remove it from this list<br />
# If you didn't do 1,2 or 3 don't touch this page! This is not a wishlist or collection of ideas!<br />
<br />
==Marketing==<br />
This is tracked on [[openSUSE:Conference_promotion_todo_list]]<br />
<br />
==Program==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
| Ask the speakers to blog about their submissions -CFP<br />
| <br />
|-<br />
| Print the program that falls out of indico as A4 handouts and very large posters.<br />
| Robert<br />
|-<br />
| Finish the [[openSUSE:Conference speaker guidelines|guidelines for speakers]]<br />
|<br />
|- <br />
| Write and announce the [[openSUSE:Conference_code_of_conduct|conference code of conduct]]<br />
|<br />
|- <br />
| Organize Lightning Talks<br />
| Bryen<br />
|- <br />
| Organize a whiteboard for BoF scheduling for the registration desk<br />
|<br />
|}<br />
<br />
==Sponsoring==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|}<br />
<br />
===Travel Sponsorship===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Pay the money to the accepted applicants<br />
|Jos, AJaeger, AlanClark<br />
|-<br />
|}<br />
<br />
==Venue==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Find volunteers to record the main hall talks with their own cameras.<br />
|Bryen, Jürgen Weigert<br />
|-<br />
|Organize cleaning service for Wednesday the 7.<br/> ''Status: Meeting in the rooms in CW 35 with the chief of cleaning service, cleaning happens in CW 36''<br />
|Olli<br />
|-<br />
|Organize insurance for damage and theft of hardware<br />
|Ajaeger<br />
|-<br />
|Direction signs from the subway station to the venue<br />
|Jürgen Weigert<br />
|-<br />
|Direction signs inside the venue<br />
|Jürgen Weigert<br />
|-<br />
|}<br />
<br />
===Entry Area===<br />
<br />
====Lounge/Beergarden====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Buy flowers <br />
|<br />
|-<br />
|Organize old SUSE stuff for decoration<br/>''Status: Get from stock cw 35 to get an overview''<br />
|Olli<br />
|-<br />
|Get the SUSE sofas/tables to the venue<br/>''Status: Will be done with rental car on thursday, sept. 8th.''<br />
|Klaas, Tom, Olli<br />
|-<br />
|Organize a wardrobe<br />
|Klaas, Tom, Olli<br/>''Status: Olli will bring a wardrobe from home''<br />
|-<br />
|Organize 20 sets of benches and tables for the beergarden:<br/>''Status: 80 crates of Old Toad and 20 benches and tables will be on friday, 9th directly to zentrifuge by the brewery. The stuff is picked up again on thursday, 15 th. september''<br />
|Klaas<br />
|-<br />
|Organize waste bins<br />
|Klaas, Tom<br />
|-<br />
|Buy toys like a football, frisbee<br />
|Henne<br />
|}<br />
<br />
==== Snack Bar ([[openSUSE:Conference_snack_bar|details]]) ====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to <br />
|-<br />
|Organize the Bar from Coca Cola<br/>''Status: Coca Cola delivers at sept. 8th.''<br />
|Olli<br />
|-<br />
|Organize the sandwiches/softdrinks/ice-cream<br/>''Status:''<br />
* ''softdrinks: Delivery on sept. 8th''<br />
* ''sandwiches: every day delivery in the morning by Metzger Wolf''<br />
* ''ice-cream: Wont happen, too much hassle''<br />
|Olli<br />
|-<br />
|Organize Beer - <br/>''Status: see above: 80 beer crates will be delivered to the conference venue on sept. 9th.''<br />
|Klaas<br />
|-<br />
|Organize fridges for the softdrinks/beer<br/>''Status: Delivery by Coca Cola on sept. 8th to Zentrifuge''<br />
|Olli<br />
|-<br />
|Organize a coffee machine and plastic coffee mugs<br/>''Status: 2 pump machines from SUSE plus coffee, filters. Mugs to be bought at Metro or so.''<br />
|Olli<br />
|-<br />
|Buy 2 buckets, clouts, soap and a dish washing bowl as we only have water on the opposite of the main hall.<br />
|Ajaeger, Klaas<br />
|-<br />
|Organize a fruit basket<br />
|Klaas, Tom<br />
|- <br />
|}<br />
<br />
====Registration/Help Desk====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Find volunteers to run the registration desk: ''done, see [[openSUSE:Conference_volunteers|the Volunteers Page]]''<br />
|Klaas, Tom<br />
|-<br />
|Create [http://www.flickr.com/photos/blogwiese/3185417530/ pin buttons] as badges with name<br />
|Henne, Robert<br />
|-<br />
|Organize openSUSE/Sponsor goodies<br />
|Jos, Ajaeger, Izabel<br />
|- <br />
|Organize Bags to put goodies in<br />
|Robert<br />
|-<br />
|Organize Nürnberg brochures from the tourist info<br />
|Henne<br />
|-<br />
|Organize a network printer<br/>''Status: done.''<br />
|Olli<br />
|-<br />
|}<br />
<br />
===Main Room===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Bring the speaker desk from the all-hands area<br />
|Ajaeger<br />
|-<br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
===Ballroom===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
===Seminar Rooms===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Mark one of the small rooms upstairs as speaker room<br />
|Ajaeger<br />
|-<br />
|Organize 4 projectors from SUSE<br/>''Status: one is at Henne to check. Three others to investigate.''<br />
|Olli<br />
|-<br />
|Organize 4 projector screens<br />
|Christopher<br />
|-<br />
|Organize 4 flip charts from SUSE<br/>''Status: Done.''<br />
|Olli<br />
|- <br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
==Social Events==<br />
<br />
===Party===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Organize barbecue food/grill/dishes<br />
|Henne, Olli<br />
|- <br />
|Buy red/white wine and organize enough glasses<br />
|Cboltz, Henne<br />
|-<br />
|Invite the companies at Zentrifuge to the party and inform them of the conference<br />
|Henne<br />
|- <br />
|}<br />
<br />
===Afternoon Program===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|}<br />
<br />
[[Category:Conference]]</div>Kfreitaghttps://en.opensuse.org/index.php?title=openSUSE:Conference_todo_list&diff=42733openSUSE:Conference todo list2011-08-29T15:07:28Z<p>Kfreitag: /* Registration/Help Desk */</p>
<hr />
<div>{{Conference organizing navbar}}<br />
{{Intro|The following is a list of tasks to be completed for the organization of the upcoming openSUSE 2011 Conference. Even if a task is assigned, you can still volunteer to assist. We encourage everyone to take something fun that they can enjoy and develop with.}}<br />
<br />
==How to handle this page==<br />
# If you do a task put it onto this list<br />
# If you take over a task add your name to it<br />
# If you finish a task remove it from this list<br />
# If you didn't do 1,2 or 3 don't touch this page! This is not a wishlist or collection of ideas!<br />
<br />
==Marketing==<br />
This is tracked on [[openSUSE:Conference_promotion_todo_list]]<br />
<br />
==Program==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
| Ask the speakers to blog about their submissions -CFP<br />
| <br />
|-<br />
| Print the program that falls out of indico as A4 handouts and very large posters.<br />
| Robert<br />
|-<br />
| Finish the [[openSUSE:Conference speaker guidelines|guidelines for speakers]]<br />
|<br />
|- <br />
| Write and announce the [[openSUSE:Conference_code_of_conduct|conference code of conduct]]<br />
|<br />
|- <br />
| Organize Lightning Talks<br />
| Bryen<br />
|- <br />
| Organize a whiteboard for BoF scheduling for the registration desk<br />
|<br />
|}<br />
<br />
==Sponsoring==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|}<br />
<br />
===Travel Sponsorship===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Pay the money to the accepted applicants<br />
|Jos, AJaeger, AlanClark<br />
|-<br />
|}<br />
<br />
==Venue==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Find volunteers to record the main hall talks with their own cameras.<br />
|Bryen, Jürgen Weigert<br />
|-<br />
|Organize cleaning service for Wednesday the 7.<br/> ''Status: Meeting in the rooms in CW 35 with the chief of cleaning service, cleaning happens in CW 36''<br />
|Olli<br />
|-<br />
|Organize insurance for damage and theft of hardware<br />
|Ajaeger<br />
|-<br />
|Direction signs from the subway station to the venue<br />
|Jürgen Weigert<br />
|-<br />
|Direction signs inside the venue<br />
|Jürgen Weigert<br />
|-<br />
|}<br />
<br />
===Entry Area===<br />
<br />
====Lounge/Beergarden====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Buy flowers <br />
|<br />
|-<br />
|Organize old SUSE stuff for decoration<br/>''Status: Get from stock cw 35 to get an overview''<br />
|Olli<br />
|-<br />
|Get the SUSE sofas/tables to the venue<br/>''Status: Will be done with rental car on thursday, sept. 8th.''<br />
|Klaas, Tom, Olli<br />
|-<br />
|Organize a wardrobe<br />
|Klaas, Tom, Olli<br/>''Status: Olli will bring a wardrobe from home''<br />
|-<br />
|Organize 20 sets of benches and tables for the beergarden:<br/>''Status: 80 crates of Old Toad and 20 benches and tables will be on friday, 9th directly to zentrifuge by the brewery. The stuff is picked up again on thursday, 15 th. september''<br />
|Klaas<br />
|-<br />
|Organize waste bins<br />
|Klaas, Tom<br />
|-<br />
|Buy toys like a football, frisbee<br />
|Henne<br />
|}<br />
<br />
==== Snack Bar ([[openSUSE:Conference_snack_bar|details]]) ====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to <br />
|-<br />
|Organize the Bar from Coca Cola<br/>''Status: Coca Cola delivers at sept. 8th.''<br />
|Olli<br />
|-<br />
|Organize the sandwiches/softdrinks/ice-cream<br/>''Status:''<br />
* ''softdrinks: Delivery on sept. 8th''<br />
* ''sandwiches: every day delivery in the morning by Metzger Wolf''<br />
* ''ice-cream: Wont happen, too much hassle''<br />
|Olli<br />
|-<br />
|Organize Beer - <br/>''Status: see above: 80 beer crates will be delivered to the conference venue on sept. 9th.''<br />
|Klaas<br />
|-<br />
|Organize fridges for the softdrinks/beer<br/>''Status: Delivery by Coca Cola on sept. 8th to Zentrifuge''<br />
|Olli<br />
|-<br />
|Organize a coffee machine and plastic coffee mugs<br/>''Status: 2 pump machines from SUSE plus coffee, filters. Mugs to be bought at Metro or so.''<br />
|Olli<br />
|-<br />
|Buy 2 buckets, clouts, soap and a dish washing bowl as we only have water on the opposite of the main hall.<br />
|Ajaeger, Klaas<br />
|-<br />
|Organize a fruit basket<br />
|Klaas, Tom<br />
|- <br />
|}<br />
<br />
====Registration/Help Desk====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Find volunteers to run the registration desk: ''done, see [[openSUSE:Conference_volunteers|the Volunteers Page]]''<br />
|Klaas, Tom<br />
|-<br />
|Create [http://www.flickr.com/photos/blogwiese/3185417530/ pin buttons] as badges with name<br />
|Henne, Robert<br />
|-<br />
|Organize openSUSE/Sponsor goodies<br />
|Jos, Ajaeger, Izabel<br />
|- <br />
|Organize Bags to put goodies in<br />
|Robert<br />
|-<br />
|Organize Nürnberg brochures from the tourist info<br />
|Henne<br />
|-<br />
|Organize a network printer<br/>''Status: done.''<br />
|Olli<br />
|-<br />
|}<br />
<br />
===Main Room===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Bring the speaker desk from the all-hands area<br />
|Ajaeger<br />
|-<br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
===Ballroom===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
===Seminar Rooms===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Mark one of the small rooms upstairs as speaker room<br />
|Ajaeger<br />
|-<br />
|Organize 4 projectors from SUSE<br />
|Olli<br />
|-<br />
|Organize 4 projector screens<br />
|Christopher<br />
|-<br />
|Organize 4 flip charts from SUSE<br />
|Olli<br />
|- <br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
==Social Events==<br />
<br />
===Party===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Organize barbecue food/grill/dishes<br />
|Henne, Olli<br />
|- <br />
|Buy red/white wine and organize enough glasses<br />
|Cboltz, Henne<br />
|-<br />
|Invite the companies at Zentrifuge to the party and inform them of the conference<br />
|Henne<br />
|- <br />
|}<br />
<br />
===Afternoon Program===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|}<br />
<br />
[[Category:Conference]]</div>Kfreitaghttps://en.opensuse.org/index.php?title=openSUSE:Conference_todo_list&diff=42732openSUSE:Conference todo list2011-08-29T15:07:01Z<p>Kfreitag: /* Snack Bar (details) */</p>
<hr />
<div>{{Conference organizing navbar}}<br />
{{Intro|The following is a list of tasks to be completed for the organization of the upcoming openSUSE 2011 Conference. Even if a task is assigned, you can still volunteer to assist. We encourage everyone to take something fun that they can enjoy and develop with.}}<br />
<br />
==How to handle this page==<br />
# If you do a task put it onto this list<br />
# If you take over a task add your name to it<br />
# If you finish a task remove it from this list<br />
# If you didn't do 1,2 or 3 don't touch this page! This is not a wishlist or collection of ideas!<br />
<br />
==Marketing==<br />
This is tracked on [[openSUSE:Conference_promotion_todo_list]]<br />
<br />
==Program==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
| Ask the speakers to blog about their submissions -CFP<br />
| <br />
|-<br />
| Print the program that falls out of indico as A4 handouts and very large posters.<br />
| Robert<br />
|-<br />
| Finish the [[openSUSE:Conference speaker guidelines|guidelines for speakers]]<br />
|<br />
|- <br />
| Write and announce the [[openSUSE:Conference_code_of_conduct|conference code of conduct]]<br />
|<br />
|- <br />
| Organize Lightning Talks<br />
| Bryen<br />
|- <br />
| Organize a whiteboard for BoF scheduling for the registration desk<br />
|<br />
|}<br />
<br />
==Sponsoring==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|}<br />
<br />
===Travel Sponsorship===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Pay the money to the accepted applicants<br />
|Jos, AJaeger, AlanClark<br />
|-<br />
|}<br />
<br />
==Venue==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Find volunteers to record the main hall talks with their own cameras.<br />
|Bryen, Jürgen Weigert<br />
|-<br />
|Organize cleaning service for Wednesday the 7.<br/> ''Status: Meeting in the rooms in CW 35 with the chief of cleaning service, cleaning happens in CW 36''<br />
|Olli<br />
|-<br />
|Organize insurance for damage and theft of hardware<br />
|Ajaeger<br />
|-<br />
|Direction signs from the subway station to the venue<br />
|Jürgen Weigert<br />
|-<br />
|Direction signs inside the venue<br />
|Jürgen Weigert<br />
|-<br />
|}<br />
<br />
===Entry Area===<br />
<br />
====Lounge/Beergarden====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Buy flowers <br />
|<br />
|-<br />
|Organize old SUSE stuff for decoration<br/>''Status: Get from stock cw 35 to get an overview''<br />
|Olli<br />
|-<br />
|Get the SUSE sofas/tables to the venue<br/>''Status: Will be done with rental car on thursday, sept. 8th.''<br />
|Klaas, Tom, Olli<br />
|-<br />
|Organize a wardrobe<br />
|Klaas, Tom, Olli<br/>''Status: Olli will bring a wardrobe from home''<br />
|-<br />
|Organize 20 sets of benches and tables for the beergarden:<br/>''Status: 80 crates of Old Toad and 20 benches and tables will be on friday, 9th directly to zentrifuge by the brewery. The stuff is picked up again on thursday, 15 th. september''<br />
|Klaas<br />
|-<br />
|Organize waste bins<br />
|Klaas, Tom<br />
|-<br />
|Buy toys like a football, frisbee<br />
|Henne<br />
|}<br />
<br />
==== Snack Bar ([[openSUSE:Conference_snack_bar|details]]) ====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to <br />
|-<br />
|Organize the Bar from Coca Cola<br/>''Status: Coca Cola delivers at sept. 8th.''<br />
|Olli<br />
|-<br />
|Organize the sandwiches/softdrinks/ice-cream<br/>''Status:''<br />
* ''softdrinks: Delivery on sept. 8th''<br />
* ''sandwiches: every day delivery in the morning by Metzger Wolf''<br />
* ''ice-cream: Wont happen, too much hassle''<br />
|Olli<br />
|-<br />
|Organize Beer - <br/>''Status: see above: 80 beer crates will be delivered to the conference venue on sept. 9th.''<br />
|Klaas<br />
|-<br />
|Organize fridges for the softdrinks/beer<br/>''Status: Delivery by Coca Cola on sept. 8th to Zentrifuge''<br />
|Olli<br />
|-<br />
|Organize a coffee machine and plastic coffee mugs<br/>''Status: 2 pump machines from SUSE plus coffee, filters. Mugs to be bought at Metro or so.''<br />
|Olli<br />
|-<br />
|Buy 2 buckets, clouts, soap and a dish washing bowl as we only have water on the opposite of the main hall.<br />
|Ajaeger, Klaas<br />
|-<br />
|Organize a fruit basket<br />
|Klaas, Tom<br />
|- <br />
|}<br />
<br />
====Registration/Help Desk====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Find volunteers to run the registration desk: ''done, see [[openSUSE:Conference_volunteers|the Volunteers Page]]''<br />
|Klaas, Tom<br />
|-<br />
|Create [http://www.flickr.com/photos/blogwiese/3185417530/ pin buttons] as badges with name<br />
|Henne, Robert<br />
|-<br />
|Organize openSUSE/Sponsor goodies<br />
|Jos, Ajaeger, Izabel<br />
|- <br />
|Organize Bags to put goodies in<br />
|Robert<br />
|-<br />
|Organize Nürnberg brochures from the tourist info<br />
|Henne<br />
|-<br />
|Organize a network printer<br />
|Olli<br />
|-<br />
|}<br />
<br />
===Main Room===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Bring the speaker desk from the all-hands area<br />
|Ajaeger<br />
|-<br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
===Ballroom===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
===Seminar Rooms===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Mark one of the small rooms upstairs as speaker room<br />
|Ajaeger<br />
|-<br />
|Organize 4 projectors from SUSE<br />
|Olli<br />
|-<br />
|Organize 4 projector screens<br />
|Christopher<br />
|-<br />
|Organize 4 flip charts from SUSE<br />
|Olli<br />
|- <br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
==Social Events==<br />
<br />
===Party===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Organize barbecue food/grill/dishes<br />
|Henne, Olli<br />
|- <br />
|Buy red/white wine and organize enough glasses<br />
|Cboltz, Henne<br />
|-<br />
|Invite the companies at Zentrifuge to the party and inform them of the conference<br />
|Henne<br />
|- <br />
|}<br />
<br />
===Afternoon Program===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|}<br />
<br />
[[Category:Conference]]</div>Kfreitaghttps://en.opensuse.org/index.php?title=openSUSE:Conference_todo_list&diff=42730openSUSE:Conference todo list2011-08-29T14:57:56Z<p>Kfreitag: /* Lounge/Beergarden */</p>
<hr />
<div>{{Conference organizing navbar}}<br />
{{Intro|The following is a list of tasks to be completed for the organization of the upcoming openSUSE 2011 Conference. Even if a task is assigned, you can still volunteer to assist. We encourage everyone to take something fun that they can enjoy and develop with.}}<br />
<br />
==How to handle this page==<br />
# If you do a task put it onto this list<br />
# If you take over a task add your name to it<br />
# If you finish a task remove it from this list<br />
# If you didn't do 1,2 or 3 don't touch this page! This is not a wishlist or collection of ideas!<br />
<br />
==Marketing==<br />
This is tracked on [[openSUSE:Conference_promotion_todo_list]]<br />
<br />
==Program==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
| Ask the speakers to blog about their submissions -CFP<br />
| <br />
|-<br />
| Print the program that falls out of indico as A4 handouts and very large posters.<br />
| Robert<br />
|-<br />
| Finish the [[openSUSE:Conference speaker guidelines|guidelines for speakers]]<br />
|<br />
|- <br />
| Write and announce the [[openSUSE:Conference_code_of_conduct|conference code of conduct]]<br />
|<br />
|- <br />
| Organize Lightning Talks<br />
| Bryen<br />
|- <br />
| Organize a whiteboard for BoF scheduling for the registration desk<br />
|<br />
|}<br />
<br />
==Sponsoring==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|}<br />
<br />
===Travel Sponsorship===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Pay the money to the accepted applicants<br />
|Jos, AJaeger, AlanClark<br />
|-<br />
|}<br />
<br />
==Venue==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Find volunteers to record the main hall talks with their own cameras.<br />
|Bryen, Jürgen Weigert<br />
|-<br />
|Organize cleaning service for Wednesday the 7.<br/> ''Status: Meeting in the rooms in CW 35 with the chief of cleaning service, cleaning happens in CW 36''<br />
|Olli<br />
|-<br />
|Organize insurance for damage and theft of hardware<br />
|Ajaeger<br />
|-<br />
|Direction signs from the subway station to the venue<br />
|Jürgen Weigert<br />
|-<br />
|Direction signs inside the venue<br />
|Jürgen Weigert<br />
|-<br />
|}<br />
<br />
===Entry Area===<br />
<br />
====Lounge/Beergarden====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Buy flowers <br />
|<br />
|-<br />
|Organize old SUSE stuff for decoration<br/>''Status: Get from stock cw 35 to get an overview''<br />
|Olli<br />
|-<br />
|Get the SUSE sofas/tables to the venue<br/>''Status: Will be done with rental car on thursday, sept. 8th.''<br />
|Klaas, Tom, Olli<br />
|-<br />
|Organize a wardrobe<br />
|Klaas, Tom, Olli<br/>''Status: Olli will bring a wardrobe from home''<br />
|-<br />
|Organize 20 sets of benches and tables for the beergarden:<br/>''Status: 80 crates of Old Toad and 20 benches and tables will be on friday, 9th directly to zentrifuge by the brewery. The stuff is picked up again on thursday, 15 th. september''<br />
|Klaas<br />
|-<br />
|Organize waste bins<br />
|Klaas, Tom<br />
|-<br />
|Buy toys like a football, frisbee<br />
|Henne<br />
|}<br />
<br />
==== Snack Bar ([[openSUSE:Conference_snack_bar|details]]) ====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to <br />
|-<br />
|Organize the Bar from Coca Cola<br />
|Olli<br />
|-<br />
|Organize the sandwiches/softdrinks/ice-cream<br />
|Olli<br />
|-<br />
|Organize Beer - ''see above: 80 beer crates will be delivered to the conference venue on sept. 9th.''<br />
|Klaas<br />
|-<br />
|Organize fridges for the softdrinks/beer/ice-cream<br />
|Olli<br />
|-<br />
|Organize a coffee machine and plastic coffee mugs<br />
|Olli<br />
|-<br />
|Buy 2 buckets, clouts, soap and a dish washing bowl as we only have water on the opposite of the main hall.<br />
|Ajaeger, Klaas<br />
|-<br />
|Organize a fruit basket<br />
|Klaas, Tom<br />
|- <br />
|}<br />
<br />
====Registration/Help Desk====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Find volunteers to run the registration desk: ''done, see [[openSUSE:Conference_volunteers|the Volunteers Page]]''<br />
|Klaas, Tom<br />
|-<br />
|Create [http://www.flickr.com/photos/blogwiese/3185417530/ pin buttons] as badges with name<br />
|Henne, Robert<br />
|-<br />
|Organize openSUSE/Sponsor goodies<br />
|Jos, Ajaeger, Izabel<br />
|- <br />
|Organize Bags to put goodies in<br />
|Robert<br />
|-<br />
|Organize Nürnberg brochures from the tourist info<br />
|Henne<br />
|-<br />
|Organize a network printer<br />
|Olli<br />
|-<br />
|}<br />
<br />
===Main Room===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Bring the speaker desk from the all-hands area<br />
|Ajaeger<br />
|-<br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
===Ballroom===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
===Seminar Rooms===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Mark one of the small rooms upstairs as speaker room<br />
|Ajaeger<br />
|-<br />
|Organize 4 projectors from SUSE<br />
|Olli<br />
|-<br />
|Organize 4 projector screens<br />
|Christopher<br />
|-<br />
|Organize 4 flip charts from SUSE<br />
|Olli<br />
|- <br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
==Social Events==<br />
<br />
===Party===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Organize barbecue food/grill/dishes<br />
|Henne, Olli<br />
|- <br />
|Buy red/white wine and organize enough glasses<br />
|Cboltz, Henne<br />
|-<br />
|Invite the companies at Zentrifuge to the party and inform them of the conference<br />
|Henne<br />
|- <br />
|}<br />
<br />
===Afternoon Program===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|}<br />
<br />
[[Category:Conference]]</div>Kfreitaghttps://en.opensuse.org/index.php?title=openSUSE:Conference_todo_list&diff=42726openSUSE:Conference todo list2011-08-29T14:53:34Z<p>Kfreitag: /* Venue */</p>
<hr />
<div>{{Conference organizing navbar}}<br />
{{Intro|The following is a list of tasks to be completed for the organization of the upcoming openSUSE 2011 Conference. Even if a task is assigned, you can still volunteer to assist. We encourage everyone to take something fun that they can enjoy and develop with.}}<br />
<br />
==How to handle this page==<br />
# If you do a task put it onto this list<br />
# If you take over a task add your name to it<br />
# If you finish a task remove it from this list<br />
# If you didn't do 1,2 or 3 don't touch this page! This is not a wishlist or collection of ideas!<br />
<br />
==Marketing==<br />
This is tracked on [[openSUSE:Conference_promotion_todo_list]]<br />
<br />
==Program==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
| Ask the speakers to blog about their submissions -CFP<br />
| <br />
|-<br />
| Print the program that falls out of indico as A4 handouts and very large posters.<br />
| Robert<br />
|-<br />
| Finish the [[openSUSE:Conference speaker guidelines|guidelines for speakers]]<br />
|<br />
|- <br />
| Write and announce the [[openSUSE:Conference_code_of_conduct|conference code of conduct]]<br />
|<br />
|- <br />
| Organize Lightning Talks<br />
| Bryen<br />
|- <br />
| Organize a whiteboard for BoF scheduling for the registration desk<br />
|<br />
|}<br />
<br />
==Sponsoring==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|}<br />
<br />
===Travel Sponsorship===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Pay the money to the accepted applicants<br />
|Jos, AJaeger, AlanClark<br />
|-<br />
|}<br />
<br />
==Venue==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Find volunteers to record the main hall talks with their own cameras.<br />
|Bryen, Jürgen Weigert<br />
|-<br />
|Organize cleaning service for Wednesday the 7.<br/> ''Status: Meeting in the rooms in CW 35 with the chief of cleaning service, cleaning happens in CW 36''<br />
|Olli<br />
|-<br />
|Organize insurance for damage and theft of hardware<br />
|Ajaeger<br />
|-<br />
|Direction signs from the subway station to the venue<br />
|Jürgen Weigert<br />
|-<br />
|Direction signs inside the venue<br />
|Jürgen Weigert<br />
|-<br />
|}<br />
<br />
===Entry Area===<br />
<br />
====Lounge/Beergarden====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Buy flowers <br />
|<br />
|-<br />
|Organize old SUSE stuff for decoration<br />
|Olli<br />
|-<br />
|Get the SUSE sofas/tables to the venue<br />
|Klaas, Tom, Olli<br />
|-<br />
|Organize a wardrobe<br />
|Klaas, Tom, Olli<br />
|-<br />
|Organize 20 sets of benches and tables for the beergarden: ''80 crates of Old Toad and 20 benches and tables will be on friday, 9th directly to zentrifuge by the brewery. The stuff is picked up again on thursday, 15 th. september''<br />
|Klaas<br />
|-<br />
|Organize waste bins<br />
|Klaas, Tom<br />
|-<br />
|Buy toys like a football, frisbee<br />
|Henne<br />
|}<br />
<br />
==== Snack Bar ([[openSUSE:Conference_snack_bar|details]]) ====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to <br />
|-<br />
|Organize the Bar from Coca Cola<br />
|Olli<br />
|-<br />
|Organize the sandwiches/softdrinks/ice-cream<br />
|Olli<br />
|-<br />
|Organize Beer - ''see above: 80 beer crates will be delivered to the conference venue on sept. 9th.''<br />
|Klaas<br />
|-<br />
|Organize fridges for the softdrinks/beer/ice-cream<br />
|Olli<br />
|-<br />
|Organize a coffee machine and plastic coffee mugs<br />
|Olli<br />
|-<br />
|Buy 2 buckets, clouts, soap and a dish washing bowl as we only have water on the opposite of the main hall.<br />
|Ajaeger, Klaas<br />
|-<br />
|Organize a fruit basket<br />
|Klaas, Tom<br />
|- <br />
|}<br />
<br />
====Registration/Help Desk====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Find volunteers to run the registration desk: ''done, see [[openSUSE:Conference_volunteers|the Volunteers Page]]''<br />
|Klaas, Tom<br />
|-<br />
|Create [http://www.flickr.com/photos/blogwiese/3185417530/ pin buttons] as badges with name<br />
|Henne, Robert<br />
|-<br />
|Organize openSUSE/Sponsor goodies<br />
|Jos, Ajaeger, Izabel<br />
|- <br />
|Organize Bags to put goodies in<br />
|Robert<br />
|-<br />
|Organize Nürnberg brochures from the tourist info<br />
|Henne<br />
|-<br />
|Organize a network printer<br />
|Olli<br />
|-<br />
|}<br />
<br />
===Main Room===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Bring the speaker desk from the all-hands area<br />
|Ajaeger<br />
|-<br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
===Ballroom===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
===Seminar Rooms===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Mark one of the small rooms upstairs as speaker room<br />
|Ajaeger<br />
|-<br />
|Organize 4 projectors from SUSE<br />
|Olli<br />
|-<br />
|Organize 4 projector screens<br />
|Christopher<br />
|-<br />
|Organize 4 flip charts from SUSE<br />
|Olli<br />
|- <br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
==Social Events==<br />
<br />
===Party===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Organize barbecue food/grill/dishes<br />
|Henne, Olli<br />
|- <br />
|Buy red/white wine and organize enough glasses<br />
|Cboltz, Henne<br />
|-<br />
|Invite the companies at Zentrifuge to the party and inform them of the conference<br />
|Henne<br />
|- <br />
|}<br />
<br />
===Afternoon Program===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|}<br />
<br />
[[Category:Conference]]</div>Kfreitaghttps://en.opensuse.org/index.php?title=openSUSE:Conference_todo_list&diff=42724openSUSE:Conference todo list2011-08-29T14:52:49Z<p>Kfreitag: /* Venue */</p>
<hr />
<div>{{Conference organizing navbar}}<br />
{{Intro|The following is a list of tasks to be completed for the organization of the upcoming openSUSE 2011 Conference. Even if a task is assigned, you can still volunteer to assist. We encourage everyone to take something fun that they can enjoy and develop with.}}<br />
<br />
==How to handle this page==<br />
# If you do a task put it onto this list<br />
# If you take over a task add your name to it<br />
# If you finish a task remove it from this list<br />
# If you didn't do 1,2 or 3 don't touch this page! This is not a wishlist or collection of ideas!<br />
<br />
==Marketing==<br />
This is tracked on [[openSUSE:Conference_promotion_todo_list]]<br />
<br />
==Program==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
| Ask the speakers to blog about their submissions -CFP<br />
| <br />
|-<br />
| Print the program that falls out of indico as A4 handouts and very large posters.<br />
| Robert<br />
|-<br />
| Finish the [[openSUSE:Conference speaker guidelines|guidelines for speakers]]<br />
|<br />
|- <br />
| Write and announce the [[openSUSE:Conference_code_of_conduct|conference code of conduct]]<br />
|<br />
|- <br />
| Organize Lightning Talks<br />
| Bryen<br />
|- <br />
| Organize a whiteboard for BoF scheduling for the registration desk<br />
|<br />
|}<br />
<br />
==Sponsoring==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|}<br />
<br />
===Travel Sponsorship===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Pay the money to the accepted applicants<br />
|Jos, AJaeger, AlanClark<br />
|-<br />
|}<br />
<br />
==Venue==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Find volunteers to record the main hall talks with their own cameras.<br />
|Bryen, Jürgen Weigert<br />
|-<br />
|Organize cleaning service for Wednesday the 7., ''Status: Meeting in the rooms in CW 35 with the chief of cleaning service, cleaning happens in CW 36''<br />
|Olli<br />
|-<br />
|Organize insurance for damage and theft of hardware<br />
|Ajaeger<br />
|-<br />
|Direction signs from the subway station to the venue<br />
|Jürgen Weigert<br />
|-<br />
|Direction signs inside the venue<br />
|Jürgen Weigert<br />
|-<br />
|}<br />
<br />
===Entry Area===<br />
<br />
====Lounge/Beergarden====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Buy flowers <br />
|<br />
|-<br />
|Organize old SUSE stuff for decoration<br />
|Olli<br />
|-<br />
|Get the SUSE sofas/tables to the venue<br />
|Klaas, Tom, Olli<br />
|-<br />
|Organize a wardrobe<br />
|Klaas, Tom, Olli<br />
|-<br />
|Organize 20 sets of benches and tables for the beergarden: ''80 crates of Old Toad and 20 benches and tables will be on friday, 9th directly to zentrifuge by the brewery. The stuff is picked up again on thursday, 15 th. september''<br />
|Klaas<br />
|-<br />
|Organize waste bins<br />
|Klaas, Tom<br />
|-<br />
|Buy toys like a football, frisbee<br />
|Henne<br />
|}<br />
<br />
==== Snack Bar ([[openSUSE:Conference_snack_bar|details]]) ====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to <br />
|-<br />
|Organize the Bar from Coca Cola<br />
|Olli<br />
|-<br />
|Organize the sandwiches/softdrinks/ice-cream<br />
|Olli<br />
|-<br />
|Organize Beer - ''see above: 80 beer crates will be delivered to the conference venue on sept. 9th.''<br />
|Klaas<br />
|-<br />
|Organize fridges for the softdrinks/beer/ice-cream<br />
|Olli<br />
|-<br />
|Organize a coffee machine and plastic coffee mugs<br />
|Olli<br />
|-<br />
|Buy 2 buckets, clouts, soap and a dish washing bowl as we only have water on the opposite of the main hall.<br />
|Ajaeger, Klaas<br />
|-<br />
|Organize a fruit basket<br />
|Klaas, Tom<br />
|- <br />
|}<br />
<br />
====Registration/Help Desk====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Find volunteers to run the registration desk: ''done, see [[openSUSE:Conference_volunteers|the Volunteers Page]]''<br />
|Klaas, Tom<br />
|-<br />
|Create [http://www.flickr.com/photos/blogwiese/3185417530/ pin buttons] as badges with name<br />
|Henne, Robert<br />
|-<br />
|Organize openSUSE/Sponsor goodies<br />
|Jos, Ajaeger, Izabel<br />
|- <br />
|Organize Bags to put goodies in<br />
|Robert<br />
|-<br />
|Organize Nürnberg brochures from the tourist info<br />
|Henne<br />
|-<br />
|Organize a network printer<br />
|Olli<br />
|-<br />
|}<br />
<br />
===Main Room===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Bring the speaker desk from the all-hands area<br />
|Ajaeger<br />
|-<br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
===Ballroom===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
===Seminar Rooms===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Mark one of the small rooms upstairs as speaker room<br />
|Ajaeger<br />
|-<br />
|Organize 4 projectors from SUSE<br />
|Olli<br />
|-<br />
|Organize 4 projector screens<br />
|Christopher<br />
|-<br />
|Organize 4 flip charts from SUSE<br />
|Olli<br />
|- <br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
==Social Events==<br />
<br />
===Party===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Organize barbecue food/grill/dishes<br />
|Henne, Olli<br />
|- <br />
|Buy red/white wine and organize enough glasses<br />
|Cboltz, Henne<br />
|-<br />
|Invite the companies at Zentrifuge to the party and inform them of the conference<br />
|Henne<br />
|- <br />
|}<br />
<br />
===Afternoon Program===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|}<br />
<br />
[[Category:Conference]]</div>Kfreitaghttps://en.opensuse.org/index.php?title=openSUSE:Conference_todo_list&diff=42718openSUSE:Conference todo list2011-08-29T13:16:03Z<p>Kfreitag: /* Registration/Help Desk */</p>
<hr />
<div>{{Conference organizing navbar}}<br />
{{Intro|The following is a list of tasks to be completed for the organization of the upcoming openSUSE 2011 Conference. Even if a task is assigned, you can still volunteer to assist. We encourage everyone to take something fun that they can enjoy and develop with.}}<br />
<br />
==How to handle this page==<br />
# If you do a task put it onto this list<br />
# If you take over a task add your name to it<br />
# If you finish a task remove it from this list<br />
# If you didn't do 1,2 or 3 don't touch this page! This is not a wishlist or collection of ideas!<br />
<br />
==Marketing==<br />
This is tracked on [[openSUSE:Conference_promotion_todo_list]]<br />
<br />
==Program==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
| Ask the speakers to blog about their submissions -CFP<br />
| <br />
|-<br />
| Print the program that falls out of indico as A4 handouts and very large posters.<br />
| Robert<br />
|-<br />
| Finish the [[openSUSE:Conference speaker guidelines|guidelines for speakers]]<br />
|<br />
|- <br />
| Write and announce the [[openSUSE:Conference_code_of_conduct|conference code of conduct]]<br />
|<br />
|- <br />
| Organize Lightning Talks<br />
| Bryen<br />
|- <br />
| Organize a whiteboard for BoF scheduling for the registration desk<br />
|<br />
|}<br />
<br />
==Sponsoring==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|}<br />
<br />
===Travel Sponsorship===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Pay the money to the accepted applicants<br />
|Jos, AJaeger, AlanClark<br />
|-<br />
|}<br />
<br />
==Venue==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Find volunteers to record the main hall talks with their own cameras.<br />
|Bryen, Jürgen Weigert<br />
|-<br />
|Organize cleaning service for Wednesday the 7.<br />
|Olli<br />
|-<br />
|Organize insurance for damage and theft of hardware<br />
|Ajaeger<br />
|-<br />
|Direction signs from the subway station to the venue<br />
|Jürgen Weigert<br />
|-<br />
|Direction signs inside the venue<br />
|Jürgen Weigert<br />
|-<br />
|}<br />
<br />
===Entry Area===<br />
<br />
====Lounge/Beergarden====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Buy flowers <br />
|<br />
|-<br />
|Organize old SUSE stuff for decoration<br />
|Olli<br />
|-<br />
|Get the SUSE sofas/tables to the venue<br />
|Klaas, Tom, Olli<br />
|-<br />
|Organize a wardrobe<br />
|Klaas, Tom, Olli<br />
|-<br />
|Organize 20 sets of benches and tables for the beergarden: ''80 crates of Old Toad and 20 benches and tables will be on friday, 9th directly to zentrifuge by the brewery. The stuff is picked up again on thursday, 15 th. september''<br />
|Klaas<br />
|-<br />
|Organize waste bins<br />
|Klaas, Tom<br />
|-<br />
|Buy toys like a football, frisbee<br />
|Henne<br />
|}<br />
<br />
==== Snack Bar ([[openSUSE:Conference_snack_bar|details]]) ====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to <br />
|-<br />
|Organize the Bar from Coca Cola<br />
|Olli<br />
|-<br />
|Organize the sandwiches/softdrinks/ice-cream<br />
|Olli<br />
|-<br />
|Organize Beer - ''see above: 80 beer crates will be delivered to the conference venue on sept. 9th.''<br />
|Klaas<br />
|-<br />
|Organize fridges for the softdrinks/beer/ice-cream<br />
|Olli<br />
|-<br />
|Organize a coffee machine and plastic coffee mugs<br />
|Olli<br />
|-<br />
|Buy 2 buckets, clouts, soap and a dish washing bowl as we only have water on the opposite of the main hall.<br />
|Ajaeger, Klaas<br />
|-<br />
|Organize a fruit basket<br />
|Klaas, Tom<br />
|- <br />
|}<br />
<br />
====Registration/Help Desk====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Find volunteers to run the registration desk: ''done, see [[openSUSE:Conference_volunteers|the Volunteers Page]]''<br />
|Klaas, Tom<br />
|-<br />
|Create [http://www.flickr.com/photos/blogwiese/3185417530/ pin buttons] as badges with name<br />
|Henne, Robert<br />
|-<br />
|Organize openSUSE/Sponsor goodies<br />
|Jos, Ajaeger, Izabel<br />
|- <br />
|Organize Bags to put goodies in<br />
|Robert<br />
|-<br />
|Organize Nürnberg brochures from the tourist info<br />
|Henne<br />
|-<br />
|Organize a network printer<br />
|Olli<br />
|-<br />
|}<br />
<br />
===Main Room===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Bring the speaker desk from the all-hands area<br />
|Ajaeger<br />
|-<br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
===Ballroom===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
===Seminar Rooms===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Mark one of the small rooms upstairs as speaker room<br />
|Ajaeger<br />
|-<br />
|Organize 4 projectors from SUSE<br />
|Olli<br />
|-<br />
|Organize 4 projector screens<br />
|Christopher<br />
|-<br />
|Organize 4 flip charts from SUSE<br />
|Olli<br />
|- <br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
==Social Events==<br />
<br />
===Party===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Organize barbecue food/grill/dishes<br />
|Henne, Olli<br />
|- <br />
|Buy red/white wine and organize enough glasses<br />
|Cboltz, Henne<br />
|-<br />
|Invite the companies at Zentrifuge to the party and inform them of the conference<br />
|Henne<br />
|- <br />
|}<br />
<br />
===Afternoon Program===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|}<br />
<br />
[[Category:Conference]]</div>Kfreitaghttps://en.opensuse.org/index.php?title=openSUSE:Conference_todo_list&diff=42717openSUSE:Conference todo list2011-08-29T13:11:26Z<p>Kfreitag: /* Snack Bar (details) */</p>
<hr />
<div>{{Conference organizing navbar}}<br />
{{Intro|The following is a list of tasks to be completed for the organization of the upcoming openSUSE 2011 Conference. Even if a task is assigned, you can still volunteer to assist. We encourage everyone to take something fun that they can enjoy and develop with.}}<br />
<br />
==How to handle this page==<br />
# If you do a task put it onto this list<br />
# If you take over a task add your name to it<br />
# If you finish a task remove it from this list<br />
# If you didn't do 1,2 or 3 don't touch this page! This is not a wishlist or collection of ideas!<br />
<br />
==Marketing==<br />
This is tracked on [[openSUSE:Conference_promotion_todo_list]]<br />
<br />
==Program==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
| Ask the speakers to blog about their submissions -CFP<br />
| <br />
|-<br />
| Print the program that falls out of indico as A4 handouts and very large posters.<br />
| Robert<br />
|-<br />
| Finish the [[openSUSE:Conference speaker guidelines|guidelines for speakers]]<br />
|<br />
|- <br />
| Write and announce the [[openSUSE:Conference_code_of_conduct|conference code of conduct]]<br />
|<br />
|- <br />
| Organize Lightning Talks<br />
| Bryen<br />
|- <br />
| Organize a whiteboard for BoF scheduling for the registration desk<br />
|<br />
|}<br />
<br />
==Sponsoring==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|}<br />
<br />
===Travel Sponsorship===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Pay the money to the accepted applicants<br />
|Jos, AJaeger, AlanClark<br />
|-<br />
|}<br />
<br />
==Venue==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Find volunteers to record the main hall talks with their own cameras.<br />
|Bryen, Jürgen Weigert<br />
|-<br />
|Organize cleaning service for Wednesday the 7.<br />
|Olli<br />
|-<br />
|Organize insurance for damage and theft of hardware<br />
|Ajaeger<br />
|-<br />
|Direction signs from the subway station to the venue<br />
|Jürgen Weigert<br />
|-<br />
|Direction signs inside the venue<br />
|Jürgen Weigert<br />
|-<br />
|}<br />
<br />
===Entry Area===<br />
<br />
====Lounge/Beergarden====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Buy flowers <br />
|<br />
|-<br />
|Organize old SUSE stuff for decoration<br />
|Olli<br />
|-<br />
|Get the SUSE sofas/tables to the venue<br />
|Klaas, Tom, Olli<br />
|-<br />
|Organize a wardrobe<br />
|Klaas, Tom, Olli<br />
|-<br />
|Organize 20 sets of benches and tables for the beergarden: ''80 crates of Old Toad and 20 benches and tables will be on friday, 9th directly to zentrifuge by the brewery. The stuff is picked up again on thursday, 15 th. september''<br />
|Klaas<br />
|-<br />
|Organize waste bins<br />
|Klaas, Tom<br />
|-<br />
|Buy toys like a football, frisbee<br />
|Henne<br />
|}<br />
<br />
==== Snack Bar ([[openSUSE:Conference_snack_bar|details]]) ====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to <br />
|-<br />
|Organize the Bar from Coca Cola<br />
|Olli<br />
|-<br />
|Organize the sandwiches/softdrinks/ice-cream<br />
|Olli<br />
|-<br />
|Organize Beer - ''see above: 80 beer crates will be delivered to the conference venue on sept. 9th.''<br />
|Klaas<br />
|-<br />
|Organize fridges for the softdrinks/beer/ice-cream<br />
|Olli<br />
|-<br />
|Organize a coffee machine and plastic coffee mugs<br />
|Olli<br />
|-<br />
|Buy 2 buckets, clouts, soap and a dish washing bowl as we only have water on the opposite of the main hall.<br />
|Ajaeger, Klaas<br />
|-<br />
|Organize a fruit basket<br />
|Klaas, Tom<br />
|- <br />
|}<br />
<br />
====Registration/Help Desk====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Find volunteers to run the registration desk<br />
|Klaas, Tom<br />
|-<br />
|Create [http://www.flickr.com/photos/blogwiese/3185417530/ pin buttons] as badges with name<br />
|Henne, Robert<br />
|-<br />
|Organize openSUSE/Sponsor goodies<br />
|Jos, Ajaeger, Izabel<br />
|- <br />
|Organize Bags to put goodies in<br />
|Robert<br />
|-<br />
|Organize Nürnberg brochures from the tourist info<br />
|Henne<br />
|-<br />
|Organize a network printer<br />
|Olli<br />
|-<br />
|}<br />
<br />
===Main Room===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Bring the speaker desk from the all-hands area<br />
|Ajaeger<br />
|-<br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
===Ballroom===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
===Seminar Rooms===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Mark one of the small rooms upstairs as speaker room<br />
|Ajaeger<br />
|-<br />
|Organize 4 projectors from SUSE<br />
|Olli<br />
|-<br />
|Organize 4 projector screens<br />
|Christopher<br />
|-<br />
|Organize 4 flip charts from SUSE<br />
|Olli<br />
|- <br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
==Social Events==<br />
<br />
===Party===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Organize barbecue food/grill/dishes<br />
|Henne, Olli<br />
|- <br />
|Buy red/white wine and organize enough glasses<br />
|Cboltz, Henne<br />
|-<br />
|Invite the companies at Zentrifuge to the party and inform them of the conference<br />
|Henne<br />
|- <br />
|}<br />
<br />
===Afternoon Program===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|}<br />
<br />
[[Category:Conference]]</div>Kfreitaghttps://en.opensuse.org/index.php?title=openSUSE:Conference_todo_list&diff=42715openSUSE:Conference todo list2011-08-29T13:10:14Z<p>Kfreitag: /* Lounge/Beergarden */</p>
<hr />
<div>{{Conference organizing navbar}}<br />
{{Intro|The following is a list of tasks to be completed for the organization of the upcoming openSUSE 2011 Conference. Even if a task is assigned, you can still volunteer to assist. We encourage everyone to take something fun that they can enjoy and develop with.}}<br />
<br />
==How to handle this page==<br />
# If you do a task put it onto this list<br />
# If you take over a task add your name to it<br />
# If you finish a task remove it from this list<br />
# If you didn't do 1,2 or 3 don't touch this page! This is not a wishlist or collection of ideas!<br />
<br />
==Marketing==<br />
This is tracked on [[openSUSE:Conference_promotion_todo_list]]<br />
<br />
==Program==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
| Ask the speakers to blog about their submissions -CFP<br />
| <br />
|-<br />
| Print the program that falls out of indico as A4 handouts and very large posters.<br />
| Robert<br />
|-<br />
| Finish the [[openSUSE:Conference speaker guidelines|guidelines for speakers]]<br />
|<br />
|- <br />
| Write and announce the [[openSUSE:Conference_code_of_conduct|conference code of conduct]]<br />
|<br />
|- <br />
| Organize Lightning Talks<br />
| Bryen<br />
|- <br />
| Organize a whiteboard for BoF scheduling for the registration desk<br />
|<br />
|}<br />
<br />
==Sponsoring==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|}<br />
<br />
===Travel Sponsorship===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Pay the money to the accepted applicants<br />
|Jos, AJaeger, AlanClark<br />
|-<br />
|}<br />
<br />
==Venue==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Find volunteers to record the main hall talks with their own cameras.<br />
|Bryen, Jürgen Weigert<br />
|-<br />
|Organize cleaning service for Wednesday the 7.<br />
|Olli<br />
|-<br />
|Organize insurance for damage and theft of hardware<br />
|Ajaeger<br />
|-<br />
|Direction signs from the subway station to the venue<br />
|Jürgen Weigert<br />
|-<br />
|Direction signs inside the venue<br />
|Jürgen Weigert<br />
|-<br />
|}<br />
<br />
===Entry Area===<br />
<br />
====Lounge/Beergarden====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Buy flowers <br />
|<br />
|-<br />
|Organize old SUSE stuff for decoration<br />
|Olli<br />
|-<br />
|Get the SUSE sofas/tables to the venue<br />
|Klaas, Tom, Olli<br />
|-<br />
|Organize a wardrobe<br />
|Klaas, Tom, Olli<br />
|-<br />
|Organize 20 sets of benches and tables for the beergarden: ''80 crates of Old Toad and 20 benches and tables will be on friday, 9th directly to zentrifuge by the brewery. The stuff is picked up again on thursday, 15 th. september''<br />
|Klaas<br />
|-<br />
|Organize waste bins<br />
|Klaas, Tom<br />
|-<br />
|Buy toys like a football, frisbee<br />
|Henne<br />
|}<br />
<br />
==== Snack Bar ([[openSUSE:Conference_snack_bar|details]]) ====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to <br />
|-<br />
|Organize the Bar from Coca Cola<br />
|Olli<br />
|-<br />
|Organize the sandwiches/softdrinks/ice-cream<br />
|Olli<br />
|-<br />
|Organize Beer<br />
|Klaas<br />
|-<br />
|Organize fridges for the softdrinks/beer/ice-cream<br />
|Olli<br />
|-<br />
|Organize a coffee machine and plastic coffee mugs<br />
|Olli<br />
|-<br />
|Buy 2 buckets, clouts, soap and a dish washing bowl as we only have water on the opposite of the main hall.<br />
|Ajaeger, Klaas<br />
|-<br />
|Organize a fruit basket<br />
|Klaas, Tom<br />
|- <br />
|}<br />
<br />
====Registration/Help Desk====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Find volunteers to run the registration desk<br />
|Klaas, Tom<br />
|-<br />
|Create [http://www.flickr.com/photos/blogwiese/3185417530/ pin buttons] as badges with name<br />
|Henne, Robert<br />
|-<br />
|Organize openSUSE/Sponsor goodies<br />
|Jos, Ajaeger, Izabel<br />
|- <br />
|Organize Bags to put goodies in<br />
|Robert<br />
|-<br />
|Organize Nürnberg brochures from the tourist info<br />
|Henne<br />
|-<br />
|Organize a network printer<br />
|Olli<br />
|-<br />
|}<br />
<br />
===Main Room===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Bring the speaker desk from the all-hands area<br />
|Ajaeger<br />
|-<br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
===Ballroom===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
===Seminar Rooms===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Mark one of the small rooms upstairs as speaker room<br />
|Ajaeger<br />
|-<br />
|Organize 4 projectors from SUSE<br />
|Olli<br />
|-<br />
|Organize 4 projector screens<br />
|Christopher<br />
|-<br />
|Organize 4 flip charts from SUSE<br />
|Olli<br />
|- <br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
==Social Events==<br />
<br />
===Party===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Organize barbecue food/grill/dishes<br />
|Henne, Olli<br />
|- <br />
|Buy red/white wine and organize enough glasses<br />
|Cboltz, Henne<br />
|-<br />
|Invite the companies at Zentrifuge to the party and inform them of the conference<br />
|Henne<br />
|- <br />
|}<br />
<br />
===Afternoon Program===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|}<br />
<br />
[[Category:Conference]]</div>Kfreitaghttps://en.opensuse.org/index.php?title=openSUSE:Conference_todo_list&diff=42714openSUSE:Conference todo list2011-08-29T13:08:11Z<p>Kfreitag: /* Lounge/Beergarden */</p>
<hr />
<div>{{Conference organizing navbar}}<br />
{{Intro|The following is a list of tasks to be completed for the organization of the upcoming openSUSE 2011 Conference. Even if a task is assigned, you can still volunteer to assist. We encourage everyone to take something fun that they can enjoy and develop with.}}<br />
<br />
==How to handle this page==<br />
# If you do a task put it onto this list<br />
# If you take over a task add your name to it<br />
# If you finish a task remove it from this list<br />
# If you didn't do 1,2 or 3 don't touch this page! This is not a wishlist or collection of ideas!<br />
<br />
==Marketing==<br />
This is tracked on [[openSUSE:Conference_promotion_todo_list]]<br />
<br />
==Program==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
| Ask the speakers to blog about their submissions -CFP<br />
| <br />
|-<br />
| Print the program that falls out of indico as A4 handouts and very large posters.<br />
| Robert<br />
|-<br />
| Finish the [[openSUSE:Conference speaker guidelines|guidelines for speakers]]<br />
|<br />
|- <br />
| Write and announce the [[openSUSE:Conference_code_of_conduct|conference code of conduct]]<br />
|<br />
|- <br />
| Organize Lightning Talks<br />
| Bryen<br />
|- <br />
| Organize a whiteboard for BoF scheduling for the registration desk<br />
|<br />
|}<br />
<br />
==Sponsoring==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|}<br />
<br />
===Travel Sponsorship===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Pay the money to the accepted applicants<br />
|Jos, AJaeger, AlanClark<br />
|-<br />
|}<br />
<br />
==Venue==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Find volunteers to record the main hall talks with their own cameras.<br />
|Bryen, Jürgen Weigert<br />
|-<br />
|Organize cleaning service for Wednesday the 7.<br />
|Olli<br />
|-<br />
|Organize insurance for damage and theft of hardware<br />
|Ajaeger<br />
|-<br />
|Direction signs from the subway station to the venue<br />
|Jürgen Weigert<br />
|-<br />
|Direction signs inside the venue<br />
|Jürgen Weigert<br />
|-<br />
|}<br />
<br />
===Entry Area===<br />
<br />
====Lounge/Beergarden====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Buy flowers <br />
|<br />
|-<br />
|Organize old SUSE stuff for decoration<br />
|Olli<br />
|-<br />
|Get the SUSE sofas/tables to the venue<br />
|Klaas, Tom, Olli<br />
|-<br />
|Organize a wardrobe<br />
|Klaas, Tom, Olli<br />
|-<br />
|Organize 20 sets of benches and tables for the beergarden: ''delivery will be on friday, 9th directly to zentrifuge by the brewery. The stuff is picked up again on thursday, 15 th. september''<br />
|Klaas<br />
|-<br />
|Organize waste bins<br />
|Klaas, Tom<br />
|-<br />
|Buy toys like a football, frisbee<br />
|Henne<br />
|}<br />
<br />
==== Snack Bar ([[openSUSE:Conference_snack_bar|details]]) ====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to <br />
|-<br />
|Organize the Bar from Coca Cola<br />
|Olli<br />
|-<br />
|Organize the sandwiches/softdrinks/ice-cream<br />
|Olli<br />
|-<br />
|Organize Beer<br />
|Klaas<br />
|-<br />
|Organize fridges for the softdrinks/beer/ice-cream<br />
|Olli<br />
|-<br />
|Organize a coffee machine and plastic coffee mugs<br />
|Olli<br />
|-<br />
|Buy 2 buckets, clouts, soap and a dish washing bowl as we only have water on the opposite of the main hall.<br />
|Ajaeger, Klaas<br />
|-<br />
|Organize a fruit basket<br />
|Klaas, Tom<br />
|- <br />
|}<br />
<br />
====Registration/Help Desk====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Find volunteers to run the registration desk<br />
|Klaas, Tom<br />
|-<br />
|Create [http://www.flickr.com/photos/blogwiese/3185417530/ pin buttons] as badges with name<br />
|Henne, Robert<br />
|-<br />
|Organize openSUSE/Sponsor goodies<br />
|Jos, Ajaeger, Izabel<br />
|- <br />
|Organize Bags to put goodies in<br />
|Robert<br />
|-<br />
|Organize Nürnberg brochures from the tourist info<br />
|Henne<br />
|-<br />
|Organize a network printer<br />
|Olli<br />
|-<br />
|}<br />
<br />
===Main Room===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Bring the speaker desk from the all-hands area<br />
|Ajaeger<br />
|-<br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
===Ballroom===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
===Seminar Rooms===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Mark one of the small rooms upstairs as speaker room<br />
|Ajaeger<br />
|-<br />
|Organize 4 projectors from SUSE<br />
|Olli<br />
|-<br />
|Organize 4 projector screens<br />
|Christopher<br />
|-<br />
|Organize 4 flip charts from SUSE<br />
|Olli<br />
|- <br />
|Decorate the room<br />
|<br />
|-<br />
|}<br />
<br />
==Social Events==<br />
<br />
===Party===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Organize barbecue food/grill/dishes<br />
|Henne, Olli<br />
|- <br />
|Buy red/white wine and organize enough glasses<br />
|Cboltz, Henne<br />
|-<br />
|Invite the companies at Zentrifuge to the party and inform them of the conference<br />
|Henne<br />
|- <br />
|}<br />
<br />
===Afternoon Program===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|}<br />
<br />
[[Category:Conference]]</div>Kfreitaghttps://en.opensuse.org/index.php?title=openSUSE:Conference_snack_bar&diff=42712openSUSE:Conference snack bar2011-08-29T12:58:41Z<p>Kfreitag: /* Bar */</p>
<hr />
<div>{{Conference organizing navbar}}<br />
<br />
Links: [[openSUSE:Conference_todo_list#Snack_Bar_.28details.29|Todo list]] | <br />
[[openSUSE:Conference_volunteers#The_Snack_Bar|Volunteers]] <br />
<br />
=== Bar ===<br />
<br />
The bar will be a "mobile" bar from coca cola, delivery:<br />
Size:<br />
<br />
refrigerated display case<br />
<br />
=== Offers ===<br />
<br />
Sunday Lunch (13:00): Chilli con carne, Chilli sin carne with cream, bread 6 Euro<br />
<br />
Regular offers: Sandwiches, Sweets, Muffins, Brownies<br />
<br />
=== Prices ===</div>Kfreitaghttps://en.opensuse.org/index.php?title=File:Volunteers.jpg&diff=41775File:Volunteers.jpg2011-07-29T13:11:49Z<p>Kfreitag: uploaded a new version of &quot;File:Volunteers.jpg&quot;</p>
<hr />
<div></div>Kfreitaghttps://en.opensuse.org/index.php?title=File:Volunteers.jpg&diff=41767File:Volunteers.jpg2011-07-29T09:24:06Z<p>Kfreitag: </p>
<hr />
<div></div>Kfreitaghttps://en.opensuse.org/index.php?title=openSUSE:Conference_todo_list&diff=41741openSUSE:Conference todo list2011-07-28T12:11:34Z<p>Kfreitag: /* Beergarden */</p>
<hr />
<div>{{Conference organizing navbar}}<br />
{{Intro|The following is a list of tasks to be completed for the organization of the upcoming openSUSE 2011 Conference. Even if a task is assigned, you can still volunteer to assist. We encourage everyone to take something fun that they can enjoy and develop with.}}<br />
<br />
==How to handle this page==<br />
# If you do a task put it onto this list<br />
# If you take over a task add your name to it<br />
# If you finish a task remove it from this list<br />
# If you didn't do 1,2 or 3 don't touch this page! This is not a wishlist or collection of ideas!<br />
<br />
==Marketing==<br />
This is tracked on [[openSUSE:Conference_promotion_todo_list]]<br />
<br />
==Program==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
| Ask the speakers to blog about their submissions -CFP<br />
| <br />
|-<br />
| Print the program that falls out of indico as A4 handouts and very large posters.<br />
| Robert<br />
|-<br />
| Get a mobile app going for the program<br />
| Tom<br />
|-<br />
| Finish the [[openSUSE:Conference speaker guidelines|guidelines for speakers]]<br />
|<br />
|-<br />
|Find and announce a keynote speaker for Sunday<br />
|Jos<br />
|-<br />
|Find and announce a keynote speaker for Monday<br />
|AJ<br />
|-<br />
|Find and announce a keynote speaker for Tuesday<br />
|Klaas<br />
|-<br />
|Find and announce a keynote speaker for Wednesday<br />
|Vuntz<br />
|-<br />
| Announce the schedule once its reasonably done<br />
|<br />
|- <br />
| Write and announce the [[openSUSE:Conference_code_of_conduct|conference code of conduct]]<br />
|<br />
|- <br />
| Organize Lightning Talks<br />
| <br />
|- <br />
| Organize a printed BoF schedule or a whiteboard for BoF scheduling for the registration desk<br />
|<br />
|}<br />
<br />
==Budget==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Handle money for professional registration before the event!<br />
|Ajaeger, Jos, AlanClark<br />
|}<br />
<br />
==Sponsoring==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
| Find a sponsor to pay for the internet connection. We would need at least 10MBit, SDSL.<br />
| Izabel<br />
|-<br />
| Find a sponsor to pay for the WIFI network on site. We need access points to handle 300-500 people and ways to connect the 5 different rooms via wifi.<br />
| Ajaeger<br />
|-<br />
|}<br />
<br />
===Travel Sponsorship===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Review applications to [mailto:travel-support@opensuse.org travel-support@opensuse.org]<br />
|Bruno, Jos, Izabel, Henne<br />
|-<br />
|Pay the money to the accepted applicants<br />
|Jos, AJaeger, AlanClark<br />
|-<br />
|Discuss how we can work with external sponsors<br />
|Bruno, Jos, Izabel, Henne<br />
|-<br />
|Create a Visum Letter<br />
|[[User:Warlordfff|Kostas Koudaras]]<br />
|-<br />
|}<br />
<br />
==Venue==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Technical Support. Find 4 volunteers (2 downstairs/2 upstairs) for each day to act as techsupport for projector/mic/room support<br />
|<br />
|-<br />
|Find volunteers to record the main hall talks with their own cameras.<br />
|Bryen<br />
|-<br />
|Find volunteers to help setting the venue up on Friday. <br />
|Ajaeger<br />
|-<br />
|Organize cleaning, restroom services.<br />
|Ajaeger<br />
|-<br />
|Organize insurance for damage and theft of hardware<br />
|Ajaeger<br />
|-<br />
|Organize a van for setup and during the conference<br />
|Ajaeger<br />
|-<br />
|Organize a volunteer for each day to open/close the venue<br />
|Ajaeger<br />
|-<br />
|Direction signs from the subway station to the venue<br />
|Tom<br />
|-<br />
|Check the options to hang the huge openSUSE banner at the venue<br />
|Tom<br />
|-<br />
|}<br />
<br />
===Beergarden===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|organize 20 sets of benches and tables<br />
|Klaas<br />
|-<br />
| organize waste bins<br />
|Klaas, Tom<br />
|-<br />
|Check if we can bring toys like a football, frisbee etc. and organize them.<br />
|Freitag, Tom<br />
|}<br />
<br />
===Entry Area ===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Buy lightning and bring the existing ones<br />
|Klaas, Tom<br />
|-<br />
|Buy flowers <br />
|Klaas (Sara)<br />
|-<br />
|Organize old SUSE posters<br />
|Ajaeger, Izabel<br />
|-<br />
|Get the SUSE sofas/tables to the venue.<br />
|Klaas, Tom, OFecher<br />
|-<br />
|Organize a wardrobe.<br />
|Klaas, Tom, OFecher<br />
|}<br />
<br />
====Snack Bar====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to <br />
|-<br />
|Build bar out of the empty Old Toad cradles we have<br />
|Klaas, Tom<br />
|-<br />
|Organize the sandwiches/softdrinks/ice-cream<br />
|Olli, Klaas, Tom<br />
|-<br />
|Organize Beer<br />
|Klaas<br />
|-<br />
|Organize fridges for the softdrinks/beer/ice-cream<br />
|Olli<br />
|-<br />
|Organize a coffee machine and plastic coffee mugs<br />
|Olli<br />
|-<br />
|Organize volunteers (4) to run the bar and sell things<br />
|Ajaeger, Klaas<br />
|}<br />
<br />
====Registration/Help Desk====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Find volunteers to run the registration desk<br />
|Klaas, Tom<br />
|-<br />
|Create [http://www.flickr.com/photos/blogwiese/3185417530/ pin buttons] as badges. Different colours for orgas, speakers, simple attendees. Name/Nickname.<br />
* Machine including 1.000 buttons in 56mm costs 240€<br />
* A cutter for the paper costs 70€<br />
* Both can be used for other things (Keyrings, Magnets, Cap openers) too.<br />
|Henne<br />
|-<br />
|Organize openSUSE goodies/Sponsor goodies and bags.<br />
|Jos, Ajaeger, Izabel<br />
|- <br />
|}<br />
<br />
===Main Room===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Organize a PA<br />
* Must handle both speech and music<br />
* Wireless Headset for the speaker <br />
* 3 mobile microphones<br />
|Christopher<br />
|-<br />
|Organize a stage<br />
|Christopher<br />
|-<br />
|Take the speaker desk from the all-hands area<br />
|Ajaeger<br />
|-<br />
|Organize large projector and a screen<br />
|Christopher<br />
|-<br />
|Organize the chairs<br />
|Ajaeger, Izabel<br />
|}<br />
<br />
===Seminar Rooms===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Mark one of the small rooms upstairs as speaker room<br />
|Ajaeger<br />
|-<br />
|Organize 4 projectors from SUSE<br />
|Olli<br />
|-<br />
|Organize 4 projector screens<br />
|Christopher<br />
|-<br />
|Organize 4 flip charts from SUSE<br />
|Olli<br />
|- <br />
|}<br />
<br />
===Ballroom===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Organize a PA<br />
* Must handle speech<br />
* Wireless Headset for the speaker <br />
* 2 mobile microphones<br />
|Christopher<br />
|-<br />
|Get paper for darkening the room<br />
|Robert<br />
-<br />
|}<br />
<br />
==Social Events==<br />
<br />
===Party===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Organize a Band/DJ.<br />
|cwh<br />
|-<br />
|Organize barbecue food/grill/dishes<br />
|Henne/Olli<br />
|-<br />
|Organize entertainment: Bull Riding.<br />
* Need to check AC options at the venue. <br />
|Henne<br />
|- <br />
|Buy red/white wine and some wine glasses<br />
|Henne, Izabel<br />
|-<br />
|Invite the companies at Zentrifuge to the party and inform them of the conference<br />
|Henne<br />
|- <br />
|}<br />
<br />
===Afternoon Program===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Organize volunteers to organize an activity for Sunday evening. Ideas are: <br />
* A photo competition<br />
* geocaching<br />
* Ancient hardware exhibition<br />
* Computer Flea market<br />
* artist sessions<br />
* computer art<br />
* Sporting ideas such as BMX, Inliner, Soccer, human kicker game (Outdoor, huge hall)<br />
* RC Cars competitions (Huge Hall)<br />
* RC helicopters (Outdoor)<br />
* Grafity activities/classes?<br />
* there is a soccer hall nearby, soccer turnament, eg. KDE Hotspur against Kernel Crunchers FC?<br />
|Henne<br />
|-<br />
|Organize the "8bit music" workshop on Tuesday. <br />
|cwh<br />
|-<br />
|Organize the closing session on Wednesday<br />
|Jos<br />
|-<br />
|}<br />
<br />
==Hotels==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Check with the conference hotels about the contingent on August 1st to see if we need to push for extension.<br />
|Ajaeger<br />
|-<br />
|}<br />
<br />
[[Category:Conference]]</div>Kfreitaghttps://en.opensuse.org/index.php?title=openSUSE:Conference_todo_list&diff=41740openSUSE:Conference todo list2011-07-28T12:10:01Z<p>Kfreitag: /* Entry Area */</p>
<hr />
<div>{{Conference organizing navbar}}<br />
{{Intro|The following is a list of tasks to be completed for the organization of the upcoming openSUSE 2011 Conference. Even if a task is assigned, you can still volunteer to assist. We encourage everyone to take something fun that they can enjoy and develop with.}}<br />
<br />
==How to handle this page==<br />
# If you do a task put it onto this list<br />
# If you take over a task add your name to it<br />
# If you finish a task remove it from this list<br />
# If you didn't do 1,2 or 3 don't touch this page! This is not a wishlist or collection of ideas!<br />
<br />
==Marketing==<br />
This is tracked on [[openSUSE:Conference_promotion_todo_list]]<br />
<br />
==Program==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
| Ask the speakers to blog about their submissions -CFP<br />
| <br />
|-<br />
| Print the program that falls out of indico as A4 handouts and very large posters.<br />
| Robert<br />
|-<br />
| Get a mobile app going for the program<br />
| Tom<br />
|-<br />
| Finish the [[openSUSE:Conference speaker guidelines|guidelines for speakers]]<br />
|<br />
|-<br />
|Find and announce a keynote speaker for Sunday<br />
|Jos<br />
|-<br />
|Find and announce a keynote speaker for Monday<br />
|AJ<br />
|-<br />
|Find and announce a keynote speaker for Tuesday<br />
|Klaas<br />
|-<br />
|Find and announce a keynote speaker for Wednesday<br />
|Vuntz<br />
|-<br />
| Announce the schedule once its reasonably done<br />
|<br />
|- <br />
| Write and announce the [[openSUSE:Conference_code_of_conduct|conference code of conduct]]<br />
|<br />
|- <br />
| Organize Lightning Talks<br />
| <br />
|- <br />
| Organize a printed BoF schedule or a whiteboard for BoF scheduling for the registration desk<br />
|<br />
|}<br />
<br />
==Budget==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Handle money for professional registration before the event!<br />
|Ajaeger, Jos, AlanClark<br />
|}<br />
<br />
==Sponsoring==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
| Find a sponsor to pay for the internet connection. We would need at least 10MBit, SDSL.<br />
| Izabel<br />
|-<br />
| Find a sponsor to pay for the WIFI network on site. We need access points to handle 300-500 people and ways to connect the 5 different rooms via wifi.<br />
| Ajaeger<br />
|-<br />
|}<br />
<br />
===Travel Sponsorship===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Review applications to [mailto:travel-support@opensuse.org travel-support@opensuse.org]<br />
|Bruno, Jos, Izabel, Henne<br />
|-<br />
|Pay the money to the accepted applicants<br />
|Jos, AJaeger, AlanClark<br />
|-<br />
|Discuss how we can work with external sponsors<br />
|Bruno, Jos, Izabel, Henne<br />
|-<br />
|Create a Visum Letter<br />
|[[User:Warlordfff|Kostas Koudaras]]<br />
|-<br />
|}<br />
<br />
==Venue==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Technical Support. Find 4 volunteers (2 downstairs/2 upstairs) for each day to act as techsupport for projector/mic/room support<br />
|<br />
|-<br />
|Find volunteers to record the main hall talks with their own cameras.<br />
|Bryen<br />
|-<br />
|Find volunteers to help setting the venue up on Friday. <br />
|Ajaeger<br />
|-<br />
|Organize cleaning, restroom services.<br />
|Ajaeger<br />
|-<br />
|Organize insurance for damage and theft of hardware<br />
|Ajaeger<br />
|-<br />
|Organize a van for setup and during the conference<br />
|Ajaeger<br />
|-<br />
|Organize a volunteer for each day to open/close the venue<br />
|Ajaeger<br />
|-<br />
|Direction signs from the subway station to the venue<br />
|Tom<br />
|-<br />
|Check the options to hang the huge openSUSE banner at the venue<br />
|Tom<br />
|-<br />
|}<br />
<br />
===Beergarden===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|organize 20 sets of benches and tables<br />
|Klaas<br />
|-<br />
| organize sun shades<br />
|Ajaeger, Izabel<br />
|-<br />
| organize waste bins<br />
|Ajaeger, Izabel<br />
|-<br />
|Check if we can bring toys like a football, frisbee etc. and organize them.<br />
|Ajaeger, Henne<br />
|}<br />
<br />
===Entry Area ===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Buy lightning and bring the existing ones<br />
|Klaas, Tom<br />
|-<br />
|Buy flowers <br />
|Klaas (Sara)<br />
|-<br />
|Organize old SUSE posters<br />
|Ajaeger, Izabel<br />
|-<br />
|Get the SUSE sofas/tables to the venue.<br />
|Klaas, Tom, OFecher<br />
|-<br />
|Organize a wardrobe.<br />
|Klaas, Tom, OFecher<br />
|}<br />
<br />
====Snack Bar====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to <br />
|-<br />
|Build bar out of the empty Old Toad cradles we have<br />
|Klaas, Tom<br />
|-<br />
|Organize the sandwiches/softdrinks/ice-cream<br />
|Olli, Klaas, Tom<br />
|-<br />
|Organize Beer<br />
|Klaas<br />
|-<br />
|Organize fridges for the softdrinks/beer/ice-cream<br />
|Olli<br />
|-<br />
|Organize a coffee machine and plastic coffee mugs<br />
|Olli<br />
|-<br />
|Organize volunteers (4) to run the bar and sell things<br />
|Ajaeger, Klaas<br />
|}<br />
<br />
====Registration/Help Desk====<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Find volunteers to run the registration desk<br />
|Klaas, Tom<br />
|-<br />
|Create [http://www.flickr.com/photos/blogwiese/3185417530/ pin buttons] as badges. Different colours for orgas, speakers, simple attendees. Name/Nickname.<br />
* Machine including 1.000 buttons in 56mm costs 240€<br />
* A cutter for the paper costs 70€<br />
* Both can be used for other things (Keyrings, Magnets, Cap openers) too.<br />
|Henne<br />
|-<br />
|Organize openSUSE goodies/Sponsor goodies and bags.<br />
|Jos, Ajaeger, Izabel<br />
|- <br />
|}<br />
<br />
===Main Room===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Organize a PA<br />
* Must handle both speech and music<br />
* Wireless Headset for the speaker <br />
* 3 mobile microphones<br />
|Christopher<br />
|-<br />
|Organize a stage<br />
|Christopher<br />
|-<br />
|Take the speaker desk from the all-hands area<br />
|Ajaeger<br />
|-<br />
|Organize large projector and a screen<br />
|Christopher<br />
|-<br />
|Organize the chairs<br />
|Ajaeger, Izabel<br />
|}<br />
<br />
===Seminar Rooms===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Mark one of the small rooms upstairs as speaker room<br />
|Ajaeger<br />
|-<br />
|Organize 4 projectors from SUSE<br />
|Olli<br />
|-<br />
|Organize 4 projector screens<br />
|Christopher<br />
|-<br />
|Organize 4 flip charts from SUSE<br />
|Olli<br />
|- <br />
|}<br />
<br />
===Ballroom===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Organize a PA<br />
* Must handle speech<br />
* Wireless Headset for the speaker <br />
* 2 mobile microphones<br />
|Christopher<br />
|-<br />
|Get paper for darkening the room<br />
|Robert<br />
-<br />
|}<br />
<br />
==Social Events==<br />
<br />
===Party===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Organize a Band/DJ.<br />
|cwh<br />
|-<br />
|Organize barbecue food/grill/dishes<br />
|Henne/Olli<br />
|-<br />
|Organize entertainment: Bull Riding.<br />
* Need to check AC options at the venue. <br />
|Henne<br />
|- <br />
|Buy red/white wine and some wine glasses<br />
|Henne, Izabel<br />
|-<br />
|Invite the companies at Zentrifuge to the party and inform them of the conference<br />
|Henne<br />
|- <br />
|}<br />
<br />
===Afternoon Program===<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Organize volunteers to organize an activity for Sunday evening. Ideas are: <br />
* A photo competition<br />
* geocaching<br />
* Ancient hardware exhibition<br />
* Computer Flea market<br />
* artist sessions<br />
* computer art<br />
* Sporting ideas such as BMX, Inliner, Soccer, human kicker game (Outdoor, huge hall)<br />
* RC Cars competitions (Huge Hall)<br />
* RC helicopters (Outdoor)<br />
* Grafity activities/classes?<br />
* there is a soccer hall nearby, soccer turnament, eg. KDE Hotspur against Kernel Crunchers FC?<br />
|Henne<br />
|-<br />
|Organize the "8bit music" workshop on Tuesday. <br />
|cwh<br />
|-<br />
|Organize the closing session on Wednesday<br />
|Jos<br />
|-<br />
|}<br />
<br />
==Hotels==<br />
{|class="wikitable sortable" style="width: 95%;"<br />
!Task<br />
!Assigned to<br />
|-<br />
|Check with the conference hotels about the contingent on August 1st to see if we need to push for extension.<br />
|Ajaeger<br />
|-<br />
|}<br />
<br />
[[Category:Conference]]</div>Kfreitag