Am Do., 21. Feb. 2019 um 15:32 Uhr schrieb Lars Vogdt
As such, maintaining 447  openSUSE members should not depend on a
single tool. Especially not if the used tool has open, well known
security issues since years.
On Thu, 21 Feb 2019 11:41:19 +0100 Richard Brown wrote:
> This isn't the first time I've asked this question on a public stage,
> but in the hope that this time I get an answer;
> Who volunteers to tackle the problem with connect.o.o and drive
> forward a solution?
I made my proposal already and I stand the point: shut down an insecure
what does "drive forward a solution" mean? Can we integrate the
functions of connect.o.o into other services at openSUSE which are
allready maintained like the openSUSE wiki? A form for travel support
An application for membership could be done by e-mail to an e-mail
address of the membership officials. Elections could be done with an
eVote software like https://github.com/mdipierro/evote for example, but
probably there are better tools.
What did I miss?
I think Lars is right an we should shutdown this insecure system as soon
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
I plan to have meetings for the planning of the openSUSE Conference
starting next week every Tuesday at 18:00 UTC on the opensuse-project
IRC channel. I'll plan to continue this until the conference in June. We
might switch the meeting over to discord and use the bot on IRC to
record the minutes.
We will be using venueless (https://github.com/venueless/venueless) for
the conference. I'm trying to get some documentation to better
understand the features. I have access to our instance at
https://opensuse.venueless.events/ If you want to know more about it,
there was video done last year here https://youtu.be/u95cNlC25Ic Some
of the features have changed. If you want to help with this, please let
me know. Otherwise, I'll see you on Tuesday.
If you haven't registered or submitted a talk for the conference, you
can do so at https://events.opensuse.org/. The Call for Papers is open
until May 4.
It was suggested I repost this here. I originally posted it in Project
on the openSUSE Discord Server.
"I don't know if this is the proper place for this to get attention
but I'll post this here anyway.
Firstly I want to praise all the people who contribute to the
required work to keep Tumbleweed rolling on.
The latest snapshot was a huge undertaking and much work was required
to make it a success.
So thanks to all those people.
That said however many people had a painful experience obtaining this snapshot.
For whatever reason there was much timing out and many had to manually
ride herd on the dup.
I don't think it is an issue of sufficiency of mirrors.
I think it has more to do with MirrorBrain.
It's just not routing people to the closest and most robust mirror.
Here on Discord there was much discussion of the multi day difficulty
in getting the multi gigabyte snapshot downloaded. Is there something
that can be done about this?"
This is a reoccurring issue.
Apply appropriate technology. Use what works without prejudice.
Steven L Hess ARS K6KGE DM05gd22
Owner Flex-1500, Flex-6300, Flex-6400, FT-857D, and FT-817ND
927.0875Mhz and 441.125 analog 441.575 DMR, and 441.600 Fusion
Repeaters Taft Ca.
openSUSE Tumbleweed KDE Plasma with Packman
[ I wanted to wait a few days after this meeting so that the proper ]
[ announcement of Syds goes out before these minutes, and then ... ]
[ missed. Apologies. Note that the 2020-02-15 meeting was really short, ]
[ just an informal chat, and we did not have one on 2020-03-01, so with ]
[ this there's only one set of minutes outstanding. ]
==== Minutes of openSUSE Board meeting 2020-02-01 ====
Present: Axel, Gerald, Gertjan, Neal, Vinz
== Treasurer ==
* Introduction Syds
* Financial controller/accountant for 15 years, variety of businesses
* "everything with computers and numbers"
* openSUSE member since last year
* General discussion on the role of treasurer
* SUSE is willing to share opex budget spent on openSUSE with board
AI Simon: reach out to Andrew (outgoing treasurer) before any announcement
== Follow-up on Year End Survey ==
* Not everyone on the board could join, but all very positive about
* Good conversations
* No specific actions for the board as a body
* Individually we do/will support
== Communications ==
* A bit of confusion around upgrade of the forums software, which turned
out to be a misunderstanding
* Idea: It would be great if various team share somewhat regular updates
(monthly to quartlery maybe) about all the goodness they do, WIP, and
AI Neal: approach other Heroes on the idea of some regular update
== Leap 15.3 ==
* One of us mentioned some specific technical issues they saw
* Suggestion to raise with openSUSE release engineering team
Am 22.03.21 um 08:46 schrieb Gerald Pfeifer:
> On Mon 2021-03-08, ddemaio wrote:
> Does one really need to find bugs to qualify for the T-shirt? If so,
> maybe you running with Hungarian language setting will unveal some,
> translation or otherwise?
How many years did we receive only a low number of Translation bugs?
But that is a good idea, if you can speak multiple languages.
Try another language setup and test other languages. That qualifies for
Bete test bug reports, too.
I would like to move the following repos to the openSUSE Github
The suserpmutil repo has utilities for vendoring Rust and Go modules. The
scripts are rather simple but they get the vendor tarballs created with
with advanced versions of v8.
Also if possible, I would like to join the public list at:
A good symbol to go along with the release of openSUSE Leap 15.3 I
believe is the yin and yang. I propose that artwork to market this
release show the symbiotic relationship of Leap and SLE with a yin yang
design. The imagery should help with the marketing. I put the topic in
the marketing work group notes - https://etherpad.opensuse.org/p/153wg.
If you have any designs you want to share or other ideas on this topic,
I'd love to read it.