https://en.opensuse.org/api.php?action=feedcontributions&user=Rajko+m&feedformat=atomopenSUSE Wiki - User contributions [en]2024-03-28T09:14:24ZUser contributionsMediaWiki 1.37.6https://en.opensuse.org/index.php?title=openSUSE:OSEP_0001&diff=65460openSUSE:OSEP 00012013-12-14T07:59:05Z<p>Rajko m: Protected "openSUSE:OSEP 0001" ([edit=autoconfirmed] (indefinite) [move=autoconfirmed] (indefinite))</p>
<hr />
<div><pre>__________________________________________________________________<br />
OSEP: 0001<br />
Title: Process proposal: openSUSE Enhancement Proposal<br />
Version: 0.1<br />
Last-Modified: 10 Dec 2013<br />
Author: Jos Poortvliet <jpoortvliet@suse.de>, Antonio Larrosa <alarrosa@suse.de><br />
Status: Draft <br />
Type: Process<br />
Created: 02 Dec 2013<br />
Post-History: <br />
_____________________________________________________________________<br />
<br />
Process proposal: openSUSE Enhancement Proposal<br />
-----------------------------------------------<br />
<br />
OSEP (_openSUSE Enhancement Proposal_) is a document providing information<br />
to the openSUSE community or describing a process in Factory or its<br />
environment. The OSEP should provide a concise specification and rationale of<br />
the process it's explaining.<br />
<br />
OSEPs are intended to be the primary mechanisms for proposing major new<br />
procedures and for documenting the design decisions that have gone into<br />
Factory. The OSEP author is responsible for building consensus within the<br />
community and documenting dissenting opinions.<br />
<br />
Because the OSEPs are maintained as text files in a versioned repository, their<br />
revision history is the historical record of each proposal<br />
footnoteref:[note_repo, https://www.github.com/TBD].<br />
<br />
OSEP Types<br />
----------<br />
<br />
There are two kinds of OSEP:<br />
<br />
- An _Informational OSEP_ describes an issue, or provides general guidelines or<br />
information to the openSUSE developers, but does not propose a new feature.<br />
Informational OSEPs do not necessarily represent a community consensus or<br />
recommendation, so users and implementers are free to ignore Informational<br />
OSEPs or follow their advice.<br />
<br />
- A _Process OSEP_ describes a process surrounding Factory, or proposes a change<br />
to a process. They may propose an implementation, but not to packages; they<br />
often require community consensus; unlike Informational OSEPs, they are more<br />
than recommendations, and users are typically not free to ignore them.<br />
Examples include procedures, changes to the decision-making process, and<br />
changes to the tools or environment used in Factory development.<br />
<br />
Submitting an OSEP<br />
------------------<br />
<br />
The OSEP process begins with a new idea for openSUSE. It is highly recommended<br />
that a single OSEP contain a single key proposal or new idea. Small enhancements<br />
or patches don't need an OSEP.<br />
<br />
It's recommended that the author of an OSEP brings his/her idea to key people<br />
from the community to see the acceptance the idea would have before sending it<br />
for review. The received feedback should be introduced in the first draft<br />
document, so that it's as complete as possible and long open-ended discussions<br />
on public mailing lists are avoided.<br />
<br />
Once a draft is written in the style described below, it should be presented to<br />
the _opensuse-factory_ mailing list.<br />
<br />
OSEPs should be submitted in asciidoc format footnoteref:[asciidoc_userguide,<br />
http://www.methods.co.nz/asciidoc/userguide.html] with UTF-8 codification.<br />
<br />
OSEPs may include auxiliary files such as diagrams. Such files must be named<br />
+osep-XXXX-Y.ext+, where _XXXX_ is the OSEP number, _Y_ is a serial number<br />
(starting at 1), and _ext_ is replaced by the actual file extension (e.g.<br />
+png+).<br />
<br />
OSEP Review & Resolution<br />
------------------------<br />
<br />
Once an author has completed an OSEP, it will be reviewed and discussed at the<br />
Factory mailing list, who will find a consensus to accept or reject it.<br />
<br />
Once an OSEP has been accepted, the enhancement has to be implemented.<br />
Once this implementation is complete and accepted, the status will be<br />
changed to _Final_.<br />
<br />
An OSEP can also be assigned status _Deferred_. The OSEP author (or in his/her<br />
abscense, the Factory maintainers) can assign the OSEP this status when no<br />
progress is being made for some time. After an OSEP is deferred, it can be<br />
re-assigned to draft status.<br />
<br />
An OSEP can also be _Rejected_. Perhaps after all is said and done it was not a<br />
good idea. It is still important to have a record of this fact. The _Withdrawn_<br />
status is similar - it means that the OSEP author themselves has decided that<br />
the OSEP is actually a bad idea, or has accepted that a competing proposal is a<br />
better alternative.<br />
<br />
OSEPs can also be superseded by a different OSEP, rendering the original<br />
obsolete (where version 2 of a policy, for example, might replace version 1).<br />
<br />
The possible paths of the status of OSEPs are as follows:<br />
<br />
image::osep-0001-1.png[OSEP workflow]<br />
<br />
Some Informational and Process OSEPs may also have a status of _Active_ if they<br />
are never meant to be completed. E.g. OSEP-0001 (this OSEP).<br />
<br />
What belongs in a successful OSEP?<br />
----------------------------------<br />
<br />
Each OSEP should have the following parts:<br />
<br />
- *Preamble* -- RFC 822 style headers containing meta-data about the OSEP,<br />
including the OSEP number, a short descriptive title (limited to a maximum of<br />
44 characters), the names, and optionally the contact info for each author,<br />
etc.<br />
<br />
- *Abstract* -- a short (~200 word) description of the issue being addressed.<br />
<br />
- *Copyright/public domain* -- Each OSEP must either be explicitly labeled as<br />
placed in the public domain (see this OSEP as an example) or licensed under<br />
the Open Publication License footnoteref:[note_openpub_license,<br />
http://www.opencontent.org/openpub/].<br />
<br />
- *Specification* -- The technical specification should describe the specific<br />
areas of openSUSE that would be touched by this OSEP. If new functionality<br />
is being introduced, what packages will that functionality affect? If new<br />
policy, who will be affected?<br />
<br />
- *Motivation and Rationale* -- The motivation is critical for OSEPs that want<br />
to modify the openSUSE distribution. It should clearly explain why the<br />
existing policies are inadequate to address the problem that the OSEP solves.<br />
OSEP submissions without sufficient motivation may be rejected outright.<br />
+<br />
The rationale fleshes out the specification by describing what<br />
motivated the design and why particular design decisions were made. It should<br />
describe alternate designs that were considered and related work, e.g. how the<br />
enhancement has been done in other distributions.<br />
<br />
OSEP Header Preamble<br />
--------------------<br />
<br />
Each OSEP must begin with an RFC 822 style header preamble. The headers must<br />
appear in the following order. Headers marked with "*" are optional and are<br />
described below. All other headers are required.<br />
<br />
_____________________________________________________________________<br />
OSEP: <OSEP number><br />
Title: <OSEP title><br />
Version: <version string><br />
Last-Modified: <date string><br />
Author: <list of authors' real names and optionally, email addrs><br />
Status: <Draft | Active | Accepted | Deferred | Rejected |<br />
Withdrawn | Final | Superseded><br />
Type: <Informational | Process><br />
Created: <date created on, in dd-mmm-yyyy format><br />
Post-History: <dates of postings to opensuse-factory><br />
* Replaces: <OSEP number><br />
* Superseded-By: <OSEP number><br />
______________________________________________________________________<br />
<br />
The +Author+ header lists the names, and optionally the email addresses of all<br />
the authors/owners of the OSEP. The format of the Author header value must be<br />
<br />
Random J. User <address@dom.ain><br />
<br />
if the email address is included, and just<br />
<br />
Random J. User<br />
<br />
if the address is not given.<br />
<br />
If there are multiple authors, each should be on a separate line following RFC<br />
2822 continuation line conventions. Note that personal email addresses in OSEPs<br />
will be obscured as a defense against spam harvesters.<br />
<br />
The +Type+ header specifies the type of OSEP: +Informational+, or +Process+.<br />
<br />
The +Created+ header records the date that the OSEP was assigned a number, while<br />
+Post-History+ is used to record the dates of when new versions of the OSEP were<br />
posted to _opensuse-factory_ and/or _opensuse-project_. Both headers should be<br />
in _dd-mmm-yyyy_ format, e.g. _14-Aug-2001_.<br />
<br />
OSEPs may also have a +Superseded-By+ header indicating that an OSEP has been<br />
rendered obsolete by a later document; the value is the number of the OSEP that<br />
replaces the current document. The newer OSEP must have a +Replaces+ header<br />
containing the number of the OSEP that it rendered obsolete.<br />
<br />
<br />
Reporting OSEP Bugs, or Submitting OSEP Updates<br />
-----------------------------------------------<br />
<br />
For the early draft stages of the OSEP, it's best to send comments and changes<br />
directly to the OSEP author. For more mature, or finished OSEPs corrections<br />
should be submitted to openSUSE's bugzilla footnoteref:[note_bnc,<br />
https://bugzilla.novell.com/] so that changes don't get lost.<br />
<br />
Transferring OSEP Ownership<br />
---------------------------<br />
<br />
The Factory maintainers can transfer the ownership of an OSEP to another<br />
author if the original author does no longer have the time or interest in<br />
updating it or follow through with the OSEP process.<br />
<br />
Credits<br />
-------<br />
<br />
The OSEP concept, and, in fact, much of the text of this document, is liberally<br />
stolen from Python's PEP-0001<br />
footnote:[http://www.python.org/dev/peps/pep-0001/] (by Barry A. Warsaw, Jeremy<br />
Hylton, and David Goodger) and from Gentoo's GLEP-0001<br />
footnote:[http://www.gentoo.org/proj/en/glep/glep-0001.html] (by Grant<br />
Goodyear).<br />
<br />
Copyright<br />
---------<br />
<br />
This document has been placed in the public domain.<br />
</pre><br />
<br />
[[Category:OSEP]]</div>Rajko mhttps://en.opensuse.org/index.php?title=Category:OSEP&diff=65459Category:OSEP2013-12-14T07:58:29Z<p>Rajko m: Removed protection from "Category:OSEP"</p>
<hr />
<div>Listing of all OSEP starting with bootstrap 0001.</div>Rajko mhttps://en.opensuse.org/index.php?title=Category:OSEP&diff=65458Category:OSEP2013-12-14T07:57:43Z<p>Rajko m: Protected "Category:OSEP" ([edit=autoconfirmed] (indefinite) [move=autoconfirmed] (indefinite))</p>
<hr />
<div>Listing of all OSEP starting with bootstrap 0001.</div>Rajko mhttps://en.opensuse.org/index.php?title=Portal:OSEP/Topics&diff=65457Portal:OSEP/Topics2013-12-14T07:48:06Z<p>Rajko m: first OSEP</p>
<hr />
<div><!-- Manual listing with title and short intro --><br />
* [[openSUSE:OSEP 0001|OSEP 0001]] Process proposal: openSUSE Enhancement Proposal</div>Rajko mhttps://en.opensuse.org/index.php?title=openSUSE:OSEP_0001&diff=65456openSUSE:OSEP 00012013-12-14T07:44:39Z<p>Rajko m: copy of mail list text</p>
<hr />
<div><pre>__________________________________________________________________<br />
OSEP: 0001<br />
Title: Process proposal: openSUSE Enhancement Proposal<br />
Version: 0.1<br />
Last-Modified: 10 Dec 2013<br />
Author: Jos Poortvliet <jpoortvliet@suse.de>, Antonio Larrosa <alarrosa@suse.de><br />
Status: Draft <br />
Type: Process<br />
Created: 02 Dec 2013<br />
Post-History: <br />
_____________________________________________________________________<br />
<br />
Process proposal: openSUSE Enhancement Proposal<br />
-----------------------------------------------<br />
<br />
OSEP (_openSUSE Enhancement Proposal_) is a document providing information<br />
to the openSUSE community or describing a process in Factory or its<br />
environment. The OSEP should provide a concise specification and rationale of<br />
the process it's explaining.<br />
<br />
OSEPs are intended to be the primary mechanisms for proposing major new<br />
procedures and for documenting the design decisions that have gone into<br />
Factory. The OSEP author is responsible for building consensus within the<br />
community and documenting dissenting opinions.<br />
<br />
Because the OSEPs are maintained as text files in a versioned repository, their<br />
revision history is the historical record of each proposal<br />
footnoteref:[note_repo, https://www.github.com/TBD].<br />
<br />
OSEP Types<br />
----------<br />
<br />
There are two kinds of OSEP:<br />
<br />
- An _Informational OSEP_ describes an issue, or provides general guidelines or<br />
information to the openSUSE developers, but does not propose a new feature.<br />
Informational OSEPs do not necessarily represent a community consensus or<br />
recommendation, so users and implementers are free to ignore Informational<br />
OSEPs or follow their advice.<br />
<br />
- A _Process OSEP_ describes a process surrounding Factory, or proposes a change<br />
to a process. They may propose an implementation, but not to packages; they<br />
often require community consensus; unlike Informational OSEPs, they are more<br />
than recommendations, and users are typically not free to ignore them.<br />
Examples include procedures, changes to the decision-making process, and<br />
changes to the tools or environment used in Factory development.<br />
<br />
Submitting an OSEP<br />
------------------<br />
<br />
The OSEP process begins with a new idea for openSUSE. It is highly recommended<br />
that a single OSEP contain a single key proposal or new idea. Small enhancements<br />
or patches don't need an OSEP.<br />
<br />
It's recommended that the author of an OSEP brings his/her idea to key people<br />
from the community to see the acceptance the idea would have before sending it<br />
for review. The received feedback should be introduced in the first draft<br />
document, so that it's as complete as possible and long open-ended discussions<br />
on public mailing lists are avoided.<br />
<br />
Once a draft is written in the style described below, it should be presented to<br />
the _opensuse-factory_ mailing list.<br />
<br />
OSEPs should be submitted in asciidoc format footnoteref:[asciidoc_userguide,<br />
http://www.methods.co.nz/asciidoc/userguide.html] with UTF-8 codification.<br />
<br />
OSEPs may include auxiliary files such as diagrams. Such files must be named<br />
+osep-XXXX-Y.ext+, where _XXXX_ is the OSEP number, _Y_ is a serial number<br />
(starting at 1), and _ext_ is replaced by the actual file extension (e.g.<br />
+png+).<br />
<br />
OSEP Review & Resolution<br />
------------------------<br />
<br />
Once an author has completed an OSEP, it will be reviewed and discussed at the<br />
Factory mailing list, who will find a consensus to accept or reject it.<br />
<br />
Once an OSEP has been accepted, the enhancement has to be implemented.<br />
Once this implementation is complete and accepted, the status will be<br />
changed to _Final_.<br />
<br />
An OSEP can also be assigned status _Deferred_. The OSEP author (or in his/her<br />
abscense, the Factory maintainers) can assign the OSEP this status when no<br />
progress is being made for some time. After an OSEP is deferred, it can be<br />
re-assigned to draft status.<br />
<br />
An OSEP can also be _Rejected_. Perhaps after all is said and done it was not a<br />
good idea. It is still important to have a record of this fact. The _Withdrawn_<br />
status is similar - it means that the OSEP author themselves has decided that<br />
the OSEP is actually a bad idea, or has accepted that a competing proposal is a<br />
better alternative.<br />
<br />
OSEPs can also be superseded by a different OSEP, rendering the original<br />
obsolete (where version 2 of a policy, for example, might replace version 1).<br />
<br />
The possible paths of the status of OSEPs are as follows:<br />
<br />
image::osep-0001-1.png[OSEP workflow]<br />
<br />
Some Informational and Process OSEPs may also have a status of _Active_ if they<br />
are never meant to be completed. E.g. OSEP-0001 (this OSEP).<br />
<br />
What belongs in a successful OSEP?<br />
----------------------------------<br />
<br />
Each OSEP should have the following parts:<br />
<br />
- *Preamble* -- RFC 822 style headers containing meta-data about the OSEP,<br />
including the OSEP number, a short descriptive title (limited to a maximum of<br />
44 characters), the names, and optionally the contact info for each author,<br />
etc.<br />
<br />
- *Abstract* -- a short (~200 word) description of the issue being addressed.<br />
<br />
- *Copyright/public domain* -- Each OSEP must either be explicitly labeled as<br />
placed in the public domain (see this OSEP as an example) or licensed under<br />
the Open Publication License footnoteref:[note_openpub_license,<br />
http://www.opencontent.org/openpub/].<br />
<br />
- *Specification* -- The technical specification should describe the specific<br />
areas of openSUSE that would be touched by this OSEP. If new functionality<br />
is being introduced, what packages will that functionality affect? If new<br />
policy, who will be affected?<br />
<br />
- *Motivation and Rationale* -- The motivation is critical for OSEPs that want<br />
to modify the openSUSE distribution. It should clearly explain why the<br />
existing policies are inadequate to address the problem that the OSEP solves.<br />
OSEP submissions without sufficient motivation may be rejected outright.<br />
+<br />
The rationale fleshes out the specification by describing what<br />
motivated the design and why particular design decisions were made. It should<br />
describe alternate designs that were considered and related work, e.g. how the<br />
enhancement has been done in other distributions.<br />
<br />
OSEP Header Preamble<br />
--------------------<br />
<br />
Each OSEP must begin with an RFC 822 style header preamble. The headers must<br />
appear in the following order. Headers marked with "*" are optional and are<br />
described below. All other headers are required.<br />
<br />
_____________________________________________________________________<br />
OSEP: <OSEP number><br />
Title: <OSEP title><br />
Version: <version string><br />
Last-Modified: <date string><br />
Author: <list of authors' real names and optionally, email addrs><br />
Status: <Draft | Active | Accepted | Deferred | Rejected |<br />
Withdrawn | Final | Superseded><br />
Type: <Informational | Process><br />
Created: <date created on, in dd-mmm-yyyy format><br />
Post-History: <dates of postings to opensuse-factory><br />
* Replaces: <OSEP number><br />
* Superseded-By: <OSEP number><br />
______________________________________________________________________<br />
<br />
The +Author+ header lists the names, and optionally the email addresses of all<br />
the authors/owners of the OSEP. The format of the Author header value must be<br />
<br />
Random J. User <address@dom.ain><br />
<br />
if the email address is included, and just<br />
<br />
Random J. User<br />
<br />
if the address is not given.<br />
<br />
If there are multiple authors, each should be on a separate line following RFC<br />
2822 continuation line conventions. Note that personal email addresses in OSEPs<br />
will be obscured as a defense against spam harvesters.<br />
<br />
The +Type+ header specifies the type of OSEP: +Informational+, or +Process+.<br />
<br />
The +Created+ header records the date that the OSEP was assigned a number, while<br />
+Post-History+ is used to record the dates of when new versions of the OSEP were<br />
posted to _opensuse-factory_ and/or _opensuse-project_. Both headers should be<br />
in _dd-mmm-yyyy_ format, e.g. _14-Aug-2001_.<br />
<br />
OSEPs may also have a +Superseded-By+ header indicating that an OSEP has been<br />
rendered obsolete by a later document; the value is the number of the OSEP that<br />
replaces the current document. The newer OSEP must have a +Replaces+ header<br />
containing the number of the OSEP that it rendered obsolete.<br />
<br />
<br />
Reporting OSEP Bugs, or Submitting OSEP Updates<br />
-----------------------------------------------<br />
<br />
For the early draft stages of the OSEP, it's best to send comments and changes<br />
directly to the OSEP author. For more mature, or finished OSEPs corrections<br />
should be submitted to openSUSE's bugzilla footnoteref:[note_bnc,<br />
https://bugzilla.novell.com/] so that changes don't get lost.<br />
<br />
Transferring OSEP Ownership<br />
---------------------------<br />
<br />
The Factory maintainers can transfer the ownership of an OSEP to another<br />
author if the original author does no longer have the time or interest in<br />
updating it or follow through with the OSEP process.<br />
<br />
Credits<br />
-------<br />
<br />
The OSEP concept, and, in fact, much of the text of this document, is liberally<br />
stolen from Python's PEP-0001<br />
footnote:[http://www.python.org/dev/peps/pep-0001/] (by Barry A. Warsaw, Jeremy<br />
Hylton, and David Goodger) and from Gentoo's GLEP-0001<br />
footnote:[http://www.gentoo.org/proj/en/glep/glep-0001.html] (by Grant<br />
Goodyear).<br />
<br />
Copyright<br />
---------<br />
<br />
This document has been placed in the public domain.<br />
</pre><br />
<br />
[[Category:OSEP]]</div>Rajko mhttps://en.opensuse.org/index.php?title=Portal:OSEP/Navigation&diff=65455Portal:OSEP/Navigation2013-12-14T07:41:45Z<p>Rajko m: </p>
<hr />
<div><categorytree mode=pages hideroot=on>OSEP</categorytree></div>Rajko mhttps://en.opensuse.org/index.php?title=Portal:OSEP&diff=65454Portal:OSEP2013-12-14T07:40:14Z<p>Rajko m: category OSEP</p>
<hr />
<div><!-- This portal was created using Template:Portal template <br />
<br />
Left column<br />
--><div class="grid_11" style="float:left"><br />
{{Box-header|<big>Welcome to the {{PAGENAME}} Portal</big>|{{FULLPAGENAME}}/Intro|}}<br />
{{:{{FULLPAGENAME}}/Intro}}<br />
{{Box-footer|}}<br />
{{Box-header|Topics|{{FULLPAGENAME}}/Topics|}}<br />
{{:{{FULLPAGENAME}}/Topics}}<br />
{{Box-footer|}}<br />
</div><!--<br />
<br />
Right column<br />
--><div class="grid_5" style="float:right"><br />
{{Box-header|Navigation|{{FULLPAGENAME}}/Navigation|}}<br />
{{:{{FULLPAGENAME}}/Navigation}}<br />
{{Box-footer|}}<br />
</div><br />
<br />
<br style="clear: both;" /><br />
__NOTOC__ __NOEDITSECTION__<br />
[[Category:Portals|{{PAGENAME}}]]<br />
[[Category:OSEP]]</div>Rajko mhttps://en.opensuse.org/index.php?title=Category:OSEP&diff=65453Category:OSEP2013-12-14T07:39:14Z<p>Rajko m: description</p>
<hr />
<div>Listing of all OSEP starting with bootstrap 0001.</div>Rajko mhttps://en.opensuse.org/index.php?title=Portal:OSEP/Navigation&diff=65452Portal:OSEP/Navigation2013-12-14T07:37:48Z<p>Rajko m: listing of all OSEP</p>
<hr />
<div><categorytree>OSEP</categorytree></div>Rajko mhttps://en.opensuse.org/index.php?title=Portal:OSEP/Intro&diff=65451Portal:OSEP/Intro2013-12-14T07:34:13Z<p>Rajko m: basic about OSEP</p>
<hr />
<div>What is OSEP? <br />
<br />
OSEP (openSUSE Enhancement Proposal) is a document providing information<br />
to the openSUSE community or describing a process in Factory or its<br />
environment. The OSEP should provide a concise specification and rationale of the process it is explaining.<br />
<br />
OSEPs are intended to be the primary mechanisms for proposing major new<br />
procedures and for documenting the design decisions that have gone into<br />
Factory. The OSEP author is responsible for building consensus within the<br />
community and documenting dissenting opinions.</div>Rajko mhttps://en.opensuse.org/index.php?title=Portal:OSEP&diff=65450Portal:OSEP2013-12-14T07:31:05Z<p>Rajko m: base skeleton</p>
<hr />
<div><!-- This portal was created using Template:Portal template <br />
<br />
Left column<br />
--><div class="grid_11" style="float:left"><br />
{{Box-header|<big>Welcome to the {{PAGENAME}} Portal</big>|{{FULLPAGENAME}}/Intro|}}<br />
{{:{{FULLPAGENAME}}/Intro}}<br />
{{Box-footer|}}<br />
{{Box-header|Topics|{{FULLPAGENAME}}/Topics|}}<br />
{{:{{FULLPAGENAME}}/Topics}}<br />
{{Box-footer|}}<br />
</div><!--<br />
<br />
Right column<br />
--><div class="grid_5" style="float:right"><br />
{{Box-header|Navigation|{{FULLPAGENAME}}/Navigation|}}<br />
{{:{{FULLPAGENAME}}/Navigation}}<br />
{{Box-footer|}}<br />
</div><br />
<br />
<br style="clear: both;" /><br />
__NOTOC__ __NOEDITSECTION__<br />
[[Category:Portals|{{PAGENAME}}]]</div>Rajko mhttps://en.opensuse.org/index.php?title=openSUSE:Board_election_2013_platform_anditosan&diff=65449openSUSE:Board election 2013 platform anditosan2013-12-14T01:24:50Z<p>Rajko m: category</p>
<hr />
<div>{{Board navbar}}<br />
== Platform ==<br />
{{Info|'''Note:''' This page is used by the candidate of the board election as a platform to show his views and answer some standard questions. }}<br />
<br />
[[File:anditosan.jpg|300px|center]]<br />
<br />
[http://facebook.com/anditosan Facebook] [https://twitter.com/anditosan Twitter] [https://plus.google.com/117802949293805242912 Google +] [http://s1108.photobucket.com/user/anditosan/library Photobucket] [http://anditosan.deviantart.com Deviantart] [http://www.flickr.com/photos/97479886@N00 Flickr]<br />
<br />
==Introduction and Biography== <br />
I am Andres (Andy) Betts. I was born and raised in Chile until 2003 when I moved to the United States. Most people know me by "Anditosan," as I am no nick named on IRC. I am by definition a creative. I have tried to learn out of curiosity anything that comes my way. I have been a drawing artist, painter, comic book artist, singer, historian, technology enthusiast and a Linux fan. I am almost at my 30s (Party announcement coming soon!) and have been a participant of the openSUSE Community for about 3-4 years.<br />
I currently work as a web hosting specialist and I enjoy it thoroughly!<br />
<br />
== Major Issues ==<br />
<br />
==== Communication ====<br />
I believe it is important for the Board, and also the project as a whole, to have the best means of communication amongst each other. There is a strong bond that unites the openSUSE project, which other teams wish they had, yet we still need a stronger push for more communication from within our team. While there are standards of communication within our team--IRC, Email Lists, Conferences-- I believe there is still room for improvement. By that I mean to have a strong camaraderie between us. One that is welcoming and heartfelt. It is time for us to interact as friends in the project and not as unknowns. As a board member I will be ready to help new members and contributors to channel their passion for Linux through our project and welcome them to enjoy the wonderful opportunity that it is to be an openSUSE member.<br />
[[File:conference.png|left|500px]]<br />
<br />
==== Determination ====<br />
<br />
While most of us would not like to discuss this, as in any project, we face challenges. Working with a worldwide community is not easy, neither is it to steer the project in meaningful ways. Many times we would like to think that the project needs to let itself be, yet because of this lack of determination into steering the project, we lose on code, or other kinds of contributions, given to the project that we forget or pass unnoticed. There are many of us who would like to see our project be a beacon for new heights in technology advancement and for that we must work harder to find those interested in making our project a leader and boost their contributions. openSUSE is an excellent harness of those looking to enhance the project. We welcome you!<br />
<br />
==== Vision ====<br />
<br />
Our team prides itself in the wide focus of our project. We welcome everyone who is interested in our project to participate with no specific technical requirements. We welcome everyone to make a contribution and solidify Linux's position as a technology leader in the world. Wonderful new developments in mobile and even gaming are coming to our solid project. This huge influx of new development venues should stir our project into making stronger commitments to the advancement of technology and no let the opportunity of a strong project and a leader pass us by. As a board member I will strive to work hand to hand with my fellow board members to gather elements that will give our project a vision for the future. We cannot think only of our next release, we must think of our impact as a worldwide technological community.<br />
<br />
== Minor Issues ==<br />
<br />
====openSUSE Advocate Program====<br />
<br />
Our ambassador program was recently revamped and designed to work with our contributors around the world in more effective ways. Now we will have "Advocates," contributors looking to pass the word about our project in their local communities. Always looking to find a person to person contact that can better and strengthen our project. I believe this program needs further push for it to happen by actively looking for those willing to become an openSUSE Advocate. As a board member I will take on such task and strengthen the Advocate program.<br />
<br />
[[File:Summit2012.png|right|500px]]<br />
<br />
====Wiki Updates====<br />
Our team has recently voiced their concerns for lack of updates to our wiki pages. I have myself experienced lack of newer or more understandable information and have recently started a project of my own to help our Artwork wiki pages to reflect nuances in our project. However, artwork wiki pages are not the only ones in need of a revamp. For that I will dedicate time to identify and work on wiki pages that need updating. Bettering the wiki is a must. Long time contributors as well as new ones, rely heavily on our wiki pages to find useful information that can help them work on their individual projects.<br />
<br />
== Role of the board ==<br />
<br />
====Active====<br />
<br />
Our Board has alway been a stronghold of community building and management. A place where coordination and vision for the project is harnessed and strengthened. I believe that as a member of the board I will help enhance the board's message and work for our community. I will push for a Board that is actively engaged with the community and it's developments. Caring not only for problems of dissension which may arise, but also boosting positive action that can help our community grow.<br />
<br />
====Resourceful====<br />
<br />
Our community looks up to the Board for guidance and valuable input. As such, I believe, it is the task of the Board to be a source of information for our members in explaining community rules and traditions and also helping our members route their efforts into making effective contributions to the project.<br />
<br />
==Why you should vote for me?==<br />
<br />
<br />
<br />
== Aims/Goals ==<br />
<br />
I believe in Linux as a force of good in the world. I view our project as a leader in this technology advancements. We produce quality software for free, and as radical as that may sound, we do it passionately and selflessly. With such high stakes, I intend to provide the Board with a strong collaborator into making our project a solid one. I intend to strengthen our vision and new changes coming to our project. I intend to work with our members caring for their needs and aspirations.<br />
<br />
[[File:Summit2013.png|500px|middle]]<br />
<br />
== Endorsements ==<br />
''Room for your supporters to leave a word about you''<br />
<br />
=== Alan Clark ===<br />
<br />
It's great to see that Andi is seeking a position on the Board. He brings a unique perspective to the board, is a diligent community member and a positive influence to the community. He will be a great asset to the Board.<br />
-AlanClark<br />
<br />
=== Marguerite Su ===<br />
<br />
Andy is the most productive artist I see. You know, artists for a distribution has many limits. One of the most anti-human things is: You can't just design when ideas push you to. Andy's ideas are infinite and instinctive. They come out just the time you say "oh we need an idea". I hope this characteristic can spread to every corner of our community. We just never stop being creative!<br />
<br />
And I think currently our board are just "in one direction": Developers. No matter what you're known for, you must have developer background to reach there. I hope Andy's nomination can diversify our board a little bit, eg: We may need a marketing people keep tracking down the "trends", and a designer to improve our usability (Usability improvement can never reach an end) as well as look and feel. Andy is just that type of people.<br />
<br />
[[User:MargueriteSu|MargueriteSu]] ([[User talk:MargueriteSu|talk]]) 04:23, 3 December 2013 (UTC)<br />
<br />
=== Drew Adams ===<br />
I consider Andy a great friend, fun collaborator, and an all around great person! His contributions, involvement and leadership have helped the project in countless ways. He is the finest mix of determined passion, creativity, and skill. I am constantly impressed with Andy's abilities as a servant-leader. He is perfect for the Board... Vote for Andy and have a lot of fun!!<br />
<br />
--Drew Adams (aka [http://en.opensuse.org/User:druonysus Druonysus]) openSUSE Member & Ambassador<br />
<br />
=== Jos Poortvliet ===<br />
Andi has shown tremendous growth in his role in openSUSE, from an outsider sharing ideas to a team player and now team builder. He shows he's not giving up easily and open for learning. He gets stuff done, in a fun, collaborative and friendly way. Awesome. -- [[user:jospoortvliet|jospoortvliet]]<br />
<br />
=== CarlosRibeiro ===<br />
Working in a partnership and in a collaboration way with Andy for a while I got the opportunity to see how much he has growing during this years showing lots of commitment with the openSUSE Project and also with the people involved inside the project, not only in artwork field, but also has contributed with other areas like news and marketing too.<br />
He is a nice person that is pretty easily to work with as he have lots of experience and good creative mind. Last but not least he has proven many times that is a good teamplayer to have around or inside the Board as I understand and recommend it -- [[user:CarlosAlbertoNovell|CarlosRibeiro]]<br />
<br />
[[Category:Board]]</div>Rajko mhttps://en.opensuse.org/index.php?title=openSUSE:Marketing_priorities&diff=65416openSUSE:Marketing priorities2013-12-12T03:11:07Z<p>Rajko m: /* Mentoring & Karma */ category marketing</p>
<hr />
<div>{{Intro|This is about priorities right now (Dec, 2013). As Marketing team is rebooting, this is current state of priorities.<br />
<br />
Currently we collect draft ideas in temporary document at [https://docs.google.com/spreadsheet/ccc?key{{=}}0AsHNJIS5xTiDdDcydFM4cTRydG1GUGhmYlpMVWIwZXc#gid{{=}}0 Priorities for marketing] which is hosted at Google. The reasons:<br />
* server will not disappear at most inconvenient time as some free alternatives already did, <br />
* wiki is not well suited for concurrent work, ie. high frequency edits, but it can be used to store daily copy of this document. Format will be a bit different to make wiki editing easier.}}<br />
<br />
==News==<br />
* Description: What is news about.<br />
* Publishing time: One time, Periodic.<br />
* Source: Who is source of information? Teams, public online, public off line, etc.<br />
* List of outlets: Where information will be published? Mail list, wiki, news.o.o, forums.<br />
* Layout: Fancy, modest, simple, or describe it.<br />
* Medium: Wiki, forum, other online, pdf, odf, image, mix.<br />
<br />
===Announcements===<br />
* Description: As the name tells, announcements.<br />
* One time: Before event.<br />
* Source: Teams at openSUSE.<br />
* Layout: The simplest for the medium and outlet.<br />
* Medium: news.o.o, forums, mail list.<br />
* List of outlets:<br />
<br />
===Weekly news===<br />
* Description: Short recapitulation of previous week.<br />
* Periodic: Each week.<br />
* Source: Teams at openSUSE.<br />
* Layout: Simple that is easy to create and translate. Nothing more then a wiki page in its simplest form.<br />
* Medium: wiki.<br />
* List of outlets:<br />
<br />
===Monthly news===<br />
* Periodic: Each month.<br />
* Interesting events of past month.<br />
* Source: Weekly news with some additional work.<br />
* Medium: <br />
* Layout: Slightly fancier format than Weekly News. Some added pictures, for instance. <br />
<br />
===End year report=== <br />
* Periodic: Once a year.<br />
* Description: What we did last year.<br />
* Source: Monthly news, plus some original articles.<br />
* Medium: <br />
* Layout: Fancy, in multiple file formats.<br />
<br />
==Events==<br />
===FOSDEM14=== <br />
===OSC14=== <br />
===Latinoware===<br />
===Foz do Iguacu===<br />
* Where: Brazil <br />
===FISL===<br />
* Where: Porto Alegre - Brazil <br />
===Summit===<br />
===Launch Parties===<br />
* Where: Worldwide <br />
===Marketing Hackfest=== <br />
<br />
==Merchandize==<br />
===Box===<br />
===DVD=== <br />
===USB=== <br />
===T-shirts=== <br />
===Flyers=== <br />
===Banners=== <br />
===Stickers=== <br />
===Geekos=== <br />
===Posters=== <br />
<br />
==Presentation and Slides==<br />
===13.1===<br />
===About the Distro=== <br />
===Edu li-f-e===<br />
===About Educational=== <br />
===OBS===<br />
===Home Users===<br />
For new users or home users <br />
===Advanced Users===<br />
For advanced users <br />
===Developers===<br />
For developers <br />
===Project===<br />
About the project in general <br />
<br />
==Artwork and Identity==<br />
How to make the openSUSE identity and brand stronger from the marketing perspective <br />
<br />
==Mentoring & Karma== <br />
<br />
Certificate for Members as discussed few months ago during project meeting - IRC<br />
<br />
<br />
[[Category:Marketing]]</div>Rajko mhttps://en.opensuse.org/index.php?title=openSUSE:Marketing_priorities&diff=65415openSUSE:Marketing priorities2013-12-12T03:00:28Z<p>Rajko m: Initial version and some additions to google doc</p>
<hr />
<div>{{Intro|This is about priorities right now (Dec, 2013). As Marketing team is rebooting, this is current state of priorities.<br />
<br />
Currently we collect draft ideas in temporary document at [https://docs.google.com/spreadsheet/ccc?key{{=}}0AsHNJIS5xTiDdDcydFM4cTRydG1GUGhmYlpMVWIwZXc#gid{{=}}0 Priorities for marketing] which is hosted at Google. The reasons:<br />
* server will not disappear at most inconvenient time as some free alternatives already did, <br />
* wiki is not well suited for concurrent work, ie. high frequency edits, but it can be used to store daily copy of this document. Format will be a bit different to make wiki editing easier.}}<br />
<br />
==News==<br />
* Description: What is news about.<br />
* Publishing time: One time, Periodic.<br />
* Source: Who is source of information? Teams, public online, public off line, etc.<br />
* List of outlets: Where information will be published? Mail list, wiki, news.o.o, forums.<br />
* Layout: Fancy, modest, simple, or describe it.<br />
* Medium: Wiki, forum, other online, pdf, odf, image, mix.<br />
<br />
===Announcements===<br />
* Description: As the name tells, announcements.<br />
* One time: Before event.<br />
* Source: Teams at openSUSE.<br />
* Layout: The simplest for the medium and outlet.<br />
* Medium: news.o.o, forums, mail list.<br />
* List of outlets:<br />
<br />
===Weekly news===<br />
* Description: Short recapitulation of previous week.<br />
* Periodic: Each week.<br />
* Source: Teams at openSUSE.<br />
* Layout: Simple that is easy to create and translate. Nothing more then a wiki page in its simplest form.<br />
* Medium: wiki.<br />
* List of outlets:<br />
<br />
===Monthly news===<br />
* Periodic: Each month.<br />
* Interesting events of past month.<br />
* Source: Weekly news with some additional work.<br />
* Medium: <br />
* Layout: Slightly fancier format than Weekly News. Some added pictures, for instance. <br />
<br />
===End year report=== <br />
* Periodic: Once a year.<br />
* Description: What we did last year.<br />
* Source: Monthly news, plus some original articles.<br />
* Medium: <br />
* Layout: Fancy, in multiple file formats.<br />
<br />
==Events==<br />
===FOSDEM14=== <br />
===OSC14=== <br />
===Latinoware===<br />
===Foz do Iguacu===<br />
* Where: Brazil <br />
===FISL===<br />
* Where: Porto Alegre - Brazil <br />
===Summit===<br />
===Launch Parties===<br />
* Where: Worldwide <br />
===Marketing Hackfest=== <br />
<br />
==Merchandize==<br />
===Box===<br />
===DVD=== <br />
===USB=== <br />
===T-shirts=== <br />
===Flyers=== <br />
===Banners=== <br />
===Stickers=== <br />
===Geekos=== <br />
===Posters=== <br />
<br />
==Presentation and Slides==<br />
===13.1===<br />
===About the Distro=== <br />
===Edu li-f-e===<br />
===About Educational=== <br />
===OBS===<br />
===Home Users===<br />
For new users or home users <br />
===Advanced Users===<br />
For advanced users <br />
===Developers===<br />
For developers <br />
===Project===<br />
About the project in general <br />
<br />
==Artwork and Identity==<br />
How to make the openSUSE identity and brand stronger from the marketing perspective <br />
<br />
==Mentoring & Karma== <br />
<br />
Certificate for Members as discussed few months ago during project meeting - IRC</div>Rajko mhttps://en.opensuse.org/index.php?title=openSUSE:Build_Service_Concept_Trust&diff=65340openSUSE:Build Service Concept Trust2013-12-07T04:53:30Z<p>Rajko m: /* Status of this document */ correct link to old-en wiki</p>
<hr />
<div>{{Buildservice navbar}}<br />
[[Category:Build Service draft concepts]]<br />
=Status of this document=<br />
This document describes the preliminary concept for the integration of some metrics into the [http://build.opensuse.org openSUSE build service]. It is based on [http://old-en.opensuse.org/index.php?title=Build_Service/Concepts/Trust&oldid=70661 Adrian's brain dump] (in old en wiki) and inspired by many good talks with co-workers at SUSE and colleagues within the open source community. Please note that this concept only proposes possible metrics that may be implemented. Based on the feedback these will be chosen in the next weeks.<br />
<br />
All ideas and proposals are with a strong focus on the openSUSE Build Service, but they should be utilisable in other infrastructure parts of openSUSE. This document does not describe the [[openSUSE:Build_Service_Concept_Trust_Implementation|trust implementation]].<br />
<br />
Despite the fact that [[User:Markojung|Marko's]] thesis will focus on the proposed trust metrics, this paper proposes further characteristics (quality & maintenance) which came up during the interviews Marko did at SUSE.<br />
<br />
Feedback welcome!<br />
<br />
__TOC__<br />
<br />
= Aim of the project =<br />
The [https://build.opensuse.org openSUSE build service] offers everyone the opportunity to build packages for many Linux distributions with relatively little effort. Hence the amount of available versions and variants per package is comparatively high. Therefore we need a powerful but also simple instrument to evaluate these packages, which are immediately available at the [http://software.opensuse.org/search/ openSUSE software portal].<br />
<br />
This paper proposes some prospects for gaining many different values which can be classified in three main categories:<br />
* trust<br />
* ratings & acceptance<br />
* quality & maintenance<br />
For each category we can compute an accumulated value based on the sum of the weighted singled values, which can be represented for the user. An even more generic final score may also be computed. As a possible extension to this, an authenticated user should be able to configure individual scores based on the existing metrics to fulfil his individual needs.<br />
<br />
The whole project is mainly based on information retrieval, data mining and statistics, but also includes different aspects from other research areas. <br />
<br />
We intend to get as much software evaluated by this system as possible. Therefore, it is essential that the participation in this rating is as attractive as possible for the openSUSE build service community. Since a diverse group of people like the open source community will most likely not totally agree on all implemented metrics, each user can disable the whole system and may explicitly prohibit the computation of each possible value. <br />
<br />
Despite that all proposed values make an effort to evaluate a package and not its producers, this project does a lot of data mining. Therefore, it has to be evaluated if there are any violations of privacy. In addition to this, all metrics which would enable performance measurement of Novell employees should be disabled by default as soon as the employee flag is set for an account.<br />
<br />
= Short summary of possible metrics =<br />
== Trust ==<br />
:''Trust is a relationship of reliance. A trusted party is presumed to seek to fulfil policies, ethical codes, law and their previous promises. [http://en.wikipedia.org/wiki/Trust_(sociology)]''<br />
<br />
Because trust is of highly individual nature and extremely subjective, a widely accepted global trust level is hardly to derive for the process we would like to measure. Therefore, we need a commonly accepted method for characterizing a person's actions within the openSUSE build service.<br />
<br />
''Please note that all following metrics can not assure that someone who has malicious intentions and spares no effort, can also gain a high rating.''<br />
<br />
==== Criteria for trust rating====<br />
Everybody has his own criteria for defining what is trustworthy or not. In terms of software packaging it became clear within discussions with many fellow workers at SUSE that the three main factors are:<br />
* Carefulness<br />
* Reliability<br />
* Reactivity<br />
Because the weighting between these and further factors strongly depends on personal preferences, the openSUSE build service should enable the user to configure the relevance of each available value to his personal needs.<br />
<br />
=== Metrics ===<br />
* Code of conduct<br />''Binary value if the user accepted to follow some guiding principles.''<br />
* Proven identity<br />''The user has identified himself to the openSUSE project.''<br />
* Action based ratings<br />''Ratings for the user's requests (Imagine a feedback mechanism similar to a well known online auction and shopping site.).''<br />
* Trust network<br />''Each user can assign trust levels to other users and projects.''<br />
* Dependable relationships: <br />
** affiliation state<br />''A person may have one or more affiliations to openSUSE, e.g. by being employeed or beeing a business partner of Novell. Another example is an openSUSE membership.''<br />
** upstream affiliation<br />''A person may have a relation to upstream development, e.g. being developer, maintainer or packager.''<br />
* Reviews<br />''Each package may be reviewed on several criteria.''<br />
** Specfile reviewed by openSUSE maintainer<br />
** Code & patches reviewed by openSUSE maintainer<br />
** Code & patches reviewed by openSUSE security team<br />
* Official manufacturer tags<br />''Tag software as supplied by its manufacturer to enable users to use only official repositories.''<br />
<br />
== Ratings & Acceptance ==<br />
This is probably the most important category because it is the most interactive one and every user of the software portal may be able to contribute to it. <br />
<br />
=== Metrics ===<br />
* Popularity/Acceptance<br />
** Amount of Package Downloads<br />
** Amount of Repo-Metadata Downloads<br />''(Both values should be available as total, per time period, per version or per release.)''<br />
* User ratings <br />
<br />
== Quality & maintenance ==<br />
=== Metrics ===<br />
* rpmlint & lintian/linda<br />''Derive some quality metrics from rpmlint or lintian/linda results''<br />
* Package history / version numbers<br />''Check update frequency of a package against upstream updates.''<br />
* Availability for several architectures and products<br />''Keep a history of all builds on all architectures and products.''<br />
* Changelog<br />''Parse the changelog for cross references and extract some minimal information from the referenced bug trackers.''<br />
* Activity/vitality<br />
* Dependencies and reverse Build dependencies<br />
<br />
=== Not available metrics ===<br />
* Bug statistics<br />
** # open bugs<br />
** # blocker bugs<br />
** # critical bugs<br />
** # major bugs<br />
<br />
<br />
= Detailed metric descriptions =<br />
== Trust ==<br />
=== Methods for measuring trust ===<br />
==== Code of conduct ====<br />
If a user signs the code of conduct (some [http://en.opensuse.org/Guiding_Principles guiding principles] for openSUSE and the openSUSE build service), he states that he takes his work serious and his contributions have the main goal to bring a benefit to the whole community.<br />
<br />
Although this is a binary value, it shows whether or not someone grants to respect to the basic rules.<br />
<br />
==== Proven identity ====<br />
A user that identifies himself in a trusted way, by sending e.g. his work/living address, contact details or a copy of his id, in a trusted way to a trusted entity makes himself much more responsible for his work. A SUSE/Novell employee has done this identification by signing his work contract, but others shall be able to get on the same level by sending their id to a review board or an adequate standardized process. <br />
<br />
Several options are possible. For example, we could adopt the assurance process of [http://www.cacert.org CAcert.org], where a new user has to get approved by several existing ones, before he is able to create certificates. Another possibility is to request a user to submit his public [http://www.gnupg.org/ GNU Privacy Guard] key, which has to be signed by a given amount of well known openSUSE build service users.<br />
<br />
==== Action based ratings ====<br />
:Motivation: ''A person which is well known for doing great stuff within one or more projects is more trustworthy than a newbie doing his first steps in packaging.''<br />
<br />
With its open design, the openSUSE build service encourages its users to collaborate and share their knowledge. The collaboration process is mapped on so called [http://en.opensuse.org/Build_Service/Concepts/Submit_Request submit requests], properly meaning a user requests the addition of changes from a package to another one - typically from another project. The receiver of a request evaluates the submitted modifications and then chooses to accept or decline the request. <br />
<br />
We would like to add a rating to the submit request (and [http://en.opensuse.org/Build_Service/Concepts/Requests prospective ones]), so that every user can rate all his previously handled requests on a simple scale (excellent - worse). These ratings are stored in a central database containing some additional information (e.g. sender, source project, source package, receiver, target project, target package), so that two ratings, one with respect to a given project and an overall score, can be derived as soon as a sufficient sample quantity is available.<br />
<br />
These ratings can for example be displayed by the openSUSE build service clients with each new request or we can compute a per person rating for each project.<br />
<br />
==== Trust network ====<br />
Depending on the chosen implementation for identifying users, this value may also show how well known a user is within the openSUSE build service community. Therefore, a non binary value would make this fact more meaningful. Optionally, we can split this into a boolean value: has the user proven his id in a standardised process and a kind of social network where users may add rated links between each other or not? These ratings are highly subjective but we should use a well known scheme, like the [http://www.gnupg.org/gph/en/manual.html#AEN346 GNU Privacy Guard's levels] 'unknown', 'none', 'marginal' and 'full'.<br />
<br />
As an alternative to the GNU Privacy Guard approach, the [http://www.advogato.org/trust-metric.html Advogato Trust Metric] should be considered. It is based on a [http://c2.com/cgi/wiki?CapacityConstrainedFlowNetwork Capacity Constrained Flow Network] [http://en.wikipedia.org/wiki/Flow_network] and should therefore be more resistant against a massive attack. It is not that hard to understand and quite fast to compute.<br />
<br />
==== Dependable relationships: affiliation state ====<br />
If a group of people (this can be an open source project or a company) signs a contract to be reactive on reports and handle upcoming issues for a defined time frame for a repository, they prove their intent to maintain their software packages. Therefore, a given workforce has to be guaranteed during the term of the contracts. If an individual leaves the group, the remaining group has to nominate a substitute or the contract has to be suspended until the team is complete again. There should be a few levels mainly depending on the reaction time and team size. Employees of allied companies should fit into this relationship scheme.<br />
<br />
Novell employees have an even more dependable relationship.<br />
<br />
There should be about three to five levels for this relationship:<br />
* Novell employee<br />
* Novell contractor <br />
* openSUSE member<br />
* no relation<br />
<br />
==== Dependable relationships: upstream affiliation ====<br />
A person or a team with a strong connection to upstream may have a much higher interest in maintain their packages than people without any relation to the project. This may also apply for the quality of the packages.<br />
<br />
Due to the fact that a user may be maintainer of one or more openSUSE build service projects, there should be information per project available whether or not he has a relation to the upstream project, e.g. <br />
* developer<br />
* maintainer<br />
* packager<br />
* no relation<br />
<br />
==== Official manufacturer tags ====<br />
Some users only want to install manufacturer provided software. Therefore we should add manufacturer tags for each project which are maintained by a team of bureaucrats. A user may then choose between all available tags from which vendors he would like to install software on his systems. <br />
<br />
An initial approach may be implemented by assigning a set of signing keys to manufacturers or something similar.<br />
<br />
== User ratings & acceptance==<br />
This is probably the most important category beneath trust because it is the most interactive one and every user of the software portal may be able to contribute to it.<br />
<br />
=== Methods for gaining user ratings and further available data ===<br />
==== User ratings ====<br />
Similar to [http://search.wikia.com/ Wikia Search] I would like to add some AJAX based rating and comment functions to the software portal. <br />
<br />
A user should be able to rate without any barriers like the need to login or similar for each presented package. This rating should be instead of the relevance of this package for this search result like in Wikia the overall feedback of the user on this package. The more stars, the better. In addition to this the user may give one package the spotlight tag, meaning this package should get additional attention. Short single line comments which may be deleted afterwards should be available to registered users. The may add some nice hints or warnings for other users. <br />
<br />
Some administrative buttons like ''report a bug'' or ''alert security team'' should complete the interactive search result.<br />
<br />
==== Popularity/acceptance (download statistics) ====<br />
[http://en.wikipedia.org/wiki/Survival_of_the_fittest "Survival of the fittest"] also applies to packages and repositories meaning the users only selects those repositories which do not break their system and bring them great benefits.<br />
<br />
The downloads.opensuse.org redirector mechanism is a valuable source for measuring a repository's or a package's popularity. We should compute time dependent statistics on the amount of package downloads (per package and repository) and metadata downloads (per repository).<br />
<br />
== Quality & maintenance ==<br />
Without a strong connection between packages and bugs, it is nearly impossible to get quality and security metrics for packages. Therefore, I strongly recommend to integrate a possibility to assign a bug to a package, like all other major distributions do [https://bugzilla.redhat.com/query.cgi] [http://www.debian.org/Bugs/] [https://bugs.launchpad.net/ubuntu] in [https://bugzilla.novell.com/ Novell's Bugzilla]. On the other hand, the build service team should consider creating its own bug tracker because it may not be desirable to have all bugs for all packages from the openSUSE build service within Novell's bug tracking system. The preferred way would probably be an own bug tracking system for each build service project.<br />
<br />
However, some metrics for the package quality can be derived by automated tests and similar stuff.<br />
<br />
=== Methods for measuring quality ===<br />
==== rpmlint & lintian/linda ====<br />
There exist automated tools to check a package against common errors and policy violations. Hence a package without any failures reported by these automated checks likely has a much higher quality than one with several complaints.<br />
<br />
[http://rpmlint.zarb.org/ rpmlint] is a tool for checking common errors in rpm packages. The following checks are included in the default rpmlint package:<br />
* Tag checks (TagsCheck): ''a check to see if some rpm tags are present.''<br />
* Distribution specific checks (DistributionCheck): ''checks the distribution specificities in a binary rpm package.''<br />
* Binary checks (BinaryCheck): ''checks binary files in a binary rpm package.''<br />
* Configuration file checks (ConfigCheck): ''checks if all configuration files are in place.''<br />
* Location, permission, group and owner checks (FileCheck): ''tests various aspects of files: locations, owners, groups, permissions, setuid, setguids, etc.''<br />
* Signature checks (SignatureCheck): ''checks the presence of a PGP signature.''<br />
* FHS checks (FHSCheck): ''checks FHS conformity.''<br />
* Source specific checks (SourceCheck): ''verifies source package correctness.''<br />
* i18n checks (I18NCheck): ''tests for i18n bugs.''<br />
* Menu system checks (MenuCheck): ''tests against the menu system.''<br />
* %post; %pre, %postun and %preun script checks (PostCheck): ''plenty of checks agains the post/pre scripts.''<br />
* /etc/rc.d/init.d checks (InitScriptCheck): ''checks init scripts.''<br />
* Spec file checks (SpecCheck): ''various tests against the spec file of a source rpm.''<br />
* Zip/Jar file checks (ZipCheck): ''verify Zip/Jar file correctness.''<br />
* Pam configuration file checks (PamCheck): ''checks for correct PAM configuration.''<br />
* Rpm file checks (RpmFileCheck): ''checks the filename length (!>64).''<br />
* Branding checks (BrandingPolicyCheck): ''verifies that branding related things comply.''<br />
* Desktop translation checks (DesktopTranslationCheck): ''searches untranslated desktop files.''<br />
* Documentation files dependency check (DocFilesCheck): ''%doc files must not introduce new dependencies.'''<br />
* Duplicates check (DuplicatesCheck): ''checks for duplicate files packaged separately.''<br />
* KMP policy check (KMPPolicyCheck): ''verifies that kmps' have proper dependencies.''<br />
* Library policy check (LibraryPolicyCheck): ''verifies whether shared library packages comply with the corresponding packaging policy.''<br />
* LSB checks (LSBCheck): ''checks for LSB compliance.''<br />
* Naming policy checks (NamingPolicyCheck): ''verifies the correct naming for a few packages (e.g. pyhton, perl, php, ruby, apache).''<br />
A first implementation should only check whether any test failed and possibly how many problems have been found. As a subsequent improvement, I would suggest to add a parser to identify the failed tests and to further add a severity measure for the identified problems.<br />
<br />
The corresponding Debian tools are [http://lintian.debian.org/ lintian] and [http://people.debian.org/~stevenk/linda/ linda]. They perform various checks against the [http://www.debian.org/doc/debian-policy/ Debian Policy Manual] and thus they should be integrated into the Debian packaging process of the build service. (See FATE request [https://keeper.suse.de/webfate/match/id?value=304951 #304951].)<br />
<br />
==== Possible further data sources ====<br />
* metadata<br />
* changelog<br />
* tests from <tt>submitpac</tt><br />
<br />
=== Methods for measuring maintenance ===<br />
==== Package history / version numbers ====<br />
Some users have a high demand for bleeding edge software. On the other hand, many users just want to get (security) bugs fixed without any further changes or feature additions. <br />
<br />
To derive a metric for these demands and for the estimation how active a package is maintained, we should keep a history of all software versions including some crucial dates (first upload, first successful build, first build passing all automated tests). In combination with a link to the upstream repository for new releases (e.g. CVS, SVN, Git, http/ftp download URL), we could derive some interesting metrics:<br />
* Time t between two upstream updates<br />&Delta; (t<sub>upstream version i</sub>; t<sub>upstream version i-1</sub>)<br />
* Time t between two package uploads/check-ins<br />&Delta; (t<sub>upload version i</sub>; t<sub>upload i-1</sub>)<br />
* Time t between two successful package builds (with check failures)<br />&Delta; (t<sub>build version i</sub>; t<sub>build i-1</sub>)<br />
* Time t between two perfect package builds<br />&Delta; (t<sub>perfect version i</sub>; t<sub>perfect i-1</sub>)<br />
In combination with a meaningful weighting function we could derive long term statistics including variance and expectation value for each of these time parameters.<br />
<br />
In addition to this we can compare these values with each other to get even more significant values:<br />
* Time t between an upstream update and the corresponding package upload <br />&Delta; (t<sub>upstream version i</sub>; t<sub>upload version i</sub>)<br />
* Time t between an upstream update and the corresponding package build (with check failures)<br />&Delta; (t<sub>upstream version i</sub>; t<sub>build version i</sub>)<br />
* Time t between an upstream update and the corresponding perfect package build<br />&Delta; (t<sub>upstream version i</sub>; t<sub>perfect version i</sub>)<br />
<br />
The value how long a package is broken may probably also be in the interest of the user:<br />
* Time t between a package break and a successful or perfect build<br />min{&Delta; (t<sub>break i</sub>; t<sub>build j</sub>); &Delta; (t<sub>break i</sub>; t<sub>perfect j</sub>)} with j=>i. <br />
<br />
Due to the nature of the distributed development process a package can be broken for a decent time as long as a prior working version is available. It has to be differentiated between a build problem caused by a build dependency or a build problem caused by the package itself.<br />
<br />
As a future improvement we could also regard the left out package versions and add a weight considering major/minor numbers of the upstream versions.<br />
<br />
==== Availability for several architectures and products ====<br />
A good packager takes care of his packages for all shipped architectures (like i586, amd64, s390, ppc) as well as older (not discontinued) products (e.g. openSUSE 10.2, openSUSE 10.3). In addition to the history described above we should enhance the version and build history to observe all platforms and products.<br />
<br />
==== Derive metrics from a package's Changelog ====<br />
Amongst other things the [[openSUSE:Packaging_guidelines|SUSE Package Conventions]] define some basic rules [[openSUSE:Packaging_Patches_guidelines#Current_set_of_abbreviations|how to cite major bug trackers]] like Novell Bugzilla, GCC, Gnome or KDE in a package's Changelog. They syntax mainly consists of a token for a bug tracker followed by a hash and the bug number enclosed by parentheses, e.g. <tt>(GCC#4711)</tt>, <tt>(bgo#0815)</tt> or <tt>(KDE#2342)</tt><br />
<br />
In addition there is also a defined format for citing [http://cve.mitre.org/ CVE&copy;] [http://cve.mitre.org/cve/identifiers/index.html identifiers]. CVE&copy; is a publicly available and free to use list or dictionary of standardized identifiers for common computer vulnerabilities and exposures. Changelog entries which contain CVE identifiers most likely contain a security fix or at least deal with the given threat.<br />
<br />
Similar to the given metrics for the upstream and package version histories we could parse the Changelogs for cross references and extract some minimal information from the bug trackers and calculate some values:<br />
* amount of fixed/covered bugs per package version<br />
* long time average of fixed/covered bugs per version<br />
* average time between bug report and fix per bug <br />
* average time between bug report and fix per package version<br />
To get significant values we should observe them in combination with the above mentioned version histories. We should also calculate variance and expectation values where feasible.<br />
<br />
==== Activity index / vitality ====<br />
''TODO''<br />
<br />
==== Reverse Build dependencies ====<br />
A rule of thumb is that a package is much easier to maintain, if it has few build dependencies. The more build dependencies, the easier the package may break and the more effort of the packages may be necessary. <br />
<br />
Even though this is a weak indicator for good maintenance this value is very important for several users of the build service. For instance the release managers strongly depend on this value for their decisions which packages to update in a late release process or not.<br />
<br />
==== Possible further data sources ====<br />
* Introduction of a new base repository<br />
** How quick do packagers add a new base repository?<br />
** How quick do they gain a high percentage of packages successfully build against it?<br />
* Evaluate tags for new package versions (e.g. optional, recommended, security)<br />
* Continuity (Measure how long someone is participating in projects. Extremely weak indicator?)<br />
<br />
= See also =<br />
* [[Build_Service/Concepts/TrustImplemenation|openSUSE trust implementation proposal]]<br />
* [http://www.advogato.org/trust-metric.html Advogato trust metric]<br />
* [http://www.trustlet.org/wiki/Trust_Metrics_Evaluation_project Trust Metrics Evaluation Project]<br />
<br />
[[Category:Build Service]]</div>Rajko mhttps://en.opensuse.org/index.php?title=User:Rajko_m/wip&diff=65220User:Rajko m/wip2013-12-05T05:33:19Z<p>Rajko m: /* Pads around */</p>
<hr />
<div>== Installation==<br />
<br />
* http://en.opensuse.org/SDB:Download_help<br />
<br />
It is about using delta rpm files to save download traffic.<br />
<br />
'''In general:''' One can use delta rpm to save on download time and volume, but they work only when there is existing rpm that can be updated. <br />
<br />
For users on a metered connection there can be substantial savings, but they will have to leave all rpm files used during installation. With today computers and hard disk sizes that is cheaper then to pay for downloads.<br />
<br />
Default is not to save, but it can be changed, although it is:<br />
* not obvious how to do that,<br />
* not advertised as an option to save bandwidth.<br />
Majority of users will leave default. Even those that can profit from<br />
smaller downloads.<br />
<br />
==Multimedia==<br />
* [[Portal:Multimedia]] is in a bad shape.<br />
<br />
== Live USB stick ==<br />
* split content per operating system<br />
* offer 2 layouts<br />
; Main article as is [[SDB:Live USB stick]]<br />
* right side - small index to choose all in one or per topic (operating system)<br />
* left side - all in one transcluded from separate pages, one page per frame<br />
;Subarticles<br />
* [[SDB:Live USB stick (Windows)]]<br />
* [[SDB:Live USB stick (Linux)]]<br />
* [[SDB:Live USB stick (Mac OS X)]]<br />
<br />
;All in one will use the same layout as Portal pages <br />
* There will be no subpages, but common, right hand side, navigation bar located as subpage of [[SDB:Live USB stick]] (it will not appear anywhere as title so it doesn't matter that is subpage)<br />
* To enable navigation bar all articles must be in [[:Category:Live USB stick]], then we use <nowiki><categorytree>Category:Live USB stick</categorytree></nowiki> on [[SDB:Live USB stick/navigation]].<br />
* Each of pages will be one section in the frame ETA: next week<br />
<br />
<br />
==For bugzilla ==<br />
* <s>Put HCL under revision control</s> <br />
** Requested in bugzilla as {{bnc|683964}}<br />
** Opened discussion on a opensuse-web mail list.<br />
* <s>Missing images for wiki user that is not logged in</s><br />
** Reported as {{bnc|683966}}.<br />
<br />
== Testing ==<br />
* [https://bugzilla.novell.com/report.cgi?x_axis_field=bug_severity&y_axis_field=product&z_axis_field=bug_status&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&longdesc_type=fulltext&longdesc=&classification=openSUSE&product=openSUSE+11.3&product=openSUSE+11.4&product=openSUSE+12.1&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=NEEDINFO&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= Bugs in currently supported releases]<br />
<br />
==Fix==<br />
*[[openSUSE:WebYaST TrainingKit]] capitalization is wrong in whole article<br />
<br />
==Pads around==<br />
* [http://piratepad.net/tpJmpiYeNG You can contribute to Free and Open Source Software]<br />
* [http://piratepad.net/PcPEkhGf2l Marketing Mix]<br />
* [http://piratepad.net/VQM25U4GMy Posters by karl-tux-stadt]<br />
* [http://piratepad.net/ycKrGlRqLr Celadon knocks on the door]<br />
<br />
==Google==<br />
<br />
==Wikipedia==<br />
<br />
* http://simple.wikipedia.org/wiki/SuSE<br />
* http://en.wikipedia.org/wiki/SUSE_Linux_distributions<br />
* http://commons.wikimedia.org/wiki/File:Suse_logo.svg<br />
* http://commons.wikimedia.org/wiki/File:Linux-SuSE-KDE.png<br />
* http://en.wikipedia.org/wiki/Category:SUSE_Linux<br />
* http://en.wikipedia.org/wiki/File:Vista-suse.png<br />
<br />
==Facebook==<br />
* http://www.facebook.com/group.php?gid=2256834487<br />
* http://www.facebook.com/pages/SUSE/106751842697603<br />
And few more search Google for:<br/><br />
site:facebook.com opensuse<br />
<br />
==Intersting==<br />
* http://userstyles.org/styles/6080<br />
* http://rpm.pbone.net/<br />
<br />
<br />
* How to write about software in the new wiki?<br />
** Main namespace - article that is software presentation that doesn't change very often. To achieve this use links to upstream project (latest news, change log, main page, svn/git, where to report problems), software search ( http://software.opensuse.org ) for the openSUSE packages, give description of software as found upstream (but check how current it is), some screenshots (with added version to which they relate).<br />
** SDB namespace, should contain installation, configuration, workaround for bugs and troubleshooting instructions, but even here it should be add on value that is not present on upstream pages. For instance, instructions for versions delivered in opensuse. Such information can be hard to find upstream.<br />
** In general, we don't want to duplicate upstream information, we want to give readers something that can't be found there, at bare minimum to cover flow from the moment user learns about software trough installation and configuration, and also the ways to report problems and ask for solution. <br />
<br />
*[[openSUSE:A-Z]] is new entry to wiki <br />
<br />
'''Procedure: Prepare pages that should be copied to language wikis'''<br/><br />
# List pages and give them for discussion on project list and wiki forum<br />
# Fix pages that make wiki skeleton<br />
# Export them all <br />
# Grep for all links, templates and categories<br />
# Add them to the list <br />
# Export new list to see sizes, <br />
# Group them under the 4 MB limit and export again.<br />
# Fix titles to be LANG-English_title<br />
# Import in local instance to check links <br />
# Fix links in en.o.o exported files<br />
# Import in each of the wikis<br />
<br />
<br />
* fixing pages that should be used as base for translations<br />
** fixing portals till [[Portal:How to participate]]<br />
<br />
* check KDE pages starting with [[Portal:KDE]]</div>Rajko mhttps://en.opensuse.org/index.php?title=Template:Last_version&diff=65219Template:Last version2013-12-05T05:22:56Z<p>Rajko m: </p>
<hr />
<div>12.3<noinclude><br />
<br />
----<br />
This is just a number of the previous (last) openSUSE version that can be used in article sections where this is the only change that will happen with newly released version. <br />
<br />
For instance in a template [[template:version note]] used in some page this template will keep page automatically updated as soon as this template is updated. No need to change tens of pages all over the wiki. <br />
<br />
[[Category:Timeline templates]]<br />
</noinclude></div>Rajko mhttps://en.opensuse.org/index.php?title=Template:Current_version&diff=65218Template:Current version2013-12-05T05:22:32Z<p>Rajko m: </p>
<hr />
<div>13.1<noinclude><br />
<br />
----<br />
This is just a number of the current openSUSE version that can be used in article sections where this is the only change that will happen with newly released version. <br />
<br />
For instance in a template [[template:version note]] used in some page this template will keep page automatically updated as soon as this template is updated. No need to change tens of pages all over the wiki. <br />
<br />
[[Category:Timeline templates]]<br />
</noinclude></div>Rajko mhttps://en.opensuse.org/index.php?title=Portal:Teams/Teams&diff=65147Portal:Teams/Teams2013-12-01T16:10:38Z<p>Rajko m: missing "}}" to close template</p>
<hr />
<div>__NOTOC____NOEDITSECTION__<!--<br />
--><div style="background-color:#f6f6f6;color:#0b5147;"><br />
==Community==<br />
</div><br />
{| style="background:none;border:0px solid none;width:98%;margin:0 0 0 .5em;padding:0;"<br />
|-<br />
|style="vertical-align:top;width:50%; margin:0"|<br />
{{Point here|[[File:Logo-art.png|link=openSUSE:Art team|28px]]|<br />
'''[[openSUSE:Art team|Art]]''' <br/><br />
The artists of openSUSE.}}<br />
|style="vertical-align:top;width:50%;margin:0"|<br />
{{Point here|[[Image:Marble.png|link=openSUSE:Board|Board|32px]]|<br />
'''[[openSUSE:Board|Board]]''' <br /><br />
Provides guidance to the project.}}<br />
|-<br />
|style="vertical-align:top;width:50%;margin:0"|<br />
{{Point here|[[Image:Icon-community.png|link=openSUSE:Conference_program_committee|32px]]|<br />
'''[[openSUSE:Conference program committee|Conference]]''' <br/><br />
Organization of the openSUSE Conference.}}<br />
|style="vertical-align:top;width:50%;margin:0"|<br />
{{Point here|[[Image:Membership-officials.png|link=|32px]]|<br />
'''[[openSUSE:Community Council|Community Council]]''' <br/><br />
Solves internal and external conflicts and communication issues.}}<br />
|-<br />
|style="vertical-align:top;width:50%;margin:0"|<br />
{{Point here|[[File:Icon-internet.png|link=openSUSE:Forums team|32px]]|<br />
'''[[openSUSE:Forums team|Forums]]''' <br/><br />
Care of discussion area.}}<br />
|style="vertical-align:top;width:50%;margin:0"|<br />
{{Point here|[[File:Doku-wichtl.png|link=openSUSE:Documentation_team|Docu|32px]]|<br />
'''[[openSUSE:Documentation_team|Documentation]]''' <br/><br />
Manuals, Guides, Whitepapers for the producs. }}<br />
|-<br />
|style="vertical-align:top;width:50%;margin:0"|<br />
{{Point here|[[Image:Marketing.png|link=openSUSE:Marketing team|32px]]|<br />
'''[[openSUSE:Marketing team|Marketing]]''' <br/><br />
Spread the word in all directions.}}<br />
|style="vertical-align:top;width:50%; margin:0"|<br />
{{Point here|[[File:Icon-news.png|link=openSUSE:News team|28px]]|<br />
'''[[openSUSE:News team|News]]''' <br/><br />
The news editors of openSUSE.}}<br />
|-<br />
|style="vertical-align:top;width:50%;margin:0"|<br />
{{Point here|[[Image:Membership-officials.png|link=openSUSE:Membership officials|32px]]|<br />
'''[[openSUSE:Membership officials|Membership officials]]''' <br/><br />
Handle membership requests. }}<br />
|style="vertical-align:top;width:50%;margin:0"|<br />
{{Point here|[[Image:Preferences-system-performance.png|link=|32px]]|<br />
'''[[openSUSE:OpenSUSE team|openSUSE team at SUSE]]''' <br/><br />
The SUSE internal openSUSE team.}}<br />
|-<br />
|style="vertical-align:top;width:50%;margin:0"|<br />
{{Point here|[[File:Community-logo.png|link=http://opensuse-community.org|30px]]|<br />
'''[http://opensuse-community.org/Help:Team openSUSE-community.org]''' <br/><br />
More efforts in your favourite distro.}}<br />
|style="vertical-align:top;width:50%;margin:0"|<br />
{{Point here|[[Image:audio-input-microphone.png|link=openSUSE:People of openSUSE|32px]]|<br />
'''[[openSUSE:People|People of openSUSE]]''' <br/><br />
Who is who in openSUSE. }}<br />
|-<br />
|style="vertical-align:top;width:50%;margin:0"|<br />
{{Point here|[[File:Logo-PlanetSUSE.png|link=openSUSE:Planet openSUSE team|32px]]|<br />
'''[[openSUSE:Planet|Planet openSUSE]]''' <br/><br />
Care of blogs aggregation server.}}<br />
|style="vertical-align:top;width:50%;margin:0"|<br />
{{Point here|[[Image:Icon-video.jpeg|link=openSUSE:Video team|28px]]|<br />
'''[[openSUSE:Video team|Video clips]]''' <br/><br />
The video tutorial makers.}}<br />
|-<br />
|style="vertical-align:top;width:50%;margin:0"|<br />
{{Point here|[[File:Icon-wiki.png|link=openSUSE:Wiki team|Wiki|32px]]|<br />
'''[[openSUSE:Wiki team|Wiki]]''' <br/><br />
The masters of the wikies. }}<br />
|style="vertical-align:top;width:50%;margin:0"|<br />
{{Point here|[[Image:Icon-community.png|link=openSUSE:Women|32px]]|<br />
'''[[openSUSE:Women|Women]]''' <br/><br />
Women of openSUSE.}}<br />
|}<br />
<br />
<div style="background-color:#f6f6f6;color:#0b5147;"><br />
==Support==<br />
</div><br />
{| style="background:none;border:0px solid none;width:98%;margin:0 0 0 .5em;padding:0;"<br />
|-<br />
|style="vertical-align:top;width:50%;margin:0"|<br />
{{Point here|[[File:Logo-fate.png|link=openSUSE:openfate screening|32px]]|<br />
'''[[openSUSE:openfate_screening|openFATE screening]]'''<br/><br />
Taking care of the feature requests.}}<br />
|style="vertical-align:top;width:50%;margin:0"|<br />
{{Point here|[[Image:Icon-security.png|link=openSUSE:Security team|32px]]|<br />
'''[[openSUSE:Security team|Security]]''' <br/><br />
The security before and after the release. }}<br />
|-<br />
|style="vertical-align:top;width:50%;margin:0"|<br />
{{Point here|[[Image:Lokalize.png|link=openSUSE:Localization team|32px]]|<br />
'''[[openSUSE:Localization team|Localization]]'''<br/><br />
Translating applications to various languages.}}<br />
|style="vertical-align:top;width:50%;margin:0"|<br />
{{Point here|[[Image:Icon-usage.png|link=|32px]]|<br />
'''[[openSUSE:Maintenance team|Maintenance]]''' <br/><br />
Coordinating maintenance updates. }}<br />
|-<br />
|style="vertical-align:top;width:50%;margin:0"|<br />
{{Point here|[[Image:Icon-kernel.png|link=openSUSE:Kernel team|32px]]|<br />
'''[[openSUSE:Kernel team|Kernel]]''' <br/><br />
Developing and maintaining the openSUSE kernel. }}<br />
|style="vertical-align:top;width:50%;margin:0"|<br />
{{Point here|[[Image:Icon-factory.png|link=openSUSE:Release team|32px]]|<br />
'''[[openSUSE:Release team|Release]]''' <br/><br />
Taking care of the Factory distribution.}}<br />
|}<br />
<br />
<div style="background-color:#f6f6f6;color:#0b5147;"><br />
==Desktop==<br />
</div><br />
{| style="background:none;border:0px solid none;width:98%;margin:0 0 0 .5em;padding:0;"<br />
|-<br />
|style="vertical-align:top;width:50%;margin:0"|<br />
{{Point here|[[File:Logo-gnome.png|link=openSUSE:GNOME team|32px]]|<br />
'''[[openSUSE:GNOME team|GNOME]]''' <br/><br />
desktop integration into openSUSE.}}<br />
|style="vertical-align:top;width:50%;margin:0"|<br />
{{Point here|[[File:Logo-kde.png|link=openSUSE:KDE team|32px]]|<br />
'''[[openSUSE:KDE team|KDE]]''' <br/><br />
desktop integration into openSUSE.}}<br />
|-<br />
|style="vertical-align:top;width:50%;margin:0"|<br />
{{Point here|[[File:Logo-Lxde.png|link=openSUSE:LXDE team|32px]]|<br />
'''[[openSUSE:LXDE team|LXDE]]''' <br/><br />
desktop integration into openSUSE.}}<br />
|valign="TOP" width=50%;"|<br />
{{Point here|[[File:Logo-Xfce.png|link=openSUSE:Xfce team|32px]]|<br />
'''[[openSUSE:Xfce team|Xfce]]''' <br/><br />
desktop integration into openSUSE.<br />
}}<br />
|}<br />
<br />
<div style="background-color:#f6f6f6;color:#0b5147;"><br />
==Development==<br />
</div><br />
{| style="background:none;border:0px solid none;width:98%;margin:0 0 0 .5em;padding:0;"<br />
|-<br />
|style="vertical-align:top;width:50%;margin:0"|<br />
{{Point here|[[File:Perl.png|link=openSUSE:Perl team|32px]]|<br />
'''[[openSUSE:Perl team|Perl]]''' <br/><br />
integration into openSUSE.}}<br />
|style="vertical-align:top;width:50%;margin:0"|<br />
{{Point here|[[File:Php.png|link=openSUSE:PHP team|32px]]|<br />
'''[[openSUSE:PHP team|PHP]]''' <br/><br />
integration into openSUSE.}}<br />
|-<br />
|style="vertical-align:top;width:50%;margin:0"|<br />
{{Point here|[[File:Python.png|link=openSUSE:Python team|32px]]|<br />
'''[[openSUSE:Python team|Python]]''' <br/><br />
integration into openSUSE.}}<br />
|style="vertical-align:top;width:50%;margin:0"|<br />
{{Point here|[[File:Ruby.png|link=openSUSE:Ruby team|32px]]|<br />
'''[[openSUSE:Ruby team|Ruby]]''' <br/><br />
and Rails integration into openSUSE.}}<br />
|}<br />
<br />
<br />
<div style="background-color:#f6f6f6;color:#0b5147;"><br />
==Infrastructure==<br />
</div><br />
{| style="background:none;border:0px solid none;width:98%;margin:0 0 0 .5em;padding:0;"<br />
|-<br />
|style="vertical-align:top;width:50%;margin:0"|<br />
{{Point here|[[File:Logo-obs.png|link=openSUSE:Build Service team|32px]]|<br />
'''[[openSUSE:Build Service team|Build Service]]''' <br/><br />
Development platform for the openSUSE and others. }}<br />
|style="vertical-align:top;width:50%;margin:0"|<br />
{{Point here|[[Image:Testing-Group-Logo.png|link=openSUSE:Testing Core team|32px]]|<br />
'''[[openSUSE:Testing Core team|Testing]]''' <br/><br />
We [[openSUSE:Testing|test]] and feed [[openSUSE:Submitting bug reports|Bugzilla]].}}<br />
|-<br />
|style="vertical-align:top;width:50%;margin:0"|<br />
{{Point here|[[Image:Icon-yast.png|link=openSUSE:YaST team|32px]]|<br />
'''[[openSUSE:YaST team|YaST]]''' <br/><br />
Installation and system management tool YaST.}}<br />
|style="vertical-align:top;width:50%;margin:0"|<br />
{{Point here|[[Image:Icon-yast.png|link=openSUSE:Zypper team|32px]]|<br />
'''[[openSUSE:Zypper team|Zypper]] / [[openSUSE:Libzypp team|Libzypp]]''' <br/><br />
ZYpp Package management tool.}}<br />
|-<br />
|style="vertical-align:top;width:50%;margin:0"|<br />
{{Point here|[[Image:Packman-logo.png|link=http://packman.links2linux.org/|32px]]|<br />
'''[http://packman.links2linux.org/ Packman]''' <br/><br />
We look after the Packman on openSUSE}}<br />
|style="vertical-align:top;width:50%;margin:0"|<br />
{{Point here|[[Image:Lizards.png|link=openSUSE:Lizards team|32px]]|<br />
'''[[openSUSE:Lizards team|Lizards]]''' <br/><br />
We maintain the ''Lizards'' blogs .}}<br />
|-<br />
|style="vertical-align:top;width:50%;margin:0"|<br />
{{Point here|[[Image:Icon-factory.png|link=openSUSE:OpenSUSE review team|32px]]|<br />
'''[[openSUSE:OpenSUSE review team|Packaging review]]''' <br/><br />
Review of packages for openSUSE.}}<br />
|style="vertical-align:top;width:50%;margin:0"|<br />
{{Point here|[[File:Maintenance.png|link=openSUSE:Services team|32px]]|<br />
'''[[openSUSE:Services team|Services]]''' <br/><br />
Package reviews and all administration related tasks.}}<br />
|}<br />
<br />
<div style="background-color:#f6f6f6;color:#0b5147;"><br />
==Projects==<br />
</div><br />
{| style="background:none;border:0px solid none;width:98%;margin:0 0 0 .5em;padding:0;"<br />
|-<br />
|style="vertical-align:top;width:50%;margin:0"|<br />
{{Point here|[[File:OpenSUSE-Edu.png|link=openSUSE:Education team|32px]]|<br />
'''[[openSUSE:Education team|Education]]''' <br/><br />
Edu-CD for openSUSE. }}<br />
|style="vertical-align:top;width:50%;margin:0"|<br />
{{Point here|[[Image:Medical.png|link=openSUSE:Medical team|22px]]|<br />
'''[[openSUSE:Medical team|Medical]]''' <br/><br />
Software for doctor's practice.}}<br />
|-<br />
|style="vertical-align:top;width:50%;margin:0"|<br />
{{Point here|[[Image:Packman-logo.png|link=openSUSE:Software portal team|22px]]|<br />
'''[[openSUSE:Software portal team|Software portal]]''' <br/><br />
Building the [[openSUSE:Software portal|Software portal]] project.}}<br />
|}</div>Rajko mhttps://en.opensuse.org/index.php?title=User:Rajko_m/Sandbox&diff=65124User:Rajko m/Sandbox2013-11-30T18:42:26Z<p>Rajko m: initial copy and some formating</p>
<hr />
<div>'''Title:''' '''''RPM packaging for beginners'''''<br />
(based on [http://dominique.leuenberger.net/blog/2009/05/rpm-packaging-for-beginners/ Dominique Leuenberger's blog post]).<br />
<br />
Let’s start with something simple, which does not end up in a complex spec file. The spec file are the package building instructions. During the Community week, I was asked to package up cairo-clock, which ended up being fairly easy and suits perfect for this example.<br />
<br />
==Prerequisites==<br />
Knowledge how to install a program from a source tarball.<br />
Typically this is handled with<br />
<pre><br />
./configure<br />
make<br />
sudo make install<br />
</pre><br />
<br />
And this is exactly true for cairo-clock (once all the build dependencies are satisfied).<br />
<br />
==Layout==<br />
How does a spec file look? It consists of sections:<br />
* preamble<br />
* %prep<br />
* %build<br />
* %install <br />
* %clean<br />
* %files<br />
* %changelog <br />
<br />
===Preamble===<br />
<br />
The preamble contains all the information about the package, that is visible to the user and is important for package manager and for the build process. Some are required, and some are optional. The list given below are not all considered required for an RPM to build successfully, but I would highly suggest to have them always in.<br />
<pre><br />
Name: cairo-clock<br />
Summary: Cairo-rendered on-screen clock<br />
Version: 0.3.3<br />
Release: 1<br />
URL: http://macslow.thepimp.net/cairo-clock<br />
Source0: cairo-clock_0.3.3-1.tar.bz2<br />
License: GPL v2<br />
Group: Productivity/Other<br />
BuildRoot: %{_tmppath}/%{name}-%{version}-build<br />
</pre><br />
Fairly easy to understand: <br />
:'''Name:''' is the name of the package and <br />
:'''Summary:''' is a short summary. This is both shown in yast (and zypper) when you look for the package. <br />
:'''Version:''' is what the program author said the program’s version is. <br />
:'''Release:''' is the number of released versions of the RPM you prepared. <br />
The Version and release tag should not be confused though. <br />
If you’re using the openSUSE Build Service, it will actually take care of the Release number and increase it internally whenever you make a change.<br />
<br />
'''URL:''' is for reference and tells where the project lives. This is very practical information if somebody wants to cross reference or even for yourself, if you want to verify if a newer version is available.<br />
Source is the filename of the source tarball. License should be fairly easy to understand and has to be of course what the author of the application released it under. The Group is where you can find the package in yast, when you use the Group view.<br />
And last, BuildRoot: I would say: just copy this one always around. It’s a safe assumption, creating the temporary buildroot in your tmp folder. Should anything mess up, you can always delete it and your system should not be risked.<br />
<br />
Also part of the preamble are the BuildRequires: those can sometimes take some time to find what is required, but you’d have the exact same problem when you build an application from source yourself. A good way to go is to just ‘build’ the package with the missing BuildRequires. Configure is most likely going to tell you what is missing, and you can add the specific dependencies.<br />
<br />
For Caire-Clock, this give the following list:<br />
<br />
BuildRequires: fdupes<br />
BuildRequires: gtk2-devel<br />
BuildRequires: pango-devel<br />
BuildRequires: fontconfig-devel<br />
BuildRequires: libglade2-devel<br />
BuildRequires: librsvg2-devel<br />
BuildRequires: perl-XML-Parser<br />
BuildRequires: update-desktop-files <br />
<br />
fdupes and update-desktop-files are not mandatory for the build to succeed; they are here to get the package a bit nicer (space savings for example) and to fix up some things.<br />
<br />
Not as difficult as you thought it would be, right?<br />
The %prep section<br />
<br />
In the %prep section, the build process (rpm-build for example) is instructed on what to do, before we can actually build the package.<br />
very common you will have %setup in there. I normally add -q, which just suppresses some output, makes the log more readable.<br />
<br />
So what does %setup mean? It will extract (tar -xf) the file specified in the preamble as Source. It’s expected that the tarball creates a folder named %{name}-%{version}, so in the case of this package cairo-clock-0.3.3. For this source package this is true, so nothing more is needed.<br />
<br />
The %build section<br />
<br />
So, how exactly is this program to be compiled? Simply try to get the compile process done without trying to package the application. For cairo clock this was fairly simple:<br />
<br />
./configure && make<br />
<br />
is all we need. This typically installs programs to /usr/local, which is not what we want when building a program for distribution via packages. They should cleanly ntegrate with the system (/usr/local is defined to be for locally built applications. This would only be true for your own machine).<br />
<br />
Instead of writing ./configure with all it’s parameters, we use the provided macro.<br />
<br />
%configure<br />
%__make %{?jobs:-j%jobs}<br />
<br />
That’s what we put in the final spec file for this package. The %__make is just taking care of differences between different systems. I’s safe to always use this line.<br />
The %install section<br />
<br />
So far, the tarball has been extracted, we configured the build and compiled the source. Next step in a regular install would be make install, and the same we do now in the spec file.<br />
<br />
%makeinstall<br />
rm -f $RPM_BUILD_ROOT%{_libdir}/*.la<br />
%suse_update_desktop_file -r -G "Generic Name" %{name} X-SuSE-DesktopUtility<br />
%fdupes %{buildroot}%{_datadir}/%{name}<br />
%find_lang %{name}<br />
<br />
%makeinstall is the call for make install as you would do manually, but it takes care of redirecting the installation to a temporary folder. We need to be sure to stay in the buildroot after all (as defined in the preamble).<br />
<br />
The other commands and their meaning:<br />
<br />
rm -f $RPM_BUILD_ROOT%{_libdir}/*.la : Deletes all libtool archives that were just installed. They can cause much more trouble than they are good for.<br />
%suse_update_desktop_files [...] : takes care of putting the originally provided .desktop file in a category we know on a openSUSE Gnome system<br />
%fdupes %{buildroot}%{_libdir}%{name}: cairo-clock installs several themes and a lot of files are equal in the themes. This is wasting space on the harddisks. To reduce the install size, those files are linked (ln).<br />
%find_lang %{name}: finds all the files called cairo-clock.mo that were installed and creates a list for us, nicely prepended with the language specific information. To be used later in the %files section.<br />
<br />
The %clean section<br />
<br />
At the end, when our package is built, we don’t want to leave a mess on the system we were working ourselves. So we clean up everything.<br />
The %files section<br />
<br />
%files contains a list of all the files we need to copy in our RPM, so everything that should finally be installed with our package.<br />
<br />
%files -f %{name}.lang<br />
%defattr(-,root,root)<br />
%doc AUTHORS COPYING INSTALL NEWS README TODO<br />
%{_bindir}/*<br />
%{_datadir}/*/%{name}.*<br />
%{_datadir}/%{name}<br />
%{_mandir}/*/%{name}.*<br />
<br />
As said, we make use of the list of the translation files from the %instal section. %files -f %{name}.lang instructs to use the list from cairo-clock.lang to start with.<br />
%defattr sets the default permissions and file owner and groups: the permission is set to ‘-’, which means we use what the installation did. This is typically safe to follow. All files installed will be owned by user root and group root.<br />
The %doc line copies some files that were not installed during %install, but should nevertheless be part of every package to acknowledge the source and to confrom with the license. If available, you should also package eventual original README files. It might even make sense to put your own README with further instructions regarding coniguration, in your packages.<br />
<br />
and finally we have a complete list of files to be included.<br />
DONE<br />
<br />
Sounds like a higly complex task at first, but understandin what the different lines mean make the entire process almost child play.<br />
<br />
I hope you can get some valuable information out of this and the openSUSE community is looking forward to your valuable additions.</div>Rajko mhttps://en.opensuse.org/index.php?title=Portal:Hardware/Related_links&diff=64940Portal:Hardware/Related links2013-11-24T16:39:53Z<p>Rajko m: smolt was retired</p>
<hr />
<div>*[[Hardware troubleshooting]]<br />
*[[Power management - Suspend]]<br />
*[[SDB:Printer buying guide]]<br />
*[[SDB:NVIDIA]] is about NVIDIA 3D support.<br />
*[[SDB:ATI]] is about ATI 3D support. <br />
*[[SDB:VIA]] is about VIA support.<br />
*[[POWER@SUSE]] is openSUSE on PPC architecture, but currently due to lack of maintainers is not supported.<br />
*[[Smolt]] was hardware information collection.</div>Rajko mhttps://en.opensuse.org/index.php?title=Smolt&diff=64939Smolt2013-11-24T16:37:13Z<p>Rajko m: /* External Link */</p>
<hr />
<div>{{Intro|'''Smolt is retired.'''}}<br />
* [https://fedoraproject.org/wiki/Smolt_retirement Smolt Retirement] on Fedora project wiki is now in effect.<br />
* http://www.smolts.org/ is retired.<br />
<br />
As any project that lost upstream support, we had to remove it from openSUSE distribution. It was included in openSUSE releases from 11.1 to 12.2.<br />
<br />
==General==<br />
Gathering hardware information in one place is long existing desire in Linux. Smolt was not first attempt, nor only, but it was first initiative that was accepted by few major Linux distributions. <br />
<br />
Smolt was a combined effort of few Linux projects to gather hardware information from computers running Linux with respect to user privacy. Information collection was voluntary and anonymous: <br />
* Smolt program was configured not to run automatically; it had be started manually. <br />
* When hardware profile was complete, program will present collected information and ask for permission to send it to the [http://www.smolts.org/ smolt server].<br />
<br />
Collecting hardware information as a cross distribution initiative resulted in a huge amount of data which was intended to:<br />
* aid developers in detection of computer hardware that is not well supported<br />
* focus efforts on popular hardware<br />
* provide workarounds and fixes trough tips on [https://fedorahosted.org/smolt/wiki Smolt wiki] or, in case of openSUSE specific tips, [[Portal:Hardware]].<br />
* help users to choose best distribution for their hardware<br />
* convince hardware vendors to offer support for their hardware under [[Linux]]<br />
<br />
== Smolt and openSUSE HCL == <br />
<br />
HCL is acronym for Hardware Compatibility List. That is collection of articles created with intention to inform users how certain type of hardware works driven by openSUSE. Without Smolt adding hardware to the list is task for advanced users that knew how to test hardware. Now that Smolt is discontinued it is time to resort to the old methods. <br />
<br />
==External link==<br />
* [http://en.wikipedia.org/wiki/Smolt_%28Linux%29 Wikipedia article ''Smolt (Linux)''] updated to show it was discontinued. <br />
<br />
[[Category:Hardware]]<br />
[[Category:Applications:Hardware]]<br />
<br />
[[it:Smolt]]<br />
[[es:Smolt]]<br />
[[ru:Smolt]]</div>Rajko mhttps://en.opensuse.org/index.php?title=Smolt&diff=64938Smolt2013-11-24T16:36:49Z<p>Rajko m: updated: smolt is discontinued, a bit of history</p>
<hr />
<div>{{Intro|'''Smolt is retired.'''}}<br />
* [https://fedoraproject.org/wiki/Smolt_retirement Smolt Retirement] on Fedora project wiki is now in effect.<br />
* http://www.smolts.org/ is retired.<br />
<br />
As any project that lost upstream support, we had to remove it from openSUSE distribution. It was included in openSUSE releases from 11.1 to 12.2.<br />
<br />
==General==<br />
Gathering hardware information in one place is long existing desire in Linux. Smolt was not first attempt, nor only, but it was first initiative that was accepted by few major Linux distributions. <br />
<br />
Smolt was a combined effort of few Linux projects to gather hardware information from computers running Linux with respect to user privacy. Information collection was voluntary and anonymous: <br />
* Smolt program was configured not to run automatically; it had be started manually. <br />
* When hardware profile was complete, program will present collected information and ask for permission to send it to the [http://www.smolts.org/ smolt server].<br />
<br />
Collecting hardware information as a cross distribution initiative resulted in a huge amount of data which was intended to:<br />
* aid developers in detection of computer hardware that is not well supported<br />
* focus efforts on popular hardware<br />
* provide workarounds and fixes trough tips on [https://fedorahosted.org/smolt/wiki Smolt wiki] or, in case of openSUSE specific tips, [[Portal:Hardware]].<br />
* help users to choose best distribution for their hardware<br />
* convince hardware vendors to offer support for their hardware under [[Linux]]<br />
<br />
== Smolt and openSUSE HCL == <br />
<br />
HCL is acronym for Hardware Compatibility List. That is collection of articles created with intention to inform users how certain type of hardware works driven by openSUSE. Without Smolt adding hardware to the list is task for advanced users that knew how to test hardware. Now that Smolt is discontinued it is time to resort to the old methods. <br />
<br />
==External Link==<br />
* [http://en.wikipedia.org/wiki/Smolt_%28Linux%29 Wikipedia article ''Smolt (Linux)''] updated to show it was discontinued. <br />
<br />
[[Category:Hardware]]<br />
[[Category:Applications:Hardware]]<br />
<br />
[[it:Smolt]]<br />
[[es:Smolt]]<br />
[[ru:Smolt]]</div>Rajko mhttps://en.opensuse.org/index.php?title=Portal:Hardware/Intro&diff=64900Portal:Hardware/Intro2013-11-23T23:57:06Z<p>Rajko m: removed Smolt</p>
<hr />
<div>Hardware support provides challenges to any distribution of Linux. The following pages are used by the openSUSE community to record the compatibility of various hardware and full systems with openSUSE community Linux distribution. Please share your experience by adding your hardware, especially if you had some issue that you was able to solve.<br />
<br />
If a link to some device is red, that means we have no information about it yet. Please help by contributing what you have learned, or experienced about it. <br />
<br />
===How to add hardware information to the list?===<br />
<br />
The easiest way would be to use:<br />
{{shell|hwinfo --short}}<br />
which will give some information about devices.<br />
<br />
There are some other ways to obtain hardware information, often in a better format.<br />
<br />
After you have data, you can post that as separate page in HCL namespace. Page title should be something like:<br />
<pre>HCL:Dell Inspiron 545 (hardware)</pre><br />
Adding HCL: will keep hardware information away from direct wiki search, but it will be available trough special wiki search powered by Google search at [[Mediawiki:GoogleSearch]]. <br />
<br />
===Comments or improvement ideas===<br />
<br />
We are discussing how to improve Hardware Compatibility List as current table layout is not really the best option. If you have ideas please post your comment in http://forums.opensuse.org/english/other-forums/community-fun/opensuse-wiki-discussions/ .</div>Rajko mhttps://en.opensuse.org/index.php?title=File:SilhueteGeeko.svg&diff=64888File:SilhueteGeeko.svg2013-11-23T16:30:31Z<p>Rajko m: </p>
<hr />
<div></div>Rajko mhttps://en.opensuse.org/index.php?title=openSUSE:Security_Perfect_Forward_Secrecy&diff=63552openSUSE:Security Perfect Forward Secrecy2013-10-26T22:38:28Z<p>Rajko m: added to category security</p>
<hr />
<div>= TLS with Perfect Forward Secrecy =<br />
<br />
Given recent reports about mass scale network surveillance and privacy breaches, one<br />
particular feature in network traffic encryption<br />
has become more interesting and mandatory, namely ''Perfect Forward Secrecy'' (PFS).<br />
<br />
Since there is a lot of confusion what PFS is about and what possible limitations are,<br />
we will outline the most important parts with respect to SUSE products.<br />
<br />
The wikipedia page [http://en.wikipedia.org/wiki/Perfect_forward_secrecy Perfect Forward Secrecy] has more background and references about PFS.<br />
<br />
During the SSL/TLS handshake (TLS is basically SSL version 3.1) which is necessary<br />
to establish a secure connection, a so called ''pre-master-secret'' is generated<br />
and exchanged. This secret is used for deriving encryption keys ('''Enc''') for the upcoming<br />
secure communication based on symmetric algorithms such as AES.<br />
Traditionally TLS is using (public) RSA keys inside its X509 certificates which are<br />
sent to the client, among other things such as a list of supported symmetric ciphers etc.<br />
The client uses this public RSA key of the server to encrypt the ''pre-master-secret'' before<br />
it is sent to the server.<br />
Attackers which recorded these handshakes and which are eventually able to obtain<br />
the private part of the RSA key can decrypt all communication that they are hold of.<br />
Even after a lot of time (decades) has passed between recording and breaking the key.<br />
<br />
PFS is about to change that.<br />
<br />
PFS is implemented via ''Ephemeral Keying'' (EK). Both terms can be used interchangeably.<br />
EK means that the key used for encrypting the ''pre-master-secret'' is unique to each handshake.<br />
PFS splits the process of encrypting the Key-Exchange ('''Kx''') from the process of protecting<br />
its integrity. For TLS this means that RSA can still be used to protect ('''Au''') the integrity<br />
of the Kx by signing/verifying the exchanged messages.<br />
For transfering the encryption-secret a different algorithm<br />
is used: Diffie Hellmann (DH). Because of its Ephemeral nature (keys are unique to the Kx), its called DHE or formerly EDH, meaning the same.<br />
<br />
You can read more about the DH Kx here:<br />
[http://en.wikipedia.org/wiki/Diffie_hellman DH Kx]<br />
<br />
As there are now four different algorithms involved with the TLS handshake,<br />
(the forth algorithm is the Hash function ('''Mac''') used with RSA for signing, such as SHA)<br />
one says that the cipher used is DHE + RSA + AES + SHA or DHE_RSA_AES_SHA.<br />
<br />
As generating new DH Keys on the fly for each new client is a quite expensive<br />
operation, a faster approach using Elliptic Curve Cryptography (ECC) was developed<br />
which allows for use of shorter keys, speeding up the computation during the Kx,<br />
named ECDHE or EECDH):<br />
[http://en.wikipedia.org/wiki/Elliptic_curve_Diffie%E2%80%93Hellman ECDHE].<br />
<br />
Note that ECC per se has nothing to do with PFS. PFS works still ''Perfect'' without<br />
ECC, yet its a bit slower as it is using larger keys. The E with respect<br />
to PFS inside ECDHE or DHE means ''Ephemeral'', not Elliptic!<br />
<br />
Other algorithms which can subsitute RSA for the Au are DSS or ECDSA.<br />
<br />
== Availability ==<br />
<br />
To check which ciphers your OpenSSL installation supports, you can use the '''openssl''' program. The OpenSSL API allows programs such as '''apache''' to set a list of prefered<br />
ciphers. By default, OpenSSL orders them by itself, but you can force PFS by<br />
choosing an appropriate cipher list. For a remote site that configured<br />
its webserver to use PFS, an example connect shows:<br />
<br />
<pre><br />
user@host:~> openssl s_client -connect www.ccc.de:443<br />
[...]<br />
SSL handshake has read 4818 bytes and written 646 bytes<br />
---<br />
New, TLSv1/SSLv3, Cipher is DHE-RSA-AES256-SHA<br />
Server public key is 4096 bit<br />
[...]<br />
<br />
</pre><br />
<br />
The '''DHE-RSA-AES256-SHA''' shows that Ephemeral DH is used, which is PFS.<br />
<br />
<br />
SUSE Linux Enterprise 11 currently installs openssl version 0.9.8j, which supports<br />
Diffie Hellman Kx (DHE) and which makes it PFS capable, even if ECC is not supported.<br />
You can check this with '''openssl''' command:<br />
<br />
<pre><br />
user@sle11-sp1:~> openssl ciphers -v<br />
DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1<br />
DHE-DSS-AES256-SHA SSLv3 Kx=DH Au=DSS Enc=AES(256) Mac=SHA1<br />
AES256-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA1<br />
DHE-RSA-CAMELLIA256-SHA SSLv3 Kx=DH Au=RSA Enc=Camellia(256) Mac=SHA1<br />
DHE-DSS-CAMELLIA256-SHA SSLv3 Kx=DH Au=DSS Enc=Camellia(256) Mac=SHA1<br />
CAMELLIA256-SHA SSLv3 Kx=RSA Au=RSA Enc=Camellia(256) Mac=SHA1<br />
EDH-RSA-DES-CBC3-SHA SSLv3 Kx=DH Au=RSA Enc=3DES(168) Mac=SHA1<br />
EDH-DSS-DES-CBC3-SHA SSLv3 Kx=DH Au=DSS Enc=3DES(168) Mac=SHA1<br />
DES-CBC3-SHA SSLv3 Kx=RSA Au=RSA Enc=3DES(168) Mac=SHA1<br />
DES-CBC3-MD5 SSLv2 Kx=RSA Au=RSA Enc=3DES(168) Mac=MD5 <br />
DHE-RSA-AES128-SHA SSLv3 Kx=DH Au=RSA Enc=AES(128) Mac=SHA1<br />
DHE-DSS-AES128-SHA SSLv3 Kx=DH Au=DSS Enc=AES(128) Mac=SHA1<br />
AES128-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(128) Mac=SHA1<br />
DHE-RSA-CAMELLIA128-SHA SSLv3 Kx=DH Au=RSA Enc=Camellia(128) Mac=SHA1<br />
DHE-DSS-CAMELLIA128-SHA SSLv3 Kx=DH Au=DSS Enc=Camellia(128) Mac=SHA1<br />
CAMELLIA128-SHA SSLv3 Kx=RSA Au=RSA Enc=Camellia(128) Mac=SHA1<br />
RC2-CBC-MD5 SSLv2 Kx=RSA Au=RSA Enc=RC2(128) Mac=MD5 <br />
RC4-SHA SSLv3 Kx=RSA Au=RSA Enc=RC4(128) Mac=SHA1<br />
RC4-MD5 SSLv3 Kx=RSA Au=RSA Enc=RC4(128) Mac=MD5 <br />
RC4-MD5 SSLv2 Kx=RSA Au=RSA Enc=RC4(128) Mac=MD5 <br />
EDH-RSA-DES-CBC-SHA SSLv3 Kx=DH Au=RSA Enc=DES(56) Mac=SHA1<br />
EDH-DSS-DES-CBC-SHA SSLv3 Kx=DH Au=DSS Enc=DES(56) Mac=SHA1<br />
DES-CBC-SHA SSLv3 Kx=RSA Au=RSA Enc=DES(56) Mac=SHA1<br />
DES-CBC-MD5 SSLv2 Kx=RSA Au=RSA Enc=DES(56) Mac=MD5 <br />
EXP-EDH-RSA-DES-CBC-SHA SSLv3 Kx=DH(512) Au=RSA Enc=DES(40) Mac=SHA1 export<br />
EXP-EDH-DSS-DES-CBC-SHA SSLv3 Kx=DH(512) Au=DSS Enc=DES(40) Mac=SHA1 export<br />
EXP-DES-CBC-SHA SSLv3 Kx=RSA(512) Au=RSA Enc=DES(40) Mac=SHA1 export<br />
EXP-RC2-CBC-MD5 SSLv3 Kx=RSA(512) Au=RSA Enc=RC2(40) Mac=MD5 export<br />
EXP-RC2-CBC-MD5 SSLv2 Kx=RSA(512) Au=RSA Enc=RC2(40) Mac=MD5 export<br />
EXP-RC4-MD5 SSLv3 Kx=RSA(512) Au=RSA Enc=RC4(40) Mac=MD5 export<br />
EXP-RC4-MD5 SSLv2 Kx=RSA(512) Au=RSA Enc=RC4(40) Mac=MD5 export<br />
<br />
<br />
</pre><br />
<br />
openSUSE 12.2 and newer versions use openssl 1.0.1 and so support TLS versions 1.0 up to 1.2 with DHE as well as ECDHE, among others.<br />
<br />
== Apache configuration ==<br />
<br />
The SSL Vhost has a setting to limit the available cryptographic ciphers by specifying '''SSLCipherSuite'''.<br />
<br />
Currently the suggested string in the template is <br />
<pre><br />
SSLCipherSuite ALL:!aNULL:!eNULL:!SSLv2:!LOW:!EXP:!MD5:@STRENGTH<br />
</pre><br />
<br />
To enforce DH Kx, add <code>kEDH</code> for DHE or <code>kECDHE</code> for elliptic curve DH, like eg:<br />
<pre><br />
SSLCipherSuite kEDH:ALL:!kRSA:!ADH:!RC4:!LOW:!EXP:HIGH:!MD5:!aNULL:!AESGCM:@STRENGTH<br />
</pre><br />
or<br />
<pre><br />
SSLCipherSuite kECDHE:ALL:!kRSA:!ADH:!RC4:!LOW:!EXP:HIGH:!MD5:!aNULL:!AESGCM:@STRENGTH<br />
</pre><br />
As SUSE Linux Enterprise Server 11 only supports the traditional Diffie Hellman Kx use <code>kEDH</code> there.<br />
<br />
For openSUSE 13.1 or later that includes Apache 2.4.x, please follow the instructions in the following <br />
[https://community.qualys.com/blogs/securitylabs/2013/08/05/configuring-apache-nginx-and-openssl-for-forward-secrecy|blog post]<br />
<br />
You can find the list of ciphers that you can specify for the '''SSLCipherSuite'''<br />
[http://www.openssl.org/docs/apps/ciphers.html here]<br />
<br />
You can verify the ciphers used locally on your machine with the ''openssl'' commandline tool,<br />
<pre><br />
openssl ciphers -v 'kEDH:ALL:!kRSA:!ADH:!RC4:!LOW:!EXP:HIGH:!MD5:!aNULL:!AESGCM:@STRENGTH'<br />
<br />
DHE-RSA-CAMELLIA256-SHA SSLv3 Kx=DH Au=RSA Enc=Camellia(256) Mac=SHA1<br />
DHE-DSS-CAMELLIA256-SHA SSLv3 Kx=DH Au=DSS Enc=Camellia(256) Mac=SHA1<br />
DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1<br />
DHE-DSS-AES256-SHA SSLv3 Kx=DH Au=DSS Enc=AES(256) Mac=SHA1<br />
EDH-RSA-DES-CBC3-SHA SSLv3 Kx=DH Au=RSA Enc=3DES(168) Mac=SHA1<br />
EDH-DSS-DES-CBC3-SHA SSLv3 Kx=DH Au=DSS Enc=3DES(168) Mac=SHA1<br />
DHE-RSA-CAMELLIA128-SHA SSLv3 Kx=DH Au=RSA Enc=Camellia(128) Mac=SHA1<br />
DHE-DSS-CAMELLIA128-SHA SSLv3 Kx=DH Au=DSS Enc=Camellia(128) Mac=SHA1<br />
DHE-RSA-AES128-SHA SSLv3 Kx=DH Au=RSA Enc=AES(128) Mac=SHA1<br />
DHE-DSS-AES128-SHA SSLv3 Kx=DH Au=DSS Enc=AES(128) Mac=SHA1<br />
</pre><br />
<br />
== Limitations ==<br />
<br />
The P inside PFS is not really perfect. Even if said before that attackers cannot<br />
decrypt sessions that have been recorded before the RSA key has been<br />
compromised, there are some pitfalls:<br />
<br />
If attackers can solve the underlying Discrete Logarithm problem on which<br />
the DH Kx is based, they ''can'' decrypt recorded sessions backward-in-time.<br />
PFS only protects you against a compromise of your servers RSA key.<br />
<br />
The same is true for the symmetric algorithm which is in use. If you use single DES,<br />
not even PFS can protect you. The above cipher-suite excludes such weak cipers<br />
via the <code>!LOW</code> and <code>!EXP</code> specification.<br />
<br />
PFS does not protect against Man-on-a-side (MoaS) or Man-in-the-Middle (MiM) attacks,<br />
as the DH happens with the attacker, not the legit endpoint. Therefore,<br />
the attacker already has the ''pre-master-secret'' at the time the handshake happens.<br />
To prevent such attacks you have to setup your own certificate authority (CA), as<br />
recently has become clear that the public CA's can easily be forced by their juristication<br />
to sign wrong/evil certificates and that network traffic is indeed re-routed in order to<br />
mount such attacks:<br />
[http://www.theguardian.com/world/2013/sep/09/nsa-spying-brazil-oil-petrobras petrobras]<br />
<br />
<br />
== References ==<br />
<br />
* [http://www.heise.de/security/artikel/Forward-Secrecy-testen-und-einrichten-1932806.html Heise News Article (german language)]<br />
* [https://community.qualys.com/blogs/securitylabs/2013/06/25/ssl-labs-deploying-forward-secrecy Qualys Article]<br />
* [http://vincent.bernat.im/en/blog/2011-ssl-perfect-forward-secrecy.html article by Vincent Bernat]<br />
* [https://www.ssllabs.com/ssltest/analyze.html Tester by Qualys ... good ciphers will be listed labeled with a green FS]<br />
* [http://www.openssl.org/docs/ssl/SSL_CTX_set_tmp_dh_callback.html Hook functions in openssl for DH]<br />
<br />
<br />
[[Category:Security]]</div>Rajko mhttps://en.opensuse.org/index.php?title=Template:Application&diff=63145Template:Application2013-10-05T16:28:00Z<p>Rajko m: </p>
<hr />
<div><!-- This page was created using Template:Application template --><br />
{{Infobox|<br />
name=Application|<br />
packagename=packagename|<br />
developer=ApplicationProject|<br />
image=[[Image:Icon-applications.png|200px]]|<br />
description=The description of the above image|<br />
vendor=ApplicationVendor|<br />
license=License|<br />
website=http://application.org|<br />
}}<br />
<br />
==About==<br />
<!-- Describe the application to a novice user --><br />
Application is a calendering solution to organize your personal and professional life. It will help you to never forget birthdays or the staff meeting again.<br />
<br />
----<br />
==Features==<br />
<!-- Describe the features of the application as a bullet list --><br />
* Reoccurring Appointments<br />
* Tag your appointments<br />
* Setup various reminders. From pop ups to SMS.<br />
<br />
----<br />
==See also==<br />
<!-- Other applications that provide similar functionality --><br />
* [[Sunbird]]<br />
* [[Evolution]]<br />
<br />
----<br />
==External links==<br />
<!-- Links to external documentation resources and the like --><br />
*[http://application.org Application's website]<br />
*[http://en.wikipedia.org/wiki/Calendaring_software Calendaring software on wikipedia]<br />
<br />
<!-- Find a suitable category on Category:Applications and add it below --><br />
<!-- Don't forget to remove the <includeonly> and </includeonly> tags--><br />
<includeonly><br />
[[Category:Applications:Calendar]]<br />
</includeonly><br />
<noinclude><br />
[[Category:Article templates]]<br />
</noinclude></div>Rajko mhttps://en.opensuse.org/index.php?title=Google_Earth&diff=63144Google Earth2013-10-05T16:17:58Z<p>Rajko m: removed 11.x references</p>
<hr />
<div>{{Intro|'''Google Earth''' is a virtual globe program. It maps the Earth by the superimposition of images obtained from satellite imagery, aerial photography and GIS 3D globe. }}<br />
___NOTOC___<br />
<br />
==Prerequisites==<br />
<br />
[[Image:Earth.png|thumb|400px|right|Screenshot of Google Earth]]<br />
<br />
<br />
* System Memory (RAM): 512MB (256MB will do if swap space available)<br />
* Hard Disk: 2GB free space<br />
* Network Speed: 768 Kbits/sec<br />
* Graphics Card: 3D-capable with 32MB of VRAM<br />
* Screen: 800x600, 24 bit color<br />
<br />
==Installation==<br />
<br />
* Go to [http://earth.google.com/ Google Earth web page]<br />
* Click on [http://earth.google.com/download-earth.html download] link,<br />
* Select the .rpm file corresponding to your system (in case you are not sure, open a terminal and look at the output of 'uname -r': if you see x86_64, you run a 64 bits OS. If you see i386/i586/i686, you are running a 32 bits OS.)<br />
* Save file and install the .rpm file with your favorite installer!<br />
<br />
==Problem solving==<br />
===Problem with libssl===<br />
* '''Version 5.0:''' Try to start google earth via terminal (type: googleearth), if you get the following error, follow the steps behind.<br />
{{Shell|./googleearth-bin: symbol lookup error: /usr/lib/libssl.so.0.9.8: undefined symbol: EVP_camellia_128_cbc}}<br />
<br />
:1. Log in as ''root''.<br />
:2. localize ''libcrypto.so.0.9.8'':<br />
{{Shell|whereis libcrypto.so.0.9.8}}<br />
:3. Move original library as backup:<br />
{{Shell|mv /opt/google-earth/libcrypto.so.0.9.8 /opt/google-earth/libcrypt.so.0.9.8.old}}<br />
:4. Set link to the system-library. (Attention! Maybe you have to change the path)<br />
{{Shell|ln -s /usr/lib/libcrypto.so.0.9.8 /opt/google-earth/libcrypto.so.0.9.8}}<br />
<br />
If you get this error:<br />
googleearth-bin: error while loading shared libraries: libGL.so.1: cannot open shared object file: No such file or directory<br />
<br />
You are running 64 bit linux but Google Earth is a 32 bit executable and needs the 32 bit versions of the libraries. <br />
<br />
Log in as ''root''.<br />
{{Shell|# zypper install Mesa-32bit}}<br />
<br />
'''Comprehension:'''<br /><br />
You replace the libcrypto.so.0.9.8 from Google Earth trough a symbolic link to the native libcrypto.so.0.9.8.<br />
<br />
===Panoramio photos not appearing when clicked===<br />
<br />
===Possible problem with nvidia drivers===<br />
* '''Version 5.1 and 6:''' If google-earth rendering is garbled and/or extremely slow, this may very well be triggered by desktop compositing in conjunction with an nvidia card and driver. Disable compositing (under System settings -> Desktop -> Desktop Effects -> General) and try again.<br />
<br />
===Google Earth locks/freezes the display ===<br />
<br />
===Google Earth does not Start with ATI FGLRX===<br />
* '''Version 6.1.0.5001:''' Under OpenSuse 12.1<br />
If you get this Error:<br />
googleearth-bin: error while loading shared libraries: libGL.so.1: cannot open shared object file: No such file or directory<br />
You need to symbolically link ATI's fglrx-libGL.so.1.2 to libGL.so.1<br />
<br />
{{Shell|# ln -s /usr/X11R6/lib/fglrx/fglrx-libGL.so.1.2 /opt/google/earth/free/libGL.so.1}}<br />
Please check your paths and filenames to match your system and versions.<br />
<br />
The issue is discussed in more detail here:<br />
[[http://forums.opensuse.org/english/get-technical-help-here/applications/468748-google-earth-opensuse-12-1-fglrx.html forums.opensuse.org]]<br />
<br />
<br />
googleearth-bin: error while loading shared libraries: libGL.so.1: cannot open shared object file: No such file or directory<br />
You need to symbolically link ATI's fglrx-libGL.so.1.2 to libGL.so.1<br />
<br />
{{Shell|# ln -s /usr/X11R6/lib/fglrx/fglrx-libGL.so.1.2 /opt/google/earth/free/libGL.so.1}}<br />
Please check your paths and filenames to match your system and versions.<br />
<br />
<br />
===Version 7: Under OpenSuse 12.1 x64===<br />
I got folowing error by executing:<br />
.googleearth/crashlogs/crashlog-50d60b60.txt<br />
Major Version 7<br />
Minor Version 0<br />
Build Number 0002<br />
Build Date Dec 13 2012<br />
Build Time 17:54:43<br />
OS Type 3<br />
OS Major Version 3<br />
OS Minor Version 1<br />
OS Build Version 10<br />
OS Patch Version 16<br />
Crash Signal 11<br />
Crash Time 1356204896<br />
Up Time 0.006256<br />
<br />
Stacktrace from glibc:<br />
./libgoogleearth_free.so(+0x1e9fab)[0xf7612fab]<br />
./libgoogleearth_free.so(+0x1ea1f3)[0xf76131f3]<br />
[0xffffe400]<br />
<br />
I reported bug to Google earth.<br />
<br />
==External Links==<br />
<br />
* [http://earth.google.com Google Earth Homepage]<br />
<br />
==See also== <br />
* [[SDB:Installing Google Picasa]]<br />
<br />
<br />
[[Category:Applications:Internet]]</div>Rajko mhttps://en.opensuse.org/index.php?title=Template:Popular_portals&diff=63057Template:Popular portals2013-09-30T03:12:02Z<p>Rajko m: </p>
<hr />
<div>{{Box-header|Popular Portals|{{FULLPAGENAME}} }}<br />
{|width="100%" style="margin-left:auto; margin-right:auto;"<br />
|<DynamicPageList><br />
namespace=Portal<br />
category=Portals<br />
stablepages=only<br />
count=8<br />
shownamespace=false<br />
ordermethod=popularity<br />
</DynamicPageList><br />
|<DynamicPageList><br />
namespace=Portal<br />
category=Portals<br />
stablepages=only<br />
count=8<br />
offset=8<br />
shownamespace=false<br />
ordermethod=popularity<br />
</DynamicPageList><br />
|<DynamicPageList><br />
namespace=Portal<br />
category=Portals<br />
stablepages=only<br />
count=8<br />
offset=16<br />
shownamespace=false<br />
ordermethod=popularity<br />
</DynamicPageList><br />
|<DynamicPageList><br />
namespace=Portal<br />
category=Portals<br />
stablepages=only<br />
count=8<br />
offset=24<br />
shownamespace=false<br />
ordermethod=popularity<br />
</DynamicPageList><br />
|<DynamicPageList><br />
namespace=Portal<br />
category=Portals<br />
stablepages=only<br />
count=8<br />
offset=32<br />
shownamespace=false<br />
ordermethod=popularity<br />
</DynamicPageList><br />
|}<br />
{{Box-footer}}<br />
<noinclude><br />
[[Category:Navigational_bars]]<br />
</noinclude></div>Rajko mhttps://en.opensuse.org/index.php?title=Portal:Wiki/Intro&diff=63056Portal:Wiki/Intro2013-09-30T03:08:37Z<p>Rajko m: </p>
<hr />
<div>The [[Portal:Wiki|openSUSE wiki]] is the source of information about the openSUSE project and distribution. <br />
<br />
The goal is to provide high quality documentation and a place for collaboration on all parts of the project. This is done in a well structured, standardized and easy readable way. Content is created, edited and refined by all community members.<br />
<noinclude><br />
[[Category:Topic introductions]]<br />
[[pl:Portal:Wiki/Intro]]<br />
</noinclude></div>Rajko mhttps://en.opensuse.org/index.php?title=Portal:Distribution/Intro&diff=63055Portal:Distribution/Intro2013-09-30T02:57:51Z<p>Rajko m: </p>
<hr />
<div>The [[Portal:Distribution|openSUSE distribution]] is a stable, easy to use and complete multi-purpose distribution.<br />
<br />
It is aimed towards users and developers working on the desktop or server. It is great for beginners, experienced users and ultra geeks alike, in short, it is perfect for everybody! The latest release, [[Portal:12.3|openSUSE 12.3]], features new and massively improved versions of all useful server and desktop applications. It comes with more than 1,000 open source applications.<br />
<br />
openSUSE is also the base for SUSE's award-winning [http://www.suse.com/ SUSE Linux Enterprise] products.<br />
<noinclude>[[pl:Portal:Distribution/Intro]]</noinclude></div>Rajko mhttps://en.opensuse.org/index.php?title=Portal:Project&diff=63054Portal:Project2013-09-30T02:53:59Z<p>Rajko m: </p>
<hr />
<div><!-- This portal was created using Template:Portal template --><br />
<!--<br />
Left column<br />
--><div style="width:70%; float:left"><br />
{{Box-header|<big>Welcome to the {{PAGENAME}} Portal</big>|{{FULLPAGENAME}}/Intro|}}<br />
{{:{{FULLPAGENAME}}/Intro}}<br />
{{Box-footer|}}<br />
{{Box-header|Topics|{{FULLPAGENAME}}/Topics|}}<br />
{{:{{FULLPAGENAME}}/Topics}}<br />
{{Box-footer|}}<br />
<br />
</div><!--<br />
Right column<br />
--><div style="width:30%; float:right"><br />
{{Box-header|Navigation|{{FULLPAGENAME}}/Sub-projects|}}<br />
{{:{{FULLPAGENAME}}/Sub-projects}}<br />
{{Box-footer|}}<br />
{{Box-header|Community Map|{{FULLPAGENAME}}/Map|}}<br />
{{:{{FULLPAGENAME}}/Map}}<br />
{{Box-footer|[[openSUSE:Map|See the live and zoomable map]]}}<br />
{{Box-header|Communicate|{{FULLPAGENAME}}/Communicate|}}<br />
{{:{{FULLPAGENAME}}/Communicate}}<br />
{{Box-footer|}}<br />
<!--<br />
{{Box-header|News|{{FULLPAGENAME}}/News|}}<br />
{{:{{FULLPAGENAME}}/News}}<br />
{{Box-footer|}}<br />
--><br />
</div><br />
<br />
<br style="clear: both;" /><br />
<br />
[[Category:Portals|{{PAGENAME}}]]<br />
{{IW|Portal:Project}}<br />
__NOTOC__ __NOEDITSECTION__</div>Rajko mhttps://en.opensuse.org/index.php?title=Portal:Project/Intro&diff=63053Portal:Project/Intro2013-09-30T02:32:37Z<p>Rajko m: </p>
<hr />
<div>The [[Portal:Project|openSUSE project]] is a worldwide effort that promotes the use of Linux everywhere. openSUSE creates one of the world's best Linux distributions, working together in an open, transparent and friendly manner as part of the worldwide [[Free and Open Source Software]] community.<br />
<br />
The project is controlled by its community and relies on the contributions of individuals, working as testers, writers, translators, usability experts, artists and ambassadors or developers. The project embraces a wide variety of technology, people with different levels of expertise, speaking different languages and having different cultural backgrounds. <br />
<br />
'''Have a lot of fun...'''<br />
<noinclude><br />
[[Category:Topic introductions]]<br />
</noinclude></div>Rajko mhttps://en.opensuse.org/index.php?title=Template:Cleanup&diff=62804Template:Cleanup2013-09-12T04:25:07Z<p>Rajko m: </p>
<hr />
<div>{| class="cleanup message" cellpadding="5px" cellspacing="0" <br />
|-<br />
|class="32-icon"|[[image:Icon-cleanup.png|32px|link=]]<br />
|class="vertical-align-mid"|'''This article is in need of attention''' because it does not follow our '''[[Portal:Wiki|wiki guidelines]]'''. {{#if:{{{1|}}}|{{{1}}}|}}<br/>If you want to contribute, please read the rules for this wiki and if you have any questions, don't hesitate to [[openSUSE:Wiki_team#Communicate|contact the wiki team]], we are more then willing to help you! :-)<br />
|}<noinclude><br />
{{{{PAGENAME}}/doc}}<br />
[[Category:Wiki_maintenance_templates]]<br />
[[el:Template:Cleanup]]<br />
</noinclude><br />
<includeonly>[[Category:Pages to cleanup]]</includeonly></div>Rajko mhttps://en.opensuse.org/index.php?title=Template:Cleanup&diff=62803Template:Cleanup2013-09-12T04:24:50Z<p>Rajko m: </p>
<hr />
<div>{| class="cleanup message" cellpadding="5px" cellspacing="0" <br />
|-<br />
|class="32-icon"|[[image:Icon-cleanup.png|32px|link=]]<br />
|class="vertical-align-mid"|'''This article is in need of attention''' because it does not follow our '''[[Portal:Wiki|wiki guidelines]]'''. {{#if:{{{1|}}}|{{{1}}}|}}<br/>If you want to contribute, please the rules for this wiki and if you have any questions, don't hesitate to [[openSUSE:Wiki_team#Communicate|contact the wiki team]], we are more then willing to help you! :-)<br />
|}<noinclude><br />
{{{{PAGENAME}}/doc}}<br />
[[Category:Wiki_maintenance_templates]]<br />
[[el:Template:Cleanup]]<br />
</noinclude><br />
<includeonly>[[Category:Pages to cleanup]]</includeonly></div>Rajko mhttps://en.opensuse.org/index.php?title=Cacti&diff=62802Cacti2013-09-12T04:14:13Z<p>Rajko m: Removed cleanup notice as article is small enough. Notice just confuses contributors.</p>
<hr />
<div><br />
= Definition =<br />
== What is Cacti? ==<br />
<br />
Cacti is a complete frontend to [http://oss.oetiker.ch/rrdtool/ RRDtool], it stores all of the necessary information to create graphs and populate them with data in a MySQL database. The frontend is completely PHP driven. Along with being able to maintain Graphs, Data Sources, and Round Robin Archives in a database, cacti handles the data gathering. There is also SNMP support for those used to creating traffic graphs with [http://oss.oetiker.ch/mrtg/ MRTG].<br />
<br />
[[image:cacti-promo.jpg|center|alt=Cacti]]<br />
<br />
==Data Sources==<br />
To handle data gathering, you can feed cacti the paths to any external script/command along with any data that the user will need to "fill in", cacti will then gather this data in a cron-job and populate a MySQL database/the round robin archives.<br />
<br />
Data Sources can also be created, which correspond to actual data on the graph. For instance, if a user would want to graph the ping times to a host, you could create a data source utilizing a script that pings a host and returns it's value in milliseconds. After defining options for RRDTool such as how to store the data you will be able to define any additional information that the data input source requires, such as a host to ping in this case. Once a data source is created, it is automatically maintained at 5 minute intervals.<br />
<br />
<br />
==Graphs==<br />
Once one or more data sources are defined, an RRDTool graph can be created using the data. Cacti allows you to create almost any imaginable RRDTool graph using all of the standard RRDTool graph types and consolidation functions. A color selection area and automatic text padding function also aid in the creation of graphs to make the process easier.<br />
<br />
Not only can you create RRDTool based graphs in cacti, but there are many ways to display them. Along with a standard "list view" and a "preview mode", which resembles the RRDTool frontend 14all, there is a "tree view", which allows you to put graphs onto a hierarchical tree for organizational purposes.<br />
<br />
<br />
==User Management==<br />
Due to the many functions of cacti, a user based management tool is built in so you can add users and give them rights to certain areas of cacti. This would allow someone to create some users that can change graph parameters, while others can only view graphs. Each user also maintains their own settings when it comes to viewing graphs.<br />
<br />
<br />
==Templating==<br />
Lastly, cacti is able to scale to a large number of data sources and graphs through the use of templates. This allows the creation of a single graph or data source template which defines any graph or data source associated with it. Host templates enable you to define the capabilities of a host so cacti can poll it for information upon the addition of a new host<br />
<br />
<br />
<br />
= HOW-TO=<br />
<br />
== Preparation==<br />
<br />
* add the server:monitoring repository<br />
<br />
<div class="shell"> zypper ar http://download.opensuse.org/repositories/server:/monitoring/openSUSE_12.2/ server:monitoring</div><br />
<br />
* install Mysql:<br />
<br />
<div class="shell">zypper in mysql-community-server mysql-community-server-client</div><br />
<br />
* install Cacti and Cacti addons:<br />
<br />
<div class="shell">zypper in cacti-0.8.8a cacti-plugin-autom8 cacti-plugin-boost cacti-plugin-clog cacti-plugin-cycle cacti-plugin-discovery cacti-plugin-docs cacti-plugin-flowview cacti-plugin-hostinfo cacti-plugin-loginmod cacti-plugin-mactrack cacti-plugin-monitor cacti-plugin-npc cacti-plugin-ntop cacti-plugin-realtime cacti-plugin-routerconfigs cacti-plugin-settings cacti-plugin-ssl cacti-plugin-syslog cacti-plugin-thold cacti-plugin-tools cacti-plugin-update</div><br />
<br />
== Configuration ==<br />
<br />
To get started, the basic services needed:<br />
<div class="shell">service mysql start<br><br />
service apache2 start<br>service snmpd start</div><br />
And to avoid headaches later, we'll add them at startup in RunMode 3 and 5:<br />
<div class="shell">chkconfig -a mysql<br>chkconfig -a apache2<br>chkconfig -a snmpd</div><br />
We will implement an additional layer of security by removing some vulnerabilities in MySQL:<br />
<div class="shell">/usr/bin/mysql_secure_installation</div><br />
Follows the order of questions:<br />
* Change password for user root;<br />
* Remove user anonymous;<br />
* Disable remote access;<br />
* Remove test database and flush privileges;<br />
* Reload privilege tables.<br />
<br />
If you change later the root password of MySQL, use the command:<br />
<div class="shell">/usr/bin/mysqladmin -u root -h localhost password 'new password'</div><br />
<br />
== Apache Configuration==<br />
First, locate the Cacti files:<br />
<div class="shell">find /usr/ -name cacti</div><br />
They will be in <tt>/usr/share/cacti</tt><br />
<br />
We use a virtualhost to facilitate our work:<br />
<div class="shell">cd /etc/apache2/vhosts.d/<br>cp vhost.template cacti.conf<br>vim cacti.conf</div><br />
Edit the necessary fields. See example:<br />
<VirtualHost *:80><br />
ServerAdmin rauhmaru@opensuse.org<br />
ServerName cacti.local<br />
DocumentRoot /srv/www/cacti/<br />
ErrorLog /var/log/apache2/cacti-error_log<br />
CustomLog /var/log/apache2/cacti-access_log combined<br />
HostnameLookups Off<br />
UseCanonicalName Off<br />
ServerSignature On<br />
<IfModule mod_userdir.c><br />
UserDir public_html<br />
Include /etc/apache2/mod_userdir.conf<br />
</IfModule><br />
<Directory "/usr/share/cacti"><br />
Options Indexes FollowSymLinks<br />
AllowOverride None<br />
Order allow,deny<br />
Allow from all<br />
</Directory><br />
</VirtualHost><br />
<br />
Define the user <b>wwwrun</b> of group <b>www</b> as owner of the Cacti files :<br />
<div class="shell">chown -R wwwrun:www /srv/www/cacti/</div><br />
<br />
If you want Cacti to bew the default server, edit the file /etc/sysconfig/apache2 and add CACTI as a server flag:<br />
<div class="shell">APACHE_SERVER_FLAGS="CACTI"</div><br />
<br />
== Mysql Configuration==<br />
Now we will create the basis of Cacti and a user:<br />
<div class="shell">mysql -p<br>mysql> create database cacti;<br>mysql> GRANT ALL ON cacti.* TO cactiuser@localhost IDENTIFIED BY 'cactipasswd';</div><br />
<br />
== CACTI Configuration==<br />
With Apache2 and Mysql configured, missing only the CACTI:<br />
<div class="shell">vim /srv/www/cacti/include/config.php</div><br />
<br />
Configuration of <tt>/srv/www/cacti/cacti/include/config.php</tt>:<br />
$database_type = "mysql";<br />
$database_default = "cacti";<br />
$database_hostname = "localhost";<br />
$database_username = "cactiuser";<br />
$database_password = "cactipasswd";<br />
$database_port = "3306";<br />
<br />
Executes the script <b>cacti.sql</b> of CACTI, found in <tt>/srv/www/cacti/</tt><br />
<div class="shell">mysql -u root -p -b cacti < /srv/www/cacti/cacti.sql</div><br />
<br />
Now we will start the final configuration by the browser.<br />
<br />
== In browser ==<br />
For the browser, go to address http://SERVER/cacti/install. You will see the license. Proceed<br />
[[image:cacti-licenca.gif|center|License GPL]]<br />
<br />
Defines a new installation:<br />
<br />
[[image:cacti-novainstalacao.gif|center|Nova Instalação]]<br />
<br />
Make sure the checklist is ok.<br />
<br />
[[image:cacti-checklist.gif|center|Checklist]]<br />
<br />
<br />
Finished! Now you can monitor your network assets using SNMP quite easily!<br />
<br />
[[image:cacti-login.gif|center|Login]]<br />
<div class="minutes"><b>login: admin<br>password: admin</b></div><br />
<b>After authentication, you must reset the password.</b><br />
<br />
[[Category:Applications:System]]</div>Rajko mhttps://en.opensuse.org/index.php?title=Portal:Documentation/Topics&diff=62732Portal:Documentation/Topics2013-09-04T00:03:06Z<p>Rajko m: </p>
<hr />
<div>== General information ==<br />
{{Point here|[[Image:Icon-distribution.png|48px|link=]]|<br />
'''openSUSE general information'''<br />
*[[openSUSE:FAQ|Frequently asked questions]] about the openSUSE Project<br />
*[[openSUSE:Statistics|Statistics]] about openSUSE's usage. <br />
*[[wikipedia:SUSE_Linux_distributions|SUSE Linux distributions]] on Wikipedia<br />
}}<br />
{{Point here|[[Image:Icon-question.png|48px|link=]]|<br />
'''Linux general information'''<br />
*[[Concepts]] - An introduction to many openSUSE and Linux concepts<br />
*[[Acronyms]] - What do all those darn three letter words mean?<br />
*[[Free and Open Source Software]] - The philosophy behind software.<br />
*[[SDB:How to migrate from Windows|How to migrate from Windows]]<br />
}}<br />
----<br />
== Official documentation ==<br />
{{Point here|[[Image:Icon-manual.png|48px|link=]]|<br />
[[SDB:Official documentation|Official openSUSE documentation]] in a variety of formats.<br />
}}<br />
== User documentation ==<br />
{{Point here|[[Image:Icon-manual.png|48px|link=]]|<br />
[[SDB:How to migrate to a new openSUSE version|Migration to a new openSUSE version]] - If you are a new openSUSE user, or want to do a distribution upgrade from a previous release.<br />
}}<br />
{{Point here|[[Image:Icon-installation.png|48px|link=]]|<br />
[[:Category:SDB:Installation|Installation]] - Articles covering all aspects of the installation of openSUSE.<br />
}}<br />
{{Point here|[[Image:Icon-package.png|48px|link=]]|<br />
[[Package management]] - Install, remove or update software.<br />
}}<br />
{{Point here|[[Image:Icon-usage.png|48px|link=]]|<br />
[[:Category:SDB:Configuration|Configuration]] - System and application configuration articles.<br />
}}<br />
{{Point here|[[Image:Icon-template.png|48px|link=]]|<br />
[[:Category:SDB:HOWTOs|HOWTOs]] - HowTo guides on a wide variety of topics.<br />
}}<br />
{{Point here|[[Image:Icon-laptop.png|48px|link=]]|<br />
[[Portal:Hardware|Hardware]] - Supported platforms, hardware compatibility lists, tweaking, optimizing, and troubleshooting.<br />
}}<br />
{{Point here|[[Image:Icon-question.png|48px|link=]]|<br />
[[FAQ|Frequently asked questions]] - Have questions or solutions to common questions about openSUSE? Feel free to add to this FAQ!<br />
}}<br />
----<br />
==openSUSE internals==<br />
openSUSE special configuration tools are usually named "YaST", because most of the work is done through YaST, but there are several independent tools one can get to know. We will try to have here a better documentation or links for these tools.<br />
<br />
*[[Portal:YaST|YaST]] - The installation and system management tool <br />
*[[Portal:Libzypp|Libzypp]] - The package management library<br />
*[[Portal:Zypper|Zypper]] - The package manager command line interface<br />
*[[SuSEfirewall2]] - The openSUSE firewall script<br />
<br />
----<br />
==Other resources==<br />
* [http://doc.opensuse.org Collection of user manuals and technical documentation] for openSUSE and SLES related products as well as projects.<br />
* The [[openSUSE:Cheat sheets|openSUSE cheat sheets]] are reference cards to print out for quick access.<br />
* The [[openSUSE:Community references|openSUSE Community references]] page collects information about community projects and their best practices, while the [[openSUSE:Marketing_references|openSUSE Marketing references]] page looks at other projects and reads what experts write about marketing. The goal is to build a reference for those that like to look beyond our own openSUSE community to learn from others.<br />
* [http://opensuse-guide.org openSUSE-Guide.org] - Unofficial guide to the basics and background of openSUSE, with screenshots, screencasts etc.<br />
* [http://oreilly.com/catalog/9780596154493 Linux in a Nutshell, Sixth Edition] Since September 2009 in it's 6th edition printing is a highly recommended book (or ebook) from beginning Linux users to the more advanced. Linux in a Nutshell will get anyone new to Linux up and running with a base of knowledge from which to grow from - in addition it offers more advanced users a handy detailed reference.</div>Rajko mhttps://en.opensuse.org/index.php?title=User:Linuxlalala1000/SDB_Draft_Using_signals&diff=62666User:Linuxlalala1000/SDB Draft Using signals2013-09-03T04:19:08Z<p>Rajko m: Rajko m moved page User:Linuxlalala1000/SDB Draft Using signals to SDB:UNIX software signals: It belongs in SDB</p>
<hr />
<div>#REDIRECT [[SDB:UNIX software signals]]</div>Rajko mhttps://en.opensuse.org/index.php?title=SDB:UNIX_software_signals&diff=62665SDB:UNIX software signals2013-09-03T04:19:08Z<p>Rajko m: Rajko m moved page User:Linuxlalala1000/SDB Draft Using signals to SDB:UNIX software signals: It belongs in SDB</p>
<hr />
<div>{{Warning|'''This article is a draft/work in progress stored as a subpage under the userpage of Linuxlalala1000.'''}}<br />
== Purpose of this article ==<br />
<br />
The purpose of this article is to inform users and system administrators about how signals are used on openSUSE and/or serve as a reference to advanced users. This article will focus on signals that can be used by the user to achieve a useful result. This means that signals issued by the kernel, such as SIGILL, will not be covered here.<br />
<br />
= Signals =<br />
<br />
The following signals are described in this article:<br />
<br />
== SIGTERM ==<br />
{{Info| Signal in a nutshell: <br />
''Signal number: 15''<br />
''Purpose: Ask a process to terminate}}<br />
When SIGTERM is sent to a process, it is requested to close all open files, initiate its termination sequence, and finally terminate itself. SIGTERM can be handled by processes in a different than standard way (signal trap). For example, a process can completely ignore the signal or request user confirmation.<br />
<br />
== SIGKILL ==<br />
{{Info|Signal in a nutshell:<br />
''Signal number: 9''<br />
''Purpose: Forcibly terminate a process''}}<br />
SIGKILL works the same as SIGTERM, but it cannot be handled by processes and does not allow the process which is being signaled to prepare and/or close it's open files, so it can be very useful if a process is malfunctioning or crashed.<br />
<br />
== SIGINT ==<br />
{{Info|Signal in a nutshell:<br />
''Signal number: 2''<br />
''Purpose: Interrupt the current operation of a process.''<br />
''Notes: Invoked by pressing Control+C''}}<br />
<br />
SIGINT is sent when the user wants the process being signaled to interrupt its current operation. This signal is sent when the user presses Control+C.<br />
<br />
== SIGSTOP ==<br />
{{Info|Signal in a nutshell:<br />
''Signal number: 19''<br />
''Purpose: Pause the execution for future resumption.''}}<br />
<br />
SIGSTOP is sent to a process when the user wants the process being signaled to be stopped for future resumption. Unlike its "more friendly" counterpart SIGTSTP, SIGSTOP cannot be trapped.<br />
<br />
== SIGTSTP ==<br />
{{Info|Signal in a nutshell:<br />
''Signal number: 20''<br />
''Purpose: Works almost exactly like SIGSTOP, but can be trapped.''}}<br />
<br />
SIGTSTP is the friendly counterpart of SIGSTOP. Like SIGSTOP, it pauses the execution of a process for further resumption, but unlike SIGSTOP, it allows the process to set a handle (trap) for it. It is automatically invoked by pressing Control + Z.<br />
<br />
{{Info|''Note: Processes stopped by SIGTSTP can be resumed with the fg command or SIGCONT.''}}<br />
<br />
== SIGCONT ==<br />
{{Info|Signal in a nutshell:<br />
''Signal number: 18''<br />
''Purpose: Resume a process paused by SIGSTOP or SIGTSTP.''<br />
''Notes: Using the command "fg" achieves the same result as this signal.''}<br />
SIGCONT resumes a process which was paused by SIGSTOP or SIGTSTP.<br />
<br />
== SIGHUP ==<br />
{{Info|Signal in a nutshell:<br />
''Signal number: 1''<br />
''Purpose: Notify a process of the termination of its controlling terminal/notify the signaled process that a modem hangup is in progress.''<br />
''Notes: Most servers/background processes set a trap to this signal and reread their configuration files on SIGHUP reception.''}}<br />
While SIGHUP was initially designed to notify the process that a modem hangup was in progress, it is now used to notify a process that the controlling terminal was closed. Most servers set a trap for this signal and reread their config file on SIGHUP reception.<br />
----<br />
= Further reading =<br />
* [http://en.wikipedia.org/wiki/Unix_signal Wikipedia's page on Unix signals]<br />
* [http://linux.die.net/man/1/pkill pkill(1) Linux manual page]<br />
* [http://linux.die.net/man/1/kill kill(1) Linux manual page]<br />
* ''The trap(1p) manual page''<br />
----<br />
{{DEFAULTSORT:{{PAGENAME}}}}<br />
<br />
[[Category:SDB:System administration]]</div>Rajko mhttps://en.opensuse.org/index.php?title=Archive:Screenshots_12.3&diff=62311Archive:Screenshots 12.32013-08-04T15:25:03Z<p>Rajko m: Reverted edits by Godfreyi (talk) to last revision by Cyberorg</p>
<hr />
<div>{{Current_distribution_navbar|12.3}}<br />
<br />
{{Intro|Screenshots of openSUSE 12.3 components. Unless explicitly stated all screenshots here must be public domain}}<br />
<br />
__TOC__<br />
<br />
== Installer ==<br />
<gallery><br />
File:Welcome_1_12.3_.png|Welcome 1<br />
File:Welcome_2_12.3_.png|Welcome 2<br />
File:System_Analysis_2_12.3.png|System Analysis<br />
File:Time_Zone_12.3.png|Time Zone<br />
File:Desktop_Selection_12.3.png|Desktop Selection<br />
File:Disk_preparation_12.3.png|Disk Preparation<br />
File:Installation-Overview_12.3.png|Installation Overview<br />
File:Installation_12.3.png|Installation<br />
</gallery><br />
<br />
== Booting ==<br />
<gallery><br />
File:OpenSUSE_12.3_welcome.jpg|Welcome to openSUSE 12.3!<br />
File:Grub2-1.png|Grub 2 Bootmenu<br />
File:Grub2-2.png|Grub 2 Bootmenu 2<br />
File:OpenSUSE_12.3_bootmenue.jpg|Legacy Bootmenu<br />
File:Plymouth.png|Bootsplash<br />
</gallery><br />
<br />
== KDE Plasma Workspaces 4.10 ==<br />
<gallery><br />
File:12.3_KDE-Welcome.png|Welcome Screen<br />
File:12.3_Activities.png|Activities<br />
File:12.3_Amarok.png|Amarok<br />
File:12.3_Animated-background-config-01.png|Animated background configuration 1<br />
File:12.3_Animated-background-config-02.png|Animated background configuration 2<br />
File:12.3_Configure_desktop.png|Configure Desktop<br />
File:12.3_Desktop-kde.png|Desktop KDE<br />
File:12.3_Filemanager.png|Filemanager<br />
File:12.3_Kaffeine-12.3.png|Kaffeine<br />
File:12.3_Kinfo.png|Sysinfo<br />
File:12.3_Kmail.png|Kmail<br />
File:12.3_Kontact.png|Kontact<br />
File:12.3_Right-click-file-manager.png|Right Click Filemanager<br />
File:12.3_Right-click-menu.png|Right Click Menu<br />
File:12.3_Shutdown.png|Shutdown<br />
File:12.3_Startup-menu.png|Startup Menu<br />
File:12.3_Widgets.png|Widgets<br />
File:12.3_Yast-01.png|Yast 01<br />
File:12.3_Yast-02.png|Yast 02<br />
</gallery><br />
<br />
== GNOME 3.6 ==<br />
<gallery><br />
File:Lock_screen1.png|Lock Screen<br />
File:Login_screen.png|Lock Screen 2<br />
File:Applications.png|Applications<br />
File:Libreoffice.png|Notification area<br />
File:Clocks.png|Clocks 1<br />
File:Clocks-2.png|Clocks 2<br />
File:File_Manager.png|File Manager<br />
File:Right_click.png|Improved Right Click Workflows<br />
File:Log_out_menu.png|User Menu<br />
File:GNOME_boxes1.png|GNOME Boxes<br />
File:GNOME_boxes2.png|GNOME Boxes 2<br />
File:GNOME_boxes3.png|GNOME Boxes customisation<br />
File:GNOME_disk_usage.png|Disk Usage Analyser<br />
File:GNOME_disks.png|Disks Tool<br />
</gallery><br />
<br />
== Enlightenment ==<br />
<gallery><br />
File:OpenSUSE_12.3_E17_desktop.jpg|E17 Desktop<br />
File:OpenSUSE_12.3_E17_menu.jpg|Menu<br />
File:OpenSUSE_12.3_E17_about.jpg|About<br />
</gallery><br />
<br />
== Xfce ==<br />
<gallery><br />
File:OpenSUSE_12.3_xfce_login.jpg|Login<br />
File:OpenSUSE_12.3_xfce_spalsh.jpg|Splash<br />
File:OpenSUSE_12.3_xfce_desktop.jpg|Desktop<br />
File:OpenSUSE_12.3_xfce_imageviewer.jpg|Image Viewer<br />
File:OpenSUSE_12.3_xfce_launcher.jpg|Launcher<br />
File:OpenSUSE_12.3_xfce_menu.jpg|Menu<br />
File:OpenSUSE_12.3_xfce_settings.jpg|Settings<br />
File:OpenSUSE_12.3_xfce_taskmgr.jpg|Task Manager<br />
File:OpenSUSE_12.3_xfce_filemanager.jpg|File Manager<br />
</gallery><br />
<br />
== LXDE ==<br />
<gallery><br />
File:12.3_LXDE_desktop.png|Desktop<br />
File:12.3_LXDE_launcher.png|Launcher<br />
File:12.3_LXDE_menu.png|Menu<br />
File:12.3_LXDE_settings.png|Settings<br />
File:12.3_LXDE_taskmanager.png|Task Manager<br />
File:12.3_LXDE_filemanager.png|File Manager<br />
</gallery><br />
<br />
== Applications ==<br />
<gallery><br />
File:OpenSUSE_12.3_xfce_firefox.jpg|Firefox<br />
File:12.3-lo.png|LibreOffice<br />
File:12.3-yast-gtk.png|YaST GTK<br />
File:OpenSUSE_12.3_YaST-ncurses.png|YaST NCurses<br />
File:Yast-kde-4.10.png|YaST Qt<br />
</gallery><br />
<br />
== openSUSE Edu Li-f-e ==<br />
<gallery><br />
File:life123-welcome.png|Welcome screen<br />
File:life123-boot.png|Boot menu<br />
File:life123-kde.png|KDE<br />
File:life123-gnome.png|GNOME<br />
File:life123-cinnamon.png|Cinnamon<br />
File:life123-edu.png|Educational applications<br />
File:life123-mulimedia.png|Multimedia apps <br />
File:life123-graphics.png|Graphics apps<br />
</gallery><br />
<br />
[[de:Bildschirmfotos]]<br />
[[es:Capturas de pantalla de la versión 12.3]]<br />
[[it:Screenshots]]<br />
[[ru:Снимки экрана 12.3]]<br />
<br />
[[Category:Screenshot|12.3]]<br />
[[Category:12.3|{{PAGENAME}}]]</div>Rajko mhttps://en.opensuse.org/index.php?title=KMail&diff=62310KMail2013-08-04T15:08:38Z<p>Rajko m: Rejected the last 4 changes (by Godfreyi) and restored revision 58336 by FirasH</p>
<hr />
<div>{{Infobox |<br />
name= KMail |<br />
developer= KDE |<br />
image= [[Image:Threading.png|200px]]|<br />
description=|<br />
license= GPL|<br />
website= http://userbase.kde.org/KMail<br />
}}<br />
==About==<br />
[[KMail]] - a mail client software, which is a part of the [[KDE]] desktop environment.<br />
<br />
It supports POP3, IMAP, dIMAP. You can send Mail via SMTP and sendmail. KMail supports OpenPGP. You can encrypt/decrypt and sign your message.<br />
<br />
==Features==<br />
* plain text and secure logins, using SSL and TLS<br />
* HTML Mail<br />
* Convert HTML Mail to Plain text<br />
* Mailing list management<br />
* Integration with spam checkers<br />
* spell-checking<br />
* Importing mail from other mail clients<br />
<br />
----<br />
==See also==<br />
* [[Thunderbird]]<br />
* [[SeaMonkey]]<br />
<br />
[[Category:Applications:Mail]]<br />
[[Category:KMail]]<br />
<br />
[[es:KMail]]<br />
[[fr:KMail]]<br />
[[it:KMail]]<br />
[[pt:KMail]]<br />
[[ru:KMail]]</div>Rajko mhttps://en.opensuse.org/index.php?title=Thunderbird&diff=62308Thunderbird2013-08-04T04:59:18Z<p>Rajko m: Rejected the last 3 changes (by Godfreyi) and restored revision 47469 by Gankov</p>
<hr />
<div>{{Infobox |<br />
name= Thunderbird |<br />
developer= Mozilla Organization |<br />
image= [[Image:Thunderbird logo.png|200px]]|<br />
description=|<br />
license= MPL v1.1/GPL v3/LGPL v3|<br />
website= http://www.mozilla.org<br />
}}<br />
{{Intro|Thunderbird is a multi-platform email/news/RSS application, available for Linux, Unix, Mac OS X, and Microsoft Windows.}}<br />
<br />
__TOC__<br />
<div class="hp_box"><br />
==Features==<br />
* Full-Featured Email<br />
* Junk Mail Filters<br />
* Anti-Phishing Protection<br />
* Advanced Security<br />
* Automatic Updates<br />
* Customize Thunderbird <br />
**Thunderbird supports OpenPGP. You can encrypt/decrypt and sign your message with the [[Enigmail]] Add-on. <br />
</div><br />
<div class="hp_box"><br />
==Current Issues==<br />
The following are issues identified with the current Thunderbird and/or Firefox packages. If you find outdated information here, please remove it.<br />
===Links in Thunderbird do NOT open in Firefox===<br />
If you update from Firefox 3 to Firefox 4, you may no longer be able to click on a link in Thunderbird and have it open in Firefox. Especially if you are using KDE. To correct the problem, issue the following as your user, from the command line:<br />
<br />
gconftool-2 --type=string -s /desktop/gnome/url-handlers/http/command "firefox %s"<br />
gconftool-2 --type=string -s /desktop/gnome/url-handlers/https/command "firefox %s"<br />
<br />
courtesy of Wolfgang on the opensuse-user list 3/31/11<br />
<br />
==See Also==<br />
* [[Mail clients|Mail programs]]<br />
* [[KMail]] <br />
* [[KNode]] <br />
* [[Sylpheed Claws]]<br />
* [[SeaMonkey |SeaMonkey Mail]]<br />
<br />
</div><br />
<div class="hp_box"><br />
<br />
==External Links==<br />
* Mozilla.org: [http://www.mozilla.org/products/thunderbird/ Product : Thunderbird] with links to download the newest thunderbird as a tar archive (not recommended for openSUSE) and to related Release Notes <br />
</div><br />
<br />
[[de:Mozilla Thunderbird]]<br />
[[es:Mozilla Thunderbird]]<br />
[[fr:Thunderbird]]<br />
[[pt:Thunderbird]]<br />
[[ru:Thunderbird]]<br />
<br />
[[Category:Applications:Mail]]<br />
[[Category:Applications:News]]<br />
[[Category:Mozilla|Thunderbird]]</div>Rajko mhttps://en.opensuse.org/index.php?title=SDB:Software_tweaks_to_improve_graphics&diff=62300SDB:Software tweaks to improve graphics2013-08-02T13:31:02Z<p>Rajko m: moved SDB:Using software tweaks to remedy graphical glithces to SDB:Software tweaks to improve graphics: shorter is better</p>
<hr />
<div>{{SDB_navbar}}<br />
{{Knowledge|<br />
*[[Portal:12.3|12.3]]<br />
|<br />
*[[SDB:AMD graphics troubleshooting]]<br />
*[[SDB:NVIDIA troubleshooting]]<br />
|<br />
*[[SDB:Configuring_graphics_cards]]<br />
}}<br />
{{Warning|Use the information presented on this page at your own risk!}} <br />
<br />
This article tries to document various tweaks in applications which may help remedy graphical glitches. The tricks are listed here by application.<br />
<br />
== Situation ==<br />
<br />
You are experiencing graphical glitches, but after extensively testing your graphics card, you find out that your hardware is not faulty. <br />
----<br />
== Procedure ==<br />
<br />
This article describes several solutions:<br />
== KDE ==<br />
<br />
=== Disable compositing in kwin ===<br />
<br />
Disabling compositig in kwin is known to fix glitches such as parts of windows being displayed in random places, seemingly corrupted framebuffer, and similar. It is also known to improve general system performance for systems with graphic cards that don't have sufficient support in Linux, forcing kwin to use software emulation. <br />
<br />
==== By editing a configuration file ====<br />
Use your favorite plain text editor to edit <tt>~/.kde4/share/config/kwinrc</tt>.<br />
In the end of the section that reads [Compositing], add the following line:<br />
<pre><br />
Enabled=false<br />
</pre><br />
<br />
==== By changing KDE's System Settings ====<br />
From the favorites tab in klauncher, open "Configure Desktop", select "Desktop Effects", then uncheck the checkbox that is called "Enable desktop effects at startup". From the same screen,<br />
you can define a shortcut to enable/disable compositing anytime.<br />
<br />
== Mozilla Firefox ==<br />
<br />
=== Disable smooth scrolling ===<br />
<br />
This tweak is known to fix font corruption while scrolling.<br />
<br />
Open the Firefox preferences dialog (''Edit>Preferences''), select the Advanced tab. Select the General subtab,then untick ''Use smooth scrolling''.<br />
<br />
=== Disable hardware acceleration ===<br />
<br />
On the Firefox preferences dialog (''Edit>Preferences''), select the Advanced tab. Select the General subtab,then untick ''Use hardware acceleration when available''.<br />
<br />
== X.org ==<br />
<br />
=== Try using the latest X11 from the X11 repository ===<br />
<br />
{{Warning| This repository might contain unstable code which may crash often, be buggy or interfere with the machine's normal booting process. The author is not responsible if anything happens to your machine.}} <br />
<br />
==== Adding the repository ====<br />
<br />
As root, run the following:<br />
<br />
<pre><br />
zypper ar http://download.opensuse.org/repositories/X11:/XOrg/openSUSE_Version/X11:XOrg.repo<br />
</pre><br />
{{Info| Replace with Version with your own OpenSUSE version}}<br />
<br />
==== Changing vendor for X-related packages and updating ====<br />
<br />
As root, execute the following command:<br />
<pre><br />
zypper dup --from X11_XOrg<br />
</pre><br />
Wait for the update to finish, then reboot.<br />
<br />
== If everything fails ==<br />
<br />
=== Check the troubleshooting article which applies to your GPU ===<br />
<br />
Try following the instruction on the troubleshooting section/article applicable to your Graphics Card (check the recommended articles for this article).<br />
<br />
=== Check whether your GPU is faulty ===<br />
<br />
Try using benchmark/stress test tools in order to determine if your Graphics Card is faulty. It is recommended you run a demanding video game with hardware acceleration enabled and on the "Ultra" settings/profile. If any artifacts are displayed, then there is a great possibility your Graphics Card is faulty.<br />
<br />
[[Category:SDB:X11]]<br />
<br />
{{DEFAULTSORT:{{PAGENAME}}}}</div>Rajko mhttps://en.opensuse.org/index.php?title=SDB:Software_tweaks_to_improve_graphics&diff=62298SDB:Software tweaks to improve graphics2013-08-02T13:13:17Z<p>Rajko m: /* Disable compositing in kwin */ improving performance in some systems (not all)</p>
<hr />
<div>{{SDB_navbar}}<br />
{{Knowledge|<br />
*[[Portal:12.3|12.3]]<br />
|<br />
*[[SDB:AMD graphics troubleshooting]]<br />
*[[SDB:NVIDIA troubleshooting]]<br />
|<br />
*[[SDB:Configuring_graphics_cards]]<br />
}}<br />
{{Warning|Use the information presented on this page at your own risk!}} <br />
<br />
This article tries to document various tweaks in applications which may help remedy graphical glitches. The tricks are listed here by application.<br />
<br />
== Situation ==<br />
<br />
You are experiencing graphical glitches, but after extensively testing your graphics card, you find out that your hardware is not faulty. <br />
----<br />
== Procedure ==<br />
<br />
This article describes several solutions:<br />
== KDE ==<br />
<br />
=== Disable compositing in kwin ===<br />
<br />
Disabling compositig in kwin is known to fix glitches such as parts of windows being displayed in random places, seemingly corrupted framebuffer, and similar. It is also known to improve general system performance for systems with graphic cards that don't have sufficient support in Linux, forcing kwin to use software emulation. <br />
<br />
==== By editing a configuration file ====<br />
Use your favorite plain text editor to edit <tt>~/.kde4/share/config/kwinrc</tt>.<br />
In the end of the section that reads [Compositing], add the following line:<br />
<pre><br />
Enabled=false<br />
</pre><br />
<br />
==== By changing KDE's System Settings ====<br />
From the favorites tab in klauncher, open "Configure Desktop", select "Desktop Effects", then uncheck the checkbox that is called "Enable desktop effects at startup". From the same screen,<br />
you can define a shortcut to enable/disable compositing anytime.<br />
<br />
== Mozilla Firefox ==<br />
<br />
=== Disable smooth scrolling ===<br />
<br />
This tweak is known to fix font corruption while scrolling.<br />
<br />
Open the Firefox preferences dialog (''Edit>Preferences''), select the Advanced tab. Select the General subtab,then untick ''Use smooth scrolling''.<br />
<br />
=== Disable hardware acceleration ===<br />
<br />
On the Firefox preferences dialog (''Edit>Preferences''), select the Advanced tab. Select the General subtab,then untick ''Use hardware acceleration when available''.<br />
<br />
== X.org ==<br />
<br />
=== Try using the latest X11 from the X11 repository ===<br />
<br />
{{Warning| This repository might contain unstable code which may crash often, be buggy or interfere with the machine's normal booting process. The author is not responsible if anything happens to your machine.}} <br />
<br />
==== Adding the repository ====<br />
<br />
As root, run the following:<br />
<br />
<pre><br />
zypper ar http://download.opensuse.org/repositories/X11:/XOrg/openSUSE_Version/X11:XOrg.repo<br />
</pre><br />
{{Info| Replace with Version with your own OpenSUSE version}}<br />
<br />
==== Changing vendor for X-related packages and updating ====<br />
<br />
As root, execute the following command:<br />
<pre><br />
zypper dup --from X11_XOrg<br />
</pre><br />
Wait for the update to finish, then reboot.<br />
<br />
== If everything fails ==<br />
<br />
=== Check the troubleshooting article which applies to your GPU ===<br />
<br />
Try following the instruction on the troubleshooting section/article applicable to your Graphics Card (check the recommended articles for this article).<br />
<br />
=== Check whether your GPU is faulty ===<br />
<br />
Try using benchmark/stress test tools in order to determine if your Graphics Card is faulty. It is recommended you run a demanding video game with hardware acceleration enabled and on the "Ultra" settings/profile. If any artifacts are displayed, then there is a great possibility your Graphics Card is faulty.<br />
<br />
[[Category:SDB:X11]]<br />
<br />
{{DEFAULTSORT:{{PAGENAME}}}}</div>Rajko mhttps://en.opensuse.org/index.php?title=User:Linuxlalala1000&diff=62280User:Linuxlalala10002013-08-01T14:27:42Z<p>Rajko m: make link subpage</p>
<hr />
<div><!-- Created using Template:Userpage. <br />
--><div style="width:70%; float:left;clear:left"><br />
{{Box-header|About Me|{{FULLPAGENAME}}|}}<br />
* '''What I like about openSUSE?'''<br />
I like its flexibility. The very fact it can be installed on a variety of systems and built-to-order by using SUSE studio or other tools for more complex situations is considered by me the best fact about OpenSUSE.<br />
* '''What am I doing at openSUSE?''' <br />
I will be writing wiki articles about issues I have solved and I have not found a solution on the Internet.<br />
* '''Notice:'''<br />
This account is the same as the inactive linuxlalala, which I cannot access.<br />
{{Box-footer|}}<br />
* '''My draft articles:'''<br />
[[User:linuxlalala1000/Graphics_tweaks|Software tweaks to remedy various graphical glitches (not yet properly named)]]<br />
</div><br />
<div style="width:30%; float:right; clear:right"><br />
{{Box-header|Contact|{{FULLPAGENAME}}|}}<br />
<br />
* [mailto:linuxlalala@hushmail.com My mail]<br />
* linuxlalala on [irc://irc.freenode.net IRC]<br />
<br />
{{Box-footer|}}<br />
</div><br />
<br style="clear:both;" /><br />
<br />
[[Category:Created with Userpage]]</div>Rajko mhttps://en.opensuse.org/index.php?title=Kaffeine&diff=61155Kaffeine2013-05-19T17:39:15Z<p>Rajko m: /* External Links */ Updated Xine link.</p>
<hr />
<div>{{Intro|'''Kaffeine''' is a full featured Multimedia-Player for [[KDE]]. By default it uses [[XINE]] as backend. Kaffeine is free software distributed under the terms of the GNU General Public License.}}{{Infobox |<br />
packagename=kaffeine|<br />
name=Kaffeine|<br />
developer=Kaffeine team|<br />
image= [[Image:Kde4-Kaffeine-main.png|200px]]|<br />
description= showing the main window of Kaffeine|<br />
vendor= |<br />
license= GPL|<br />
website= http://kaffeine.kde.org/|<br />
}}<br />
__TOC__<br />
<br />
<br />
==Installing the full version (more supported codecs) of Kaffeine==<br />
'''Note:'''Last update to [http://kaffeine.kde.org kaffeine.kde.org] was in April 2011. Currently 2 years ago, which usually indicates abandoned project.<br />
<br />
[http://packman.links2linux.org/package/kaffeine Click here] and click the '''One Click Install''' button.<br />
{{Info|Currently Packman only provides packages for [http://packman.links2linux.org/package/kde3-kaffeine kde3-kaffeine], for KDE4 just follow these instructions about [http://opensuse-community.org/Restricted_formats restricted formats installing]. On that page please select the guide suitable for your openSUSE release.<br />See [[restricted formats]] article, as well.}}<br />
<br />
<br />
==Features==<br />
* Audio Effects<br />
* DVD/VCD playback with navigation.<br />
* CDDA playback and ripping. Encoders for mp3 and OggVorbis.<br />
* Plays streams embedded in webpages<br />
* Digital Video Broadcasting<br />
* Live playback of digital TV. OSD program description.<br />
<br />
<br />
==Troubleshooting==<br />
{{Info|Full versions of '''xine''' or '''gstreamer''' are required for playback of certain audio and video codecs}}<br />
<br />
'''Q:''' '''Kaffeine''' gives an error message when trying to play DVD's<br />
<br />
'''A:''' The version shipped with openSUSE does not support DVD playback, download the full version of '''Kaffeine''' from the Packman website.<br />
<br />
'''Q:''' I cannot play copyright protected DVD's <br />
<br />
'''A:''' Please read the [[XINE]] page for a workaround.<br />
<br />
<br />
==See Also==<br />
*[[XINE]]<br />
*[[Totem]]<br />
<br />
<br />
==External Links==<br />
*http://www.xine-project.org/<br />
*http://kaffeine.sourceforge.net/<br />
<br />
[[Category:Applications:Multimedia]]<br />
<br />
[[es:Kaffeine]]<br />
[[it:Kaffeine]]<br />
[[pt:Kaffeine]]<br />
[[ru:Kaffeine]]</div>Rajko mhttps://en.opensuse.org/index.php?title=Kaffeine&diff=61154Kaffeine2013-05-19T16:46:51Z<p>Rajko m: </p>
<hr />
<div>{{Intro|'''Kaffeine''' is a full featured Multimedia-Player for [[KDE]]. By default it uses [[XINE]] as backend. Kaffeine is free software distributed under the terms of the GNU General Public License.}}{{Infobox |<br />
packagename=kaffeine|<br />
name=Kaffeine|<br />
developer=Kaffeine team|<br />
image= [[Image:Kde4-Kaffeine-main.png|200px]]|<br />
description= showing the main window of Kaffeine|<br />
vendor= |<br />
license= GPL|<br />
website= http://kaffeine.kde.org/|<br />
}}<br />
__TOC__<br />
<br />
<br />
==Installing the full version (more supported codecs) of Kaffeine==<br />
'''Note:'''Last update to [http://kaffeine.kde.org kaffeine.kde.org] was in April 2011. Currently 2 years ago, which usually indicates abandoned project.<br />
<br />
[http://packman.links2linux.org/package/kaffeine Click here] and click the '''One Click Install''' button.<br />
{{Info|Currently Packman only provides packages for [http://packman.links2linux.org/package/kde3-kaffeine kde3-kaffeine], for KDE4 just follow these instructions about [http://opensuse-community.org/Restricted_formats restricted formats installing]. On that page please select the guide suitable for your openSUSE release.<br />See [[restricted formats]] article, as well.}}<br />
<br />
<br />
==Features==<br />
* Audio Effects<br />
* DVD/VCD playback with navigation.<br />
* CDDA playback and ripping. Encoders for mp3 and OggVorbis.<br />
* Plays streams embedded in webpages<br />
* Digital Video Broadcasting<br />
* Live playback of digital TV. OSD program description.<br />
<br />
<br />
==Troubleshooting==<br />
{{Info|Full versions of '''xine''' or '''gstreamer''' are required for playback of certain audio and video codecs}}<br />
<br />
'''Q:''' '''Kaffeine''' gives an error message when trying to play DVD's<br />
<br />
'''A:''' The version shipped with openSUSE does not support DVD playback, download the full version of '''Kaffeine''' from the Packman website.<br />
<br />
'''Q:''' I cannot play copyright protected DVD's <br />
<br />
'''A:''' Please read the [[XINE]] page for a workaround.<br />
<br />
<br />
==See Also==<br />
*[[XINE]]<br />
*[[Totem]]<br />
<br />
<br />
==External Links==<br />
*http://www.xinehq.de/<br />
*http://kaffeine.sourceforge.net/<br />
<br />
[[Category:Applications:Multimedia]]<br />
<br />
[[es:Kaffeine]]<br />
[[it:Kaffeine]]<br />
[[pt:Kaffeine]]<br />
[[ru:Kaffeine]]</div>Rajko mhttps://en.opensuse.org/index.php?title=SDB:NVIDIA&diff=61153SDB:NVIDIA2013-05-19T16:32:18Z<p>Rajko m: Rejected the last change (by Bkorb) and restored revision 58701 by FirasH</p>
<hr />
<div>{{Nvidia navbox}}<br />
There are two kinds of '''drivers for NVIDIA video cards''':<br />
* The [[Free and Open Source Software|Free and Open Source]] drivers for hardware from NVIDIA are named ''nouveau''.<br />
* The drivers from the hardware manufacturer NVIDIA are themselves named ''nvidia'' and cannot be integrated directly into openSUSE because of [[Restricted formats|their license]].<br />
Fortunately for the new users, NVIDIA and openSUSE provide a very easy way to install NVIDIA drivers using [[YaST]].<br />
<br />
{{Intro|'''To install proprietary NVIDIA driver, please consult:'''<br />
* '''[[SDB:NVIDIA drivers]] if you want to use the package management system (regular users)'''<br />
* '''[[SDB:NVIDIA the hard way]] if you want to install them manually (experts)'''<br />
* '''[[SDB:NVIDIA troubleshooting]] if you experience problems with the proprietary drivers'''<br />
See [[HCL:Nvidia video cards]] for a list of hardware tested by the community.<br />
}}<br />
<br />
{{DEFAULTSORT:{{PAGENAME}}}}<br />
<br />
[[Category:SDB:Hardware]]<br />
[[Category:SDB:HOWTOs]]<br />
[[Category:SDB:X11]]<br />
[[Category:NVIDIA|1]]<br />
<br />
[[de:SDB:NVIDIA]]<br />
[[es:SDB:NVIDIA]]<br />
[[fr:SDB:NVIDIA]]<br />
[[it:SDB:NVIDIA]]<br />
[[ru:SDB:NVIDIA]]</div>Rajko mhttps://en.opensuse.org/index.php?title=User_talk:Abhijeetv2&diff=61152User talk:Abhijeetv22013-05-19T16:29:41Z<p>Rajko m: </p>
<hr />
<div>Hi Abhijeetv2,<br />
<br />
as student of electrical engineering you should be a bit more careful about editing wiki documentation. Your last changes to [[Help:Concept]] demolished page and are rejected. --Rajko m 10:29, 19 May 2013 (MDT)</div>Rajko mhttps://en.opensuse.org/index.php?title=User_talk:Abhijeetv2&diff=61151User talk:Abhijeetv22013-05-19T16:29:21Z<p>Rajko m: Demolished wiki help page.</p>
<hr />
<div>Hi Abhijeetv2,<br />
<br />
as student of electrical engineering you should be a but more careful about editing wiki documentation. Your last changes to [[Help:Concept]] demolished page and are rejected. --Rajko m 10:29, 19 May 2013 (MDT)</div>Rajko m