[opensuse-project] Some questions about openSUSE
Hi, I'm involved both in Debian and Ubuntu development, and I'm often frustrated by how little I know about the other distributions. After discussing this in a blog post[1], I got the impression that I wasn't alone in that case. So I decided to do something about that, and to go ask the other distributions' developers a few questions. If this works well (answers and interest from other distros), I might do that again, or turn this into something more formal (for example, a mailing list and/or a wiki would seem well suited for that). I'll publish the answers on my blog[2], and, if this proves to raise interest, move them to a wiki. [1] http://www.lucas-nussbaum.net/blog/?p=250 [2] http://www.lucas-nussbaum.net/blog/ Here is a first set of questions. In your answers, please avoid codenames (act as if the reader didn't know anything about your distribution). Please try to write your answer as a short paragraph, answering all the sub-questions from the questions at once. Q1. Packages How many "pieces of software" do you have in your distribution? Do you distinguish between "source packages" and "binary packages"? (if yes, give numbers for both). Are there subdivisions in the set of packages (by kind of support, by "freeness")? Are all packages supported the same way, or are there different levels of support? (If different levels, how many packages are supported with each level?) Are some packages imported from another distribution, or are most of your packages done from scratch by your developers ? Q2. Your developers What's a "developer" in your distribution? How many developers do you have? How many of these developers were active in 2007? Does a company (which one?) employ a large number of developers? Do you have different "classes" of developers, or does everybody have the same access right to all your packages? How do you integrate new developers? How do you handle contributors who don't have access rights to the archive? (is there some kind of sponsoring system?) Q3. Developers and packages ownership What's the relationship between developers and packages? Does each package have an assigned developer, or can everybody modify all packages without stepping on anyone's toes? Are packages mostly maintained by teams, or by developers working alone? Other questions: - Did I send that mail to the right mailing list? - Which question should I have asked? What should I ask next? - Do you think that this initiative is interesting? - Do you think that this should move to a seperate mailing list? Would you participate in such a mailing list? - Can you suggest a project that could host such a mailing list without annoying anyone? :) - Any other suggestions? Thank you for reading me so far -- and for answering my questions if you did. ;) If you want me to ping you when I'll publish the answers, just drop me a mail. -- | Lucas Nussbaum | lucas@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lucas@nussbaum.fr GPG: 1024D/023B3F4F | --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Lucas Nussbaum wrote:
Hi,
Hi Lucas
I'm involved both in Debian and Ubuntu development, and I'm often frustrated by how little I know about the other distributions. After discussing this in a blog post[1], I got the impression that I wasn't alone in that case.
Indeed.
So I decided to do something about that, and to go ask the other distributions' developers a few questions. If this works well (answers and interest from other distros), I might do that again, or turn this into something more formal (for example, a mailing list and/or a wiki would seem well suited for that).
(Almost) any cross-distro effort is worth joining. [...]
Q1. Packages How many "pieces of software" do you have in your distribution? Do you distinguish between "source packages" and "binary packages"? (if yes, give numbers for both). Are there subdivisions in the set of packages (by kind of support, by "freeness")? Are all packages supported the same way, or are there different levels of support? (If different levels, how many packages are supported with each level?) Are some packages imported from another distribution, or are most of your packages done from scratch by your developers ?
First of all, disclaimer: I'm not employed by Novell ;) OK, short answer first: the upcoming openSUSE 10.3 (at RC1 right now) has approximatively 3550 source packages and 6400 binary packages (only counting one architecture + noarch (portable) packages). If we also count what's in the openSUSE Build Service (see below for details), it's 3550+7200 = 10750. Also counting the most popular and very widely used 3rd party community repository Packman, that's +1314 =~ 12050 source packages. The number of binary packages can usually be inferred from that (I'm too lazy to count those, especially in the Build Service ;)), say 14000 binary packages. The packages of the "core" openSUSE distribution itself are divided in OSS (packages with OSI-compliant licenses, 98%) and non-OSS (2%) -- percentage based on number of source packages. All packages are made from scratch. There are differences in the level of support as well, as only the packages shipped with the distribution are being actively worked on by the developers whom are Novell employees, where as the packages maintained in the openSUSE Build Service and 3rd party repositories are supported on a voluntary basis, by people working on it during their free time. Also, bugfixes and security fixes on distribution packages are pushed through the openSUSE Online Update service. I won't even mention Novell's enterprise openSUSE derivatives (dubbed SUSE Linux Enterprise Desktop (SLED) and SUSE Linux Enterprise Server (SLES)), that both have a much higher degree of support, for obvious reasons (same as RHEL, for example). In terms of support as explained above and based on the numbers above, for openSUSE, it's 33% with support, 66% "unsupported" (or rather, not supported by Novell employees during their paid worktime ;)). Here come the gory details, for those whom might be interested: openSUSE 10.3 RC1 currently has the following amount of packages: * OSS (OSI-compliant) packages * source: 3502 * i586..: 5137 * x86_64: 5435 * noarch: 1226 * non-OSS packages * source: 49 * i586..: 59 * x86_64: 43 * noarch: 23 But that's only the tip of the iceberg, as the openSUSE Build Service[1] hosts many, many more packages for several distributions. The current count of _source_ packages in there is 23904, but that includes automated ports of all Debian packages (11153) and personal, highly experimental builds (5568) -- so let's count 23904 - 11153 - 5568 for the Build Service = 7183 source packages there. [1] http://en.opensuse.org/Build_Service So, to sum it up, the "core distribution" contains * 3551 source packages (counting OSS and non-OSS) * 6412 binary packages (counting only i586+noarch, not x86_64) The total amount of packages available to openSUSE users is rather around 30000 (there are several 3rd party community repositories as well, such as Packman [2]). As an example, Packman currently has: * source: 1314 * i586 : 2535 * x86_64: 2380 * noarch: 436 And my own Guru repository has: * source: 1964 * i586 : 896 * x86_64: 911 * noarch: 67 [2] http://packman.links2linux.org All in all, 14000 binary packages is probably a pretty accurate estimation. There are several levels of "support", indeed, as * packages of the core distribution are supported by the openSUSE development teams, taking bugreports, and pushing fixes through the openSUSE Online Updates service * Build Service and 3rd party repository packages are not really supported, beyond the usual sending an email to the package maintainer Novell's enterprise derivatives of openSUSE (dubbed "SLES" and "SLED" [3]) obviously provide an additional level of support, that is categorized from Level 1 to Level 3 (the higher the better). I won't go into much detail about that stuff, it's documented on Novell's website and not really on topic (IMO). [3] SUSE Linux Enterprise Server|Desktop
Q2. Your developers What's a "developer" in your distribution? How many developers do you have? How many of these developers were active in 2007? Does a company (which one?) employ a large number of developers? Do you have different "classes" of developers, or does everybody have the same access right to all your packages? How do you integrate new developers? How do you handle contributors who don't have access rights to the archive? (is there some kind of sponsoring system?)
That's a tricky question as it will be the case with all other distributions except 100% community distros such as Debian and Gentoo, because there are people who are employed by Novell to work on the distribution and its packages, whereas most of the same people also contribute to other efforts (including packages) during their spare time. And then, of course, there are a lot of people from the community as well. I would still say that "developers" are package maintainers, application developers (on openSUSE specific tools), web designers (on openSUSE related websites). Arguably, that could also be limited to the developers working for Novell. That sort of thing is currently very much in flux in the openSUSE community right now, so it's a little difficult to answer ;) The access to the packages is currently not the same for everyone, as the packages that are part of the "core" distribution itself are only modifiable for Novell employees, although there is some collaboration and communication with packagers from the community on those. That, too, is something that is going to change in the future as well though. There is currently no sponsoring system of any sort. I can't tell you the number of developers paid by Novell for working on the distribution. Could someone else give Lucas some figures on that ? AJ, Coolo, Martin, Adrian, Michl ?
Q3. Developers and packages ownership What's the relationship between developers and packages? Does each package have an assigned developer, or can everybody modify all packages without stepping on anyone's toes? Are packages mostly maintained by teams, or by developers working alone?
Depends. For the openSUSE distribution packages, it's mostly teams (KDE team, GNOME team, Mobile Devices team, Security team, etc...) [4] Packages in the openSUSE Build Service can have several people working on them but in practice, as of now, it's typically one package == one maintainer. But the openSUSE Build Service is still a rather young project ;) Packages in 3rd party aka community repositories are almost always maintained by a single packager. A notable exception is the Packman repository that is maintained by a team, but even there, it's mostly a single maintainer per package. [4] http://en.opensuse.org/Category:Teams
Other questions:
- Did I send that mail to the right mailing list?
Yes, absolutely :) You get bonus points for having found your way in our tangle of mailing-lists ;)
- Which question should I have asked? What should I ask next?
Your questions are very interesting (wrt comparing different distributions). Maybe the community apparels (events, structure, board, ...) are worth investigating too.
- Do you think that this initiative is interesting?
Possibly. If it leads to some productive and positive collaboration (or even communication) between distributions, then it's _very_ interesting ;)
- Do you think that this should move to a separate mailing list? Would you participate in such a mailing list?
I would.
- Can you suggest a project that could host such a mailing list without annoying anyone? :)
No. I mean, I'm pretty sure it could be done through an additional mailing-list over here. I wouldn't mind subscribing to a dedicated list on another distributions' infrastructure though ;)
- Any other suggestions?
Keep up the good work and stay open minded :)
Thank you for reading me so far -- and for answering my questions if you did. ;) If you want me to ping you when I'll publish the answers, just drop me a mail.
Sure. cheers - -- -o) Pascal Bleser http://linux01.gwdg.de/~pbleser/ /\ <pascal.bleser@skynet.be> <guru@unixtech.be> __v The more things change, the more they stay insane. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFG8sFer3NMWliFcXcRApaKAJ9BHglQLXCWCwyZHTdWcoPcK1RnKwCggipT dsK3gjLD5N7U4VnCsJokNXg= =AvOr -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
On 9/20/07, Pascal Bleser <pascal.bleser@skynet.be> wrote:
[2] http://packman.links2linux.org
All in all, 14000 binary packages is probably a pretty accurate estimation.
Just a note as well that comparing physical amount of packages between distributions in a typical way might not be so meaningful because of the different packaging methods. openSUSE packaging did (particularly in the past) tend to be a lot more modular. For example in KDE3 while we have kdebase3, in Ubuntu/Debian they have kdebase, kate, kfind, kcontrol, khelpcenter, kwrite, kwin packages etc etc ...for the same one package that we would have. So frequently people get the impression that Debian-based distributions have thousands of thousands more applications because of what Synaptic and Adept tells them (in contrast to YaST), but it's not so clear-cut. A more interesting comparison might be the amount of bin/* files. Source packages is interesting too. As for learning about the community -- why not join us for a while and see what it's like? :-) Getting involved in other communities is not nearly as difficult as you would think (for example, anyone can get an openSUSE build service account straight away), and it's the best way to get a real idea of things, especially if you're willing to investigate with the tools around etc. :-) Kind thoughts, -- Francis Giannaros http://francis.giannaros.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Francis Giannaros wrote:
On 9/20/07, Pascal Bleser <pascal.bleser@skynet.be> wrote:
[2] http://packman.links2linux.org
All in all, 14000 binary packages is probably a pretty accurate estimation.
Just a note as well that comparing physical amount of packages between distributions in a typical way might not be so meaningful because of the different packaging methods. openSUSE packaging did (particularly in the past) tend to be a lot more modular.
Less modular, actually ;)
For example in KDE3 while we have kdebase3, in Ubuntu/Debian they have kdebase, kate, kfind, kcontrol, khelpcenter, kwrite, kwin packages etc etc ...for the same one package that we would have.
True. Debian has lot more fine grained packages than openSUSE (which is probably rather a good thing (for Debian), although both have pros and cons).
So frequently people get the impression that Debian-based distributions have thousands of thousands more applications because of what Synaptic and Adept tells them (in contrast to YaST), but it's not so clear-cut.
True. But well, I doubt Lucas is collecting that information to do some distro bashing ;) It's worth noting though.
A more interesting comparison might be the amount of bin/* files.
Not sure that would be a better indicator in any way.
Source packages is interesting too.
Yes, source packages are much more informative than binary packages, which is why the numbers I gave Lucas are mostly mentioning the former.
As for learning about the community -- why not join us for a while and see what it's like? :-) Getting involved in other communities is not nearly as difficult as you would think (for example, anyone can get an openSUSE build service account straight away), and it's the best way to get a real idea of things, especially if you're willing to investigate with the tools around etc. :-)
I'm sure Lucas already has a lot of work on his hands ;) But clearly, I'm 200% in favour of any cross-distro effort of any kind (heck, I'm organizing the developer rooms at FOSDEM ;)). Keep the trolls away, get the people who really do stuff together, and something can be done, for sure. Lucas' initiative could be a starting point for something, who knows. Which is why I think the mailing-list he's proposing is even more interesting wrt that. cheers - -- -o) Pascal Bleser http://linux01.gwdg.de/~pbleser/ /\ <pascal.bleser@skynet.be> <guru@unixtech.be> __v The more things change, the more they stay insane. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFG8tBTr3NMWliFcXcRAlWMAJ9g68DU9Ua0o43yvMkHs/vmk03OAwCdHPsL Gy4Xcf/rFbD0+UQjHWRpnjk= =J20g -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
Pascal Bleser wrote:
There is currently no sponsoring system of any sort.
may be there is something but not clear: AMD is now a sponsor of openSUSE, but how?
- Which question should I have asked? What should I ask next?
I don't know is this is relevant, but the main community (non-novell) participation is documentation. many package are given through packman or guru, but this is a (very intersting) work by a very little number of people (as said by Pascal). the maximum number of people acting for opensuse are "hotliners" and doc writers (wiki, translations, manuals, lessons for lizards...) I understand this is not what is understood as developper work, but IMHO this is as important as the other part, a good programm without documentation being impaired :-). I must say there have always been very smart programmers in the open source world, the doc was often very far behind :-)) jdd -- http://www.dodin.net --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 jdd wrote:
Pascal Bleser wrote:
There is currently no sponsoring system of any sort.
may be there is something but not clear: AMD is now a sponsor of openSUSE, but how?
AFAIK, AMD sponsors the openSUSE Build Service through a large amount of hardware. Lucas was referring to rewarding packagers for their contributions. At least that was my understanding.
- Which question should I have asked? What should I ask next?
I don't know is this is relevant, but the main community (non-novell) participation is documentation.
I would say it's testing and bug reports.
many package are given through packman or guru, but this is a (very interesting) work by a very little number of people (as said by Pascal).
the maximum number of people acting for opensuse are "hotliners" and doc writers (wiki, translations, manuals, lessons for lizards...)
I understand this is not what is understood as developer work, but IMHO this is as important as the other part, a good program without documentation being impaired :-).
Sure. But I really think that Lucas is concentrating his research around the technical aspects of the distributions, which is mostly packaging, communication with upstream, bug triage, ... That obviously doesn't mean that documentation or any other sort of contribution (support, forums, testing, advocating, ...) isn't equally important. cheers - -- -o) Pascal Bleser http://linux01.gwdg.de/~pbleser/ /\ <pascal.bleser@skynet.be> <guru@unixtech.be> __v The more things change, the more they stay insane. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFG8tGFr3NMWliFcXcRAv3SAJ0VR7JxIz+7JwQcRpzCgjgFr2CJCACeNKQO fwSsrFTljOLCjE6SY4qpODY= =1nR2 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
On 20/09/07 at 22:01 +0200, Pascal Bleser wrote:
jdd wrote:
Pascal Bleser wrote:
There is currently no sponsoring system of any sort.
may be there is something but not clear: AMD is now a sponsor of openSUSE, but how?
AFAIK, AMD sponsors the openSUSE Build Service through a large amount of hardware. Lucas was referring to rewarding packagers for their contributions. At least that was my understanding.
Actually, there was clearly a problem with my question. I tried to ask them in a distribution-agnostic way, but I failed with this one. :-) My question should have been: How do you integrate new contributors, before they reach the point where you are confident about giving them write access to your repositories? (we use a "sponsorship process" for that in Debian, where a non-Debian Developer creates the package, and then find a DD willing to review it, and upload it under its own responsibility).
I understand this is not what is understood as developer work, but IMHO this is as important as the other part, a good program without documentation being impaired :-).
Sure. But I really think that Lucas is concentrating his research around the technical aspects of the distributions, which is mostly packaging, communication with upstream, bug triage, ...
That obviously doesn't mean that documentation or any other sort of contribution (support, forums, testing, advocating, ...) isn't equally important.
I'll try to ask questions about non-packaging work in the next set of questions. This is a very interesting aspect (and one where Debian isn't really good currently). On 20/09/07 at 20:31 +0100, Francis Giannaros wrote:
As for learning about the community -- why not join us for a while and see what it's like? :-) Getting involved in other communities is not nearly as difficult as you would think (for example, anyone can get an openSUSE build service account straight away), and it's the best way to get a real idea of things, especially if you're willing to investigate with the tools around etc. :-)
I must admit that I'm happy with my current involvement in Free Software (means: with Debian, and a bit with Ubuntu). Also, to make that effort worthwhile, I have to contact all the major distros: getting involved in the community of all the major distros at the same time is not going to be easy ;) Thank you all very much for your very interesting answers :-) -- | Lucas Nussbaum | lucas@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lucas@nussbaum.fr GPG: 1024D/023B3F4F | --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
On Fri, 21 Sep 2007, Lucas Nussbaum wrote:
How do you integrate new contributors, before they reach the point where you are confident about giving them write access to your repositories?
There are several answers to that: One is "We don't have such a probation period", we give anyone who wants write access to the build service to create, build, maintain, and offer packages of their own right away. Another one is that package maintainers take patches via Bugzilla or other means (e-mail to the respective open mailing lists, direct mail, upstream collaboration). This is how many Novell employees (including myself whose regular job doesn't include hacking) and our partners actually contribute as well. And yet another answer is that we are looking at ways in terms of processes and infrastructure to make this even easier. As a package maintainer it would be really cool to look at a diff between my package and a variant thereof in the openSUSE Build Service and have a simple way of just approving a merge of the whole set of changes or a part thereof into mine.
(we use a "sponsorship process" for that in Debian, where a non-Debian Developer creates the package, and then find a DD willing to review it, and upload it under its own responsibility).
That's similar to what we also do at FreeBSD.
I'll try to ask questions about non-packaging work in the next set of questions. This is a very interesting aspect (and one where Debian isn't really good currently).
One thing Debian is good it, if I understood that correctly, is hooking the Debian bug tracking system into others (upstream) and also keeping the bug tracking system in the loop of e-mail discussions. Comparing various approaches there is something I'd find interesting. It is definitely something where openSUSE has lots of room for improvement. Gerald -- Dr. Gerald Pfeifer E gp@novell.com SUSE Linux Products GmbH Director Inbound Product Mgmt T +49(911)74053-0 HRB 16746 (AG Nuremberg) openSUSE/SUSE Linux Enterprise F +49(911)74053-483 GF: Markus Rex --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Gerald Pfeifer wrote:
On Fri, 21 Sep 2007, Lucas Nussbaum wrote: [...]
(we use a "sponsorship process" for that in Debian, where a non-Debian Developer creates the package, and then find a DD willing to review it, and upload it under its own responsibility).
That's similar to what we also do at FreeBSD.
Sounds like a good approach, especially in the domain of packaging, which is quite complex. I'd rather call it "mentoring" than "sponsorship" though ;)
I'll try to ask questions about non-packaging work in the next set of questions. This is a very interesting aspect (and one where Debian isn't really good currently).
One thing Debian is good it, if I understood that correctly, is hooking the Debian bug tracking system into others (upstream) and also keeping the bug tracking system in the loop of e-mail discussions. Comparing various approaches there is something I'd find interesting. It is definitely something where openSUSE has lots of room for improvement.
Well frankly, the best option would be a cross-distro bug tracking and especially patch management solution. The problem is that upstream has different approaches: some have a bug tracker (bugzilla, jira, ...), some have a somewhat limited bug tracker (sf.net, google code, ...), some just list patches in a directory (e.g. xchat.org), some have nothing at all. While some patches are certainly distro-specific (e.g. use distro-specific Category names in .desktop files, distro-specific init scripts or paths, ...), I'd say most are still applicable for all. It would be both easier for upstream and for packagers. But yeah, to get back to openSUSE, that's indeed something that can be greatly enhanced. cheers - -- -o) Pascal Bleser http://linux01.gwdg.de/~pbleser/ /\ <pascal.bleser@skynet.be> <guru@unixtech.be> __v The more things change, the more they stay insane. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHAT2mr3NMWliFcXcRAosOAJ9Qsxmf8nK7IcPu+hA4M8j7Ey0CiACgoQtr NAs4nf1SZkIp06k/MAORtcQ= =SaFa -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
On 9/20/07, jdd <jdd@dodin.org> wrote:
Pascal Bleser wrote:
There is currently no sponsoring system of any sort.
may be there is something but not clear: AMD is now a sponsor of openSUSE, but how?
Although the original question was about packaging/developers, sponsorship is well defined now. See http://opensuse.org/Sponsors (AMD is a platinum sponsor). Kind thoughts, -- Francis Giannaros http://francis.giannaros.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
Pascal Bleser <pascal.bleser@skynet.be> writes:
Lucas Nussbaum wrote: [...]
I can't tell you the number of developers paid by Novell for working on the distribution.
Could someone else give Lucas some figures on that ? AJ, Coolo, Martin, Adrian, Michl ?
It's difficult to measure. Would you count a person that has one single package and makes one change to it in a year? Should I count managers, documentation, QA etc. Novell has an engineering force in our business unit that is responsible for Linux of around 300 (I haven't counted them exactly) people. Not all worked full time on 10.3 and some are in the 1 patch group. Lucas, I'm interested in the results - thanks! Andreas -- Andreas Jaeger, Director Platform/openSUSE, aj@suse.de SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
participants (6)
-
Andreas Jaeger -
Francis Giannaros -
Gerald Pfeifer -
jdd -
Lucas Nussbaum -
Pascal Bleser