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
2 days ago, Linux Unplugged published a podcast where they reviewed
https://linuxunplugged.com/387 (Review starts at 38:40)
The review was not as positive as I expected and it contains some general
remarks, so it makes sense to discuss it on project, and not on factory.
We may not agree with the remarks and findings, but we should at least listen
to them and ask ourself, how we can improve.
I try to summarize the various points for improvement (with my own words)
Website and download
It was noted that the download of images does not work under Chrome, so they
had to switch to Firefox
The section for live-images was considered 'confusing' as the hints lead to
the impression that not the full TW experience is possible (should not be used
for installation or upgrade of TW) - or that it may not work at all (limited
amount of drivers, may not run on all hardware).
-> What is the limiting factor to include more drivers in the images?
-> How can the live media be enhanced for full installation capabilities?
(enable online repos and pull packages from there?)
While the first power-on experience as well as the new partitioning tool was
perceived very positive, the installation process itself had several kinks:
- The reviewer is working on a Dell system with 4k screen resolution. The
installer is not properly scaling and shows all icons very tiny (complete EULA
fits on the screen). At the same time, there are some issues with the touchpad
(around minute 46:00), it is hardly possible to click a button.
-> Do we have a problem with 4k screens?
- setup of WIFI during installation 'is really old school' as one has to jump
between different tabs to set it up. And, finally, the WIFI setting is not
taken over to the installed system, so one has to enter it again (and he hit a
known Plasma-bug by this https://bugs.kde.org/show_bug.cgi?id=389052 )
-> can the WIFI setup be done on a single page?
-> can the wifi settings be transferred to the installed system?
- there was some confusion around the activation of online repositories during
installation from DVD. It is unclear where it is used or necessary for.
-> a clarification that enabling the online repositories gives a wider variety
of desktops and additional software should be included
-> this hits for some parts the recent discussion if we can include repos like
packman right at installation time
-> If I remember correctly, a TW DVD with online repos enabled installs only
if no new snapshot was released. Enabling the online repos on a DVD install
pulls most packages from the repository instead of the DVD. This is clearly
not a smart move, and I would consider this as bug. The reviewer had actually
the same complaint.
Installation of software
- After installation the reviewer obviously ran into severe performance
problems (where it was not clear to me if this was coming from Intel Graphics
or from free Nvidia driver). So he tried to install proprietary NVidia driver
and had the issue that his graphics card was mentioned nowhere and he was
unsure which driver to install ('this is managed on Fedora/Ubuntu with a
checkbox, Arch installs one additional package'). In the istallation process,
'YaST hangs at 64% for ages' and he was uncertain whether to kill the process.
-> can we improve the detection of hardware to recommend the right proprietary
driver? I cant comment on how other distros do it, but it looks like this was
- the installation of additional proprietary software (slack) obviously via
snap was not as easy as expected. I have a personal opinion on snap and
flatpack, but these formats are more to come, as a cheap alternatve if no
native packages are available.
-> is there a point where we can/need to improve the snap/flatpack support?
In general the YaST Softwaremanagement was seen as quite old style ('like we
did it 7/8 years ago).
As stated in the introduction, we do not need to agree with all findings, but
we should listen to them. Some of the points, esp. during installation, come
up same or similar in Leap. With 15.3 ahead, we should look into this and
check if we can improve this.
I would recommend to anybody to listen to the review, and see if we can
improve. The just-released community survey seems to have some of the same
points (I did not read it in detail so far), like finding documentation (not
only for Nvidia cards)
Please find below the minutes of the board's online video meeting on Jan 18
Board Meeting 2020-01-18
Agenda and minutes
* Documenting complaint handling best practices
Gerald would like to have this documented preferably before new complaints
arise and offers to put something up for others to review
* Tracking trademark usage approvals
Nothing we can do or have to do right now.
* Handling board tasks with progress-o-o or alternative (V)
Board discusses this. Neal proposes a pagure setup. Board also discussed
some options they would need
Neal will create up a 'review setup'.
* End of year survey
Axel: Meeting is on Jan 23 and 30, 1300 UTC. Neal notices that it was not only
nice to get the info collected, but that the survey was also mentioned in
various linux online magazines.
Board will try to join the meeting as far they can
* Wiki - self perception
Axel speaks) to improve some phrasing on our Main wiki page. Board
briefly discusses this, Gerald likes us to discuss and share input on this
with the Marketing team.
Board ends up discussing marketing.
Board disccused the Treasurer
Gertjan Lettink a.k.a. Knurpht
openSUSE Forums Team
here is an announcement from the SUSE EngInfra team.
What: We want to update our UCS identity provider that is used for
When: tomorrow 2021-01-21 08:00 - 13:00 UTC
Why: to be on the latest version, to get features and bugfixes
Who: me+jdsn, possibly with other EngInfra collegues
What to expect:
During parts of that time, no user updates (creation, password, email
changes etc) will be possible.
https://idp-portal.suse.com/ will just show "under maintenance" then.
We made preparations so that authentication can continue everywhere all
the time, but since this is not well tested, users could experience some
login problems during the update.
here are the meeting minutes for the board's meeting on 2021-01-06:
(sorry, bit late...)
Start: 2100h CET
End: 2240h CET
Present: Axel, Gerald, Gertjan, Marina, Neal, Simon, Stasiek, Vinz<br />
=== 1. Welcome new board members ===
Gerald welcomed new members of the board (Gertjan, Neal), thanked the
leaving ones Marina and Stasiek for their work.
=== 2. Communications ===
==== 2.1 Update board mailing list ====
New board members were added to private board mailing list. The archive
for board mailing list is non-existant for privacy reasons. Former board
members will be removed from board mailing list after the meeting
==== 2.2 Wiki pages ====
Board wiki pages are partially updated already, new board members will
add themselves. There are duplicates that should get merged
* AI Axel: Update Board history page
* AI Gerald: Merge openSUSE_talk:Board_meetings into general Board
==== 2.3 Telegram group ====
For convenience and privacy reasons a new group is made for Board 2021.
* AI Vinz: Setup group, invite all board members, make them admins
==== 2.4 Update on treasurer ====
The board elaborated the situation around finances, travel support
program and handling of sponsorship.
* AI Simon: Talk to Andrew Wafaa about the treasurer role
==== 2.5 Obligatory Face2face meeting ====
This is not going to happen anytime soon for obvious reasons.
=== 3. Complaints ===
==== 3.1 Recent history ====
Gerald gave an brief overview on the recent complaints happening and
being handled by the board, respectively parts of the board.
==== 3.2 Status & next steps ====
The board agrees on keep going the route of handling behavior (and the
resulting conflicts) in the community.
=== 4. Brief update from Gerald on recent changes at SUSE ===
=== 5. Slot for this meeting going forward ===
The board agrees on 2100h CET on Mondays at a bi-weekly schedule. First
meeting will happen on January 18th 2021.
* AI Axel: Set up the meeting email reminder accordingly
These minutes can be found on the wiki as well:
All previous meeting minutes are there as well:
On behalf of the board,