[14:59] <xypron> This week I worked an tools needed for UEFI booting on RISC-V.
[14:59] <xypron> Furthermore I am looking at list of all packages available for ARM64 but not for RISC-V
[14:59] <xypron> #1938898 mokutil: not built on riscv64
[14:59] <xypron> fix released
[14:59] <xypron> #1938795 efibootmgr: missing riscv64 build
[14:59] <xypron> built in ppa
[14:59] <xypron> #1938787 gcc-defaults: missing cross compilers for building on RISC-V
[15:00] <xypron> evaluated
[15:00] <xypron> #1938705 dmidecode: not built on riscv64
[15:00] <xypron> fixed released
[15:00] <xypron> #1938699 cpu-checker: riscv64 build missing
[15:00] <xypron> fixed released
[15:00] <xypron> #1938582 efitools does not build on RISC-V
[15:00] <xypron> built in ppa
[15:00] <xypron> #1938438 sbsigntool does not build on riscv64
[15:00] <xypron> built in ppa
[15:00] <xypron> #1938324 gnu-efi does not support RISC-V
[15:00] <xypron> fixed released

[15:00] <sil2100> Hey, we didn't start yet!
[15:00] <sil2100> ;)
[15:01] <bdmurray> #startmeeting Weekly Ubuntu Foundations team
[15:01] <meetingology> Meeting started at 15:01:02 UTC.  The chair is bdmurray.  Information about MeetBot at https://wiki.ubuntu.com/meetingology
[15:01] <meetingology> Available commands: action, commands, idea, info, link, nick
[15:01] <bdmurray> #topic Lightning Round
[15:01] <juliank> o/
[15:01] <bdmurray> echo $(shuf -e vorlon bdmurray doko sil2100 mwhudson juliank waveform slyon jawn-smith dbungert xypron ginggs schopin)
[15:01] <bdmurray> dbungert jawn-smith vorlon slyon doko xypron bdmurray waveform schopin juliank sil2100 mwhudson ginggs
[15:02] <dbungert> * +1 - golang-testify unstuck by way of retest clicks.  Not a flaky test, just
[15:02] <dbungert> other bugs that have been since resolved
[15:02] <dbungert> * subiquity / u-d-i - bitlocker detction - annotations code ready with final PR
[15:02] <dbungert> pending for u-d-i.  May end up adding a dedicated API for making it simpler
[15:02] <dbungert> to detect the presence of bitlocker, discussion pending
[15:02] <dbungert> * subiquity / u-d-i - free software only install option - first step here is to
[15:02] <dbungert> control the components in sources.list on the installed system.  Have a
[15:02] <dbungert> working prototype based on curtin sources_list template, but that wipes out
[15:02] <dbungert> the stock sources.list.  Exploring alternatives that can preserve stock
[15:02] <dbungert> sources.list comments at least.
[15:02] <dbungert> * LP: #1821412 - put together SRU friendly plan for a simpler code change than
[15:02] <dbungert> previous work.  Have a plausible diff, next action is to test it and prove
[15:02] <dbungert> to myself that it's worthy of upload to impish
[15:02] <dbungert> (done)
[15:02] <xypron> This week I worked an tools needed for UEFI booting on RISC-V.
[15:02] <xypron> Furthermore I am looking at list of all packages available for ARM64 but not for RISC-V
[15:02] <xypron> #1938898 mokutil: not built on riscv64
[15:02] <xypron> fix released
[15:02] <xypron> #1938795 efibootmgr: missing riscv64 build
[15:02] <xypron> built in ppa
[15:02] <xypron> #1938787 gcc-defaults: missing cross compilers for building on RISC-V
[15:02] <xypron> evaluated
[15:02] <xypron> #1938705 dmidecode: not built on riscv64
[15:02] <xypron> fixed released
[15:03] <xypron> #1938699 cpu-checker: riscv64 build missing
[15:03] <xypron> fixed released
[15:03] <xypron> #1938582 efitools does not build on RISC-V
[15:03] <xypron> built in ppa
[15:03] <xypron> #1938438 sbsigntool does not build on riscv64
[15:03] <xypron> built in ppa
[15:03] <xypron> #1938324 gnu-efi does not support RISC-V
[15:03] <xypron> fixed released

[15:03] <bdmurray> jawn-smith: how about now
[15:03] <doko> did we shuffle again?
[15:03] <jawn-smith> * Investigate failed mysql tests blocking shadow
[15:03] <bdmurray> xypron is excited
[15:03] <jawn-smith>     * unrelated, and shadow is now in -updates
[15:03] <jawn-smith> * Re-write ubuntu-image in go
[15:03] <jawn-smith>     * Image preparation steps PR merged
[15:03] <jawn-smith>     * New PR to be opened today for load_gadget_yaml and post-processing of the gadget.yaml file
[15:03] <jawn-smith>     * The following steps have functionality developed but need code cleanup and test cases:
[15:03] <jawn-smith>         * populate_rootfs_contents
[15:03] <jawn-smith>         * populate_rootfs_contents_hooks
[15:03] <jawn-smith>         * generate_disk_info
[15:04] <jawn-smith>         * calculate_rootfs_size
[15:04] <jawn-smith>         * populate_bootfs_contents
[15:04] <jawn-smith>         * populate_prepare_partitions
[15:04] <jawn-smith>     * Also need to create PR in snapd to export some things. I have begun working on that
[15:04] <jawn-smith> [done]
[15:04] <bdmurray> vorlon is out
[15:04] <slyon> - Only 1 interview & 1 take-home test this time :)
[15:04] <slyon> - Town Hall & Documentation workshops
[15:04] <slyon> - Improved zhmcclient SRU (LP: #1919451)
[15:04] <slyon> - Fixed IBM Z lvm+luks+multipath boot, provding 3 curtin fixes (LP: #1895192)
[15:04] <slyon> - Some snapd vs systemd cgroups v2 testing & review
[15:04] <slyon> [15:04] <slyon> - Upstream release of netplan 0.103 \o/
[15:04] <slyon>   + some bug grooming & changelog assembly
[15:04] <slyon>   + lots of testing
[15:04] <slyon> - Updated netplan.io packaging
[15:04] <slyon>   + fighting autopkgtests as the Ubuntu infrastructure shows some issues that
[15:04] <slyon>     did not show up in the pre-testing
[15:04] <slyon>   + prepared SRU paperwork and SRU packaging (LP: 1919451)
[15:04] <slyon> (done)
[15:04] <doko> - unplanned: investigate gcc-N-cross ftbfs, triggered by a glibc merge
[15:04] <doko> - unplanned: fix glibc-2.34 dependency generation
[15:04] <doko> - first look at x86-vN hardware compatibility report, generated from ubuntu-report
[15:04] <doko> - about to start the first impish test rebuild
[15:04] <doko> and gcc-defaults pointing to GCC 11 just migrated
[15:05] <doko> (done)
[15:05] <bdmurray> investigation into LP: #1914075 (confirmed it was fixed)
[15:05] <bdmurray> deep dive into LP: #1921427 (no answers though - SAD)
[15:05] <bdmurray> submitted PR for cassandra-charm updating apache keys
[15:05] <bdmurray> reported LP: #1938338 regarding SRU of intel-iot image building
[15:05] <bdmurray> discovered / discussed UC20 FDE w/ storage-safety unset behavior
[15:05] <bdmurray> rebuilt UC20 Intel IoT image w/ storage-safety=prefer-unencrypted
[15:05] <bdmurray> conducted an interview
[15:05] <bdmurray> merged a platform seed change regarding jasper
[15:05] <bdmurray> submitted usd-importer MP re kernel dkms universe packages for SRU reviewing
[15:05] <bdmurray> retried mysql autopkgtests (focal, hirsute) for shadow SRU
[15:06] <bdmurray> merged hints for schopin
[15:06] <bdmurray> force-reset-test ruby2.5 for bionic (regressed in -security)
[15:06] <bdmurray> submitted ubuntu-archive-tools MP re debdiff and versions
[15:06] <bdmurray> sru-verification of ubuntu-release-upgader in focal, hirsute -proposed
[15:06] <bdmurray> uploaded python-apt and ubuntu-release-upgrader for 20.04.3
[15:06] <bdmurray> submitted a PR re ubuntu-dev-tools and import-bug-from-debian re debian bug 969510
[15:06] <bdmurray> ✔ done
[15:06] <bdmurray> waveform:
[15:06] <waveform> * Finished isolated testing of u-r-u quirk for migrating users from u-boot in impish (LP: #1936401)
[15:06] <waveform> * Posted a revised patch for focal backport of update-notifier (LP: #1836475)
[15:06] <waveform> * Investigated reported kernel upgrade boot failure (LP: #1937924)
[15:06] <waveform> * Investigated UC18 boot issue with pending kernel (decompression related)
[15:06] <waveform> * pibootctl documentation work (after the docs workshop!)
[15:06] <waveform> * Pi meetings
[15:06] <waveform> * Take home tests
[15:06] <waveform> (done)
[15:06] <schopin> * Documentation workshops
[15:07] <schopin> * openssl:
[15:07] <schopin>   + test-rebuild of build-rdepends for main and universe against openssl3
[15:07] <schopin>     -> documentation of the whole procedure for future reference
[15:07] <schopin>     -> prepare software to generate a report for ubuntu-devel
[15:07] <schopin>     -> build still in progress as we speak :)
[15:07] <schopin>   + EVP SRU triggered a whole bunch of autopkgtest failure, dealt with most of it (bug #1931994)
[15:07] <schopin> * opencryptoki: SRU uploaded to hirsute-security for bug 1928780
[15:07] <schopin> * netplan: working on updating documentation for the new release
[15:07] <schopin> (done)
[15:07] <bdmurray> juliank:
[15:07] <juliank> * synced apt 2.3.7, need to follow up on update excuse.
[15:07] <juliank> * finished a new shim to submit with patches for load option parsing (LP: #1937115) (PR#393, PR#399)
[15:07] <juliank> * sponsored dmidecode, cpu-checker, efibootmgr, mokutil for xypron
[15:07] <juliank> * uploaded gnu-efi (synced), cpu-checker (synced) and sbsigntool in Debian, helping xypron merging the latter back
[15:07] <juliank> (done)
[15:08] <bdmurray> sil2100:
[15:09] <sil2100> * SRU reviews and releases
[15:09] <sil2100> * 20.04.3:
[15:09] <sil2100>   - Sync-up meetings, status updates
[15:09] <sil2100>   - Reviews for .3
[15:09] <sil2100>   - Preparing base-files upload, waiting for review
[15:09] <sil2100>   - Prepared language-pack refreshes for .3, accepted to -proposed
[15:09] <sil2100>   - Required changes to debian-cd and ubuntu-cdimage
[15:09] <sil2100>   - Lots of coordination between teams
[15:09] <sil2100> * Fixed u-boot SRU for focal to include the right target names in the postinst fix
[15:09] <sil2100> * Townhall
[15:09] <sil2100> * Rebased private-tests ESM branch to have a cleaner history
[15:09] <sil2100> * Tried releasing fix for running live-build locally
[15:09] <sil2100>   - Fix causes ADT regressions in livecd-rootfs
[15:09] <sil2100>   - Tried understandign the issue better, lots of debugging in the ADT environment
[15:09] <sil2100>   - Wasn't able to find a case that would work in all envs so reverted the change
[15:09] <sil2100> * Pushed a small fix for livecd-rootfs iotg handling
[15:09] <sil2100> * Reviewed PR for ubuntu-image initial states for William, some iterating on that
[15:09] <sil2100> * Started working on ubuntu-image manifest generation state
[15:09] <sil2100> * Reviewed LP-team spec for core snap source generation
[15:09] <sil2100> * Some work on process documentation
[15:09] <sil2100> * Discussed ways to go forward with installer images on riscv
[15:09] <sil2100> * Looking into UC22 image builds again
[15:09] <sil2100> * Lots of various discussions
[15:10] <sil2100> (done)
[15:10] <sil2100> (was still writing the status)
[15:10] <bdmurray> ginggs:
[15:10] <ginggs> * documentation workshops
[15:10] <ginggs> * retried autopkgtests for openssl SRUs
[15:10] <ginggs> * tasksel is now no longer in main, ready to pull the trigger on a sync,
[15:10] <ginggs>   barring launchpad learning about a tasks section
[15:10] <ginggs> * I looked at LP: #1779767 and decided the manpage issue mentioned in comment 13 was worth its own bug LP: #1938924
[15:10] <ginggs> * Now digging into #1922342 and LP: #1930884, which may be related
[15:10] <ginggs> (done)
[15:11] <bdmurray> are there any questions on status?
[15:11] <rs2009> Hi, would it be possible to enable CONFIG_SW_SYNC_USER and set CONFIG_ANDROID_BINDER_DEVICES to 'binder,hwbinder,vndbinder,anbox-binder,anbox-hwbinder,anbox-vndbinder' in the kernel config to get Waydroid to work out of the box on Ubuntu?
[15:12] <bdmurray> rs2009: this isn't the appropriate place for that question. you might try in #ubuntu-devel or whatever the kernel team irc channel is
[15:13] <rs2009> Okay, sure. Had asked there earlier, but didn't get a response there so thought of asking in the Foundations team meeting.
[15:13] <bdmurray> ginggs: How many things had to be done to get tasksel out of main? Seeding jasper and what else.
[15:13] <rs2009> (in #ubuntu-kernel
[15:13] <bdmurray> rs2009: The Foundations team doesn't work directly on the kernel.
[15:14] <jawn-smith> There is a #ubuntu-kernel
[15:14] <ginggs> bdmurray: sil2100 demoted tasksel, tasksel-data, ubiquity-frontend-debconf and oem-config-debconf binaries
[15:14] <rs2009> john-smith: I had asked in #ubuntu-kernel on 1st, but didn't get a response.
[15:15] <bdmurray> okay, moving on
[15:16] <bdmurray> #topic Release Incoming Bugs
[15:16] <bdmurray> #link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ii-incoming-bug-tasks.html#foundations-bugs
[15:17] <bdmurray> bug 1938588
[15:17] <bdmurray> The was discussed in a 20.04.3 meeting and is being investigated but we should card it so we don't lose track.
[15:18] <mclemenceau_> Ok, done then
[15:18] <bdmurray> #link https://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-hh-incoming-bug-tasks.html
[15:18] <bdmurray> nothing for us here
[15:18] <bdmurray> #link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ff-incoming-bug-tasks.html
[15:18] <bdmurray> nothing for us here
[15:18] <bdmurray> #topic Team proposed-migration report
[15:19] <juliank> apt is mine, duh
[15:19] <doko> link?
[15:19] <bdmurray> https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses_by_team.html#foundations-bugs
[15:19] <bdmurray> #link https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses_by_team.html#foundations-bugs
[15:20] <juliank> binutils/crash - is ddeb-retriever not working?
[15:20] <juliank> the linux-image-5.11.0-20-generic-dbgsym should be on ddebs.u.c
[15:21] <doko> uninstallability issue
[15:22] <doko> netplan.io?
[15:23] <slyon> I'm working on it. Unfortunately the tests fail on loaded systems due to a systemd-networkd regression.
[15:24] <doko> I think that's all
[15:24] <bdmurray> okay, thanks doko!
[15:24] <bdmurray> #topic AOB
[15:25] <bdmurray> anything else?
[15:26] <bdmurray> alright, thanks everybody!
[15:26] <bdmurray> #endmeeting
[15:26] <meetingology> Meeting ended at 15:26:32 UTC.  Minutes at https://new.ubottu.com/meetingology/logs/ubuntu-meeting/2021/ubuntu-meeting.2021-08-05-15.01.moin.txt
[21:37] <Guest87> Hello this is Wild Man of the membership board I am on my cell but I’m here, this is the best I can do at this time
[21:38] <sarnold> heya wildman :)
[21:38] <Guest87> hi sarnold
[21:39] <Guest87> This is hard from my cell
[21:55] <bashfulrobot> Heyo
[21:57] <diddledani> 👋🏻
[21:57] <dbungert> o/
[21:58] <Guest87> Hello this is Wild Man
[21:59] <Guest87> will all me
[21:59] <Guest87> will all members check in please
[22:00] <diddledani> ello
[22:00] <Guest87> Hi
[22:00]  * Bashing-om 
[22:01] <Guest87> This is hard by cell phone, can anyone please chair the meeting today?
[22:02] <diddledani> yup, I can do it
[22:02] <dbungert> seriously, that's some dedication
[22:02] <diddledani> #startmeeting Ubuntu Membership Board 22:00 UTC
[22:02] <meetingology> Meeting started at 22:02:57 UTC.  The chair is diddledani.  Information about MeetBot at https://wiki.ubuntu.com/meetingology
[22:03] <meetingology> Available commands: action, commands, idea, info, link, nick
[22:03] <diddledani> Hello and welcome to the Ubuntu Membership Review Board meeting for 5th August 2021. The wiki page for the Review Boards are available here: https://wiki.ubuntu.com/Membership/Boards
[22:03] <diddledani> We will attempt to get through all of the applicants that have added themselves to that list before today's meeting. If we are unable to make it through the entire list due to time constraints, then at the next meeting we will pick up where we left off.
[22:03] <diddledani> The format for the meeting is as follows: We will go through the list of applicants one by one, by date of application (FIFO).
[22:03] <diddledani> Each applicant should introduce themselves (1-5 sentences) and provide links to their Ubuntu Wiki page. After the introduction the members of the Membership Review Board will review the pages and, if needed, ask the applicant further questions.
[22:03] <diddledani> During this time it is encouraged for other members of the community to show their support for the applicant. Do not be alarmed if the members of the Membership Review Board are quiet during this time; they are most likely reading wiki/launchpad/forum/other pages and deciding how they are going to vote.
[22:03] <diddledani> When the board is ready to vote, they will publicly vote in the channel with either +1, 0, or -1 (for membership, abstain, and against membership, respectively). If the majority of the voting board members vote +1, then the applicant is now an official Ubuntu member! (feel free congratulate them!)
[22:03] <diddledani> Now, with any further ado, lets get started with the first applicant...
[22:03] <Guest87> Thank you diddledan
[22:03] <bashfulrobot> 👍
[22:03] <bashfulrobot> thanks for Chairing diddledani
[22:03] <diddledani> #topic dbungert
[22:04] <dbungert> Hello
[22:04] <Guest87> For the official record this is Wild Man
[22:04] <diddledani> Hi, dbungert , could you introduce yourself, and share your links to your wiki page and launchpad?
[22:04] <dbungert> Dan Bungert
[22:04] <dbungert> wiki: https://wiki.ubuntu.com/dbungert
[22:04] <dbungert> LP: https://launchpad.net/~dbungert
[22:04] <dbungert> User of Debian-like systems in various capacities since 2000 or so.
[22:04] <dbungert> Debian / Ubuntu has been a part of every job I've had since graduation.
[22:04] <dbungert> Joined Canonical in January with the Foundations team.
[22:04] <dbungert> Aspire to full upload rights eventually, and see Ubuntu Contributorship as a
[22:04] <dbungert> practice round and step in that direction.
[22:04] <bashfulrobot> welcome dbungert , and thanks for your time.
[22:05] <dbungert> Thanks, and same to you all.
[22:05] <bashfulrobot> Can you describe what you see yourself doing in the Ubuntu community itself beyond the "day job" related activities with you new position at Canonical?
[22:06] <bashfulrobot> (congrats by the way!)
[22:06] <bashfulrobot> We (the group) like to understand the more community driven direction that you have down in the past, as well as what you are considering for the future.
[22:07] <bashfulrobot> *done in the past*
[22:07] <dbungert> Sure.  I've really been enjoying the installer / iso related work, and hope to continue to learn more on that front, even beyond what is strictly needed for day job.  But that's overlappy.
[22:07]  * diddledani blames the spillage chickens on your phones for auto correcting wrongly
[22:07] <dbungert> I like looking at a lot of random stuff, and we have no shortage of bugs.
[22:08] <dbungert> I have a persistent interest in tiling window manager, and am inclined to help the system76 folks get their pop-os shell into the archive
[22:09] <Guest32> This is Wild Man apologies for coming and going bad connection
[22:09] <diddledani> don't worry, Guest32 . For your benefit I'll restate what bashfulrobot asked and the response:
[22:09] <diddledani> bashfulrobot> Can you describe what you see yourself doing in the Ubuntu community itself beyond the "day job" related activities with you new position at Canonical?
[22:09] <bashfulrobot> (popshell is awesome, would love to see it outside gnome too!)
[22:09] <diddledani> dbungert> Sure.  I've really been enjoying the installer / iso related work, and hope to continue to learn more on that front, even beyond what is strictly needed for day job.  But that's overlappy.
[22:09] <diddledani> dbungert> I like looking at a lot of random stuff, and we have no shortage of bugs.
[22:10] <diddledani> dbungert> I have a persistent interest in tiling window manager, and am inclined to help the system76 folks get their pop-os shell into the archive
[22:10] <diddledani> end.
[22:10] <diddledani> :-)
[22:10] <dbungert> I'm working thru learning python, maybe there can be some interesting project I can expand on that would continue that goal.  That's also day job overlappy though.
[22:11] <diddledani> overlapping is ok, we like to see a history of community engagement that isn't necessarily driven by Canonical's business objectives
[22:12] <Guest32> Does anyone have any more questions
[22:13] <diddledani> I like that you've got a couple of very good and relevant testimonials from two well known contributors
[22:13] <bashfulrobot> Have you considered taking your debian packaging skills and going for something like MOTU?
[22:13] <dbungert> I have.  MOTU or some sort of per-package sounds like a good intermediate step.
[22:14] <dbungert> My thinking on the topic is not yet much farther than that, though.
[22:14] <bashfulrobot> It's a great one as I know there is never enough people there, plus combined with the fact packaging (debs) is / seen as difficult to learn (lack of modern content)
[22:15] <Bashing-om> dbungert: You have witnesses to your credentials - great ! However, menbership has a contuing obligation - Tou have also signed the code of conduct, bow I kmaust inquire " do you agree to abide by the Code of Conduct for aslong as you are a member" ?
[22:16] <dbungert> Yes, I have signed the code of conduct and agree to abide by it, letter and spirit, as long as I am a member.
[22:17] <Bashing-om> Ouch! You have also .... now I must **
[22:17] <diddledani> any more questions from the board members?
[22:17] <bashfulrobot> I am good on my side
[22:18] <diddledani> is there anyone present that would like to offer any in-person testimonials for dbungert's application?
[22:18] <Bashing-om> my mind is made up :)
[22:19] <bashfulrobot> I am ready to vote.
[22:20] <diddledani> ok, let me start the vote then (wait for it!)
[22:20] <diddledani> #vote dbungert
[22:20] <meetingology> Please vote on: dbungert
[22:20] <meetingology> Public votes can be registered by saying +1, -1 or +0 in channel (for private voting, private message me with 'vote +1|-1|+0 #channelname')
[22:20] <diddledani> #voters bashing-om bashfulrobot Guest87
[22:20] <meetingology> Current voters: Guest87, bashfulrobot, bashing-om, diddledani
[22:20] <diddledani> go.
[22:21] <Bashing-om> +1
[22:21] <bashfulrobot>  +1
[22:21] <meetingology> +1 received from bashfulrobot
[22:21] <diddledani> +1 solid testimonials, a very positive attitude, and good plans for the future
[22:22] <diddledani> is meetingology lagging?
[22:22]  * diddledani tries my vote again
[22:22] <diddledani> +1 solid testimonials, a very positive attitude, and good plans for the future
[22:22]  * diddledani bops meetingology 
[22:23] <diddledani> +1
[22:23] <Bashing-om>  +1
[22:23] <bashfulrobot> Everything overall looks good to me! Just suggest poking a little more in the "outside Canonical" contributions. 👍 🙂
[22:23] <diddledani> silly bot
[22:23] <diddledani> Guest32: just you to vote
[22:23] <dbungert> bashfulrobot: sounds fair
[22:23] <Guest32> +1 from Wild Man
[22:23] <diddledani> I think the bot is gonna fail us
[22:23] <diddledani> #endvote
[22:23] <meetingology> Voting ended on: dbungert
[22:23] <meetingology> Votes for: 1, Votes against: 0, Abstentions: 0
[22:23] <meetingology> Motion carried
[22:23] <sarnold> heh
[22:24] <diddledani> hah. 1 vote. it was unanimous +4
[22:24] <Guest32> Wow
[22:24] <Guest32> Congratulations dbungert I have to go
[22:24] <dbungert> Thanks!
[22:25] <bashfulrobot> Congrats!
[22:25] <bashfulrobot> welcome as an Ubuntu member!
[22:26] <diddledani> congratulations dbungert, bot failing to register the votes notwithstanding, welcome to ubuntu membership. I'll get you added to the group shortly - once that's done, your @ubuntu.com address will go live within 48 hours. Don't forget to check out the perks at the bottom of https://wiki.ubuntu.com/Membership, and request the certificate (once you've got confirmation I've added you) from
[22:26] <diddledani> https://forms.canonical.com/certificate/
[22:26] <diddledani> with that, I'll end the meeting
[22:26] <diddledani> #endmeeting
[22:26] <meetingology> Meeting ended at 22:26:30 UTC.  Minutes at https://new.ubottu.com/meetingology/logs/ubuntu-meeting/2021/ubuntu-meeting.2021-08-05-22.02.moin.txt
[22:27] <dbungert> Thank you all.  Slightly related question - sometimes the wiki dates listed at https://wiki.ubuntu.com/Membership/Boards are a little out of date - is it appropriate for someone to edit them assuming the next month meeting will happen?  I felt weird updating that as it felt like I was scheduling a meeting that others may or may not have agreed to.
[22:28] <diddledani> if you see them and have wiki editor privileges then please feel free to update them - we try to remember to change them but if there isn't a meeting due to no candidates we (I) forget
[22:28] <dbungert> cool
[22:29] <bashfulrobot> I saw that myself today. We are generally watching for people adding themselves to a slot. In some ways I kind of feel like the dates should be removed over all, and maybe (if it does not exist) a friendly note stating to just add yourself (applicant) to the meeting of choice.
[22:29] <diddledani> most of, if not all of, the board members have set it to email us when there's changes so we can always go in after someone updates if they make a mistake
[22:30] <dbungert> sounds more future proof tbh than remembering to update that page every 2 wks
[22:31] <bashfulrobot> Yeah, I agree with that. Many times I almost forget about the page until there is an update.
[22:34] <Bashing-om> I see the page twice weekly anyway in the course of executing my duties. Will be no big deal for me to edit the page as I pass by.
[22:35] <bashfulrobot> 👍
[22:40] <bashfulrobot> I did however update this time around
[22:42] <Bashing-om> Slow internet connection - setting up to edit the WIKI to remove that 22:00 entry :)
[22:42] <Bashing-om> Do we now have anything for the 22:00 meeting ?
[22:48] <Bashing-om> WIKI edited - past dbungert removed from the agenda :)
[22:48] <diddledani> email sent.
[22:53] <Bashing-om> diddledani: https://lists.ubuntu.com/archives/ubuntu-announce/ also sent ? Link for UWN, please while at the top of my mind.
[22:54] <diddledani> sent to ubuntu-news-team@lists.ubuntu.com, Ubuntu-membership-boards@lists.ubuntu.com, community-council@lists.ubuntu.com - is there an additional address we need to add to that list? (https://wiki.ubuntu.com/Membership/Boards/HelpfulDocumentation/PostMeetingEmail)
[23:05] <Bashing-om> diddledani: Great - thanks - I will look later (a couple of hours hence) and see where the announcement lands in the various Mailing Lists.