On 4/28/20 3:06 AM, Guo Yunhe wrote:
> Does it mean we can make some new home page design :-)
>
I think before we do we need to sort out what our long term goals for
branding including color palettes etc. The discussions going on around
the logo will likely change that significantly which might lead to
significant wasted effort if we start the homepage process now.
Cheers
--
Simon Lees (Simotek) http://simotek.net
Emergency Update Team keybase.io/simotek
SUSE Linux Adelaide Australia, UTC+10:30
GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
Hello,
since some minutes, www.opensuse.org gets served from Nuremberg.
This move is somewhat symbolic - www.opensuse.org is a static page,
which made moving it quite easy.
Well, mostly - the /openid/ part is still living in Provo, and the
servers in Nuremberg proxy these requests to Provo. Configuring that was
funny[tm] - thanks Darix and Stasiek for your help with the haproxy
config and the testing!
Now we "only" need to move the forums and bugzilla (and of course also
openid), but that are different stories for the next weeks ;-)
Regards,
Christian Boltz
--
And lets face it, a password protected screen saver is a de-facto
control even for desktops in many settings. I may be the only person
in the house, but what if the cat decides to sleep on the keyboard?
[Anton Aylward in opensuse-factory]
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hi all,
FrOSCon is doing an online this year. Please consider filling out a talk
at https://frab.froscon.de/en/froscon2020/cfp/
The CfP is open until May 23. More info is below.
v/r
Doug
Hello,
you are receiving this mail because you have previously been involved with
making FrOSCon a successful Free and Open Source Software event.
As you might have heard we decided to make FrOSCon 15 an online only event.
If you would like to help us out again: We have started this year's Call
for Papers. See our website for details:
https://www.froscon.org/cfp/ or refer to the texts
below. Please feel free to forward this to anybody who might be interested.
For the FrOSCon Orga team,
Andreas aka ScottyTM
# Call for Papers FrOSCon 2020 Cloud edition #
Let's talk about the elephant in the room: This CfP is different as it's
all about a virus. Due to the current situation we decided to make this
years' FrOSCon an online only event
The Free and Open Source Software Conference (FrOSCon), an annual summer
conference for users and developers of FOSS, will be held from August 22nd
to August 23rd in the cloud. It is organized by the university's
Department of Computer Science in collaboration with the student body and
the FrOSCon e.V.
As its key feature, volunteer speakers will deliver a comprehensive range
of talks and workshops. Additionally we like to offer a platform to Free
Software developers and projects to organize their own
meetings or sub-conferences. There will be additional information on this.
# Topics #
We are looking for contributed papers on current trends and developments
in all areas of Free and Open Source Software, e.g.:
- Operating systems
- Software development
- Administration
- IT security
- Legal aspects
- Desktop
- Education
- Geographic Information Systems (GISs)
- Cloud
Focus areas in 2020 are:
- Antivirus software - How Open Source Software can help overcome the crisis
- Balanced by the market - video conferencing: Zoom on the Big Blue
Button in Teams
- Working (together) in spite of Corona - Lessons learned on the journey
to working from home
- Privacy vs. pandemic response - Who's protecting our data from the virus
- Clouds on the horizon - What happens when there's no space left in the
cloud
- Infrastruktur as a Scalability-Issue - Need more bandwidth, VPNs and
everything
# Submitting Contributions #
To submit a paper, create an account and submit your contribution at
https://cfp.froscon.org/. To participate in the Call for Papers, you will
have to submit a short abstract as well as a detailed description of your
proposed session.
All accepted speakers must submit slides for their talk before the event.
The call for papers is open through May 23rd, 2020. The program committee
meets to review proposals in early June. We will do our best to notify
submitters whether their proposals were accepted within a week or two.
# Language #
Talks can be held in German or in English. The choice of
language should depend solely on which language is more suitable for
presenting the chosen topic. Language of submitted texts and the resulting
talk should be the same.
# Length of the submissions #
The abstract should summarize the planned content of the talk in a precise
and succinct way. We do not place a limit on its length.
Talks should take no more than 45 minutes, in order to allow some time
for Q&A and speaker transition.
We can accept longer contributions in special cases, we ask for a
justification for the longer extent in this case.
# Format #
Abstract and description have to be submitted as plain text via the
https://cfp.froscon.de/. We ask for submission of the slides in PDF
format; other open document formats such as LibreOffice should only be
submitted after prior consultation.
# Licenses #
We will publish abstract, description, slides and a video of your
presentation online and include the abstract in the conference program. We
require that you place your contributions under the Creative Commons
Attribution 4.0 International
( https://creativecommons.org/licenses/by/4.0/ ) license (or a more
lenient license).
Unless another license is noted, we will assume that your contribution is
under this license. If you want to place your works under a less
restrictive license, please note so with your submission.
# Selection of contributions #
Contributions are selected based on their content by a program committee.
Please understand that we cannot accept all contributions and are limited
by the number and quality of the submissions. We will favor submissions
which fall under one of the aforementioned topics.
# Other remuneration #
FrOSCon is organized by volunteers and is mostly funded by partners. We
ask you to understand that we will not be able to reimburse you for your
expenses.
# Technical support #
Please contact us if you won't be able to stream or at least record your
talk adequately. We'll see how we can support you.
# Social Event #
We are planning to hold a social event online on the evening of the 22nd
and kindly invite all speakers to attend.
# Important Dates and Contact Information #
May 23rd, 2020 End of the Call for Papers. All contributions need to be
submitted by this date in order to qualify.
Mid June 2020 Notification of acceptance of all contributions .
June 30th, 2020 Final acceptance. We ask all invited speakers to give
their final confirmation by this date.
July 18th, 2020 Last date for submitting slides.
August 22nd, 2020 First day of FrOSCon.
Further information can be found on the website under
https://www.froscon.org/.
Please send questions about the Call for Papers via email to:
program(a)froscon.org
Contact the organizers via email: contact(a)froscon.org
Postal address:
FrOSCon e.V. c/o Fachhochschule Bonn-Rhein-Sieg
53757 Sankt Augustin
Germany
--
FrOSCon 2020
August 22nd - August 23rd 2020, The Internet
http://www.froscon.org --- http://www.froscon.de
_______________________________________________
Alumni mailing list
Alumni(a)lists.froscon.de
https://management.froscon.de/mailman/listinfo/alumni
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
On Mon, Apr 27, 2020 at 19:36, Guo Yunhe <i(a)guoyunhe.me> wrote:
> Does it mean we can make some new home page design :-)
Always could have, we just need something that can make project justice
as opposed to the current website, you know, more content, saner layout
and links to the relevant stuff. Frankly it would probably be better to
focus on some other website that introduces people to how to contribute
to the project, since that's a little bit too big of a task for www.o.o
(although the attempt sure was made there), so we can link to it from
www-o-o. We need links to all of the subprojects of openSUSE, like YaST,
Uyuni, OBS, openQA, Jangouts, Kubic, etc. categorized in some way that
makes it easy to understand how that related to our mission, with nice
descriptions of the process behind various things we do. Maybe some nice
explanation of the factory process, I was noodling a little with zdog to
have a nice animation (since that's a good use of JS on websites ;)
showing how contributions help with Factory, Tumbleweed and Leap, and
how that integrates with openQA and OBS. Obviously the recent work on
software-o-o, that I have to finish at some point makes it easier to
link people to the pages relevant to them, so that will mean we will not
link to "Tumbleweed" and "Leap" (plus two new distros, Kubic and
MicroOS) before people understand what they are getting themselves into.
This part might be split into get.opensuse.org, since software-o-o could
be a piece of software that can be used alongside OBS deployments. We
need to put a lot more pressure on the community aspect, and the
approachability of our communication channels. You know, just making
every aspect better, except there is way too many aspects that are
required for www.o.o remake to make sense, that we should probably start
everywhere else first.
Jeez, if only we had some team structure, so we could task those things
properly instead of jumping around the project screaming something has
to be done. Where doocracy fails is where there is more than one person
required for a task :D
LCP [Stasiek]
https://lcp.world
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hi everyone,
today I have some exciting news and a proposal to relay: SUSE wants to
go another step in openness towards the openSUSE community and suggests
to bring the relationship of openSUSE Leap and SUSE Linux Enterprise to
a new level.
Internally this idea is called "Closing the Leap Gap" and proposes to
strengthen and bring more closely together:
* developer communities, by focusing on openSUSE Leap as a
development platform for communities and industry partners;
* user communities, by leveraging the benefits of both a stable
Enterprise code base and the speed of community contributions;
* the code bases of openSUSE Leap and SUSE Linux Enterprise (SLE),
by not only sharing sources, but also offering the SUSE Linux
Enterprise binaries for inclusion in openSUSE Leap.
The proposal includes a three step approach:
1. Merge the code bases for the intersection of openSUSE Leap 15.2
and SUSE Linux Enterprise 15 SP2 as much as possible without loss
of functionality or stability. (SUSE has started a cleanup process
on the SUSE Linux Enterprise side already.)
2. In parallel to classic openSUSE Leap 15.2 create a flavor leveraging
SLE binaries, leading to an intermediate release in the October 2020
time frame.
3. Build openSUSE Leap 15.3 with SLE binaries included by default
(assuming community agreement).
As you can imagine, a number of people have been involved with this
so far, and I'd like to pull some of them in front of the curtain in
a little interview.
Q: Thomas, all of engineering at SUSE reports to you, and I know
openSUSE is something you care about quite a bit. What is SUSE
putting on the table here?
Thomas Di Giacomo: Let me step back, and give you a perspective as I see
it. SUSE for 27+ years has been a part of global open source ecosystem
that includes a vast number of developers, end users, communities,
and organizations of all sizes working together and benefiting from
the collective work. Most of our engineers are involved as well with
some open source communities that they feel passionate about.
Open source communities are an integral part of who we are and the
ecosystem we serve. Naturally, we feel responsible to support the
communities and the work done by them. openSUSE is no different and
is actually even more special and very dear to SUSE. So, it should
come as no surprise that we are fully committed towards the openSUSE
project(s) and its community. It makes us all feel proud to see Leap
and Tumbleweed grow and evolve, together with SUSE Linux Enterprise.
This effort of our engineers working together with others in the
openSUSE community will benefit everyone involved for many years
to come.
Q: And why are you doing this?
Thomas: We want open source to succeed for everyone – developers,
contributors to end users and everyone in between. The benefits of
open source are tremendous when the ecosystem grows as a result of
the positive virtuous cycle of – contributing more, supporting the
contributions, benefiting from contributions, which inspires more
people contributing, and it goes on to grow as an upward virtuous spiral.
We feel fortunate to be in the position of seeing the openSUSE community
grow in tandem with the success of SUSE Linux Enterprise, and both
feeding off each other to grow even more. This idea definitely goes in
that direction. Now, let me defer to Matthias who came up with this idea.
Q: Okay, so, Matthias, first of all: what is your role at SUSE?
Matthias Eckermann: I am leading the Product Management team for
Linux platforms, covering SUSE Linux Enterprise, Edge, and Security.
Q: And what made you propose this?
Matthias: My team and I realized that the engagement of our SLE
business with the openSUSE community does not fully fit our view
on openness, and that mutual benefits are not leveraged sufficiently.
We discussed what it would take to bridge the gap and bring the
relationship to the next level. Beyond a common ground on the
technical side, the code streams, this requires learning from each
other; for example, we need to re-establish an open feature process
between community, SUSE, and our industry partners.
Thus we developed "Closing the Leap Gap", and - to test whether it
might have a chance to fly - we outlined the initial idea with the
openSUSE Board before going for approvals by SUSE management.
Q: You mention the board, so let me ask. What is your take?
What opportunities, benefits do you see? What risks?
Dr. Axel Braun: With this change, we can make better use of our
resources, as two code bases converge - so one build target less to
consider. Everyone who packages for Leap and for Package Hub will
immediately benefit from this.
Marina Latini: It's really exciting to see how SUSE is trying to increase
its support for Leap, reducing the existing differences between our
openSUSE Leap and SLE. I can see this proposal as a way to be more
inclusive, giving to the community the opportunity to contribute in
an easier way to Leap and giving the chance to bring the openSUSE
spirit also in an Enterprise product like SLE.
On the other hand, every new move is a change and we need to be sure
that the changes won't limit our community freedom to submit packages
to Leap or won't slow down Leap for following the internal SUSE
development model.
Q: Matthias, that sounds like some extra effort required.
How is SUSE contributing, what is SUSE committing to?
Matthias: Indeed, there is quite some one-time effort needed to get
(back) to the common ground; this is covered by SUSE engineering teams;
two groups are heavily involved: The Open Build Service experts are
designing a workflow for a smooth integration of the binaries, and
for reducing the long term maintenance efforts for our community
contributors. SUSE release managers and packagers are working hard
to synchronize the code bases without losing functionality or quality.
Hundreds of change requests have been filed already, and to get this
done properly, we are delaying the release of SUSE Linux Enterprise
15 SP2 to July.
And we are willing to invest more, to drive the idea to success
quickly: we would take the burden, to create an intermediate openSUSE
Leap release in October 2020 which then would incorporate SUSE Linux
Enterprise binaries into Leap the first time.
Probably, Adrian can comment on the Build Service aspects, and Lubos
what it means to developers within SUSE and to the community release
process?
Q: So, Lubos, as release manager for Leap, what have you been doing
so far, and what is the impact you see?
Lubos Kocman: I spent most of the time on collecting data regarding SLE
and Leap differences and having follow-up discussions and transforming
feedback into action items. Max and the rest of the openSUSE release
engineering team meanwhile did an excellent job of keeping Leap release
activities going forward.
The idea of re-using should generally lower the effort on the Leap side.
However, it comes with the price of increased complexity to bring all
pieces together. A new process will allow external contributors to file
feature or update requests directly to SLE. This will already help a lot.
Q: Is this an outcome bound effort, or time bound? I know the SLE
release schedule is a bit like a 300m tanker.
Lubos: It's both. I see this as a balance between what can we deliver,
how, and to what date. It took quite some effort to create a plan
acceptable by all involved teams. Splitting the work across the
upcoming two releases seemed to be accepted well at least by
involved parties so far.
Q: So, that is SLE 15 SP2. How about Leap 15.2?
Lubos: openSUSE Leap 15.2 will have to slip by about 8 weeks to incorporate
all changes from the SLE and align with its new schedule. I believe that
the release will find a great use for extra time since we're still
finishing the refresh of packages from Factory. The prototype will
be meanwhile available in parallel to the openSUSE Leap 15.2.
Q: How is that research proceeding, Adrian?
Adrian Schröter: We have an idea about the setup in build.opensuse.org.
I anticipate to have a first prototype of the build setup in next three
weeks. And more important is how to develop the workflows to allow a
more collaborative joint effort between SLE and openSUSE development.
However, we must keep in mind that this is really an entire new way to
develop a distribution. On one hand it makes a lot of sense to integrate
for example the SUSE Backports (aka Package Hub) people directly in our
development process. This will make our distribution development stronger.
On the other hand, we also must find ways how to solve new problems.
For example how to keep our builds for architectures not covered by
SLES like Arm 32bit and RISC-V. Also the turn around times of submissions
and build results will be a challenge in the initial setup. And last but
not least, the installed systems and users may need to deal with more
repositories.
But we have one year to work on these problems in parallel to our
stable distribution. And we are indeed looking forward to make
openSUSE and SLE development more beneficial than ever.
Gerald: Thanks everyone for your input. I'll be sharing all this with
openSUSE mailing lists, and am sure there will be further questions,
offers to help, and other input, so please chime in there.
https://en.opensuse.org/Portal:Leap/FAQ/ClosingTheLeapGap has an FAQ with
more details.
Lubos is going to send a proposal with more details on the implementation
side to opensuse-factory@.
I suggest we focus technical discussions of this offer and proposals
there (opensuse-factory@) and general discussions on opensuse-project@.
So, what do you think?
Gerald
--
Dr. Gerald Pfeifer <gp(a)suse.com>, CTO @SUSE + chair @openSUSE
On the board meeting two hours ago we discussed adding an
"abstain" option to future votes. We unanimously agreed.
That is, future votings shall include "abstain" as a choice.
Thank you to all who provided feedback!
Gerald
PS: We understand board elections allow a flexible number of
choices, including choosing no candidate, so we do not see
this as applicable there.
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Dear SUSEianer,
First, I only subscribed to opensuse-project and write this disappointed
mail, because I want to reach all the experts, both company and
community. I'm pretty sure that this mail will not change anything, but
for me it was to a certain way, a must. But this sad story will be a new
thread, since I'm no able to respond to an archived mail. Sorry for
that. Honestly, it is a reply to GPs initial announcement. But,
according to the openSuSE webpage, this mailing list is for "Project and
Community related discussions". And GP ended with an open question,
isn't it?
So, may be no discussion, but a (hidden ?) view on LEAP/SLE closing. At
least, from an unknown user perspective:
There was a young growing scientist, a structural biologist, working on
protein structure determinations with computers & servers like HP, SGI,
DELL, SUN or even VAX. All of them with a nice UNIX operating system,
doing all these good things with open source software from all over the
world.
At a certain time, when the first money came in, by doing this nice
scientific research, he was thinking to learn to setup all this IT stuff
by himself, and after finalizing the PhD by using a computer with one of
these Redmond poison OS/software systems, he was thinking of a self
owned PC with one of these UNIX operating systems AND an easy
desktop/windows interface. Best with some German HowTo's/documentation
since he is still a beginner. And based on open source for free science.
In the 1990's there was an Bavarian based small software company combing
all these requirements in a LINUX distribution called SuSE ... And a
colleague of mine had S.u.S.E Linux experiences since S.u.S.E 4.2 ...
This was the start.
Yes, I'm a pure Linux'ianer, as an user, and started 20 years ago with
SuSE 6.2. First as a novice using accidentally 'rm -f' in the top
folder, but now doing the IT as a single fighter for a small 25-user
University structural biology department with NVida accelerated 3D
workstations, CUPS, NIS, SAMBA servers (still for the Redmond devils
within the group), several number cruncher, backup server, NAS
archiving, and Linux desktops with Windows 10, but within VirtualBoxes.
In total 25-35 computers. All with openSUSE, most with LEAP 15.1 at
present. Compiling and maintaining dozen of scientific open source
programs. Teaching Linux as a side work project, Office work in German
and English, plus some Spanish, Italian at colleague PCs. Using a
multilingual Linux distribution. On private level desktops and laptops
with Bumblebee, and self compiled AMD raid disk driver etc. pp. All the
time with SuSE/openSUSE. And some years ago, also one SLE 10.0.
I defend this GEEKO environment against all Scientific Linux, Redhat,
Ubuntu and Microsoft attacks. Also survived the Novell shock, went
through the Attachmate hell and hoped for MicroFocus. But always
believing on the openSUSE announcement in 2005 !!
I thought a basic LEAP/Tumbleweed OS development and a sophisticated SLE
on top (in this direction) would be the Linux paradise on earth. Also
for the company managers to earn the money.
But the Empire, the money strikes back: I read on Heise Online and also
the announcement on the opensuse mailing list in 2018 about the
2.5-billion$ EQT deal. EQT ?? This stands for equity = shareholder =
even more money makers !!
Money on/with open source ?? 2.5-billion Dollar ?? Can this work with my
Linux paradise ?!?!?! And yes, only 1,5 years later golem.de reported a
further openSUSE/SLE "rearrangement". Of course with benefits/synergism
for all, both sides. I read everything about SuSE distribution policies
on these official mailing lists and on Google since 2015.
Hey Guys, who can still believe on these 2-way "benefits" based on this
company/distribution history ??
I never thought that I would say, but openSUSE Leap 15.2 will be my last
"suse". And funnily these clever money makers gave the best advise at
the final end: "Jump" !!! Oh, I will. At least I can escape the name
fight like 42 ...
I will JUMP to https://distrowatch.com to look for a modern distribution
with several languages, based on KDE, able to use NVida acceleration,
with VBs to satisfy the group Microsoft need. I will have time to learn
and to switch my systems until 15.2 will run out of maintenance. I'm
very happy for and about this "grace time".
But Distrowatch also showed the decreasing SUSE (desktop ?) importance.
In the high time openSUSE reached more than 50% HPD of the top distro.
But permanently decreasing since the MicroFocus deal. See here:
https://www.dropbox.com/s/ntnolo8zcjbbqld/The%20SUSE%20story.pdf?dl=0
Why? May be outdated standard Kernel, QT, KDE etc. versions within the
stable openSUSE Leaps? Too much strategic company / community =
developer discussions / fights? May be too much business? In the past
1-2 year I had more and more problems / higher effort to install and use
3rd-party open source software because of missing / outdated software
versions, e.g. QT/KDE. Tumbleweed was used and tested, but was not
really stable / productive after 2-3 years. At least not in my hands.
And the latest announcement will not lead to improvements, I'm afraid. I
do not want to repeat the 13.2 - 42.1 transition experiences !! Not at
home, not at the University.
I'm sad, so sad to say, it's time to leave. But what I read (Microsoft
agreement in 2006, renewed 2011, Azure topic, etc.) and understood for
the future plans (Leap 15.2 is postponed by 8 weeks already), I do not
want to stay with a Linux distribution which is changing the product /
policy / mind every 3-5 years. May be, every new broom HAS TO sweep
clean?? At SUSE they do: SLE now "dictates" the Leap. An user view.
Yes, I'm still an user only, may be a power user, but no IT'ler, no
SUSEianer, so absolute no IT / distro making / company experience /
knowledge. But I was a customer, an openSUSE "customer". And I do not
want to become a SUSE customer. Too much business, too less freedom for
free academic research. Yes, you can and should earn money. But then
split like RedHat did. Use open source and make products, but don't use
open source community for your products. I really like, no I loved a lot
of clever (open)SuSE tools, aka YaST. But ...
I really appreciated the community AND company work on most of the
distributions. Not all, including the rolling Tumbleweed, but most. I'm
missing the Evergreens. Therefore, thank you for more than 20 SuSE
years. In 21 (Funny, half of the magic 42. This must be sign ?? :-( ) it
is time for - may be - Manjaro? At least the color will stay.
So, now it is written. As I said, this mail will neither change
something, nor it is helpful for the best LEAP/SLE closing strategy.
Sorry again, for bothering you, but now I feel - partly - better.
Sad, disappointed but kind regards and all the best for the GEEKO,
Michael
- still - an openSUSE user
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hi openSUSE Community,
We have been using Redmine as a ticketing system for a very long time.
The previous server had Redmine 2.4.5 from 2014 installed on an old
SLE 11 SP4 server.
And finally we have successfully migrated to a newer Redmine version.
Currently running Redmine 3.4.12 on a brand new server with Leap 15.1.
This is a long awaited step in a long, long journey. Much time was
spent fixing broken plugins, configuration and the database to match
the new Redmine version. And we have a new theme to make it look fresh
[1].
Thank you to all people who helped this migration run smoothly.
Estu
[1] https://progress.opensuse.org/
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
On 14/04/2020 15.53, Johannes Kastl wrote:
> On 14.04.20 at 15:20 Gerald Pfeifer wrote:
>
>>> As an aside, Jump is an awful name, since it's a way too common of a
>>> word in the English language to build any reasonable branding around it.
>>
>> Isn't Jump more like $JUMP, its actual name to be determined?
>
> We should decide on a sensible name very soon, otherwise Jump will be mentioned
> in dozens of places already... :-(
I think it is a very bad idea to change names, Yet another Time.
--
Cheers / Saludos,
Carlos E. R.
(from 15.1 x86_64 at Telcontar)
Hi all,
Thank you for those who added their input for Features for openSUSE Leap
15.2 on the wiki page - https://en.opensuse.org/Features_15.2
There are more features I will be adding. If you have an features you
would like to add, please consider adding it. I'm sure more people in
the community will probably has a better idea for some of the features
that will be in 15.2, so it would be good if you could help.
v/r
Doug
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org