I am intending to restart work on salting discourse, which has been
blocked for years by two things:
* Migration to vb5
* Fixing the database in vb4
I know there has been some progress on vb4 database fix, but vb5
migration seems to be blocked on auth which would likely be easier to
fix by just migrating to discourse right away, since it uses a system
we have integrated in other apps in the project already.
The problem I am facing is that since the vb4 fix isn't public right
now, any attempt at database migration testing I could perform on
discourse is not gonna be done on the same state of the database as we
would get after applying the fix.
How should we proceed then?
From my personal pov, setting up a duplicate vb4 setup and fixing a
database, so that we can properly test it and apply those fixes back
into the main instance is the best way to solve this issue. From there
we can just work on migrating to discourse, with testing that actually
tests the correct state of the database.
Alternatively I'm sure we could find a Nextcloud plugin to replace
forums with Nextcloud too, I'm sure that would solve all the
Just a bit of housekeeping - it would be nice if anyone amending the
stage.o.o rsync ACL on pontifex would also amend the changelog,
referencing the ticket# (if available).
Per Jessen, Linaria, Skyros (30.0°C)
Member, openSUSE Heroes
I'm currently sat on Skyros in the Aegean and I am having trouble
connecting to our VPN - I expect it is an issue on my end?
Replies please with cc to me.
Per Jessen, Skyros (28.0°C)
Member, openSUSE Heroes
Forwarding to the Heroes list from an email address thats subscribed and
should be able to post.
On 7/27/22 07:01, Wolfgang Rosenauer wrote:
> lame repost because I'm not allowed to send to heroes@
> Am 26.07.22 um 23:28 schrieb Wolfgang Rosenauer:
>> I've added the heroes directly here to that thread because I'm almost
>> sure nobody of the officials knows much about what was in connect or not.
>> I think cboltz and lars recovered the connect data at some point and
>> created the current database.
>> How that was done exactly and if anyone had an emeritus list in mind I
>> just don't know.
>> So I hope the heroes can help with that and possibly merge additional
>> About tooling for regular cleanup I unfortunately won't find time
>> anytime soon to work towards something like this.
>> Am 19.07.22 um 06:24 schrieb Simon Lees:
>>> Hi All,
>>> At the openSUSE conference I noticed that we only had 3 people listed as
>>> emeritus members. This number is very much under the expected amount
>>> which from memory should be several hundred. So the board asked me to
>>> discuss this issue with you as I atleast remember most of the details.
>>> In 2016 we did a one off run of an automated process  to contact all
>>> members that we couldn't verify were still active (using bugzilla, obs,
>>> mailing list activity etc). We sent people who we couldn't detect
>>> activity for an email asking if they still wanted to be members and
>>> those whom we got no reply from were moved into a second "openSUSE
>>> Members Emeritus" Group on connect, it seems that this got lost in the
>>> migration away from connect. Would someone in the membership officials
>>> be willing to take ownership of contacting the Heroes team to see if the
>>> list of members from this group can be recovered from a backup. From
>>> memory there was around 300 +- 100 people in that group and this process
>>> was only done once so even a backup from as far back as 2017 should have
>>> accurate info.
>>> But for not to be safe if someone considers that they were previously a
>>> member but we have no record of it but we have some form of evidence to
>>> show they contributed in the past its probably safe to presume they were
>>> are part of this list and are entitled to be added back as a member.
>>> As a side note given the election rules have clauses that require 20% of
>>> members to agree its probably in the communities interest to do this
>>> kind of clean up slightly more regularly like maybe atleast every 5
>>> years maybe more. Of course under our current rules any current members
>>> who wish to stay members are more then welcome to regardless of how
>>> active they currently are.
>>> Unfortunately however the scripts that were used last time were created
>>> and run by people who are no longer active in the community and its
>>> probably significant effort to recreate them, to this point no one has
>>> stepped up to do this which is why the process was only ever run once so
>>> if someone in the membership committee also has time to look into this
>>> it will probably benefit the community greatly.
>>> If anyone has any questions about any of this feel free to reach out and
>>> i'll do my best to give a decent answer although most of this happened
>>> at some point before I joined the board.
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
since most of our machines were updated to 15.4 already, and the usage
of older releases is declining, I had a look at what we currently
build in openSUSE:infrastructure.
I propose to do some cleanup there:
Repos to remove:
- SLE 12 SP4
- SLE 15 SP2
- Leap 15.1
- Leap 15.2
Packages to remove:
- coturn (only build for 15.1 and 15.2, link to network:telephony)
- inn (linked to server:mail + two small changes to make it build on SLE
12, but the package/link is completely broken)
- meson and meson:test (linked to Factory, only 15.2, unresolvable)
- python-FormEncode (linked to Factory, only build [failed] for 15.1 and
- python-requests (linked to Factory, only build [failed] for 15.1 and
- python-SQLObject (linked to devel:languages:python:misc, only build
for 15.1 and 15.2) Note: mirrorbrain has Requires: python-sqlobject,
therefore I wonder why the build isn't enabled for 15.4 and why
mirrorbrain works nevertheless ;-)
- supybot-redmine (links to network, only built for 15.1 and 15.2,
unresolvable for Tumbleweed)
If you think some of the mentioned repos or packages should be kept,
please tell me.
If nobody complains within a week, I'll do the cleanup as proposed
I also wonder about the getmail package which we only build for SLE 12
SP5. It's a "real" package (not a link), therefore I won't delete it.
However, I wonder if we really use it, or if it should move to a
Bonus fun: openSUSE:infrastructure:ircbot
That's a project consisting of unresolvable and broken links that would
build for SLE 11, SLE 12, Leap 15.1 and 15.2. Given the state of that
project, I wonder if we still need it, or if we should delete it.
 for details, see
<jjohansen> cboltz: we would have a lot less bugs if you would just
stop breaking things
* cboltz wonders if he needs to search for bugs introduced by jjohansen
<jjohansen> cboltz: please don't you'll break launchpad
Is there a mechanism for warnings or reprimands for questionable behavior on Bugzilla?
https://bugzilla.opensuse.org/show_bug.cgi?id=1200583 has a maintainer of a
package for TW only who will not also maintain the corresponding Leap package
repeatedly being unfriendly for no apparent good reason, and a reporter who could
have used better words himself.
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
here are the minutes of today's heroes meeting:
- Per mostly working on tickets
- countdown.o.o ported to python 3 by cboltz
- elections.o.o migrated to 15.4
- created some merge requests in Salt
- discussion about all the additional domains belonging to openSUSE (opensuse.*)
- decision: redirect most requests to www.o.o (instead of historically download.o.o)
- gitlab runners are currently horribly slow: needs testing of the whole setup/workflow chain, which might not be quickly to solve.
- bind in 15.4 no longer does chroot, which broke some things including query log rotation (and filled some disks)
- upgrade of galera cluster went surprisingly very smooth. No data loss and quick DB upgrades (new DB version)
- held messages in the queues should be deleted automatically for *-auto lists, because: more or less nobody cares anyway.
- for human lists, the story is a bit more complicated - but over all, having more than 100 held messages in one list, it's not realistic to asume that a human will clean up the list of held messages manually
-> configure *-auto messages to discard messages right away (can be changed for debugging at any time)
-> implement an automatism that will delete all but the last 100 held messages in a list. This should leave a chance for human moderators to look at least for the most common held messages.
- work on discourse is progressing: the import of old forum messages is - honestly - a nightmare because of the changed locale settings inside the DB. Idea: only migrate content starting 2011.
- /blog.php and /content.php articles won't be migrated
- most machines are already migrated to Leap 15.4, and some to Tumbleweed (see https://progress.opensuse.org/issues/113285 for details)
- wiki update worked for the english wiki, but produced funny errors on the other languages. Needs time to analyze and fix the problems
- ask on the project mailing list about feedback / needs
- if feedback is positive, provide a PoC for testing - including some of the public plugins
- it's still kind of a game of luck if Emails from *(a)opensuse.org get delivered to Google accounts. Other mail providers seem to be either more relaxed or not so evil (depending on your view). Seems like we can not do much about this (other than asking people to switch to a collaborative Mail provider).
HA setup for static / "rendered" content:
- really static content (like static.o.o, shop.o.o) already gets served by multiple machines
- we'll also do this for "rendered" content like jekyll-generated pages (news.o.o, get.o.o etc.) - it will be generated on one machine, and then rsync'd to multiple webservers
Und wer auf NTFS Verzeichnisse von Linux aus schreibend zugreifen will,
der ist es ebenfalls selber Schuld, wenn er damit mehr Schaden anrichtet
[...] und findet den schuldigen bereits am frühen morgen in seinem
Badezimmer (spätestens). Mich grinst der Typ auch so manchen morgen
blöde an. ;-) [Helmut Scholl in suse-linux]
the next heroes meeting will be on _Thursday_ (2022-07-07) at 18:00 UTC
/ 20:00 CEST in https://meet.opensuse.org/heroes
The usual topics are already listed on
Please add things you want to discuss, or just bring them up in the
> und wie lade ich Programme ein,
Hm, ruf sie an, oder schreib ihnen ne Karte.
[> Marlies/Ullrich Velter und Manfred Tremmel in suse-linux]