Project

General

Profile

Actions
Copy link

communication #72310

closed

2020-11-03 19:00 UTC: openSUSE Heroes meeting November 2020

Added by cboltz over 4 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
opensuse-admin
Category:
Event
Target version:
-
Start date:
2020-10-06
Due date:
% Done:

0%

Estimated time:

Description

Where: irc://irc.freenode.net/#openSUSE-admin IRC channel https://meet2.opensuse.org/heroes https://meet.opensuse.org/heroes
When: 2020-11-03 19:00 UTC / 20:00 CET
Who: The openSUSE Heroes team and everybody else!

Topics
see/use checklist

Note the different UTC time since europe is back to "normal" time.

Hide closed

Checklist

  • Questions and answers from the community
  • status reports about everything
  • review old tickets
  • what do we do about all of those "forum spam" tickets?
Actions
Copy link
 #1

Updated by cboltz over 4 years ago

  • Category set to Event
  • Assignee set to opensuse-admin
  • Private changed from Yes to No
Actions
Copy link
 #2

Updated by pjessen over 4 years ago

  • Checklist item changed from [ ] Questions and answers from the community, [ ] status reports about everything, [ ] review old tickets to [ ] Questions and answers from the community, [ ] status reports about everything, [ ] review old tickets, [ ] what do we do about all of those "forum spam" tickets?
Actions
Copy link
 #3

Updated by cboltz over 4 years ago

  • Description updated (diff)
Actions
Copy link
 #4

Updated by cboltz over 4 years ago

  • Status changed from New to Resolved

2020-11-03 heroes meeting - meeting minutes

Main minute taker: Christian

  • Questions and answers from the community

    • none

  • status reports about everything

    • Christian: status.opensuse.org SSL certificate renewal required to temporary disable the http -> https redirect (done manually)
    • Stasiek migrated ML archives for October to mailman3
    • Estu: add lubos as admin at progress to allow him run redmine rest api (https://progress.opensuse.org/issues/75451)
    • pagure setup mostly done, ssh access (and making it secure) is an open question
      • setup fail2ban to limit ssh attacks
      • forward ssh port from proxy to pagure VM (and limit connections from the proxy IPs to git access)? (to get started, ssh limited to those with VPN access)
      • Need to write a redmine->pagure importer for https://pagure.io/pagure-importer
      • handle mails, should create non-public tickets by default
      • migrate salt repo as private repo

  • what do we do about all of those "forum spam" tickets?

    • jdsn will look at the tickets, and will check if it makes sense to block the spammers in the login system (and do it) - and if not, will tell Malcolm that it doesn't make sense to report the spammers

  • login system: SUSE plans to cleanup / remove inactive users

    • "freeing" usernames, and allowing to re-use them, comes with some risks
    • last login is known, but for knowing where these users logged in we'd have to check each and every service
    • TODO: check if all deleted usernames can be added to a blocklist in a single LDAP entry which is covered by OpenLDAP overlay slapo-unique (probably ask Univention)
    • for this cleanup, accounts that were not migrated or used since the account migration are removal candidates
    • will not affect users who were active in an openSUSE service

  • Idea to move (parts of) the openSUSE infrastructure to the cloud

    • up for discussion
    • related to the question how independent openSUSE wants to be from SUSE
    • pros:
      • Easy to scaling
      • Support CDN more like mirror
    • cons:
      • not all heroes are familiar with cloud
      • cost risk and billing account
      • current infrastructure (VMs in the SUSE datacenter) works[tm]
    • open question: which services would benefit from the cloud?

  • review old tickets

    • skipped as usual
Actions
Copy link

Also available in: Atom PDF