Saturday 24 June 2023 Termcom Meeting

Office terminals

• DONE - Sean: setup Adobe CC Subscription on cyanide
  • one "scratch" account for everybody, one committee account for adobe stuff (due to Adobe's licensing model)
  • moving forward: contact sysadmin when getting subscriptions
• HOLD - setup the new Mac Minis (3 of them)
  • we have PCs which is better
• TODO - Frank & raymo: new hardware purchases from CIF (multiple request, think about the safe)
  • X99 - CPU and RAM
    • Put the Tesla M40 into the X99 board
  • Power Supply: gwem and natural-flavor

MEF

• TODO - Edwin & raymo: Prepare for this term's presentation beforehand
  • prepare an agenda and throw it to marketing people to make a powerpoint

Debian 12

• PEND - upgrade to Debian 12
  • let's wait for 12.1 so the stable really becomes stable
• TODO - release packages for Debian 12
  • pyceo, krb5-*, libpam-csc, csc-milter
  • termcom to do it?
• TODO - Leo: setup termcom key and add it to the keyring

pyceo

• TODO - Various: fix issues on git

Mail

• DONE - office group for general membership inquires
  • Leo: forward membership@csclub.uwaterloo.ca to Sean for this term's membership inquiry
• TODO - syscom mailing list moderation
  • Edwin
• TODO - Either document or fix webcom mailing alias
  • it's currently hard-coded on mail container to three people
• HOLD - sieve transition

CSClub Cloud

• TODO - port forwarding
  • Justin: now find a way to manage them via pyceo
  • nginx stream module: http://nginx.org/en/docs/stream/ngx_stream_core_module.html

Mirror

• TODO - mirror-checker-ng: Nathan, no sitrep since last termcom meeting
  • debian and ubuntu works
• HOLD - reverse proxy as backup mirror
  • projects don't like traffic pointing to them suddenly
• TODO - upgrade parts for mirror
  • waiting for Dave

Misc

• PEND - Should we decom the progcom VM?

webcom

• HOLD - cleanup the librarian database (we still want it to be in SQLite3 since MySQL/PostgreSQL will be an overkill)
  • webcom will only work on it next term
• TODO - log collection
  • syscom will need to know log file location and syntax (JSON being ideal)
  • Leo: will attend their meeting