Am 25. November 2020 10:02:27 schrieb "jdd(a)dodin.org" <jdd(a)dodin.org>:
> I don't mean how to contact them, but who are them...
> IMHO there are too
> many designated people around (election, membership), this is not sane.
Really? I don't think so. Three election officials are the bare minimum.
And membership officials are a different group so there are different
people necessary. Iirc they are a quite loose handful of people, actively
being five or so. Which is nothing insane IMHO but necessary as well.
All of the official people are doing other stuff (development, packaging
etc.) and volunteer for their official duties on top. So I thinks it's fair
to keep the workload per capita as low as possible.
Under "by a vote of the membership where 2/3 or more of the openSUSE
members participating in the vote approve it. " I would like to propose
an amendment to the Board Election rules (Note I rather then the board).
I believe that the events in the last year have shown a weakness in at
least one part of the rules. With the upcoming regular election I
believe this is as good a time as any to address this change.
The specific section I would like to modify is the following, I know
others have spoken about making changes to some larger sections at some
point but I believe this change is small and manageable in the current
timeframe so I'd like to keep the discussions in this thread around this
topic which is:
If 20 per cent or more of the openSUSE members require a new board,
an election will be held for the complete elected Board seats.
I believe that this is a very worth while concept, however the current
phrasing has left enough ambiguity that in practice it was hard to
organise cleanly. My personal view is that the people who authored this
text expected that should this ever be needed that some form of basic
petition or even just +1's to a mailing list thread would be done.
In practice it was decided that this would be too hard to verify and had
some privacy concerns and as such the election officials decided to
utilize our voting system which was a reasonable way to handle the
situation under the current wording. However it now leaves us in a
position where one or two people can call for such a vote that will
cripple the project for several weeks. I don't believe this was the
intent of the original wording as such I am proposing an alternative,
this is still in draft form so I am happy to hear other peoples
amendments and suggestions.
10 individual members may contact the election officials requesting
a petition of non confidence in the board. If 20 per cent or more
openSUSE members require a new board, an election will be held for
the complete elected Board seats.
The 10 is a number that I felt is reasonable i'd be open to going
slightly up and down, its a bit of a balance if 20% of members are
interested getting 10 to contact the election officials should be easy.
At the same time it should be reasonably easy for election officials to
verify 10 members by checking the membership list and sending an email
to there registered email address asking for confirmation they sent the
There was also some questions around the 20% rather then a 50% majority,
My view is to leave this as is, if 20% of people call for a forced
election it means there is quite some disagreement in the community,
however the current board can run in the election so a different 50% of
the community could still reinstate them.
My aim is to have a finalized version ready on the 8th of December (A
week before voting starts) i'd welcome anyone and everyone's feedback
anytime before then.
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
My fellow members of the openSUSE community,
I wish to declare my intent to run for one of the available openSUSE
Board seats in the upcoming election.
I have had the wonderful pleasure of being involved in openSUSE as a
contributor for the past five years, and I believe openSUSE is an
amazing project offering a Linux distribution platform with great
potential! My hope is that I can help get openSUSE to realize its
potential as a member of the Board.
In the coming weeks, I intend to more fully describe my ideals and
goals for openSUSE. Meanwhile, feel free to reach out to me and ask
about myself, my thoughts on openSUSE, and/or my candidacy for the
Thanks in advance and best regards,
Neal Gompa (ID: Pharaoh_Atem)
On behalf of the Election Committee, I confirm your candidacy has been
well received. We look forward to hearing more about your election
platform and we wish you well in the upcoming election. If you have any
questions regarding the process please reach out to us at
Best of luck,
On 22/11/2020 05:31, Nathan Wolf wrote:
> I would like to throw my name in the hat for a position on the openSUSE board.
> After all, this is my favorite Linux and open source project!
Dear fellow members of openSUSE community, I hereby notify you of my intent
to run for openSUSE board seat, I have been a member of this community
since approximately 2006, till 2009 I have been very active in the Czech
openSUSE community. My career path prevented me from being as active
community member as I would like to be, however that has changed in 2018
when I gained more free time and resumed an active role in the community,
focusing primarily on packaging efforts.
Currently my focus is dedicated to making openSUSE the number 1 Linux
platform for Haskell development, as well as to provide as much as possible
support that we as software project can provide to the emerging industry of
open-source hardware such as RISC-V.
With a seat duration of two years, I would like to achieve two goals
beyond ordinary duties of a openSUSE board member, first goal would be to
make openSUSE the number 1 platform for Haskell development, and the second
would be to make RISC-V open instruction set architecture a Tier 1 platform
for openSUSE project alongside x86_64 platform.
I will elaborate more on these strategic goals during Phase I which, I
believe is the appropriate time to present individual vision for this
project on a timescale of 2 - 5 years, in the meantime, please feel free to
reach out to me directly with any questions you may have regarding myself,
my vision, or my candidacy.
Best regards / S pozdravem,
BSc. Mark Stopka, BBA
Managing Partner (at) PERLUR Group
mobile: +420 704 373 561
Dear openSUSE members,
openSUSE Board Election 2020 
It's time to elect new Board members to fill empty seats on the
openSUSE Board. This is a regular election as defined in our
Election Rules  so the elected board members will serve till the
end of 2022.
There are three seats for election in accordance with our normal
election cycle. Stasiek is opting not to continue for the next full
year due to a change in his personal circumstances.
The election schedule is as follows:
## Phase 0
15 November 2020
- Announcement of the openSUSE Board Election 2020
- Call for Nominations and Applications for Board candidacy
29 November 2020
- Nominations and Applications for Board candidacy close
## Phase 1
30 November 2020
- Announcement of the final list of candidates
- Campaign begins
- Membership drive continues, opportunity to apply for openSUSE
Membership, but members will only be eligible to vote and not run
as a candidate
## Phase 2
15 December 2020
- Ballots open: Please cast your vote during this time
- Campaign continues
30 December 2020
- Ballots close
31 December 2020
- Announcement of results
To stand for a position in the openSUSE Board please send an email to:
* opensuse-project(a)opensuse.org and
If a member would like to nominate another member, please inform the
Election Committee and the officials will contact the nominee to ask
whether they would like to run as a Board candidate.
Only openSUSE members are eligible to run for openSUSE Board openings in
accordance with the Eligibility and Validity section of our Election
The Election Committee  are hereby calling for Nominations &
Applications for the openSUSE Board.
 Members: Ish Sookun, Edwin Zakaria and Ariez Vachha.
The Election Committee election-officials(a)opensuse.org
As part of improvements to download.opensuse.org experience, currently new pilot service is available for using with zypper.
Its primary task is to redirect zypper requests to a mirror in client's country, similar to what MirrorBrain project does.
You can try to replace in /etc/zypp/repos.d/*.repo
Since it is still a pilot, the service comes without any guarantee or obligations.
Reasons when you may want to try it:
- you want to stick to https connection (mirrorcache will try to find a mirror in your country, which supports https, if available).
- you are on ipv4-only or ipv6-only connection (mirrorcache will try to find a mirror which supports ipv4 or ipv6, depending on the request's connection);
- in case when download.opensuse.org (d.o.o) is temporary unavailable;
- redirection from d.o.o leads to a mirror, which actually doesn't have the requested file (it is rare, but can happen);
- you want to try hosting own mirrorcache instance at your physical location and enjoy fast and reliable redirection. (with very modest disk space / HW requirements).
- you want to help with improving d.o.o experience and provide feedback;
- you are interested in mirror management, for which admin's UI is available, and non-admin UI is planned (so a user can add and manage own mirror without global admin rights);
(login using UI menu and ask me for admin rights if you want to use it or see more advanced controls, like job details).
- you need some related functionality: it is possible that it can be easily achievable with mirrorcache.
Further read about differences from MirrorBrain:
How caching works:
- caching happens on folder level, so e.g., when zypper tries to access file, unknown for mirrorcache - it will be redirected to d.o.o, then a background job will collect info about mirrors. Thereafter further requests to the same folder will be properly redirected to a mirror in the client's country, honoring http/https scheme and ipv4/ipv6 connection used:
- requests to remodata/repomd.xml is not cached, so zypper always gets the latest version of packages.
If you are interested in current source code
(most of architecture is stolen from OpenQA):
In case of questions or any feedback do not hesitate to contact me.
Andrii Nikitin <andrii.nikitin(a)suse.com>
DevOPS Automation and Build Service Engineer
SUSE Software Solutions Germany GmbH
(HRB 247165, AG München)
Managing Director: Felix Imendörffer