Project

General

Profile

Actions

communication #89365

closed

2021-04-06 19:00 UTC: openSUSE Heroes meeting April 2021

Added by cboltz about 3 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Normal
Category:
Event
Target version:
-
Start date:
2021-03-02
Due date:
% Done:

0%

Estimated time:

Description

Where: https://meet.opensuse.org/heroes
When: 2021-04-06 18:00 UTC / 20:00 CEST
Who: The openSUSE Heroes team and everybody else!

Note: with Europe switching to summer time, the UTC time changed to 18:00

Topics
see/use checklist


Checklist

  • Questions and answers from the community
  • status reports about everything
  • review old tickets
Actions #1

Updated by cboltz about 3 years ago

  • Private changed from Yes to No
Actions #2

Updated by cboltz about 3 years ago

  • Description updated (diff)
Actions #3

Updated by cboltz about 3 years ago

2021-04-06 heroes meeting

community questions and answers

  • some questions around DNF - not exactly infrastructure related, but answered nevertheless ;-)

status reports

  • lcp has created lots of (~3M redirects, 340 MB file size) redirects for the old mailinglist archive
  • lists.o.o now supports login with other idendity providers (for example github)
  • matterbridge (IRC - matrix bridge) setup done
  • pagure updated, default branch is now "main", user namespaces enabled
  • noggin, freeipa-fas, etc. for new openSUSE Accounts packaged for Fedora+EPEL for account system VMs
  • forums migration: saltstates prepared, MR will follow in the next days, actual switch and upgrade planned for April 15th (forums will be read-only or down during this time)
  • ipsilon updated, some patches to upstream
  • mod_perl on bugzilla enabled, major performance improvements
  • move maintainer.zq1.de to pinot.i.o.o?
  • do we want/need containers? First find usecases, then think about using AWS or setup kubic
  • several DNS zones moved from FreeIPA to chip.i.o.o (powerdns), but not all (for example, infra.o.o is still on FreeIPA, and chip no longer answering queries for infra.o.o caused some problems) - TODO: move all zones to chip
  • making the salt repo public - no objections in the meeting, send out a mail to be sure
  • code.o.o needs a way to run CI on jenkins (until then, the salt repo on code.o.o will be read-only)
Actions #4

Updated by cboltz almost 3 years ago

  • Status changed from New to Closed
Actions

Also available in: Atom PDF