Wednesday, 2023-11-08

JayFtc-members: can I get at least one ack on this before I pop it out to the mailing list? https://etherpad.opendev.org/p/tc-ptg-summary-2024.100:04
opendevreviewGhanshyam proposed openstack/governance master: Retire js-openstack-lib  https://review.opendev.org/c/openstack/governance/+/89885802:09
gmannJayF: looks good to me, thanks for summarizing 02:16
gmannJayF: added releasenotes doc issue (i mentioned in PTG) in the tracker. same issue exist for bobcat also02:23
*** blarnath is now known as d34dh0r5315:00
fungiJayF: this should probably find its way into the chair hand-over checklist: ttps://opendev.org/opendev/irc-meetings/src/branch/master/meetings/technical-committee-meeting.yaml#L1017:23
fungisorry, mispaste. https://opendev.org/opendev/irc-meetings/src/branch/master/meetings/technical-committee-meeting.yaml#L1017:23
fungilooks like https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee contains a redundant copy of the chair info, and did get updated17:24
gmannI think wiki is the frequently looked page for TC meeting and info but agree that we should update in both places17:25
fungiwell, the yaml file content is what gets published to https://meetings.opendev.org/#Technical_Committee_Meeting17:26
fungiwhich is the site i usually use when referring people to basic meeting info17:26
gmannbut for TC meeting it is little different as location of meeting is not permanent so we need to keep the updated info in wiki 17:28
gmannhaving chair info there is quick to know but we can remove that is that is causing issue17:28
gmannand agenda too17:28
fungioptionally, the chair entry could just say something like "refer to wiki" or maybe to https://governance.openstack.org/tc/#current-members17:28
JayFDoes wiki have a way to make new accounts now?17:37
fungiJayF: same way as always. log in from launchpad17:55
fungithe login button takes you to the ubuntuone sso17:56
fungilike logging into gerrit, the first time you log in it makes an account for you17:56
JayFoh, interesting. I was told that wasn't the case17:58
JayFin that case; lets wiki it up! :D 17:58
JayFIf someone wants to propose something along the lines of what was suggested about referring to the current members doc, that'd be great, or I can get around to it eventually17:59
JayFbut I've committed to only remove things from my todo list today :D 17:59
fungisome users have hit an error when trying to log in for the first time, and we've been unable to pin down whether it's a bug in the version of the mediawiki openid plugin we're using or bad data coming from ubuntuone's openid provider17:59
fungiJayF: are you saying you want someone to propose a change to https://opendev.org/opendev/irc-meetings/src/branch/master/meetings/technical-committee-meeting.yaml#L10 to update the chair's name, or update a checklist of chair hand-over reminders somewhere?18:01
JayFThe former is what I was referring to18:01
JayFthe existing "chair responsibilities/handover" document is already large and daunting18:02
fungiJayF: https://review.opendev.org/c/opendev/irc-meetings/+/90044418:06
JayF+1; I may propose a further change later to redirect it over to the authoritative document18:08
fungias long as wikis aren't going to be authoritative documents. that server is wholly unmaintained and could in theory go away at any point without warning and without any ability for us to recover it18:09
fungiwe've been saying that for 6-7 years already and still nobody has volunteered to work on maintaining it18:09
fungiso it basically sits there ignored while people keep their fingers crossed that nothing ever happens to it18:10
fungiwe cerated the meetings site as a means of getting some of that information off the wiki eventually18:10
fungiryan lane was maintaining the server by hand after he migrated the content off the older moinmoin wiki, but never set up configuration management for it and there were no volunteers to take over after he left the community18:12
fungiJayF: maybe you were remembering hearing people say that everyone should move important information off the wiki, not that nobody can create accounts on it18:14
JayFfungi: was about to ask is it at least documented18:15
JayFfungi: then lol'd to myself at the knowledge of the answer18:15
JayFfungi: what wiki tech is it, and you all run stuff with ansible+docker, yeah?18:15
fungii think we all eventually got tired of reminding people to move off the wiki18:15
JayFno no no, I can't add stuff to my list today, even though this is super tempting18:15
* JayF goes back to removing stuff from his list, but if you leave the info here you might nerd-snipe personal-time Jay18:16
fungiJayF: it's mediawiki. the main challenges are going to be migrating the content and configuration from a many-years-out-of-date mw version18:16
fungiand also just the fact that mediawiki is a giant pile of php18:17
frickleralso no docker, no ansible, not even puppet Ithi18:21
frickler*I think. and very EOL OS18:21
JayFeh, I don't judge giant piles of php18:21
JayFI do judge all the other bits ;) 18:21
JayFbut my hope would be the hard is all in the migration, maybe can find something that's already handled the hard bits for the other parts18:22
fungiright. there are probably ansible roles and/or container images suitable for deploying modern mediawiki, which is why i say migrating the data and configs is likely to be the most challenging part18:22
JayFIDK, this would be a nice change of pace for me, if I can get a free few hours in the next week or seven we'll see :D 18:22
fungiespecially with all the plugins installed in the current wiki18:22
JayFoh. plugins. plugins are going to be the pain.18:27
fungiyeah, even the openid auth is via a plugin18:36
*** JayF is now known as JasonF18:53
*** JasonF is now known as JayF18:53

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!