diff options
34 files changed, 2574 insertions, 70 deletions
diff --git a/AMDGPU2022.mdwn b/AMDGPU2022.mdwn
new file mode 100644
index 00000000..939485a8
--- /dev/null
+++ b/AMDGPU2022.mdwn
@@ -0,0 +1,92 @@
+# GSoC Project Idea: Introduce Unit Tests to the AMDGPU Component
+Mentor: Rodrigo Siqueira (aka, Siqueira)
+Co-mentor: Melissa Wen
+## Pre-requisites
+For this project, all GSoC contributors must:
+* have any Linux-based distro as their main system
+* feel comfortable with the terminal and working with the Linux command-line
+* have a moderate knowledge of C (e.g. working with pointers should not be an issue)
+* be willing to participate on a public mailing list
+* be able to work in a group and be willing to help other people
+* fully complete the [warm-up](#warm-up) and [first patch](#firstpatch) sections
+## Warm-up
+_This section is mandatory for everybody_
+If you are interested in this project, you must complete the following pre-requisites _before_ you start your application:
+* setup a virtual machine - [[]]
+* learn how to compile the Linux kernel - [[]]
+* learn how to install and remove a Linux kernel - [[]]
+* learn how to deal with modules - [[]]
+* learn how to use kw to speed-up your workflow - [[]] and try to deploy a new kernel by using this tool (see the tutorial section)
+* learn the basics about the Linux kernel contribution process; we recommend you to at least carefully read the following pages:
+ * [[]]
+ * [[]]
+* as a project, dri-devel and the DRM community follow the Contributor Covenant, found at: [[]]
+* subscribe to the dri-devel mailing-list and join the oftc#dri-devel channel on IRC
+If you are not able to complete these steps, or did not have fun doing them, this project may not be a good fit for you.
+## First Patch
+_This section is mandatory for everybody_
+Now it is time for you to send your first set of contributions; for this part, you should send a single patch and a patchset (minimum of two patches in the patchset). You are free to send any patch to any kernel subsystem that you prefer; however, to increase your chance to get feedback and your change merged, we recommend the following:
+1. For your first contribution, we recommend something simple but useful. For this reason, here is a list of potential contributions in order of importance:
+ 1. Compile your kernel with `W=1`, capture all kernel logs in a file, and try to fix them (try to make a real fix, not simply silencing the compilation warning).
+ 1. Compile the kernel documentation, take a look at all warnings and errors and try to fix some of them.
+ 1. Run `kw codestyle` and try to fix some of the issues. If you try this type of contribution, do not improve things blindly. Find a problem, understand it, evaluate if we really need it, and then make your patch. Please, try to be very critical of yourself if you try this type of contribution because many of the complaints generated by the kernel codestyle are ignored for a reason.
+1. Since Siqueira is one of the maintainers of the display code from the amdgpu driver, we recommend you use the AMD repository: [[]]. Again, this is not mandatory, but this will increase your chances of getting a review and your change merged.
+1. You can focus on any part of the kernel that you want, but we recommend you to work on `drivers/gpu/drm/amd/display/` since we will work on these drivers during the GSoC project.
+## Project Idea
+Our goal is to explore KUnit in a production driver context. [[KUnit|]] is a lightweight [[unit testing|]] and mocking framework for the Linux kernel.
+In this project, contributors will introduce some basic unit test to an AMD display component called the Display Mode Library (DML) which is a library that computes display parameters to be set in the hardware. Aside from the unit test, we need to enable some level of integration with [[IGT GPU Test Tools|]] and, if possible, find a way to generate a code coverage report. For writing your project proposal, we recommend you to read the following links to learn more about this topic:
+* [[]]
+* [[]]
+* Basic documentation about DRM API and Display Core. We do not expect that the contributor will fully understand these pages; we just want you to have an overall idea in order to write your project proposal.
+* [[]]
+* [[]]
+* [[]]
+## How To Prepare Your Project Proposal
+The [warm-up](#warmup) section is mandatory for everyone; for this reason, your final project proposal should have one section per assignment with two or three paragraphs that describe your experience with each task. Additionally, including screenshots demonstrating that you've completed those activities (e.g. showing your VM running with your custom kernel) is a plus.
+Finally, make sure that you have the following sections in your application:
+* Basic info about you (Name, preferred pronouns, GitLab or similar, your blog page, your website, email, and IRC nickname);
+* One or two paragraphs about you;
+* A section that describes how you achieved each of the warm-up pre-requisites;
+* Sections that describe your interaction with the Linux kernel (your first patches);
+* Add a section that describes your understanding of the project. We recommend you include something about KUnit and the AMD display core.
+* A section that breaks down how you plan to execute the project proposal while following the GSoC timeline. As previously mentioned, the project's primary goal is to introduce KUnit tests to the DML component of AMD display drivers. Project proposals outside of this context will not be accepted. Although the scope of this project is well defined, contributors need to demonstrate they also understand their skills and boundaries. Therefore, contributors should build a project proposal based on their knowledge, acquired skills, as well as their own ideas. Besides that, they should propose an executive plan with tasks that fit the GSoC milestones. Please, make sure to add two main milestones (i.e. it should match the GSoC evaluation dates).
+_NOTE:_ Feel free to share your draft before submitting the final version. We'll be happy to give you feedback to improve and strengthen your proposal.
diff --git a/BoardOfDirectors.mdwn b/BoardOfDirectors.mdwn
index 11b572ce..88120f09 100644
--- a/BoardOfDirectors.mdwn
+++ b/BoardOfDirectors.mdwn
@@ -4,14 +4,14 @@
### Current Members
[[!table header="no" class="mointable" data="""
**Name** | **Affiliation** | **Contact** | **End of term** | **Office**
- [[Emma Anholt|EmmaAnholt]] | Google | emma AT anholt DOT net | Q1 2022 | **Treasurer**
+ [[Emma Anholt|EmmaAnholt]] | Google | emma AT anholt DOT net | Q1 2024 | **Treasurer**
[[Samuel Iglesias Gonsálvez | SamuelIglesiasGonsalvez]] | Igalia | siglesias AT igalia DOT com | Q1 2023 |
- [[Mark Filion|MarkFilion]] | Collabora | mark DOT filion AT collabora DOT com| Q1 2022 |
+ [[Mark Filion|MarkFilion]] | Collabora | mark DOT filion AT collabora DOT com| Q1 2024 |
[[Manasi D Navare|ManasiDNavare]] | Intel | manasi.d.navare AT intel DOT com | Q1 2023 |
- [[Keith Packard|]] | Amazon | keithp AT keithp DOT com | Q1 2022 |
+ [[Alyssa Rosenzweig|]] | Collabora | alyssa AT collabora DOT com | Q1 2024 |
[[Lyude Paul|LyudePaul]] | Red Hat | lyude AT redhat DOT com | Q1 2023 | **Secretary**
[[Daniel Vetter|DanielVetter]] | Intel | daniel.vetter AT ffwll DOT ch | Q1 2023 |
- [[Harry Wentland|HarryWentland]] | AMD | harry.wentland AT amd DOT com | Q1 2022 |
+ [[Ricardo Garcia|RicardoGarcia]] | Igalia | rgarcia AT igalia DOT com | Q1 2024 |
The board can be contacted at
@@ -42,6 +42,8 @@ The board is maintaining liaisons with other industry organizations: [[/Khronos]
### Members History
+* [[Keith Packard|]] (Amazon) keithp AT keithp DOT com (term ended Q1 2022)
+* [[Harry Wentland|HarryWentland]] (AMD) harry.wentland AT amd DOT com (term ended Q1 2022)
* [[Bryce Harrington|BryceHarrington]] (Canonical USA) bryce AT bryceharrington DOT org (term ended Q1 2020)
* [[Rob Clark|RobClark]] (Red Hat) robdclark AT gmail DOT com (term ended 2019
* [[Martin Peres|MartinPeres]] (Intel) martin.peres AT free DOT fr (term ended 2019)
diff --git a/BoardOfDirectors/Duties.mdwn b/BoardOfDirectors/Duties.mdwn
index f4b14412..d62a43b8 100644
--- a/BoardOfDirectors/Duties.mdwn
+++ b/BoardOfDirectors/Duties.mdwn
@@ -95,7 +95,7 @@ See [[XorgEVoC]] for details and policies.
ATM Daniel Vetter
-- Start nagging sponsors for the next XDC right after the last one finished. Sponsors are tracked in bod.git/Sponsors. See [[Events/SponsorshipLevels]] for policies.
+- Start nagging sponsors for the next XDC right after the last one finished. Sponsors are tracked in [[gitlab issues|]]. See [[Events/SponsorshipLevels]] for policies.
## XDC Organizer Coordinator
diff --git a/BoardOfDirectors/Elections.mdwn b/BoardOfDirectors/Elections.mdwn
index bfd1f912..f5b7e85a 100644
--- a/BoardOfDirectors/Elections.mdwn
+++ b/BoardOfDirectors/Elections.mdwn
@@ -1,6 +1,6 @@
### Upcoming Election
-[[Board of Directors Election 2021|/BoardOfDirectors/Elections/2021/]]
+[[Board of Directors Election 2022|/BoardOfDirectors/Elections/2022/]]
### Procedure
@@ -108,6 +108,16 @@ The slate of candidates will be published BB MONTH 20YY and candidate Q&A will b
$AUTHOR, on behalf of the X.Org BoD
+##### Extension of elections timeline
+Subject: 20YY X.Org Board of Directors Elections timeline extended, request for nominations
+We are seeking nominations for candidates for election to the Foundation Board of Directors. However, as we presently do not have enough nominations to start the election - the decision has been made to extend the timeline by $DURATION. Note this is a fairly regular part of the elections process.
+The new deadline for nominations to the Board of Directors is 23:59 UTC on AA MONTH 20YY.
+_(Copy paste the rest of the "Request for nominations" message here, starting from line 3)_
##### Email to the nominees
@@ -273,4 +283,10 @@ The total number of eligible votes cast in the new By-laws approval question was
[[Board of Directors Election 2019|/BoardOfDirectors/Elections/2019/]]
+[[Board of Directors Election 2020|/BoardOfDirectors/Elections/2020/]]
+[[Board of Directors Election 2021|/BoardOfDirectors/Elections/2021/]]
### Upcoming Elections
+[[Board of Directors Election 2022|/BoardOfDirectors/Elections/2022/]]
diff --git a/BoardOfDirectors/Elections/2022.mdwn b/BoardOfDirectors/Elections/2022.mdwn
new file mode 100644
index 00000000..ea04939b
--- /dev/null
+++ b/BoardOfDirectors/Elections/2022.mdwn
@@ -0,0 +1,217 @@
+The X.Org Foundation is holding elections for
+* The Board of Directors
+### Election Results
+With 52 of 80 total members voting, the results of the election as reported on on Apr 19, 2022 were as follows:
+* Emma Anholt
+* Alyssa Rosenzweig
+* Mark Filion
+* Ricardo Garcia
+Their terms will end Q1 2024.
+### Election Schedule
+* Nomination period Start: Mon 21st February
+* Nomination period End: Sun 20th March
+* Publication of Candidates & start of Candidate QA: Mon 28th March
+* Deadline of X.Org membership application or renewal: Thu 31st March
+* Election Planned Start: Mon 4th April 14:00 UTC
+* Election Planned End: Mon 18th April 14:00 UTC
+**PLEASE NOTE: The memberships of all X.Org Members have been expired, to participate in this election you MUST renew your membership by the deadline mentioned above!** Please go to the [[Members page|]] for your membership application or renewal.
+### Board Election
+The terms of the following Board Members will end this year:
+* Emma Anholt
+* Mark Filion
+* Keith Packard
+* Harry Wentland
+There are 4 seats on the X.Org Board of Directors up for reelection.
+The [[Elections overview page|/BoardOfDirectors/Elections/]]
+describes the voting methods and process.
+The election process starts with a 2 week nomination period.
+If you would like to nominate yourself please send email to the election
+committee [[]], giving your
+* name
+* current professional affiliation
+* a statement of contribution to X.Org or related technologies
+* a personal statement.
+To vote or to be elected to the Board you needed to be a Member of the
+X.Org Foundation.
+To be a Member of the X.Org Foundation you need to [[apply or renew|]] your
+membership until the end of the nomination period.
+# Nominees
+## Emma Anholt
+__Current Affiliation:__ Google
+__Personal Statement:__
+Emma has served multiple terms on the board, and is happy to continue in her
+role as treasurer.
+__Statement of Contribution:__
+I am a Google employee working on the Mesa graphics stack for ChromeOS, and
+have in the past worked for Broadcom on the Raspberry Pi (vc4, v3d) graphics
+drivers, Intel on their graphics driver and made major contributions (EXA,
+glamor) to the X Server.
+I have served as treasurer on the X.Org Foundation Board of Directors.
+## Shashank Sharma
+__Current Affiliation:__ AMD
+__Personal Statement:__
+I believe that Xorg serves as a central community for many Linux opensource
+graphics development projects, and one of the bigger challenges which any such
+big community faces is collaborative decision making. I would like to contribute
+towards easier collaboration and communication (I know many of us are already
+working on it, and I would be happy to help them).
+__Statement of Contribution:__
+* Shashank is an opensource enthusiast, he understands and promotes the
+ Linux graphics ecosystem.
+* He has total 15+ years of experience in developing embedded Linux
+ software, out of which he has been developing display and graphics
+ software for around 11+ years.
+* Has worked with many key players around the industry, has experience with
+ both Intel and ARM subsystem of graphics. Has previously worked with
+ Samsung, Nvidia and Intel for their respective Linux graphics teams. He is
+ currently working for AMD's Linux graphics org now, as a technical lead
+ for AMDGPU Kernel and middleware software stack.
+* Is one of the maintainers of AMDGPU DDX driver.
+* Has implemented several complex features for DRM ecosystem previously, has
+ 100+ contributions as author, coauthor, and reviewer in mainline Kernel.
+ Some of his work can be seen at:
+ *
+* Is actively involved and visible in various opensource graphics projects
+ across the stack, like DRM Kernel, Xorg and DDX, Wayland and Weston, Kodi
+ etc.
+* Has implemented a few complex features for DRM subsystems like HDR, HDMI
+ 2.0, YCBCR 4:2:0 etc.
+* More details about Shashank and his contributions can be found in this
+ website:
+## Ricardo Garcia
+__Current Affiliation:__ Igalia S.L.
+__Personal Statement:__
+If elected, my plan is to lend a hand so things get done, helping in matters
+such as XDC organization, CfP or anything the board could need from me.
+__Statement of Contribution:__
+I'm part of the graphics team at Igalia, where for the past 3 years I've worked
+mainly on the VK-GL-CTS Khronos project and the Vulkan specification. As part
+of my work, I communicate often with Mesa driver developers, specially the ones
+working on the V3DV and Turnip drivers, but also very often with RADV and ANV
+developers, either to clarify specification text and propose improvements to
+it, or fixing tests and adding new ones when we detect coverage gaps in CTS and
+driver bugs that go undetected.
+I've also submitted talks and participated in the last two editions of XDC and
+FOSDEM's graphics devroom this year.
+## Mark Filion
+__Current Affiliation:__ Collabora
+__Personal Statement:__
+If re-elected, I would like to continue putting my marketing knowledge to use
+to support X.Org in its growth. Key projects this year include a refresh of the
+X.Org website and finding new sponsors for the very first in-person (hopefully)
+XDC in three years.
+__Statement of Contribution:__
+Elected as the first non-technical board member (I am not a developer) just as
+Covid was taking over the world, my first term on the X.Org board has been a
+great learning experience. Prior to being elected, I was the proud organizer of
+the 2019 edition of XDC in Montreal, which brought in record attendance, new
+sponsors, and for the first time, attendee & speaker gifts.
+## Lucas Stach
+__Current Affiliation:__ Pengutronix
+__Personal Statement:__
+In 2012 the X.Org foundation enabled me to take part in XDC by covering my
+travel costs, which accelerated my professional career into open- source
+graphics. In the last few years I've been able to visit many conferences, both
+as attendee and speaker, but none of them master the balancing act of being
+both very high-profile, with in-depth technical discussions, and at the same
+time having an extremely low barrier of entry quite like XDC. I believe that
+this reflects very well on the whole X.Org community, as well as the X.Org
+foundation, which makes this possible due to its clear mission to foster this
+kind of open collaboration. When elected I would like to make sure that the
+foundation stays focused on this path and continues to be the critical resource
+it is today in bringing together our community.
+__Statement of Contribution:__
+I started my journey into open-source graphics as a hobby by contributing to
+the nouveau Mesa drivers. Since joining the Pengutronix graphics team in
+2013 my focus shifted more to embedded devices. I'm a contributor and the
+kernel driver maintainer to the etnaviv driver targeting Vivante GPUs, while
+also working on lots of other graphics related topics across the stack. I
+helped to ship quite a few products based on a fully open stack and try to
+contribute as much as possible of those developments into the upstream
+## Alyssa Rosenzweig
+__Current Affiliation:__ Collabora
+__Personal Statement:__
+I represent open graphics – not a company.
+I lead two open drivers and care for the future of each. As an employee of an
+open source consultancy (Collabora), I’m free from conflicts of interest
+between a vendor’s bottom line and what’s right for our community.
+When proprietary drivers obstructed blobless Chromebooks, I reverse-engineered
+the Mali. When Imagination posted a compiler, I advised to ensure its
+sustainability. When only Apple’s GPU blocked universal open drivers, I grabbed
+an M1 and drew some triangles.
+We’ve entered a golden age. From old allies like Intel to newcomers like
+Imagination, every vendor’s hardware is growing a viable open driver stack.
+I don’t want us to lose that.
+We are winning, but we’re swimming with corporate sharks. Not every open source
+project survives its own success. We need a strong board that protects us, that
+welcomes diverse contributors but stands up against exploitation.
+We need eight individuals committed to sustainable software freedom in the
+graphics stack.
+I would be honoured to be one of eight.
+__Statement of Contribution:__
+Princess of Panfrost. Archduchess of Asahi.
diff --git a/BoardOfDirectors/IrcLogs.mdwn b/BoardOfDirectors/IrcLogs.mdwn
index 2bb25aa1..09f590a0 100644
--- a/BoardOfDirectors/IrcLogs.mdwn
+++ b/BoardOfDirectors/IrcLogs.mdwn
@@ -338,3 +338,15 @@ Meetings are held every second Thursday.
* [[Oct. 14|BoardOfDirectors/IrcLogs/2021/10-14]]
* [[Oct. 28|BoardOfDirectors/IrcLogs/2021/10-28]]
* [[Nov. 11|BoardOfDirectors/IrcLogs/2021/11-11]]
+* [[Dec. 09|BoardOfDirectors/IrcLogs/2021/12-09]]
+## 2022
+* [[Jan. 20|BoardOfDirectors/IrcLogs/2022/01-20]]
+* [[Feb. 03|BoardOfDirectors/IrcLogs/2022/02-03]]
+* [[Feb. 17|BoardOfDirectors/IrcLogs/2022/02-17]]
+* [[Mar. 03|BoardOfDirectors/IrcLogs/2022/03-03]]
+* [[Mar. 17|BoardOfDirectors/IrcLogs/2022/03-17]]
+* [[Mar. 31|BoardOfDirectors/IrcLogs/2022/03-31]]
+* [[Apr. 28|BoardOfDirectors/IrcLogs/2022/04-28]]
+* [[May. 12|BoardOfDirectors/IrcLogs/2022/05-12]]
diff --git a/BoardOfDirectors/IrcLogs/2021/12-09.mdwn b/BoardOfDirectors/IrcLogs/2021/12-09.mdwn
new file mode 100644
index 00000000..3e475595
--- /dev/null
+++ b/BoardOfDirectors/IrcLogs/2021/12-09.mdwn
@@ -0,0 +1,112 @@
+[[!format txt """
+[13:59:53] [connected at Thu Dec 9 13:59:53 2021]
+[13:59:53] [I have joined #xf-bod]
+[14:00:34] * anholt typing up a 2020 treasurer report!
+[14:00:52] <Lyude> Hey everyone! Roll call: mfilion, mdnavare, anholt, keithp, samuelig, hwentlan_,
+[14:01:44] <hwentlan_> hello
+[14:02:01] <samuelig> hi!
+[14:02:39] * danvet here but not really
+[14:03:29] <Lyude> cool! we've got quorum, agenda for today: XDC2021 invoices status, XDC2021, XDC2022, domain status, GSoC/Outreachy/EVoC, MIPI Alliance and CSI, donation to Asahi Linux
+[14:03:58] <Lyude> I also have turnip compliance written here, but I'm fairly sure we voted on that last time
+[14:04:16] <anholt> yeah, that's done, and we're up on the khronos site as a conformant impl!
+[14:04:21] <Lyude> Cool!
+[14:05:10] <Lyude> So from my side, GSoC/Outreachy/EVoC: no updates yet. MIPI Alliance and CSI: no updates yet, I need to contact our partners again. and that's all from my side. I've got danvet's domain status update so I will post here in just a moment
+[14:06:04] <danvet> anholt, \o/
+[14:06:11] <Lyude> 2x domain transfer from keithp is stuck, danvet told emersion to drop until keithp figured it out. 3x domains confirmed owner/contact info and they're happy with the current situation. That leaves 2x other domains to figure out the owner of, and then of course
+[14:06:23] <samuelig> anholt, \o/
+[14:06:58] <Lyude> That's pretty much all from my side, anholt other then the treasurers report any status updates on XDC2021 invoices status?
+[14:07:24] <anholt> we still need a finall tally from Intel in order to settle that one. not sure what I should be doing on that front
+[14:07:41] <anholt> MS is paid
+[14:07:59] <Lyude> Maybe we've gotta start getting Intel folks here to start poking Intel again to keep them moving
+[14:08:14] <samuelig> anholt, tally in what sense? Expenses on XDC?
+[14:08:18] <anholt> samuelig: yeah
+[14:08:27] <samuelig> anholt, I had long discussion with organizers about that
+[14:08:36] <samuelig> they said their expenses where about 50 EUR
+[14:08:39] <anholt> the only other one we have open is AMD, which says they've paid but that was before I was swapped in as treasurer so I'm waiting on confirmation in spi treasurer reports to close it
+[14:08:46] <samuelig> and they don't want reimbursements
+[14:09:01] <samuelig> because we would pay more in transfers costs than the real thing
+[14:09:03] <anholt> so, do we have any invoicing to do for their sponsorship?
+[14:09:18] <anholt> or is this the "you did the work to organize, and that's good enough"
+[14:09:22] <samuelig> I guess yes, the platinum stuff
+[14:09:52] <samuelig> that means 10k USD
+[14:10:03] <samuelig> as they were organizers
+[14:11:33] <Lyude> samuelig: want to go over XDC status then?
+[14:11:37] <samuelig> I mean, they knew the cost of it before committing to be platinum, right? I mean, in the past we asked the difference to organizers
+[14:11:50] <samuelig> I don't see why we should do an exception this year
+[14:11:58] <samuelig> but I don't have strong opinion
+[14:12:32] <anholt> I was asking because I remember there being some consideration for being the organizer, but I don't remember details.
+[14:12:56] <samuelig> I don't remember that either. Maybe danvet or Lyude remember something
+[14:13:29] <samuelig> we can continue the discussion in the mailing list in any case
+[14:13:37] <Lyude> I'm not really sure I remember either, I'd have to go through meeting minutes to find out
+[14:13:46] <anholt> has some info on that
+[14:14:21] <samuelig> Lyude, no updates really on XDC 2022. If you remember, I created the website, now it has redirection and such. Organizers told me that they will plan to customize it once they have some free time.
+[14:14:36] <Lyude> gotcha
+[14:14:42] <samuelig> however, I should say that if things go as expected, I won't be able to coordinate XDC organization next year
+[14:15:14] <samuelig> as there will be changes in my personal situation that avoids me committing time to it in sustainable basis
+[14:15:45] <samuelig> so I guess, any (or several) new board members need to take care of that. I can help of course, but I cannot do everything like past years
+[14:16:03] <samuelig> so I prefer to have secondary role this time
+[14:16:56] <Lyude> Gotcha, I'm sure we'll be able to find someone else to take over
+[14:16:58] <samuelig> I'm just notifying now as some current board members could think if they volunteer for XDC 2022 coordination or we will wait for new board members after the election
+[14:17:06] <samuelig> right
+[14:17:27] <samuelig> similarly with the rest of my tasks: CFP and looking for XDC 2023 organizers
+[14:18:33] <Lyude> Alright, might want to leave an email about this on the board @ just so folks who aren't here atm know as well
+[14:18:46] <samuelig> right, I plan to do it after christmas
+[14:18:54] <Lyude> sgtm
+[14:19:02] <samuelig> as with all the parties (keep safe!) one can forget about that easily xD
+[14:19:16] <Lyude> hehe, good point :P
+[14:19:20] <samuelig> another topic somehow related to XDC
+[14:19:58] <samuelig> do you remember that we approved a dinner for XDC 2022 organizers given the extraordinary work they did? Well, given the COVID situation and such, it is not feasible to organize that
+[14:20:11] <samuelig> so they suggest if they can donate that money to a project proposed by them.
+[14:20:31] <Lyude> oh lol, I was about to mention that :P. we're talking about asahi right
+[14:20:45] <samuelig> right :)
+[14:21:36] <Lyude> Yeah - I'm all for doing that instead of the dinner if that's what they want. +1 from me, samuelig anholt hwentlan_ ?
+[14:21:41] <hwentlan_> +1
+[14:21:47] <samuelig> +1
+[14:22:22] <anholt> +1 for the donation
+[14:23:56] <danvet> anholt, samuelig yeah organizer gets platinum for 10k or gold for free, that's the discount
+[14:24:07] <danvet> +1 on sponsoring
+[14:24:07] <anholt> ok, so we do need 10k from intel then
+[14:24:46] <Lyude> We've also got to decide on how much the donation for asahi is going to be for, the unofficial cost of the dinner per person would have been 50 USD × person (and we had 3 people), samuelig suggested perhaps we round it up $200, how does that sound to folks?
+[14:25:37] <samuelig> +1 to 200 usd
+[14:26:27] <Lyude> hwentlan_, samuelig, anholt?
+[14:26:38] <samuelig> danvet, ?
+[14:26:39] <Lyude> oops, sorry mentioned your name again samuelig :P
+[14:26:41] <hwentlan_> +1
+[14:26:45] <anholt> +1
+[14:27:39] <Lyude> that's a +1 from me, so that's approved
+[14:27:54] <Lyude> samuelig: will you respond to their email and let them know?
+[14:28:02] <samuelig> ok!
+[14:29:16] <Lyude> Anyway, that should be the end of the meeting. Thanks for coming everyone!
+[14:29:28] <samuelig> oh, one last question
+[14:29:32] <Lyude> hm?
+[14:29:47] <samuelig> I guess we need to check who would pay it. Maybe anholt can ask SPI to pay? or how we do it?
+[14:30:21] <anholt> I figured I'd try to get SPI to do it, let's see if they think we can.
+[14:30:37] <samuelig> ok, thank you so much
+[14:30:45] <samuelig> Lyude, nothing else from my side :-P
+[14:31:07] <samuelig> Lyude, I guess next meeting will be Dec 23rd right?
+[14:31:12] <samuelig> or shall we skip it?
+[14:31:13] <keithp> I'm seriously lacking spoons at present; will try to work on domain stuff when possible
+[14:31:16] <Lyude> samuelig: probably should skip it
+[14:31:33] <samuelig> ok
+[14:31:42] <samuelig> sounds good to me
+[14:41:08] <anholt> does anyone remember context about the catered breakfasts for xdc 2019? did we decide it was too much or something?
+[14:41:16] * anholt has only the vaguest recollection of discussions
+[14:47:40] <mdnavare> Hi guys sorry missed todays meeting, I had another overlapping meeting
+[14:48:49] <mdnavare> One update on Intel sponsorship, I finally got hold of the Purchasing Order guys and payment should be made soon, Martin needs to resend the invoice and then Intels hould release payment right away
+[14:48:59] <anholt> mdnavare: thanks!
+[14:49:28] <anholt> could we get me cced on future info in that thread?
+[15:01:22] <Lyude> anholt: we definitely had breakfest there
+[15:01:25] <danvet> anholt, context on your breakfast question?
+[15:01:26] <Lyude> *breakfast
+[15:01:39] <anholt> I feel like there was some "whoops, we didn't mean to spend that much" or something
+[15:01:51] <danvet> anholt, oh that was on the beer pub thing
+[15:02:05] <anholt> ah, ok
+[15:02:10] * Lyude still disappointed by that beer pub :(
+[15:02:11] <anholt> the trouble with writing the report a year later!
+[15:02:18] <danvet> were they gave us a tiny corner and didn't serve us and the let us hang on the minimal consumption line
+[15:02:37] <danvet> I think breakfast was very well received and we decided to continue doing that if feasible
+[15:02:43] <anholt> great!
+[15:02:57] <danvet> iirc mfilion cut the minimal consumption thing in half together with guy
+[15:03:29] <danvet> I think in the end we've burned down 1k for not much or so, so *shrug*
+[15:14:38] [disconnected at Thu Dec 9 15:14:38 2021]
diff --git a/BoardOfDirectors/IrcLogs/2022/01-20.mdwn b/BoardOfDirectors/IrcLogs/2022/01-20.mdwn
new file mode 100644
index 00000000..445ef365
--- /dev/null
+++ b/BoardOfDirectors/IrcLogs/2022/01-20.mdwn
@@ -0,0 +1,150 @@
+[[!format txt """
+[14:01:04] [connected at Thu Jan 20 14:01:04 2022]
+[14:01:04] [I have joined #xf-bod]
+[14:01:37] <Lyude> there we go :). Time for role call, keithp anholt hwentlan___ danvet mdnavare mfilion samuelig
+[14:01:41] <samuelig> hi!
+[14:01:46] * danvet waves
+[14:02:02] <hwentlan___> hi
+[14:02:06] <danvet> Lyude, oh agenda addition if you don't have it already: election season and I guess treasurer report 21 or so
+[14:02:16] <Lyude> danvet: sure thing, will add both on
+[14:03:02] <Lyude> So agenda for today: domain status, XDC2021 invoices status, XDC2021, XDC2022, GSoC/Outreachy/EVoC, MIPI Alliance and CSI, election season, treasurer report for 2021
+[14:03:25] <Lyude> On my side: MIPI alliance and CSI: No updates yet, will ry to poke partners again
+[14:03:46] <Lyude> GSoC/Outreachy/EVoC: No updates from our end, but the program has become more flexible with longer-term projects from what I understand - so we should consider trying to get someone involved to admin the program again, maybe if someone from the board is willing?
+[14:04:26] <mfilion> o/
+[14:04:42] <Lyude> tbh - I think having someone on the board helping to run the program might just be a good idea in general, would make it easier to make sure we have someone to handle this each year
+[14:05:47] <danvet> yeah, we've just run a bit low on volunteers for internship programs recently :-(
+[14:06:10] <samuelig> it is probably worth asking after the election
+[14:06:24] <Lyude> Good point
+[14:06:48] <anholt25> I think it would be reasonable to ask for a board member to manage those as a sort of unofficial officer.
+[14:07:05] <danvet> well we can even create new official officers
+[14:07:10] <anholt25> but let's do that post-election
+[14:07:10] <Lyude> yeah I was going to say
+[14:07:14] <keithp> o/ (was making tea, sorry!)
+[14:07:20] <danvet> it's just that bylaws say that secretary+treasurer need to exist
+[14:07:33] <mfilion> +1 on creating new officers, that could work too
+[14:07:54] <Lyude> mhm, we can look at this post election I suppose. I like the sound of this plan :)
+[14:08:14] <Lyude> I think that's basically all that's from my side. danvet, any updates with domain status?
+[14:08:26] <danvet> nope, not yet poked more
+[14:09:08] <Lyude> anholt25: do we still have anything regarding XDC2021 invoices to go over? or can I remove that from the agenda
+[14:09:15] <anholt25> please remove from agenda
+[14:09:18] <Lyude> sure thing
+[14:09:36] <anholt25> current treasurer status is that the year-late report should have gone out, waiting on next report for spi to catch up on 6 months of their reports.
+[14:10:13] <Lyude> cool - did we already vote on it btw anholt25?
+[14:10:14] <anholt25> and, for the record: I am quite dissatisfied with SPI.
+[14:10:30] <anholt25> we voted on it, and it should have gone out.
+[14:10:51] <Lyude> ah whoops, I see - misunderstood your original message
+[14:11:09] <danvet> anholt25, so still not any more responsive than 1-2 years ago?
+[14:11:14] <anholt25> not at all
+[14:11:26] <mfilion> so what are we waiting for to move away from SPI?
+[14:11:41] <danvet> yeah I wonder whether we need to reevaluate all that
+[14:11:43] <Lyude> yeah - SPI hasn't been great at getting back to us with stuff, I was going to say I'm fine with us discussing alternatives
+[14:11:46] <danvet> it's pain and lots of work
+[14:11:57] <danvet> but it's also not improving
+[14:12:03] <danvet> *pain to move I mean
+[14:12:29] <Lyude> yeah - what would the alternatives for us to join be
+[14:12:30] <anholt25> we're on track for 3 years of being unable to meet our bylaws requirements because they can't track the money on time.
+[14:13:04] <danvet> well I think it's across the board that we need to do lots of poking to move anything
+[14:13:23] <danvet> e.g. the board@-private thing that started in Dec, I had to kick that can last week to move
+[14:13:32] <danvet> despite that others also already poked spi
+[14:13:41] <danvet> (don't mention the name of that thing)
+[14:13:50] * anholt25 afk a minute
+[14:13:58] <samuelig> yeah, that's not perfect
+[14:14:10] <danvet> maybe a conversation we can/need to prep for xdc?
+[14:14:17] <samuelig> Don't do the change of umbrella org require member vote?
+[14:14:26] <danvet> like looking into options a bit and maybe chatting with some folks
+[14:14:36] <danvet> samuelig, yes
+[14:14:40] <danvet> but that's probably the least thing
+[14:14:43] <keithp> sfc would be the alternative
+[14:14:46] <danvet> yeah
+[14:14:53] <Lyude> sfc seems cool
+[14:15:02] <danvet> I also wonder whether gnome foundation is interested in offering fiscal sponsoring for related stuff
+[14:15:05] <keithp> slightly higher cost, but actually paid staff, so they get stuff done
+[14:15:08] <danvet> they also seem well-run
+[14:15:17] <samuelig> ok, just to know if this is something we can do this year, or not. It seems we need to do lots of talks and discussions and the program the vote with next election?
+[14:15:17] <danvet> but yeah was also thinking sfc
+[14:15:23] <mfilion> no issues with sfc, know them well, sponsored them a few times
+[14:15:25] <samuelig> then*
+[14:15:37] <danvet> samuelig, ah yeah I don't think we can get this through this election
+[14:15:44] <keithp> uh, no
+[14:16:40] <danvet> keithp, was that "no" towards voting on umbrella org change this year?
+[14:16:49] <keithp> yes
+[14:17:13] <keithp> or, rather, I think we'd need to run that through an election, and there doesn't seem to be enough time to figure it all out
+[14:17:44] <mfilion> could we have a special vote on that during xdc, or would we need to wait until next year's board election?
+[14:18:04] <danvet> keithp, yeah it needs a bylaw changes that's for sure
+[14:18:34] <danvet> we could do a vote through the year, bug given how much work it is to run a vote I'm not a fan
+[14:18:43] <danvet> *but
+[14:19:05] <danvet> plus we need 2/3rd majority
+[14:19:21] <danvet> and combining it with board elections helps with getting there
+[14:19:26] <Lyude> yeah I'm fine waiting for the next election, it's not ideal right now but we should be able to survive fine until it's time to change away from SPI
+[14:19:28] <danvet> I think at least
+[14:19:58] <danvet> is someone volunteer to start some board<->board chats with possible orgs?
+[14:20:30] <danvet> I'd like to get the domain stuff sorted first and then I guess kick off sponsoring search, so would take me some time to get around to that
+[14:21:15] <anholt25> (back)
+[14:21:29] <danvet> but I think we'd need a name to kick this can and I'm stupid if there's no one else :-)
+[14:21:36] <mfilion> what are your thoughts on all this anholt25?
+[14:22:32] <Lyude> I think I should be able to get the discussions going
+[14:22:56] <Lyude> (and can let y'all know if I run out of time to actually do it, I -think- I should be OK w/ that though)
+[14:23:18] <anholt25> huge fan of moving sponsor orgs.  I have lots of warm fuzzies for sfc, and I feel like "is responsive" is way more important than the overhead percent, but we should definitely search a bit more too.  I don't have time to do this work, though -- I'm going to be trying to just stay on top of treasurer, and other I'm full up on being more or less
+[14:23:18] <anholt25> an employee while also trying to rebuild a house.
+[14:23:42] <Lyude> Anyone else other then SFC that we should be looking at as well that you can think of?
+[14:23:51] <anholt25> *other than that
+[14:23:52] <danvet> yeah I think maybe we should build a shopping list of what we want fixed
+[14:24:24] <mfilion> Are there really other options?
+[14:25:03] <Lyude> danvet: do we want to do that over email?
+[14:25:17] <danvet> yeah probably simplest
+[14:25:47] <mfilion> by options I mean, is there really anyone else other than SFC?
+[14:25:50] <danvet> just a list of the things we need (like the khr contracts, how much sponsor money we move and maybe how much invoicing/reimbursement or so)
+[14:26:25] <mfilion> we should just open a conversation with SFC and bring up our requirements, and see what they say, and if we're not satisfied, look for other orgs
+[14:26:32] <danvet> +1
+[14:26:46] <Lyude> +1 from me
+[14:26:52] <samuelig> +1
+[14:26:57] <hwentlan___> +1
+[14:27:17] <Lyude> although I should note - I've got 'hopeful' responses from previous conversations, so, we should definitely try to make sure whatever resolutions happen are actually realistically happening
+[14:28:02] <danvet> resolutions?
+[14:28:03] <Lyude> Alright - samuelig, anything on XDC2022?
+[14:28:04] * danvet confused
+[14:28:14] <samuelig> Lyude, nope, no news.
+[14:28:25] <Lyude> danvet: was the convo with SPI to try to discuss our issues? or is it just talking about us leaving in general
+[14:28:31] <Lyude> the former was what I meant by resolutions
+[14:28:40] <samuelig> Just as a reminder, I would like to leave my XDC responsibilities (and CFP too) to other, due to some personal changes
+[14:28:47] <samuelig> (becoming a father again!)
+[14:28:54] <Lyude> ah right - thank you for reminding me :)
+[14:29:04] <danvet> samuelig, congrats
+[14:29:04] * Lyude will add this to the agenda as well
+[14:29:06] <mfilion> woo congrats samuelig :)
+[14:29:20] <samuelig> thanks! :-D
+[14:29:27] <anholt25> congrats!
+[14:29:32] <Lyude> also yeah congrats!
+[14:29:49] <samuelig> thank you so much :)
+[14:30:02] <samuelig> my plan is to send an email once we settle the board after the elections
+[14:30:10] <samuelig> asking for volunteer(s) to run the XDC show
+[14:30:16] <hwentlan___> congrats :)
+[14:30:35] <Lyude> Next agenda item btw - election season, so do we have anyone who could volunteer regarding running things?
+[14:31:26] <danvet> so terms for anholt25 mfilion keithp and hwentlan___ are expiring, so if they all re-run everyone else would be election committee
+[14:31:44] <danvet> meaning samuelig mdnavare Lyude & me
+[14:31:45] <mfilion> Lyude just one last commet about SPI, I wouldn't waste any more time discussing issues with them, let's just begin the process of moving on.
+[14:31:47] <Lyude> Looks like people who can volunteer are samuelig, mdnavare, me, danvet, and-ah ok
+[14:32:02] <Lyude> mfilion: yeah… probably a good idea
+[14:32:11] <danvet> mfilion, yeah same
+[14:32:35] <samuelig> well, we need to keep contact with spi for the bare minimum of running our business, but yeah, other than that, just stop
+[14:32:41] <keithp> would be nice if SPI could fix their processes, but as an all-volunteer org, it's super hard to see how they'd manage that
+[14:32:56] <mfilion> yes of course samuelig, I just meant trying to fix things
+[14:33:05] <keithp> we need to get accounting info for reporting according to our bylaws
+[14:34:15] <Lyude> anwyay danvet I'm fine with volunteering to help run election stuff. it usually doesn't tend to be much work iirc?
+[14:34:45] <danvet> Lyude, it's supposed to be all documented and just a bit of clicking
+[14:35:00] <Lyude> sounds rough, but I think I can handle it :)
+[14:35:05] <Lyude> :P
+[14:35:19] <danvet> thx a lot!
+[14:35:21] <hwentlan___> requires a bit of candidate hunting, usually
+[14:35:33] <danvet> yeah I can help with that
+[14:36:13] <Lyude> anyway - the last thing up is the 2021 treasurer report, do we still have anything to go over with that?
+[14:36:44] <danvet> Lyude, it's the 2020 that we approved and anholt25 sent out, the 2021 is stuck on spi delivering
+[14:36:48] <anholt25> nope, already covered
+[14:37:27] <Lyude> cool - I think that's basically everything for this meeting then :)
+[14:37:39] <samuelig> thank you!
+[14:37:42] <Lyude> thanks for coming everyone!
+[14:37:56] <anholt25> see you later!
+[14:38:02] <mfilion> Great meeting, thank you all
+[14:40:16] <hwentlan___> thanks and see you later
+[15:10:03] [disconnected at Thu Jan 20 15:10:03 2022]
diff --git a/BoardOfDirectors/IrcLogs/2022/02-03.mdwn b/BoardOfDirectors/IrcLogs/2022/02-03.mdwn
new file mode 100644
index 00000000..32363d92
--- /dev/null
+++ b/BoardOfDirectors/IrcLogs/2022/02-03.mdwn
@@ -0,0 +1,81 @@
+[[!format txt """
+[13:59:31] [connected at Thu Feb 3 13:59:31 2022]
+[13:59:31] [I have joined #xf-bod]
+[14:00:48] <Lyude> Hey everyone! Time for roll call ( mdnavare, mfilion, keithp, hwentlan____, danvet )
+[14:01:07] <mdnavare> Hi everyone!
+[14:01:25] <keithp> o/
+[14:02:20] <hwentlan____> hi
+[14:02:55] <Lyude> Cool, we've got enough folks to start. Agenda for today: domain status, XDC2022, XDC2023, GSoC/Outreachy/EVoC, MIPI Alliance and CSI, elections + election schedule
+[14:03:18] <Lyude> I can start with the XDC stuff since samuelig isn't going to be here and gave me some updates:
+[14:03:24] <Lyude> 13:17 <samuelig> XDC2022: I will ping the organizers to start working on the website to have it on time for opening the CfP.
+[14:03:26] <Lyude> 13:19 <samuelig> XDC2023: I will start soon to nag European companies about organizing XDC 2023. The idea is the same than last year: give them enough time for internal discussions, so at the time the RFP is open, we know if there are somebody really interested on submitting a proposal.
+[14:03:45] <danvet> Lyude, I'm around
+[14:03:58] <Lyude> danvet: I figured! since we talked earlier lol
+[14:04:26] <danvet> well got sidetracked prepping salad for dinner and so still a bit occupied with eating :-)
+[14:04:33] <danvet> so not fully around yet
+[14:04:49] <danvet> Lyude, should I do quick domain update?
+[14:04:51] <Lyude> So for GSoC/Outreachy/EVoC: no updates quite yet. MIPI alliance and CSI: I need to poke partners at work again to see what the status/interest in this is
+[14:05:06] <Lyude> danvet: yeah - I think the domain update : election schedule is basically the only things we still need to go over for the meeting lol
+[14:05:23] <keithp> I haven't done anything on domains from my end
+[14:05:28] <danvet> ok I sent some mails around for and
+[14:05:32] <danvet> no replies yet
+[14:05:59] <danvet> I guess I'm also going to bite the sour grape now, I'm running out of excuses :-)
+[14:06:08] <danvet> (maybe don't put it like that in the summary ...)
+[14:06:13] <Lyude> of course lol
+[14:06:59] <danvet> also I guess I need to check with anholt for when they have bw for starting the sponsorship hunting
+[14:07:09] <danvet> but that's not yet pressing I think
+[14:07:41] <Lyude> Oh - that reminds me, I totally forgot to add switching away from SPI on the agenda. Although there's no updates with that quite yet since I haven't yet had the time to start looking into it
+[14:07:49] <anholt> I have enough bw to do the starting-invoices-process steps for sponsorships.
+[14:08:40] <danvet> anholt, cool, I'll kick it off then as soon as I find some quiet time
+[14:08:50] <anholt> what's quiet time like?
+[14:10:20] <Lyude> BTW - if no one else has anything else that just leaves the elections schedule, which only me and danvet really need to work on atm. I'm fine waiting for whenever you're finished with dinner stuff, and I think we can just call it the end of the meeting for everyone else.
+[14:10:36] <keithp> anholt: something that you get twenty years from now
+[14:15:20] <mdnavare> okay yes that was a quick one
+[14:20:08] <danvet> Lyude, got distracted?
+[14:20:34] <Lyude> danvet: nah we just don't have anything in the meeting but the election schedule stuff :P, was waiting for you to be ready
+[14:20:44] <danvet> ah sry I am
+[14:21:16] <danvet> Lyude, did you already prepare a copy of the election page?
+[14:21:33] <Lyude> np - and do you mean just having opened?
+[14:21:39] <danvet> I think we only need to do that + link it + fill in dates per guideline and then send out the heads-up about membership
+[14:21:49] <danvet> or I can type it
+[14:22:42] <Lyude> danvet: if you've got the time for that that'd be appreciated! I can try to make time for it as well if you need though
+[14:22:52] <danvet> ok let me scream at the wiki a bit
+[14:24:36] <Lyude> danvet: do we want to decide on the dates right now btw?
+[14:24:45] <danvet> hold a sec
+[14:24:49] <Lyude> sure thing
+[14:24:55] <danvet>
+[14:25:01] <danvet> copypaste from last year + adjusted
+[14:25:04] <danvet> but not yet the dates
+[14:25:14] <danvet> I think we can just roll it out now
+[14:25:24] <danvet> and then put it into minutes, if you want
+[14:25:47] <danvet> Lyude, you've done all the permission wrangly already, including membership site?
+[14:26:07] <danvet> <- i.e. we can go to step 5 now on this?
+[14:26:09] <Lyude> danvet: let me double check, pretty sure I should have done that already (you and I should have the special election permissions)
+[14:26:41] <danvet> otherwise I'd say we give the heads up now, and then start at 14th Feb with membership renewal
+[14:26:50] <danvet> week after opening nomination period
+[14:26:52] <danvet> and so on
+[14:27:11] <danvet> which is exactly 1 day earlier than last year :-)
+[14:27:21] <Lyude> yep - things should be setup there
+[14:27:43] <Lyude> danvet: sgtm
+[14:28:45] <danvet> <- looking good before I push?
+[14:30:14] <Lyude> danvet: yep - just double checked the dates, everything looks good to me
+[14:30:33] <danvet> Lyude, I'm also going right ahead an push all the updated links
+[14:30:58] <danvet> also noticed we've lost the links to 2020 elections, going to add that too
+[14:32:09] <danvet> ok now I also fixed the year in the link description, not just the link
+[14:32:13] <danvet> Lyude, I think we're ready
+[14:32:28] <danvet> Lyude, will you send out the heads-up to members@ with extra attention grabbing subject?
+[14:32:35] <danvet> for all those who don't read the minutes
+[14:32:40] <Lyude> danvet: sure thing, will get to that in just a bit!
+[14:32:44] <danvet> thx
+[14:37:16] <Lyude> I guess that's all for now, thanks!
+[14:44:01] <danvet> uh except for the most recent election, the old ballot view blows up :-/
+[14:47:25] <Lyude> danvet: hm?
+[14:48:53] <danvet> oh I just tried looking at old results on the members page
+[14:52:03] <mfilion> o/ sorry got caught up in aother meeting
+[14:52:09] <mfilion> another
+[14:53:33] <mfilion> danvet for the two domains (pipewire & gstreamer), pretty sure it's the same person that owns both
+[14:53:50] <danvet> mfilion, can you spill the beans?
+[14:53:53] <danvet> maybe in private
+[14:54:50] <mfilion> sure ok
+[15:18:31] [disconnected at Thu Feb 3 15:18:31 2022]
diff --git a/BoardOfDirectors/IrcLogs/2022/02-17.mdwn b/BoardOfDirectors/IrcLogs/2022/02-17.mdwn
new file mode 100644
index 00000000..bc3041df
--- /dev/null
+++ b/BoardOfDirectors/IrcLogs/2022/02-17.mdwn
@@ -0,0 +1,102 @@
+[[!format txt """
+[14:01:38] [connected at Thu Feb 17 14:01:38 2022]
+[14:01:38] [I have joined #xf-bod]
+[14:01:44] <tlwoerner_> hello
+[14:01:58] <Lyude> Hey everyone, time for role call while I type up the agenda for today real quick
+[14:02:58] <Lyude> Agenda for today: domain status, XDC2022, GSoC/Outreachy/EVoC, MIPI alliance and CSI, election season, treasurer report for 2021, and finding a new parent foundation
+[14:03:00] <hwentlan____> Hi
+[14:03:01] <mdnavare> Hi All!
+[14:04:55] <Lyude> Hey! So we've got quorum now, I can start on some ofthe items here. MIPI alliance and CSI: No updates, I had to take some unexpected time off so I didn't get much time to do stuff last week
+[14:07:26] <Lyude> For domain status since danvet asked I handle the update for that. danvet managed to track down the domain owners for the last few of the domains, and started up the process of fixing ownership for the domain (more info on that in email). so we can consider this done for the time being
+[14:07:45] <mfilion> Nice
+[14:09:00] <Lyude> Also for finding a new parent organization: haven't had a chance to get started with that
+[14:09:32] <Lyude> tlwoerner_: do you want to go over GSoC stuff?
+[14:09:39] <tlwoerner_> Lyude: sure
+[14:09:45] <tlwoerner_> while attending university, Rodrigo was part of a group that helped newbies get into Linux (kernel) development
+[14:09:50] <tlwoerner_> he still works with that group
+[14:09:56] <tlwoerner_> he has a couple students who he thinks would make a great addition to X.Org via GSoC
+[14:10:09] <tlwoerner_> i've setup myself as the X.Org admin and have filled out the "paperwork"
+[14:10:27] <tlwoerner_> i just need a 2nd admin and a count of the mentors and we're ready to go
+[14:10:38] <tlwoerner_> we're going to try to put Rodrigo down as the 2nd admin
+[14:11:04] <tlwoerner_> we also have Melissa Wen as a mentor, so if Rodrigo can't be an admin and a mentor, well then at least we still have Melissa
+[14:11:12] <Lyude> oh nice!
+[14:11:18] <hwentlan____> tlwoerner_: thanks for working with siqueira and melissa on that
+[14:11:21] <tlwoerner_> danvet has also stepped up and offered to mentor a drm project
+[14:11:39] <tlwoerner_> the deadline for the paperwork is Monday
+[14:11:46] <danvet> hm should maybe coordinate with melissa and rodrigo on that
+[14:11:53] <danvet> if something happens
+[14:12:05] <tlwoerner_> i've also updated the GSoC ideas page with Rodrigo's project
+[14:12:10] <danvet> tlwoerner_, should we have a #gsoc or can you ping them to join here for oddball coordination?
+[14:12:25] <tlwoerner_>
+[14:12:34] <tlwoerner_> we ask them to join #dri-devel
+[14:12:42] <tlwoerner_> and the dri-devel mailing list
+[14:12:56] <tlwoerner_> oh.. sorry
+[14:13:02] <tlwoerner_> you mean Rodrigo and Melissa
+[14:13:11] <tlwoerner_> Rodrigo is here, siqueira
+[14:13:19] <mfilion> wow very nice, so great to see all this moving again
+[14:13:25] <tlwoerner_> so i could ask Melissa to join here too
+[14:13:41] <tlwoerner_> mfilion: it always hinges on mentors
+[14:13:48] <tlwoerner_> we get mentors, we do GSoC
+[14:14:10] <tlwoerner_> siqueira is doing really awesome stepping up like this
+[14:14:26] <mfilion> *thank you* siqueira
+[14:14:50] <tlwoerner_> hwentlan____: np
+[14:15:07] <tlwoerner_> that's all for now
+[14:15:19] <Lyude> Yeah thank you big time!
+[14:15:24] <mdnavare> Yes this is excellent, thanks siqueira, is this is going to be more around VKMS project?
+[14:15:38] <Lyude> GSoC is the entire reason I'm here today, so it's really good to see us being involved with it again
+[14:16:37] <Lyude> samuelig: any chance you're around today?
+[14:17:00] <tlwoerner_> mdnavare: their project is adding unit tests to AMDGPU
+[14:17:24] <tlwoerner_> see
+[14:17:39] <Lyude> ooooooooooooh. I like that
+[14:18:13] <tlwoerner_> there are several great people in X.Org who are here because of GSoC, including Rodrigo and Melissa! ;-)
+[14:18:17] <mdnavare> tlwoerner_: Awesome thats great
+[14:19:29] <mfilion> right so what's next on today's list?
+[14:20:20] <Lyude> yeah sorry - was switching between windows for a sec
+[14:20:29] <Lyude> I think we gotta skip the XDC2022 update for today
+[14:20:53] <Lyude> election season: No updates here quite yet, next week is when nomination periods start
+[14:21:03] <mfilion> are we still sending out reminders to renew memberships?
+[14:21:41] <danvet> tlwoerner_, did you or siqueira kick of a mail to look for mentors to the usual dev lists?
+[14:21:42] <Lyude> I haven't sent one out since the first one, I'll send another one today. thanks for reminding me
+[14:21:44] <mfilion> speaking of which - mdnavare anholt keithp you haven't renewed yet :)
+[14:21:54] <danvet> since we restart I expect a lot of people simply missed this
+[14:22:07] <mfilion> 52 renewed so far, not bad
+[14:22:12] <Lyude> yeah
+[14:22:13] <mfilion> what was our count for 2021?
+[14:22:17] <Lyude> I don't think too too many people have missed it
+[14:22:43] <mfilion> I don't have admin anymore so can't see the list for 2021
+[14:22:56] <Lyude> it doesn't let you see the list?
+[14:23:03] <mfilion> nope
+[14:23:04] <Lyude> I definitely went through and re-added folks
+[14:23:06] <Lyude> weird
+[14:23:24] <mfilion> I'm up for re-election, makes sense that I'm not admin
+[14:23:36] <Lyude> mhm - just didn't realize member lists were an admin privilege
+[14:23:41] <mfilion> so, what was our count for 2021? slightly below 100 I think?
+[14:24:03] <Lyude> oh wow
+[14:24:08] <tlwoerner_> danvet: oops no. i sent one 7 days ago to the mentors listed on the ideas page but didn't sent one to the usually places, i'll go ahead and do that now
+[14:24:10] <Lyude> 66
+[14:24:16] <mfilion> really?
+[14:24:16] <keithp> oops, tnx!
+[14:24:18] <Lyude> yep
+[14:24:21] <mfilion> it was way higher before no?
+[14:24:21] <Lyude> 52 votes cast
+[14:24:29] <Lyude> yeah I am pretty sure it was higher in previous years
+[14:24:37] <hwentlan____> yeah, i remember member counts around the 100
+[14:24:49] <mfilion> hmm clearly we need to make more noise
+[14:24:51] <Lyude> 2018: membership 91, 49 votes
+[14:25:14] <mfilion> ok so I'll post a reminder on Twitter too
+[14:25:15] <hwentlan____> yeah, votes are a lot less than member, usually
+[14:25:20] <Lyude> (or 2019? think rob might have typo'd that email)
+[14:25:32] <mfilion> and will do it a few times in the next week or so. when does the election period start? march 1st?
+[14:25:53] <mfilion> oh no March 17, ok exactly one month away
+[14:26:12] <mfilion> right so I'll get some reminders going, timing is good
+[14:27:46] <Lyude> ah alright - thank you very much. do you want me to handle the email reminder mfilion?
+[14:29:09] <mfilion> yes please, I'll do Twitter
+[14:29:19] <Lyude> sgtm
+[14:29:52] <Lyude> alright - anholt is afk as well I'm fairly sure we can skip the update on treasurer report for todya
+[14:29:54] <Lyude> *today
+[14:30:18] <Lyude> Thanks for coming everyone!
+[14:32:23] <tlwoerner_> thank you
+[14:34:27] <mfilion> thanks everyone!
+[14:39:55] <anholt> sorry, was off in another meeting. no updates on treasurer today
+[15:05:00] [disconnected at Thu Feb 17 15:05:00 2022]
diff --git a/BoardOfDirectors/IrcLogs/2022/03-03.mdwn b/BoardOfDirectors/IrcLogs/2022/03-03.mdwn
new file mode 100644
index 00000000..588ab741
--- /dev/null
+++ b/BoardOfDirectors/IrcLogs/2022/03-03.mdwn
@@ -0,0 +1,83 @@
+[[!format txt """
+[14:00:45] [connected at Thu Mar 3 14:00:45 2022]
+[14:00:46] [I have joined #xf-bod]
+[14:00:54] <samuelig> hi!
+[14:01:49] <tlwoerner> hello
+[14:02:01] <anholt> hi!
+[14:02:08] <Lyude> Hi everyone! It's time for role call: anholt, danvet, keithp, hwentlan____, mfilion, mdnavare
+[14:02:18] * danvet waves
+[14:03:06] <hwentlan____> hi
+[14:03:20] <keithp> o/
+[14:03:22] <Lyude> Agenda for today is: XDC2022, XDC2023, GSoC/outreachy/EVoC, MIPI alliance, election season/extending nominations, treasurer report for 2021, and new parent organization
+[14:03:30] <Lyude> samuelig: you can go first with your XDC stuff
+[14:03:40] <mdnavare> Hi All
+[14:03:51] <samuelig> XDC 2022: organizers started editing the website. We adapted the CFP text to include wineconf proposals. We are going to remove past year sponsors from the sponsor box but we plan to add the ones confirmed sponsorship soon.
+[14:04:12] <samuelig> Organizers are looking into booking a good bunch of hotel rooms for the conference days and some days before and after. The idea is to have the majority (ideally all) attendees at the same hotel to increase hallway track and spontaneous activities.
+[14:05:06] <samuelig> but locking that rooms in the hotel is not forever. They will be available for normal booking at some point in September (conference is 4-5-6 October)
+[14:05:40] <samuelig> but the idea is to have special price for those booking them early with this.
+[14:06:00] <samuelig> XDC 2023: no news here. I still need to send emails to potential organizers but I might wait until the election finishes so the new person doing CFP and XDC stuff can take it over and start getting their hands dirty
+[14:06:17] <samuelig> with some simple task
+[14:06:30] <samuelig> (i.e. spam people xD)
+[14:06:55] <samuelig> that's all
+[14:07:01] <samuelig> any question/comment?
+[14:07:25] <Lyude> Oh wow, having a hotel block would definitely be new!
+[14:07:51] <samuelig> yeah, in the past we gave freedom because of the different budgets the attendees have
+[14:08:01] <samuelig> but if prices are reasonable, I think it is a very good idea indeed
+[14:08:34] <Lyude> usually you can get better prices by having a hotel block as well
+[14:09:11] <Lyude> anyway - since it doesn't seem there's any comments we can move on to the next thing, GSoC: tlwoerner siqueira any updates with this?
+[14:09:13] <samuelig> right
+[14:09:20] <tlwoerner> i completed our application and submitted it
+[14:09:27] <tlwoerner> we'll know the results March 7th
+[14:09:35] <samuelig> tlwoerner, siqueira THANKS A LOT!
+[14:09:39] * tlwoerner crosses fingers
+[14:09:44] <Lyude> yeah agreed, this has been a huge help
+[14:09:54] <tlwoerner> np
+[14:10:13] <samuelig> tlwoerner, also, if it is not asking too much
+[14:10:35] <samuelig> if you can document the steps so next years we don't bother you (well, unless you want to do it again ;-D)
+[14:10:50] <samuelig> that would be great.
+[14:11:45] <tlwoerner> do we have a private place to put it? i have all the questions and answers from several previous years' applications, but that's probably not something that should be public
+[14:12:14] <Lyude> We could always come up with another gitlab repo for this and have a group specifically for gsoc people/board members
+[14:12:42] <samuelig> the board has a private repo for our own business. We can use that or create a new project as Lyude says.
+[14:12:58] <tlwoerner> whatever you decide
+[14:13:14] <samuelig> either way works. Better to have another repo, so any GSoC/EVoC coordinator that is not in the board
+[14:13:17] <samuelig> can get access to it
+[14:13:42] <danvet> yeah maybe internship coordinator repo could be useful
+[14:14:43] <Lyude> tlwoerner: if you come up with the docs we can probably setup wherever you want to upload them to once they're ready
+[14:15:16] <tlwoerner> they're ready
+[14:15:36] <Lyude> tlwoerner: alright - I will look into creating a repo afterwards and add you to it
+[14:15:45] <tlwoerner> sounds good
+[14:15:45] <Lyude> danvet: any updates with domain stuff?
+[14:18:33] <danvet> Lyude, we dropped it from the agenda I thought?
+[14:18:49] <Lyude> oh right, sorry - was in previous agenda notes :)
+[14:18:58] <danvet> :-)
+[14:19:22] <danvet> only other thing I have is xdc22 sponsors, we have 2 (plus organizers) now
+[14:19:32] <danvet> but largely I just cleaned out some old gitlab issues
+[14:19:38] <danvet> not really started yet on that
+[14:21:12] <Lyude> Cool. From my side: no updates with MIPI alliance and CSI, that's my fault for not poking partners at work (will try to do that asap). As for a new parent organization, will probably start looking into doing that after the election
+[14:21:28] <Lyude> anholt: any updates on the treasurer report before we go into election stuff?
+[14:21:39] <samuelig> I need to leave, if there is any vote or something worth commenting, I will do it via email.
+[14:21:45] <Lyude> samuelig: np
+[14:21:53] <anholt> we have draft 2021 data from SPI, so I hope we'll get final books soon and I'll be able to put together the report.
+[14:21:55] <samuelig> bye!
+[14:22:28] <Lyude> anholt: Glad to hear!
+[14:23:17] <Lyude> So for the elections: we only have 3 nominations right now, so I think it might be a good idea for us to extend the elections timeline to get more time to find candidates
+[14:24:22] <anholt> oh shoot I never sent in my name.
+[14:25:05] <Lyude> oh right - it would be 4 including you
+[14:26:01] <danvet> Lyude, I thought it was 3 including anholt?
+[14:26:23] <Lyude> ffydsf yes you're right, misread the names from our pms
+[14:26:57] <danvet> anyway I pinged a pile of people, thus far not much
+[14:26:57] <Lyude> danvet, mdnavare - are we alright with extending the nomination period? I will also be sending out a reminder today regarding it jfyo
+[14:27:03] <danvet> but maybe more squeezing will help
+[14:27:14] <danvet> yeah I think we should extend by 2 weeks to align with the next bod mtg
+[14:28:04] <danvet> Lyude, can you also update the wiki with new dates?
+[14:28:12] <Lyude> danvet: sure thing
+[14:28:15] <danvet> thx
+[14:28:31] <danvet> I'll go squeeze another one now, forgot to do that earlier today
+[14:32:06] <Lyude> We have two votes on the election committee out of 4, so I guess we can consider that enough to move the deadline forward
+[14:32:35] <Lyude> That's pretty much it for the meeting, thanks for coming everyone!
+[14:32:59] <hwentlan____> thank you
+[14:39:37] <danvet> cheers
+[15:00:29] <mdnavare> Lyude: Yes fine with extending since its only 3 nominations
+[15:35:18] <Lyude> mdnavare: cool
+[15:47:30] [disconnected at Thu Mar 3 15:47:30 2022]
diff --git a/BoardOfDirectors/IrcLogs/2022/03-17.mdwn b/BoardOfDirectors/IrcLogs/2022/03-17.mdwn
new file mode 100644
index 00000000..9ce2ecec
--- /dev/null
+++ b/BoardOfDirectors/IrcLogs/2022/03-17.mdwn
@@ -0,0 +1,118 @@
+[[!format txt """
+[15:00:18] [connected at Thu Mar 17 15:00:18 2022]
+[15:00:18] [I have joined #xf-bod]
+[15:00:23] * danvet waves
+[15:00:25] <samuelig> hi
+[15:01:16] <Lyude> Hi everyone! Agenda for today: MIPI Alliance and CSI, election season, treasurer report 2021, finding more sysadmins, new parent foundation, GSoC
+[15:02:02] <Lyude> also mfilion, keithp, hwentlan____, mdnavare, anholt - who all is here?
+[15:02:08] <anholt> here
+[15:02:14] <Lyude> cool that means we have quorum :)
+[15:02:48] <Lyude> Ok - I'll start with my topics. No updates for MIPI alliance and CSI unfortunately, I still need to make the time to poke them. Same for finding a new parent foundation
+[15:03:12] <Lyude> For the finding more sysadmins item: We need to try to find more volunteer sysadmins to help with upkeeping things. No one's stepping down, but there's definitely less time availability across admins overall, so it would be good for us to try to bring additional people on the team
+[15:03:49] <danvet> agenda += xdc22 sponsors
+[15:04:03] <Lyude> danvet: added, thanks!
+[15:04:06] <danvet> but there's only a tiny update really, sponsor box on the website is now ready, kudos to daniels
+[15:04:38] <mdnavare> Hi All
+[15:04:52] <Lyude> danvet: gotcha
+[15:05:17] <Lyude> Oh btw - the admin stuff came up because I noticed an influx of spam registrations on the gitlab. So I guess if anyone else knows any ways to deal with that, let me know :)
+[15:05:37] <Lyude> (also not currently causing anyone real problems atm, but would like to get that fixed sooner then later)
+[15:05:58] <tlwoerner> how many admins are there now?
+[15:06:44] <Lyude> tlwoerner: we've got bentiss, emersion (iirc, I'm bad with names so hopefully I'm not misremembering), and daniels (although they really don't have much time available, and probably won't for quite a while)
+[15:07:40] <tlwoerner> what's involved?
+[15:07:49] <keithp> the fd.o admins have been chatting about reducing the self-hosted services to things we can't host in the cloud, and that looks to be limited to mailing lists mostly. That might help a little with the amount of work needed to manage stuff?
+[15:07:59] <tlwoerner> i guess if you want to attract people you'd need to have a "job posting", perhaps?
+[15:08:11] <Lyude> tlwoerner: 👀
+[15:08:29] <danvet> we've done that in the past at xdc presentations
+[15:08:53] <daniels> ++
+[15:08:54] <Lyude> tlwoerner: what it entails is probably a better question for daniels or bentiss. and tlwoerner yeah we've mentioned it a number of times, although I'll probably send out some mails about it once the election is over (just to make sure we're not throwing too much noise onto the mailing lists)
+[15:10:18] <Lyude> tlwoerner: are you interested at all btw?
+[15:10:39] <daniels> I can detail some things and better docs are WIP, but I was looking to step out pre-bentiss and certainly still am
+[15:11:28] <daniels> so would definitely appreciate some more active support in advertising and scouting for that
+[15:11:53] <tlwoerner> i'm considering it. i'm often "the linux person" at work and end up running the jenkins server, the svn/git server, the bugzilla instance, etc
+[15:13:02] <tlwoerner> (if that's the same sort of thing)
+[15:13:27] <Lyude> tlwoerner: for the most part, a lot of the management these days is around cloud stuff and gitlab, + some of the legacy services like the wiki
+[15:13:36] <Lyude> (although I think we'd eventually like to move stuff like the wiki into the cloud as well)
+[15:13:50] <keithp> well, gitlab pages for much of it
+[15:13:58] <Lyude> that's what I meant yeah
+[15:14:11] <tlwoerner> so... gitlab then :-)
+[15:15:04] <Lyude> I guess we can continue this over email :)
+[15:15:12] <Lyude> this would definitely be a huge help
+[15:15:33] <Lyude> anholt: do you want to go over the treasurer report stuff now?
+[15:15:52] <anholt> we have 2021 data now, so I can start writing a report when I scrape together some time
+[15:16:24] <anholt> the other treasurer issue is is still open, once again.
+[15:17:05] <Lyude> Sigh
+[15:17:21] <Lyude> danvet, mdnavare: can y'all help us again with poking Intel
+[15:17:46] <danvet> hm I haven't been involved in any of these mails
+[15:17:51] <danvet> maybe best for mdnavare to poke I guess
+[15:17:59] <danvet> or if there's something I can forward?
+[15:18:43] <mdnavare> Lyude: danvet: Yes I can poke again there
+[15:19:24] <Lyude> mdnavare: cool, thanks!
+[15:19:31] <Lyude> tlwoerner: Any updates with GSoC?
+[15:20:10] <tlwoerner> not much, potential students start applying Apr 4, so we're in a little limbo for now
+[15:20:46] <tlwoerner> by the way, if we switch parent (financial) organizations, that could get messy wrt the gsoc payment
+[15:21:02] <danvet> tlwoerner, we're not going to be that fast
+[15:21:12] <danvet> and there's going to be some overlap until everything is moved
+[15:21:18] <danvet> was at least the case when we moved to spi too
+[15:21:21] <tlwoerner> sounds good
+[15:21:23] <Lyude> tlwoerner: yeah, I was going to say as well what we would probably do in that case is make sure whenever the switchover happens is after GSoC
+[15:22:01] <Lyude> assuming there is one, since we do need to have an election on it and all
+[15:22:09] <Lyude> but I don't foresee much resistance there
+[15:22:26] <Lyude> samuelig: any updates on GSoC?
+[15:22:28] <Lyude> oops
+[15:22:30] <Lyude> sorry, XDC2022
+[15:22:33] <samuelig> xD
+[15:23:04] <mfilion> o/ sorry I'm late
+[15:23:05] <samuelig> XDC 2022, as danvet said sponsor box now shows the sponsors properly. We added the confirmed sponsors to the website as well.
+[15:23:28] <samuelig> (thanks daniels for the sponsorbox fix! And mfilion for fixing issues with sponsor logos!)
+[15:23:31] <tlwoerner> mfilion: figures… you started off early ;-)
+[15:23:40] <tlwoerner> haha
+[15:23:44] <mfilion> lol :p
+[15:23:55] <samuelig> no more news
+[15:24:41] <samuelig> I don't have news about XDC 2023 either, although I think I will send some emails to potential organizers earlier than expected, i.e. after the elections, as they were delayed
+[15:25:01] <samuelig> so I think next week I can start sending those
+[15:25:27] <samuelig> oh, about XDC 2022, I will talk to organizers to prepare the CFP announcement for April
+[15:25:37] <samuelig> before I go to the parental leave (expected end of April)
+[15:28:04] <mfilion> Lyude when is the deadline for people to renew their memberships to be able to vote?
+[15:28:11] <Lyude> samuelig: alright, thanks for the info! Next up is election season, the end of the nomination period is drawing near and we currently have 4 candidates, so I think we need to extend the election timeline again
+[15:28:23] <Lyude> mfilion: currently 31st march, but will likely be extended per ^
+[15:28:28] <Lyude> has all the info jfyi
+[15:28:28] <danvet> Lyude, we have 5
+[15:28:36] <danvet> since like 5 seconds ago
+[15:28:36] <samuelig> until when it would be extended?
+[15:28:40] <Lyude> i even took notes this time and got the wron-OH
+[15:28:41] * danvet did some arm twisting
+[15:28:44] <Lyude> lol ok
+[15:28:49] <Lyude> so I did take my notes correctly :)
+[15:28:55] <mfilion> how many do we need until we have enough?
+[15:29:05] <Lyude> 6 iirc, lemme check
+[15:29:05] <danvet> well strictly speaking 4 for 4 seats
+[15:29:09] <danvet> but that's not a real election
+[15:29:14] <danvet> 5 is good enough to go
+[15:29:18] <danvet> Lyude, why 6?
+[15:29:27] <Lyude> ah, I thought I had remembered that number from somewhere but I guess not
+[15:29:33] <samuelig> I mention that because I was waiting to the end of the election process to find a replacement for XDC coordination. But the birthday could happen before if we extend it
+[15:29:34] <Lyude> (was about to double check the election page)
+[15:29:36] <danvet> last year we had 6
+[15:30:10] <samuelig> Lyude, do we know the dates if we extend it another time?
+[15:30:12] <Lyude> I guess we're good to go with elections then! which means we'll publish candidates on the 28th of march
+[15:30:35] <Lyude> samuelig: uhh, election would end on may 2nd in that case
+[15:30:40] <Lyude> but I think we're all set
+[15:30:42] <samuelig> too late for me xD
+[15:30:48] <danvet> Lyude, can you take care of getting personal statement (aka sales pitch) and contribution statements from all of them?
+[15:30:53] <danvet> I don't think we have that yet
+[15:31:05] <samuelig> I will write an email with the tasks. I can check email and so on, but I prefer if other can take a more active role than me in that regard
+[15:31:10] <Lyude> danvet: sure thing
+[15:31:24] <mfilion> alright, I'll post some renewal reminders on Twitter
+[15:31:38] <mfilion> @lyude can you send some to the mailing lists too?
+[15:31:54] <danvet> Lyude, thx
+[15:31:58] <Lyude> mfilion: sure.
+[15:32:00] <Lyude> done
+[15:32:03] <Lyude> want to see me do it again
+[15:32:07] <Lyude> (I sent some yesterday :)
+[15:32:45] <danvet> samuelig, <- pls update that one so it's not lost
+[15:32:50] <danvet> if anything is missing there
+[15:34:07] <Lyude> alright, that's it for the meeting. thanks for coming everyone!
+[15:34:19] <samuelig> danvet, ok
+[15:36:45] <mfilion> Posted on Twitter
+[15:56:16] [disconnected at Thu Mar 17 15:56:16 2022]
diff --git a/BoardOfDirectors/IrcLogs/2022/03-31.mdwn b/BoardOfDirectors/IrcLogs/2022/03-31.mdwn
new file mode 100644
index 00000000..40d1a9d0
--- /dev/null
+++ b/BoardOfDirectors/IrcLogs/2022/03-31.mdwn
@@ -0,0 +1,206 @@
+[[!format txt """
+[14:59:28] [connected at Thu Mar 31 14:59:28 2022]
+[14:59:28] [I have joined #xf-bod]
+[15:00:13] <mfilion> o/
+[15:00:55] <Lyude> Hi everyone! Time for rolecall: danvet, mdnavare, samuelig, hwentlan____, keithp
+[15:01:06] * danvet waves
+[15:01:08] <keithp> o/
+[15:01:09] <mdnavare> Hi All
+[15:01:28] <samuelig> hi!
+[15:01:41] <Lyude> (gimme one sec, finishing up making some coffee real quick)
+[15:02:53] <Lyude> Alright hi! We've got quorum now, so the agenda for today: XDC2022, GSoC/Outreachy/EVoC, MIPI Alliance and CSI, Election season, Treasurer Report for 2021, new parent organization, find more sysadmins
+[15:03:15] <Lyude> For MIPI: no updates yet, meant to poke about this but got distracted at work. Will try to get to this soon.
+[15:03:27] <Lyude> As for the parent organization, going to start looking into that post-election
+[15:03:52] <Lyude> samuelig: do you want to go over XDC2022?
+[15:04:00] <samuelig> sure thing
+[15:04:02] <samuelig> XDC 2022: contacted organizers to prepare the CFP. We are going to do a separate announcement for XDC and WineConf, but we will mention each other in the respective ones. I plan to send it next week.
+[15:04:13] <hwentlan____> hi, sorry i'm late
+[15:04:23] <Lyude> eh, I -did- forget to remind you
+[15:04:28] <Lyude> so no worries :P
+[15:04:31] <samuelig> XDC 2023: I have contacted all European potential candidates that I am aware of. We will send the RFP email at the same time than XDC 2022 CFP one, but it is good to test waters first. I heard one that is considering it seriously :)
+[15:04:54] <samuelig> Note: At some point in the next 30 days, I will be in a parental leave. There is no volunteers yet to take over my tasks. I will try to follow-up things until the election, but we would need to find a replacement for me to avoid me blocking stuff.
+[15:05:33] <Lyude> mfilion: ^ any chance you would be up to this?
+[15:06:26] <danvet> I can help out, but given that I'm behind on sponsorship hunt probably not a good idea to rely on me
+[15:06:41] <mfilion> depends if I'm re-elected right? :p
+[15:06:53] <mfilion> ask me after the election lol
+[15:07:29] <mfilion> but sure samuelig, if I'm still here, and you need some follow ups, let me know
+[15:07:38] <samuelig> good thanks!
+[15:07:51] <Lyude> good point. I think I should have the time to be the backup volunteer if you can't find anyone samuelig until we can pass over to someone else
+[15:08:09] <samuelig> roger
+[15:08:21] <samuelig> thanks mfilion and Lyude!
+[15:09:22] <Lyude> no problem! I think we can skip the treasurer report for right now unless emma comes in later since it seems that they're mia
+[15:09:53] <Lyude> tlwoerner/siqueira : any updates on GSoC stuff?
+[15:11:58] <Lyude> (will wait a few minutes to see if they're around, and we can go ahead if I don't see any response in like 4min)
+[15:12:28] <samuelig> Just to mention that I published
+[15:12:46] <samuelig> I think we should do more effort on announcing our GSoC slots in our twitter account
+[15:12:57] <danvet> mfilion, ^^ for you
+[15:12:58] <samuelig> who is managing it? alanc ?
+[15:13:08] <Lyude> I think mfilion got the password from alanc iirc
+[15:13:08] <danvet> mfilion since a while, alanc stepped down from taht
+[15:13:26] <samuelig> I see
+[15:13:59] <alanc> both of us - I still do a bunch of the retweets there, but he does most of the new posts, since he's more in touch with what the board is up to
+[15:14:34] <mfilion> nope
+[15:14:37] <mfilion> alanc still tweeting
+[15:14:41] <mfilion> I mean I do it too
+[15:14:48] <mfilion> but he's the one retweeting stuff
+[15:15:11] <mfilion> But good idea to post more about GSoC
+[15:15:19] <mfilion> can you share the link here, I'll prepare some tweets
+[15:15:48] <mfilion> (for the link I mean the direct link to the GSoC page about X.Org)
+[15:15:49] <alanc> I did RT samuelig's tweet about his blog yesterday
+[15:16:00] <mfilion> see, thank you alanc!
+[15:16:41] <samuelig> you can also mention and It is all in my blog post, but it is worth to do a follow-up some days after
+[15:17:03] <Lyude> may still want to post something that mentions generally as well
+[15:17:27] <Lyude> also btw - I noticed you mentioned EVoC on there, we still don't have anyone running that do we?
+[15:17:32] <mfilion> thanks samuelig
+[15:17:47] <mfilion> Lyude what do you mean, mentions generally?
+[15:18:14] <samuelig> Lyude, nope, but I hope some of the new board members can be on charge of EVoC coordination
+[15:19:02] <Lyude> mfilion: I guess I'd need to see the tweet, I was just wondering if the tweet mentioned specifically in the thumbnail - but I realized that might just already be obvious since it's coming from the twitter account lol
+[15:19:07] <Lyude> so probably doesn't matter too much
+[15:19:38] <Lyude> Anyway - I think we can move on to the next item
+[15:19:46] <mfilion> Well yes, I meant tweeting from the account, to talk about GSoC and inviting students to submit
+[15:19:46] <alanc> was the RT, which mentions @XorgFoundation EVoC in the body
+[15:19:55] <Lyude> ahh gotcha
+[15:19:57] <Lyude> cool
+[15:20:21] <alanc> but yes, a specific invite from the foundation itself would be a good thing in addition to that one
+[15:21:58] <Lyude> ok - so election season, I can cover this one: Things are going smoothly, we ended the nomination period on Monday and will be ending the membership renewal period tomorrow
+[15:22:15] <mfilion> how many members do we have now, compared to last year?
+[15:22:23] * Lyude looks
+[15:22:42] <danvet> 80
+[15:22:57] <danvet> 97 last election
+[15:23:01] <mfilion> ouch ok
+[15:23:04] <danvet> so a bunch of folks didn't renew
+[15:23:13] <mfilion> that's not a good look
+[15:23:16] <danvet> mfilion, you didn't tweet enough :-P
+[15:23:21] <mfilion> apparently
+[15:23:23] <mfilion> doing it now
+[15:23:31] <Lyude> should we extend the period at all?
+[15:23:35] <danvet> 2 years ago it was 66
+[15:24:19] <danvet> 2019 was 84
+[15:24:21] <Lyude> yeah… actually I think the 81 out of 97 people voting last election was the largest turnout ever technically
+[15:24:22] <danvet> I think we're in line
+[15:24:43] <Lyude> cool
+[15:24:45] * danvet spotted a mistake in the wiki on the 2019 page
+[15:24:45] <mfilion> hmm ok. still frustrating to see it go up and down
+[15:25:25] <samuelig> losing interest? maybe this is something to discuss at the next XDC
+[15:25:42] <samuelig> and gather feedback
+[15:25:56] <Lyude> I think in general just having XDC might also make it easier to get people involved again wouldn't it?
+[15:26:04] <danvet> yeah
+[15:26:06] <samuelig> because we are increasing steadily the # attendants to XDC but I don't see that reflected in memberships
+[15:26:21] <mfilion> maybe the renewing yearly isn't ideal
+[15:26:29] <danvet> yeah xdc usually gathers a handful of applicants
+[15:26:29] <Lyude> I've been attributing a lot of loss of interest in various things recently to COVID
+[15:26:38] <danvet> mfilion, if you don't, you just clog up the membership
+[15:26:48] <danvet> also, we have very strict rules for bylaw changes
+[15:26:57] <danvet> if you drop the renewal, bylaw changes become impossible
+[15:27:01] <danvet> imo this is perfectly fine
+[15:27:10] <danvet> it's like voting in .ch, participation is low
+[15:27:10] <Lyude> and as well we want it to represent some level of activeness in the community, particularly since we use membership as a gatekeeping mechanism for VESA spec access and such
+[15:27:17] <mfilion> danvet a few people told me "you need to renew!?" when I pinged them
+[15:27:22] <danvet> because as long as the right people get elected, you kinda don't have to go vote :-)
+[15:27:44] <danvet> mfilion, I have no idea why they don't know, we do this for as long as is open to general membership
+[15:27:54] <danvet> and they all should have gotten a mail about it too
+[15:28:11] <mfilion> we could switch it around, and have it automatically renew every year except if you decline?
+[15:28:14] <Lyude> I thought I didn't send enough emails but I think every time I've looked it seems like I technically sent more reminders then last year
+[15:28:38] <danvet> mfilion, like our membership criteria is essentially "can you be bothered to care enough to renew and type in some contribution statement"
+[15:28:49] <danvet> I don't think we can lower the bar more without making it entirely meaningless
+[15:29:10] <Lyude> we could however, automate the renewal reminders couldn't we
+[15:29:19] <danvet> like if people don't care enough about to go to the link and push the button, why should they have voting rights
+[15:29:41] <mfilion> hmm good point
+[15:29:49] <mfilion> automating reminders would be nice though
+[15:29:52] <keithp> participation in the election is way more important than membership
+[15:29:52] <samuelig> IIRC gnome allows renewal of membership if you have enough contributions in hte last two years... I don't know if that means that it is renewed every other year, or it is yearly still
+[15:30:07] <samuelig> but we can consider extending the membership to two years instead, dunno
+[15:30:48] <Lyude> tbh I feel like it's not really a problem tbh
+[15:30:52] <danvet> mfilion, we also allow renewal past when candidates are published
+[15:31:03] <danvet> so if you see someone you really don't like, you can still renew in time
+[15:31:16] <danvet> and past that point it's just a number
+[15:31:20] <samuelig> I think that some people could see like membership is only for elections, and nothing else. I don't know how we can change that feeling
+[15:31:41] <Lyude> well it's definitely for more then just elections since we use it for both vesa and khronos stuff
+[15:31:46] <mfilion> that's my feeling too samuelig
+[15:31:49] <danvet> samuelig, well and all that stuff you indirectly control through that election, which is quite a bit more
+[15:31:53] <Lyude> we do mention that every state of the xorg though
+[15:32:00] <danvet> but yeah nominally the election is all you get
+[15:32:12] <danvet> ah right, I forgot
+[15:32:22] <Lyude> (also if folks are wondering - I do actually verify everyone asking for vesa stuff actually has an active membership :)
+[15:32:29] <samuelig> Lyude, good point
+[15:32:31] <mfilion> maybe when we get around to refreshing the website, we could make a clearer benefits page?
+[15:32:39] <keithp> many people have vesa and khronos interactions through corporations though; for me, is about process
+[15:32:55] <samuelig> but for the khronos thing, several people were surprised when I mention it
+[15:33:05] <samuelig> so probably we need to announce it better, like with the new website
+[15:33:14] <mfilion> ++
+[15:33:16] <Lyude> we really need a new website lol
+[15:33:32] <keithp> heh. wait another year or so and we could do web 4.0 instead
+[15:33:33] <Lyude> but I think I'm preaching to the choir with that one
+[15:33:38] <samuelig> or mfilion tweeting like crazy all these benefits xDDD
+[15:33:42] <mfilion> hahaha
+[15:33:49] <mfilion> well I did mention a new website in my re-election statement
+[15:34:02] <danvet> mfilion, yeah you volunteered pretty well for that one
+[15:34:33] <mfilion> it's on the list, already discussed with our in-house designer
+[15:35:40] <Lyude> Anyway - the last item is finding more sysadmins: although I had this on the agenda mostly to check in to see how tlwoerner was doing with that
+[15:35:48] <Lyude> erm - them volunteering I mean
+[15:36:04] <Lyude> but we do still need more sysadmins, so if anyone knows anyone else who's interested feel free to try to wrangle them into it :)
+[15:36:33] <Lyude> Anyway - I think that's it for the meeting everyone, thanks for coming!
+[15:36:44] <keithp> have fun out there
+[15:37:03] <samuelig> thanks everybody, funny meeting today :)
+[15:37:10] <mfilion> indeed. thanks everyone!
+[15:39:08] <keithp> danvet: raclette?
+[15:40:25] <danvet> keithp, eating the apple/orange/nuts/crumble thing right now
+[15:40:30] <keithp> yum!
+[15:40:32] <danvet> or do you mean what raclette is?
+[15:40:45] <keithp> oh, well aware of what raclette is, just now wanting some...
+[15:41:01] <keithp> (debconf was a fine introduction to that tradition :-)
+[15:41:06] <danvet> Sat or Sun should be below freezing, I planned it for then :-)
+[15:41:17] <keithp> excellent!
+[15:41:26] <samuelig> danvet, after following your timeline for years, I wonder if you are a kernel developer with cooking as a hobby, or a cook with kernel development as a hobby xDD
+[15:41:41] <keithp> danvet clearly lives to eat
+[15:42:20] <danvet> did you have the big raclette ovens with half cheese wheels?
+[15:42:28] <mfilion> now you're making me hungry. had raclette last month, might be do for another run soon.
+[15:42:29] <keithp> oooo
+[15:42:36] <danvet> I mean at debconf
+[15:42:40] <keithp> alas no
+[15:42:42] <danvet> at home those are serious overkill
+[15:42:43] <keithp> just table-top versions
+[15:42:53] <mfilion> danvet that's what my dad has here, it's the best
+[15:42:54] <danvet> the half wheel stuff is epic
+[15:42:54] <keithp> we do hot plate on the table here
+[15:43:00] <danvet> especially when you have open flames or so
+[15:43:08] <keithp> wow. that sounds amazing
+[15:43:29] <mfilion> haha no flames here though, just heating element
+[15:43:42] <danvet> bwidawsk witness that when I was here and was impressed with the stainless steel machinery and gas flame ovens :-)
+[15:43:50] <danvet> *he was here
+[15:43:55] <keithp> someday we'll be able to enjoy raclette in its native environment again
+[15:44:18] <mfilion> keithp I had some in Chamonix once where they would take a huge brick of cheese out of the fire burning oven, and then just slice it like a loaf of bread onto your plate....
+[15:44:35] <mfilion> just epic
+[15:44:44] <keithp> you're seriously testing the moisture tolerance of my keyboard here
+[15:45:07] <keithp> and I just had about half a kg of nutella
+[15:45:41] <danvet> hm youtube only has the electric ones
+[15:45:45] <samuelig> mfilion, I got it in geneva, that is damn good. Also I went several times to gruyère to eat fondue when I was living in Switzerland... that is the paradise
+[15:46:59] <danvet> samuelig, yeah moité-moité with well aged cheese is great
+[15:47:04] <mfilion> haha that is on my bucket list samuelig, raclette in switzerland
+[15:47:24] <danvet> mkay I do a few tweets if I remember
+[15:47:31] <danvet> but I only have a boring electric table-top thing here
+[15:48:32] <danvet> getting there
+[15:48:40] <keithp> let us know if you're building a wood-fired raclette device
+[15:48:59] <danvet>
+[15:48:59] <mfilion> lol
+[15:49:01] <danvet> that's the thing
+[15:49:17] <danvet> well you can, but the thing is it's a mess because you need to hold the wheel of cheese horizontal
+[15:49:21] <danvet> so it tends to drip down
+[15:49:27] <danvet> only recommended for camping
+[15:49:34] <keithp> 'the world of raclette'. Do we really need any other world?
+[15:51:22] <mfilion> yeah this is basically the one we have here
+[15:52:20] <keithp> ** Cheese not included **
+[15:52:57] <mfilion> ahh there it is on the TTM site
+[15:53:18] <mfilion> amazing, we've had it for 20+ years, still going strong
+[15:54:39] <danvet> dumb heating coil, nothing else needed
+[15:54:47] <danvet> some of the more modern ones have a thermostat
+[15:54:53] <danvet> all that achieves is a crap control loop
+[15:54:59] * danvet not impressed
+[15:55:06] <danvet> I have one of the really old ones here
+[15:55:14] <keithp> need an IR thermometer pointed at the cheese
+[15:55:19] <danvet> yeah
+[15:55:23] <danvet> which they don't
+[15:55:30] <danvet> so it's either too much power or not getting warm
+[15:55:34] <keithp> and which modern toasters (for bread) could also use
+[16:14:51] [disconnected at Thu Mar 31 16:14:51 2022]
diff --git a/BoardOfDirectors/IrcLogs/2022/04-28.mdwn b/BoardOfDirectors/IrcLogs/2022/04-28.mdwn
new file mode 100644
index 00000000..4fed5e96
--- /dev/null
+++ b/BoardOfDirectors/IrcLogs/2022/04-28.mdwn
@@ -0,0 +1,407 @@
+[[!format txt """
+[15:02:24] [connected at Thu Apr 28 15:02:24 2022]
+[15:02:25] [I have joined #xf-bod]
+[15:02:32] <danvet> once more for the secretary
+[15:02:34] * danvet waves
+[15:02:37] <mfilion> o/
+[15:03:08] <tlwoerner> hello
+[15:03:09] <Lyude> Alright - we can actually skip roll call since we've got quorum (other members present: alyssa, rg3igalia)
+[15:03:10] <alyssa> hello!
+[15:03:25] <rg3igalia> hi secretary! :)
+[15:03:35] <Lyude> hi! so: Agenda for today: Elections, XDC2022, XDC2023, GSoC/Outreachy/EVoC, MIPI alliance and CSI, treasurer report for 2021, new parent organization, sysadmins
+[15:04:03] <Lyude> So elections of course finished, and we have two new board members: alyssa and rg3igalia! Congrats on making it onto the board :)
+[15:04:15] <rg3igalia> thank you!
+[15:04:20] <mfilion> Indeed, welcome
+[15:04:21] <danvet> congrats!
+[15:04:49] <alyssa> thank you ^^
+[15:05:03] <tlwoerner> technically, is there a date elections are supposed to take place?
+[15:05:27] <danvet> Lyude, we had one thing from that: Dropping the board vote step in the election procedure
+[15:05:28] <Lyude> tlwoerner: not precisely, we usually come up with the schedule on the spot but it's usually around the same time each year
+[15:05:32] <danvet> should probably vote on that?
+[15:05:36] <Lyude> danvet: ah right, yeah definitely
+[15:06:02] <danvet> for everything else mfilion already volunteered to deliver a perfect show next year with no flaws :-P
+[15:06:32] <Lyude> tl;dr for those not in the know: it turns out for whatever reason we have an extra step on the election instructions: step 18: "Present results to full board of Directors for certification…"
+[15:06:42] <mfilion> Before talking procedure though, we need to discuss the actual results
+[15:07:04] <Lyude> mfilion: do we? I'm pretty sure we already approved them
+[15:07:10] <mfilion> After losing nearly 20% in membership year to year, we had our worst election turnout since 2018
+[15:07:30] <mfilion> I see this as a huge wake up call for X.Org
+[15:08:08] <mfilion> If people don't even care about renewing their membership, and even less (significantly less) about taking a minute to vote, what does that say about the Foundation
+[15:08:21] <alyssa> ...or maybe just the elections procedure.
+[15:08:50] <Lyude> tbh I think I probably should have sent out more reminders, the other thing is I'm wondering how many election emails actually got out
+[15:09:00] <mfilion> I think this is the time for us to take a step back and see what we need to do to turn things around, and give more credibility to
+[15:09:08] <mfilion> I don't even think its a question of reminders
+[15:10:04] <danvet> in the past turn out was very much a question of reminders
+[15:10:12] <mfilion> I'm glad we're looking at moving parent org, but I think it might also be time to look at a rebrand as well
+[15:10:26] <danvet> like for bylaw changes we sent folks daily reminders in the 2nd week
+[15:10:52] <danvet> mfilion, you mean like a non-garbage website and stuff?
+[15:11:14] <alyssa> FWIW-- I talked to a member, who commented that they don't usually vote because of the overhead of voting (including "fixing [their] account")... which isn't a high priority for them compared to other FOSS graphics duties.
+[15:11:24] <alyssa> Nothing to do with credibility and everything to do with procedures
+[15:11:38] <Lyude> yeah
+[15:11:43] <danvet> alyssa, you can log in with gitlab account
+[15:11:45] <alyssa> And the fact that, let's face it, no matter who wins the board election, will probably be fine
+[15:12:06] <mfilion> X.Org is dying, it's time to refresh it
+[15:12:11] <alyssa> ("Funny thing to say as someone who just campaigned." "Ah, well.")
+[15:12:41] <danvet> so LF technical board (aka the linux kernel board) votes last year
+[15:12:44] <danvet> Board had 1012 authorized voters; 237 of them cast ballots.
+[15:13:06] <danvet> I'm not sure whether you want to make a case that the linux kernel is irrelevant
+[15:13:33] <mfilion> lol are you comparing us to the LF?
+[15:13:39] <danvet> and LF tech board authorized voters is a lot stricter than what we have, iirc it's 50 commits
+[15:13:48] <danvet> well strictly speaking this is the only board the kernel has
+[15:13:56] <danvet> and it was the only one I could quickly find results for
+[15:14:17] <mfilion> I'm just saying, we had 83% turnout last yea, it had been going up every year for 3 consecutive years, and now huge drop
+[15:14:23] <mfilion> and if we're going to be moving parent org
+[15:14:38] <mfilion> I think we should take the opportunity to also consider a rebrand
+[15:14:57] <tlwoerner> xxorg
+[15:14:59] <Lyude> mfilion: while I'm totally in favor of a rebrand (and I think it's totally needed as well), I just caution against taking the election turnout results as a prediction of the future
+[15:15:00] <mfilion> i.e. Freedesktop Foundation instead of X.Org Foundation
+[15:15:23] <rg3igalia> might agree on the rebranding, but a single data point can hardly be considered a trend to conclude the org is dying, imho
+[15:15:25] <danvet> mfilion, I'm not seeing how that fixes anything
+[15:15:31] <mfilion> It would instantly give us more scope & reach
+[15:15:40] <alyssa> ...Would it?
+[15:15:41] <mfilion> i.e. I spoke to some GStreamer people and they would join if we did that
+[15:15:48] <danvet> like actual non-shitty website, or some outreach effort and all that, absolutely
+[15:16:01] <danvet> changing the name is kinda meh
+[15:16:07] <danvet> and an absolute pile of work
+[15:16:14] <mfilion> SFC can help us with that
+[15:16:17] <mfilion> easily
+[15:16:31] <danvet> it would drop the need to stop caring about our domain name troubles
+[15:16:44] <alyssa> is coveted? ;p
+[15:17:22] <Lyude> lol, will pm you about that in a bit alyssa
+[15:17:29] <mfilion> even if we have a nice modern website, it's still only, and xdc is still our only source of revenue.
+[15:17:33] <alyssa> "It would instantly give us more scope & reach" It's not self-evident why that's something to strive for.
+[15:17:34] <danvet> alyssa, yeah you're pm are disabled or something
+[15:17:50] <alyssa> danvet: try again now, allowlisted you
+[15:18:01] * danvet not cool enough probably
+[15:18:05] <Lyude> I mean I think it's a good idea to strive for since we do want to make sure we have a steady stream of income in order to maintain things like gitlab
+[15:18:24] <Lyude> I'm just a bit surprised that something like a name would be the determining factor for folks like gstreamer joining
+[15:18:47] <danvet> yeah the entire " does anything but" has become a running gag for years
+[15:19:06] <danvet> so really can't use it to explain why suddenly all the people who got the joke in the past forgot about it
+[15:19:28] <danvet> and it is a pretty cool domain :-)
+[15:19:47] <mfilion> haha yes it is a cool domain
+[15:19:48] <Lyude> but how much of this is really just speculation in terms of how effective solutions are, we do have the ability to ask our users and get more data on this.
+[15:20:26] <Lyude> I think the more important thing is just getting across to new people what does do, make it apparent on the front page - that sort of thing
+[15:20:57] <danvet> yeah also can we get through the agenda and do the big philosophical brainstorming at the end?
+[15:21:04] <Lyude> yeah good point lol
+[15:21:10] <mfilion> lol in a rush danvet?
+[15:21:37] <danvet> mfilion, it's like half past 9 and I might not have a life, but I do want some evenings
+[15:21:49] <Lyude> we just want t omake sure we get the items done so that we don't run out of time :P, we have the rest of the meeting after that
+[15:21:49] <mfilion> we can do these meetings earlier
+[15:22:02] <mfilion> also, I think we should move these meetings away from irc, but we can discuss that later to
+[15:22:48] <danvet> imo as long as are on irc we might as well be too, otherwise it's just more complicated
+[15:23:06] <Lyude> So XDC2022/2023: Since samuel is on leave, I've been handling the XDC stuff - sent out the CFP (for XDC2022) and RFP (for XDC2023) this week
+[15:23:27] <Lyude> Oh- also we're waiting on LPC to get plans together for shipping us throw mics
+[15:24:03] <Lyude> MIPI alliance and CSI: haven't gotten to this, I guess I should be able to start poking again at the same time that I start poking SFC
+[15:24:04] <mfilion> that's just a lame excuse danvet
+[15:24:08] <danvet> I have +4 sponsors committed, 2 are in the "ensure budge stage" so that part is going fine too
+[15:24:29] <danvet> mfilion, we do occassionally need to pull in people here, so if they're not on whatever platform you want it's a pin
+[15:24:34] <danvet> they are pretty much all here
+[15:24:39] <danvet> they = lots of our members
+[15:24:56] <danvet> so no no lame excuse, I agree we should have something a tad more modern maybe for our communities
+[15:25:04] <danvet> but just moving the board achives not much imo
+[15:25:19] <Lyude> it's also easier for members to read the meeting transcripts (which does happen)
+[15:25:50] <mfilion> I would interested to see how many actually reads the transcripts
+[15:26:01] <Lyude> I know phoronix definitely does
+[15:26:17] <alyssa> I occassionally do (well, did.)
+[15:26:19] <rg3igalia> I usually do
+[15:26:19] <mfilion> he doesn't, he has a tool that skims through them automatically
+[15:26:26] <Lyude> huh
+[15:26:41] <alyssa> usually just read Lyude's excellent summaries, though
+[15:26:43] <mfilion> all his news are automated, that's how he finds stuff so quickly
+[15:26:53] <tlwoerner> ooh, we could mess with his tool
+[15:27:05] <tlwoerner> or at least prod it
+[15:27:14] <mfilion> lol
+[15:27:20] <rg3igalia> now that you mention phoronix, did they publish anything about the elections this year?
+[15:27:24] <Lyude> Also, new parent organization: no updates yet, will start poking folks now that elections are over
+[15:27:30] <alyssa> rg3igalia: I didn't see anything
+[15:28:07] <Lyude> Sysadmins: we definitely need more sysadmins as always!
+[15:28:18] <Lyude> and tlwoerner: do you want to go over GSoC stuff?
+[15:28:26] <tlwoerner> okay
+[15:28:32] <mfilion> Lyude what updates are you looking for regarding parent org?
+[15:28:43] <Lyude> mfilion: oh nothing, this is on me to start working on
+[15:28:55] <tlwoerner> the contributor proposal period ended Apr 19
+[15:28:57] <Lyude> i had just been planning on starting this at the end of elections
+[15:29:03] <tlwoerner> we have received 5 proposals: 4 genuine, 1 spam
+[15:29:13] <tlwoerner> we have until May 12 to rank the 4 proposals and put in our slot request
+[15:29:21] <tlwoerner> i was asked to send the payment info to Martin Michlmayr, which i did
+[15:29:44] <tlwoerner> we have 7 mentors
+[15:30:27] <mfilion> nice nice
+[15:30:30] <Lyude> tlwoerner: nice work!
+[15:30:52] * anholt arrives
+[15:30:59] <alyssa> anholt: welcome :)
+[15:31:06] <Lyude> oh wow, just in time anholt
+[15:31:19] <tlwoerner> the GSoC rules have changed substantially this year, it's causing some turmoil
+[15:31:36] <tlwoerner> but i'm sure we'll be okay
+[15:31:38] <Lyude> You mean the ability to have different lengths of projects, right?
+[15:31:55] <danvet> anholt, in case you didn't see it, I had a question on the google xdc issue, would be good to confirm that one way or another
+[15:31:59] <tlwoerner> the worst change is that the participant be "new" to open source
+[15:32:06] <danvet> or should I ping stephane?
+[15:32:08] <Lyude> oh dear
+[15:32:14] <tlwoerner> but there's not definition of "new"
+[15:32:54] <tlwoerner> on one hand we have one proposal for a young person who is still in school, but has been contributing to the linux kernel for over a year
+[15:33:18] <tlwoerner> of course the first couple patches are trivial, but then they get more sophisticated
+[15:33:52] <tlwoerner> on the other hand we have one proposal from a person who graduated 3 years ago, has no open source contributions anywhere, and works as a software developer
+[15:34:03] <anholt> danvet: sorry, I'm missing it. what xdc issue?
+[15:34:15] <danvet>
+[15:34:29] <danvet> you said you started the invoice, afaik they're not yet committed
+[15:34:36] <danvet> if they're committed I should add the logo asap
+[15:34:45] <anholt> hmm, let me check, did I reply to the wrong issue?
+[15:34:46] <Lyude> tlwoerner: sheesh, yeah that rule doesn't sound good at all
+[15:35:10] <danvet> anholt, iirc you had that reply on all the others that needed an invoice too
+[15:35:23] <Lyude> It really shouldn't be up to google on determining things like that but on the actual mentoring organizations…
+[15:35:30] <danvet> anholt, there's 4 in the invoicing process now, all assigned to you
+[15:36:24] <Lyude> tlwoerner: is that all of the gsoc stuff
+[15:36:26] <Lyude> *?
+[15:36:38] <Lyude> also - do you have an email with the proposals that we need to rate anywhere?
+[15:36:43] <tlwoerner> Lyude: yes, sorry
+[15:37:33] <Lyude> anholt: want to go over the 2021 treasurer report?
+[15:37:45] <anholt> I don't think there's anything to go over, i just need to push it out
+[15:37:46] <tlwoerner> Lyude: the rating should be done by the mentors. do you want to mentor? ;-)
+[15:37:53] <Lyude> oh oops :P
+[15:37:58] <Lyude> anholt: sounds good
+[15:38:16] <Lyude> then we've just got a vote on procedure, and we can finish off with mfilion's topic
+[15:38:46] <mfilion> and continue the discussion about moving this off irc
+[15:38:49] <danvet> anholt, thx for typing up the report and all
+[15:39:45] <Lyude> so is everyone ( anholt, danvet, mfilion, alyssa, rg3igalia, mdnavare)
+[15:39:51] <Lyude> oops
+[15:39:57] <Lyude> *is everyone OK with us removing rule 18 here?
+[15:40:12] <alyssa> Why was rule 18 added in the first place?
+[15:40:14] <rg3igalia> can you give a bit more context?
+[15:40:21] <mfilion> yep I'm fine with it
+[15:40:59] <Lyude> rg3igalia: basically we have an election rule that states that before the election results are final, all board members have to certify the election results beforehand. the reason we want to remove it is because I don't think this has actually been followed the last few elections
+[15:41:04] <Lyude> alyssa: that I'm not totally sure about
+[15:41:16] <Lyude> I have a feeling it might have something to do with the xfree86 days
+[15:41:34] <anholt> it seems like a plausible safeguard to me, and doesn't feel like a problem
+[15:41:36] <danvet> alyssa, git blame says "port over election process from old board wiki"
+[15:41:41] <danvet> I don't have the old board wiki
+[15:41:50] <anholt> but I don't feel strongly
+[15:42:09] <alyssa> danvet: quite..
+[15:42:15] <danvet> yeah I think at most it causes 1-2 days more or so
+[15:42:27] <danvet> imo it's fine, the entire thing is like 2 months anyway
+[15:42:36] <rg3igalia> same opinion as anholt, I guess it's good just in case the election committee goes rogue or something, but I don't have strong feelings either way
+[15:42:45] <danvet> but mfilion wasnt to chain the world here, so that's why it came up
+[15:42:46] <tlwoerner> if nothing else, clarify which board should certify it: the outgoing board or the incoming
+[15:42:58] <anholt> seems obviously like outgoing to me.
+[15:43:07] <rg3igalia> only makes sense to be the outgoing one, yes
+[15:43:11] <danvet> tlwoerner, yeah that's a good point, but outgoing is the only one that exists at that point really
+[15:43:13] <anholt> like, they haven't been certified, so they're not on the board.
+[15:43:42] <danvet> anholt, I guess you could also make a case that the outgoing board might have gone rogue, but at that point the org is probably dead and needs to be reconstituted somehow
+[15:44:08] <danvet> imo it's ok to keep it, and there might be a case where this prevents org disaster
+[15:44:15] <mfilion> how so?
+[15:44:36] <Lyude> I assume a situation similar to what happened originally with xfree86
+[15:44:37] <danvet> election committee messing with the vote
+[15:44:53] <danvet> but yeah at that point your org is probably dead enough that you need a new one
+[15:44:58] <tlwoerner> someone disagreeing with the method, or the software
+[15:45:08] <tlwoerner> what if a bug is found in the way the tally is done
+[15:45:33] <rg3igalia> or someone complains again about not being able to leave slots blank :P
+[15:45:40] <mfilion> right but look at this latest election, we had two new members, two returning members, leaving only 4 to certify, one of which was on paternity leave, and 2 (3?) who were on the election committee
+[15:46:03] <mfilion> so what was the point of getting it "certified" if only the committee members could certify it lol
+[15:46:05] <Lyude> why not give the opportunity to reject the results, without making it mandatory that we vote to accept them?
+[15:46:37] <rg3igalia> that also sounds sensible
+[15:46:38] <danvet> Lyude, well if the vote isn't mandatory you can just certify the result
+[15:46:51] <mfilion> exactly
+[15:46:52] <danvet> and often it's quicker to get the vote than to have like a few days of time built in for rejectio
+[15:47:27] <danvet> mfilion, the full outgoing board votes, so your issue isn't an issue
+[15:47:39] <danvet> unless the board is sub-par, for which there's already rules in the bylaws
+[15:48:41] <Lyude> danvet: I guess the way I see it is that in terms of certification, the more important thing is that there's a route to challenge the results. having something like "Unless objections are raised in the 3 days after posting these results, they may be considered final"
+[15:48:44] <danvet> I think the only case here is when the election committee goes bonkers, and puts only their special friends on the list
+[15:48:59] <danvet> and all the people who re-run get ousted or something
+[15:49:31] <danvet> Lyude, yeah maybe we can put that in, and state that any member can raise objections and the outgoing board will consider them or something like that
+[15:49:48] <alyssa> IMHO the better fix there is make membership permanent (or at least last for longer than 2 years without renewal)... might help effective turnout, too... would need a bylaw change I guess
+[15:50:05] <Lyude> well, the problem is that we want membership to reflect active participation
+[15:50:29] <danvet> alyssa, then would have a pile of people on the membership list who haven't been active for 10+ years
+[15:50:38] <anholt> alyssa: the issue with that is then you have an approximately-0% voting rate among members, which iirc runs into trouble with other bylaws about needing x% voting to make changes.
+[15:50:42] <danvet> the old member system was very informative in this regard
+[15:50:47] <Lyude> especially when it comes to stuff like khronos certification and vesa spec access (I think it's also worth considering that x's place in the world tends to be those things, gitlab + XDC)
+[15:50:50] <danvet> plus what anholt says
+[15:50:54] <alyssa> anholt: ah, right.
+[15:50:55] <tlwoerner> …must have X commits … in the last Y days!
+[15:50:56] <danvet> and Lyude
+[15:51:04] <mfilion> I wouldn't make membership permanent
+[15:51:10] <mfilion> but I would make it every 2 years instead of yearly
+[15:51:10] <danvet> tlwoerner, yeah the downside of that is that it's gatekeep-y
+[15:51:17] <Lyude> yeah, making it longer might not be a bad idea
+[15:51:22] <Lyude> so long as it isn't permanent
+[15:51:25] <danvet> atm our gate is "bothered to renew" which personally I really like as a balance
+[15:51:47] <Lyude> (also I will brb)
+[15:51:49] <danvet> mfilion, then people forget that they need to renew and you get see-saw in membership
+[15:51:51] <mfilion> 20% didn't bother to renew, and of those who did, 35% didn't bother voting
+[15:52:01] <danvet> it's like foxes and rabbits in population density
+[15:52:13] <mfilion> and I don't know if anyone noticed, but of the 4 people elected, each had at least 20% of voters saying they shouldn't be on the board
+[15:52:48] <rg3igalia> that's... normal?
+[15:52:50] <danvet> mfilion, we don't have full preferential voting, which means tactical voting is a possibility
+[15:52:53] <danvet> aka you can't say that
+[15:53:04] <danvet> also 20% is effing low imo
+[15:53:12] <mfilion> not really, good luck at past results
+[15:53:15] <mfilion> nowhere near that
+[15:54:00] <mfilion> in your election danvet, you only had 10% putting you off the board :p
+[15:54:11] <mfilion> and you finished first
+[15:54:18] <keithp> that was probably danvet voting though
+[15:54:22] <mfilion> hahaha
+[15:54:38] <Lyude> there are very few instance I've ever voted someone at the bottom with the reason being me not wanting them on the board
+[15:54:51] <Lyude> the majority of the time it's more like "I want these people on the board more"
+[15:55:10] <anholt> same.
+[15:55:11] <Lyude> for reasons like that I feel like it's kind of hard to draw intent from a ranked voting system
+[15:55:19] <rg3igalia> agreed
+[15:55:20] <Lyude> besides who they want on the board, of course
+[15:55:36] <danvet> yeah we don't do full preference voting, so tactical voting is a good strategy aka I do the same as Lyude and anholt
+[15:55:50] <Lyude> I do think this does bring up a point for us needing to fix the empty ballot issue
+[15:56:00] <Lyude> because then those votes can be directly interpreted as such
+[15:56:05] <Lyude> or rather lack of
+[15:56:34] <mfilion> We had a solid drop in membership, and even bigger drop in turnout (it was 83.5% a year ago), I'm not looking forward to next year's election
+[15:56:53] <danvet> Lyude, if we do preference instead of points your true preference would be the best voting strategy, but we do points so it isn't indeed
+[15:57:16] <danvet> mfilion, more reminders and it should be fixed really
+[15:57:35] <danvet> we've tanked the first "should we join spi" vote like this too
+[15:57:37] <anholt> mfilion: I think you are really underestimating the importance of reminders to turnout.
+[15:58:00] <danvet> our reminder was literally "make your vote and these stop"
+[15:58:11] <daniels> re fd.o vs. X.Org - our infra is as much for GSt/NM/PipeWire as for gfx - currently they have no representation and all they contribute is some runners. given the everlasting existential issue has been getting interest in keeping the org sustainable, I genuinely don’t understand the position that we shouldn’t widen the net.
+[15:58:16] <danvet> same about reminding folks to renew
+[15:58:43] <daniels> and that if we keep the scope narrow by trying to keep a small target, that’s self-perpetuating
+[15:58:55] <mfilion> +1
+[15:59:00] <daniels> (cf. what I said when we merged fd.o in under the umbrella)
+[15:59:02] <danvet> daniels, I did propose widening the net when we did the fd.o merger, and reception wasn't the greatest iirc
+[15:59:12] <daniels> danvet: amongst whom?
+[15:59:36] <daniels> the same bunch of people the net doesn’t already cover … ?
+[16:00:09] <Lyude> i feel like there's multiple stats issues here. not to say I don't agree with widening the net: I think at the very least it's something we should be looking into, but I'm also noticing a lot of points in this discussion that equate correlation to causation. like what danvet just mentioned: daniels is right in that that's not really a good sample
+[16:00:28] <daniels> right now we’re in a weird position of being responsible to/for GSt but pushing them far enough away they do their own everything. ditto PipeWire, NM, etc. I don’t see how the arbitrary division helps any of us.
+[16:00:45] <Lyude> we don't actually know what the reception is, we know what the reception was from the people who voted - which begs the question who voted and in which portions of the community, and why
+[16:01:12] <danvet> daniels, I did ping them all on domain names, and maybe that was the wrong thing, but didn't get any vibes they'd want to join
+[16:01:25] <danvet> but yeah I guess we can kick this off
+[16:01:33] <daniels> I mean, has anyone here other than me (as an admin primarily) and mfilion (working closely with the media people) actually ever spoken to GSt/PW/etc?
+[16:01:41] <danvet> and the discussion back was more with our net
+[16:02:03] <Lyude> daniels: yeah, that's definitely a good point
+[16:02:07] <daniels> danvet: why would Wim hand over to an org which explicitly disclaims responsibility for PW?
+[16:02:10] <daniels> I wouldn’t
+[16:02:13] <anholt> daniels: yeah, I haven't talked to gstreamer since back when I was trying to do gstreamer gl work.
+[16:02:43] <daniels> anholt: my condolences. it’s still that bad. but I would like to fix that in part by building more bridges :)
+[16:03:20] <Lyude> I feel like these are things we should start surveying communities (explicitly so) that we serve
+[16:03:26] <daniels> ++
+[16:03:28] <alyssa> ^^
+[16:03:32] <danvet> yeah that sounds solid
+[16:03:54] <Lyude> does anyone want to take this up by the way?
+[16:04:03] <danvet> daniels, I figured at least someone would bring that up, but got nothing
+[16:04:11] <danvet> but then mail isn't all that great for this stuff
+[16:04:16] <alyssa> "responsible to/for GSt but pushing them far enough away" <--- IMO this is the most persuasive point in favour of expansion
+[16:04:47] <Lyude> I think that's why we need to look at talking to community leaders in spots like pipewire, gst, etc. because at the very least I'd expect them to have a general idea of how their communities feel
+[16:05:10] <daniels> danvet: I’m also in favour of not-email/IRC because it’s good for procedural things but bad for wider-ranging open discussion
+[16:05:13] <tlwoerner> does WINE fall under the fd.o umbrella
+[16:05:25] <daniels> and the discussion we need to have with them is not point-by-point
+[16:05:29] <daniels> tlwoerner: no
+[16:05:45] <tlwoerner> co-locating events with members would be a good start, or at least speaking at their events
+[16:05:55] <tlwoerner> ironic that XDC is co-located with a non-fd.o org?
+[16:06:07] <Lyude> Something else to think about too: while I'm not concerned about the election results, I think in retrospect: things like keeping around are definitely going to require active effort, which means we need to be ahead of the curb in terms of keeping relevant as opposed to being strictly reactive
+[16:06:16] <danvet> daniels, yeah I guess kicking off the old "should stuff fd.o hosts also have membership rights" thing might be good
+[16:06:19] <daniels> Lyude: I can provide all the contacts and intros on demand
+[16:06:30] <danvet> since things changed a lot with the huge amount of infra we provide now
+[16:07:02] <Lyude> I do think membership rights likely should be a given to some extent, btw
+[16:08:16] <Lyude> anyway - rg3igalia, mfilion, alyssa - would any of y'all be up to starting these discussions?
+[16:09:44] <mfilion> I'll discuss this further with @daniels and see who we need to speak too, but sure happy to bring it up with the gst & pw people, already know most of them
+[16:09:55] <alyssa> Lyude: I don't feel I have the relevant skills/connections/etc
+[16:10:09] <alyssa> mfilion: seems eager though?
+[16:10:17] <rg3igalia> same here, glad mfilion spoke up :)
+[16:10:39] <Lyude> alyssa: fwiw, it's easier then it looks :) (also I was kind of expecting someone would provide the connections here anyway), I'm fine with whoever wants to do it. Just want to make sure I'm not overvolunteering mfilion
+[16:10:47] <Lyude> (delegation is important)
+[16:12:08] <mfilion> so what's left on the discussion list today?
+[16:12:46] <Lyude> mfilion: that was it (I think we may have forgotten to finish the vote on the election rules though), I wanted to have your item last so we'd get the most time to talk about it
+[16:13:33] <daniels> mfilion: you want more? haha
+[16:14:38] <mfilion> @daniels lol still don't have a consensus here about these meetings & IRC. but we can discuss that again in two weeks.
+[16:14:57] <Lyude> yeah - there's a lot to go over here still, and I'll make sure that's on the agenda
+[16:15:47] <Lyude> anyway, thanks for the meeting everyone!
+[16:16:21] <danvet> mfilion, if you want to move the irc thing, imo this isn't the place
+[16:16:38] <danvet> instead figure out options (including how to bridge them to irc or I think it'll be impossible to sell)
+[16:16:48] <mfilion> to sell to who?
+[16:16:50] <hwentlan____> as an interested party that's no longer on the board I appreciate that the board meetings are public (though I'm not set on IRC per se). I guess tlwoerner and daniels would agree
+[16:16:54] <danvet> kick of discussion with our communities, set up a server, get people moving
+[16:16:56] <mfilion> GNOME stopped using IRC 10 years ago this year. we're clearly overdue. and it's not the transcripts that count but the minutes. which is what you already note anyway Lyude.
+[16:16:57] <danvet> and I'll move with them
+[16:17:12] <danvet> but moving the board is imo completely pointless
+[16:17:16] <danvet> *the board only
+[16:17:19] <mfilion> our communities can stay on irc
+[16:17:31] <mfilion> but these meetings staying here is dumb
+[16:17:42] <danvet> why?
+[16:17:52] <alyssa> oh, tangent question re: including gstreamer and pipewire -- would the media subsystem of the kernel also want to move? what about the audio subsystem?
+[16:18:05] <alyssa> given that DRM is here
+[16:18:21] <danvet> alyssa, I had some chats whether they would want to move to fd.o
+[16:18:29] <danvet> and they had reservations
+[16:18:38] <alyssa> and not the DMA kind? :-p
+[16:18:47] <danvet> dma?
+[16:18:57] <alyssa> dma reservations :-p
+[16:18:59] <mfilion> danvet I don't know any other foundation that relies on irc in 2022 for their board meetings. every time I mention to people that we're still on irc, their jaw just drops to the floor.
+[16:19:02] <rg3igalia> we could also go step by step, maybe they would be easier to convince if pipewire and gstreamer are already in
+[16:20:42] <Lyude> i think more convincing arguments might have reasoning as to why, since I assume people's preference for IRC has to do with it being easy for us. i also think that members should at least get asked how they feel about this since it does affect their ability to see transcripts as we mentioned before
+[16:21:22] <Lyude> I do see some value in having meetings on something else btw: although some of that stems from the discussion I feel is going to come at some point soon around us just onsidering something other then IRC in general
+[16:21:52] <danvet> mfilion, if you're thinking voice or so that would seriously suck
+[16:22:00] <danvet> since then I'd actually have to be here all the time
+[16:22:18] <danvet> anything text is much easier for these
+[16:22:24] <Lyude> i think we can reschedule meetings too, I mean we usually update the schedule every so often depending on what timezone the moast board members are in now
+[16:22:33] <daniels> hwentlan____: obviously minutes are completely essential - I don’t think we get any non-member participation other than me & tlwoerner tbf
+[16:22:46] <daniels> so I don’t think we can say that IRC helps that
+[16:23:12] <daniels> danvet: being present is arguably a feature …
+[16:23:15] <anholt> danvet: ok, I think I've flushed my treasurer queue.
+[16:24:03] <mfilion> lol danvet what's the point if you can't be bothered to be fully present once every two weeks? and most of the time, our meetings last 30 minutes...
+[16:24:09] <Lyude> fwiw too - it's not like I wasn't able to do minutes at all with video meetings
+[16:24:38] <mfilion> exactly, you do a great job at taking notes Lyude
+[16:24:53] <danvet> <- anholt should that read Khronos or copypasta mistake?
+[16:25:05] <Lyude> mfilion: when you have an organization that's mostly run by developers then the amount of time those poeple have to spend on the organization is limited - and it kind of needs to stay that way because otherwise it's more difficult to find volunteers since most people can't put in more time
+[16:25:06] <mfilion> danvet what you just said about being present sums up why people aren't renewing and aren't voting. they can't be bothered.
+[16:25:33] <danvet> mfilion, dude I pulled in like 200k while "not being present"
+[16:26:05] <danvet> or maybe it's only 150k dunno, I'm "not present enough" I guess
+[16:26:48] <Lyude> also, I think the value of the meetings is really dependent on if we're not getting things done. if we're getting things done, then what is the purpose of moving the meeting elsewhere? if we're not getting things done, which things? these are actual questions btw
+[16:26:55] <danvet> there's occasionally a quicke in the oven or some other shit to do
+[16:26:59] <danvet> and text allows me to take care of that
+[16:27:09] <danvet> voice would be like "why am I bothering with this" frankly
+[16:29:02] <Lyude> hm.
+[16:29:27] <anholt> we do waste some time here being async when we could probably wrap a meeting in a bit less time. but, also, it's pretty great for me to be able to catch up to the meeting if I show up late. I'm in favor of text for this.
+[16:29:46] <Lyude> we need video meetings sometimes because of the benefits of long form discussion especially when it comes to topics like this one, but we want IRC meetings because most of the time the things we're dealing with don't require long form discussions.
+[16:29:52] <Lyude> *shrugs*
+[16:29:55] <Lyude> why not both
+[16:30:28] <Lyude> we could have IRC meetings as regularly scheduled, and have monthly or bi monthly video meetings or whatever kind of schedule we deem needed
+[16:30:31] * anholt heads out
+[16:30:35] <Lyude> see ya!
+[16:30:40] * alyssa as well
+[16:31:01] <danvet> Lyude, we had one per year, and aside from electing a few officers those tended to be about as much as these here
+[16:31:08] <danvet> at xdc
+[16:31:36] * rg3igalia also has to leave, thanks everyone!
+[16:32:08] <Lyude> danvet: yeah
+[16:32:31] <Lyude> i guess just thinking about this it really comes down to needs and why we're doing this. like, mfilion, do you know what gnome's stated reasoning for moving their meetings from IRC was?
+[16:32:32] <danvet> and at least in the past all substantial long form stuff was xdc hallway track or long mail threads
+[16:32:58] <danvet> also personally I absolutely suck at discussions in big meetings without serious prep work and material
+[16:33:05] <mfilion> Not sure Lyude, I could reach out and ask.
+[16:33:07] <Lyude> (also btw, the meeting is over but I'm happy to continue discussing this and probably will)
+[16:33:29] <danvet> mail forces people to provide that material so I can ponder it upfront and then type a reply
+[16:33:52] <Lyude> danvet: yeah I'm not great at verbal discussion either
+[16:34:18] <danvet> 1:1 is ok, but anything else I routinely tell people I wont show here at intel until they deliver the material upfront
+[16:34:43] <danvet> "we'll explain in the meeting" "yeah and I won't be able to parse it fast enough and think it through"
+[16:34:52] <danvet> so yeah, not a fan in the least
+[16:34:59] <Lyude> it's also worth noting for some folks that can be an actual barrier to being able to participate in meetings
+[16:35:21] <mfilion> I'm not going to push if everyone is against it.
+[16:35:30] <danvet> we should have more hallway track for this stuff, that's at least for me been dearly missing past 2.5 years
+[16:35:34] <Lyude> mfilion: fwiw I think it's really good you're bringing up all this stuff
+[16:35:41] <danvet> and I guess it starts to show :-(
+[16:35:55] <mfilion> I just think if we want to grow, we need to look at what other foundations are doing
+[16:37:16] <Lyude> mfilion: imho: it's more about keeping the org around, healthy and sustainable. I think growth is nice if it happens, but if it's needed and we're doing things to keep relevant it'll likely happen as we need it. keep in mind, "things to keep relevant" being getting a new website, looking into better representation for various projects under our umbrella, etc.
+[16:37:59] <Lyude> and definitely making sure we don't only keep member counts, but have an influx of new members
+[16:38:21] <Lyude> one situation I've thought about for a long time that I want to make sure we don't run into is a mass exodus of people retiring in a decade or two and causing the community to fall apart
+[16:38:55] <Lyude> I think we've been doing a good job of that, but it's definitely important we stay on top of things to keep it that way
+[16:39:04] <mfilion> right that's where the rebrand discussion comes in, why we need to expand to remain relevant
+[16:39:21] <Lyude> mhm, realizing I think we may have had slightly different definitions of expand and grow
+[16:41:02] <Lyude> if by expand you mean in terms of communities we have under our umbrella, then yeah i can't agree with that more
+[16:41:12] <mfilion> the name is just a legacy thing now, and weighs on how people perceive us. I mean, just look at our gsoc projects, not one has to do with X.
+[16:44:13] <Lyude> mhm.
+[16:45:35] <Lyude> mfilion: I actually have to start getting to work on other stuff as well, I guess we can continue next week when you've got some more input from various communities?
+[16:46:48] <daniels> re meeting format, async things by definition don’t require everyone to be present at a certain time
+[16:47:35] <Lyude> sorry, next meeting week
+[16:47:55] <daniels> so if async is a feature then it can be in issues with reminders/dates/etc - and keep the sync for less formulaic/procedural/ack-only so you can use the valuable time for more valuable things
+[16:49:48] <daniels> Lyude: btw when fd.o and X.Org merged, a GNOME board-to-board was proposed to share experiences - they were keen but we didn’t follow through on it - would be worth the session though I think
+[16:50:43] <Lyude> yeah definitely
+[17:12:29] <danvet> yeah we were a bit distracted with a sudden hole in the bank and a lot of that fell through cracks :-(
+[17:17:45] <daniels> danvet: yeah … I remember that :\
+[17:18:17] <daniels> but that’s another argument for having an organisation not necessarily comprised entirely of full-time developers tbh
+[17:20:07] <danvet> Lyude, we forgot the khronos topic
+[17:20:13] <danvet> which isn't great :-(
+[17:20:37] <danvet> instead of philosophical blattering we should have done our jobs at least ...
+[17:23:14] <mfilion> danvet what's needed? can we do via email?
+[17:25:03] <danvet> yeah I typed one up
+[17:25:43] <danvet> mfilion, Lyude anholt mdnavare rg3igalia see board@
+[17:25:49] <danvet> alyssa seems gone already
+[17:41:21] [disconnected at Thu Apr 28 17:41:21 2022]
diff --git a/BoardOfDirectors/IrcLogs/2022/05-12.mdwn b/BoardOfDirectors/IrcLogs/2022/05-12.mdwn
new file mode 100644
index 00000000..9143aca8
--- /dev/null
+++ b/BoardOfDirectors/IrcLogs/2022/05-12.mdwn
@@ -0,0 +1,132 @@
+[[!format txt """
+[14:59:27] [connected at Thu May 12 14:59:27 2022]
+[14:59:27] [I have joined #xf-bod]
+[14:59:39] <tlwoerner> hello
+[15:00:10] <alyssa> Hello! :)
+[15:00:33] <Lyude> Hi! Time for rolecall ( alyssa, danvet, mfilion, rg3igalia, mdnavare ) (the other two directors are absent, jfyi)
+[15:00:48] <rg3igalia> hi!
+[15:00:51] * danvet somewhat here-ish
+[15:01:50] <Lyude> Cool! We should have enough people :), agenda for today:
+[15:03:28] <Lyude> XDC2023, XDC2022, GSoC/Outreachy/EVoC, MIPI alliance and CSI, and SPI replacement
+[15:04:13] <Lyude> Oh- krhonos adopters agreement for opencl I think should also be on the agenda according to
+[15:04:43] <alyssa> is there anything to discuss for opencl?
+[15:04:44] <tlwoerner> were we going to discuss a possible time change (not that i'm giving any opinion either way)
+[15:04:47] <alyssa> thought we're waiting on khronos
+[15:05:07] <Lyude> For MIPI alliance and CSI: No progress from my end but we had someone from the fdo community poke us and ask if we'd be interested in them getting us some contacts to try.
+[15:05:32] <Lyude> alyssa: ah you're right, take the opencl off then
+[15:05:39] <Lyude> tlwoerner: yeah I thought I was missing something
+[15:06:38] <Lyude> Although I wonder if we should do the time change over email to make sure everyone gets a chance to give their opinion. I guess we can start it here and finish it off on email for anholt
+[15:07:26] <Lyude> So on the SPI replacement: didn't actually get the time to start this but will be doing so asap now that elections are over
+[15:07:36] <alyssa> \o/
+[15:08:02] <Lyude> XDC2022/XDC2023: no real updates other than I sent out the CFP, however I'm a bit concerned that I haven't seen any kind of talks come through yet since posting the CFP. Is that normal this early on?
+[15:08:42] <alyssa> I wager "first in-person conf since the pandemic for a lot of us" is a part of that?
+[15:08:56] <rg3igalia> I suppose so, it's probably too early to send reminders also
+[15:09:08] <tlwoerner> proposals only come in a day or two before/after closing
+[15:09:48] <Lyude> ahh, as long as it's normal then I'm fine with it :). I just wanted to make sure the email didn't somehow miss mailing lists or something like that
+[15:10:03] * alyssa is still in denial that there's an in-person XDC
+[15:11:16] <Lyude> Alright, wow we have a short agenda today. I guess tlwoerner you can go over GSoC stuff?
+[15:11:32] <tlwoerner> today is slot request day, i've got our 4 proposals ranked and ready to go
+[15:11:39] <tlwoerner> we'll find out on May 20th
+[15:11:44] <mdnavare> Hi All, sorry for joining late
+[15:11:46] <tlwoerner> perhaps we could run any slots we don't get as EVoC?
+[15:11:51] <tlwoerner> (that's all)
+[15:11:54] <mfilion> o/
+[15:12:10] <Lyude> tlwoerner: if the mentors we've got would be willing to help run such a program I'd be alright with that!
+[15:12:28] <rg3igalia> +1
+[15:12:30] <tlwoerner> sounds good
+[15:12:44] <alyssa> I thought we weren't doing EVoC this year? i'm confused
+[15:13:01] <Lyude> alyssa: only because of a lack of volunteers
+[15:13:09] <Lyude> but if that's not an issue I see no problem
+[15:13:13] <alyssa> right, okay
+[15:14:14] <Lyude> Alright - so one thing I did forget to add real quick:
+[15:14:49] <Lyude> one more sponsor since the last sponsor update we had. that's pretty much all on that
+[15:16:13] <Lyude> So that just leaves the timechange: I guess a good question is what timezone is everyone actually in? I'm in EST, iirc mdnavare is PDT, not sure what everyone else is
+[15:16:26] <alyssa> EST
+[15:16:32] * anholt_ here now
+[15:16:34] <alyssa> that's America/Toronto, not America/New_York ;p
+[15:16:46] <anholt_> pdt
+[15:16:52] <tlwoerner> alyssa: you mean EDT
+[15:16:54] <mdnavare> Yup I am in PDT
+[15:17:00] <alyssa> tlwoerner: err yes I do. can never remember which is which
+[15:17:05] <alyssa> thanks
+[15:17:18] <rg3igalia> Europe/Madrid, the current time is a bit atrocious for me
+[15:17:38] <Lyude> danvet, mfilion if you are here: what timezone are you two in?
+[15:17:49] <Lyude> Also I know samuelig is in rg3igalia's timezone iirc
+[15:17:54] <rg3igalia> yes, he is
+[15:18:16] <tlwoerner> i assume danvet is in CEST?
+[15:18:20] <danvet> yup
+[15:18:26] <danvet> also not really here :-(
+[15:19:08] <tlwoerner> mfillion is in Montréal? so that's EDT as well
+[15:19:17] <Lyude> hm, I guess then the bigger question is whether folks in EDT-PDT would be ok with the meeting getting made earlier
+[15:19:44] <alyssa> Lyude: Any time during regular work hours is good for me
+[15:20:09] <Lyude> I could likely do 11-12 but in that case we might need to move the meeting to a different day of the week
+[15:20:25] <Lyude> which probably isn't too big of a deal tbh
+[15:22:05] <rg3igalia> any time earlier than now is good for me, and the only other fixed meeting I have during the week is on Thursdays 7:30am-8:30am Pacific Daylight Time
+[15:22:09] <Lyude> So like - would wed at like 11-12 AM EDT - ~5-6 PM
+[15:22:16] <Lyude> work?
+[15:22:23] <Lyude> sorry-~5-6 PM CEST
+[15:22:37] <tlwoerner>,12,8&h=5&hf=1
+[15:22:57] <Lyude> ah yes, my good buddy world time buddy
+[15:23:40] <rg3igalia> works very well for me
+[15:23:56] <anholt_> I wouldn't be available at that time, I'm getting the kid to school.
+[15:24:09] <mdnavare> Lyude: Usually mornings till 10 am PDT are a lot fo wrk meetings since colleagues in India time and Europe time zone
+[15:24:45] <Lyude> anholt_: is that all week or just certain days of the week?
+[15:24:53] <anholt_> all week, unfortunately.
+[15:25:15] <tlwoerner> what about 1 hour earlier than the current?
+[15:25:15] <mfilion> lyude - same timezone as alyssa, EDT
+[15:26:04] <Lyude> anholt_: if it was at 12 would you be able to make it? Because I think that just leaves us 12PM and 1PM
+[15:26:17] <anholt_> that works for me
+[15:26:22] <Lyude> (assume I'm saying my times in EDT, jfyi)
+[15:26:51] <Lyude> Alright, 12AM EDT on wednesdays then
+[15:27:11] <tlwoerner> 12am??
+[15:27:18] <Lyude> *pm, sorry lol
+[15:27:22] <tlwoerner> lol
+[15:27:22] <Lyude> AM/PM always gets me confused
+[15:27:50] <danvet> is that 3h earlier than now?
+[15:27:54] <alyssa> danvet: yeah
+[15:28:01] <tlwoerner> noon for mfilion alyssa tlwoerner
+[15:28:05] <danvet> +1
+[15:28:10] <rg3igalia> would it be possible to keep it on thursdays at that time?
+[15:28:30] <rg3igalia> or does wednesday work better for everyone?
+[15:28:45] * danvet doesn't care either way
+[15:29:00] <Lyude> rg3igalia: unfortunately 11AM-~12PM is when I've got meetings on thursdays, and meeting with my boss biweekly before that. so if we could do a different day that'd probably be preferable, but I can make thursday work if needed
+[15:29:48] <Lyude> can do p much any other day of the week as well
+[15:30:24] <rg3igalia> no problem, my attendance may be spotty a few times before summer but it should be ok after that
+[15:30:43] <Lyude> that's np, wed it is then
+[15:31:24] <Lyude> mfilion, mdnavare does that work for y'all?
+[15:31:40] <danvet> Lyude, btw edt or in cet like we have now for tz fun?
+[15:32:18] <Lyude> danvet: 12PM my time, 6PM yours
+[15:32:32] <danvet> Lyude, I mean do we fix this into edt or cet
+[15:32:37] <tlwoerner> danvet: it *was* switching with Europe before, so let's switch it with NA this time :-D
+[15:32:44] <tlwoerner> haha
+[15:32:47] <danvet> i.e. will it move relative to cet when you switch from summer to winter time
+[15:32:57] <danvet> tlwoerner, atm it's cet fixed
+[15:33:03] <danvet> and before that it was pdt iirc
+[15:33:09] <danvet> I don't think we ever had it aligned with europe tz
+[15:33:40] <mdnavare> Lyude: Yes 9am PST Wed then? Every 3 weeks, I have a meeting at that time, but otherwise its hould work
+[15:33:42] <Lyude> oh, I was probably going to keep it UTC
+[15:33:44] <danvet> oh also sorry I meant UTZ fixed
+[15:33:50] * danvet not working
+[15:33:53] <danvet> *UTC
+[15:34:00] <tlwoerner> yes, we could set it to UTC
+[15:34:24] <danvet> I mean they all suck somewhat, but UTC seems to have resulted in least amount of "uh I missed the meeting by 1h" twice a year
+[15:34:37] <Lyude> mhm, plus in a year the US won't even have DST
+[15:35:18] <alyssa> ooh
+[15:35:26] <Lyude> anyway, seems like we've got a new time :). so that's the end of the meeting everyone, thanks for coming!
+[15:35:29] <tlwoerner>,12,8,100&h=5&hf=1
+[15:35:57] <danvet> so is it edt or utc fixed now?
+[15:36:05] <danvet> I need to adjust my calendar entry correctly :-)
+[15:36:06] <tlwoerner> i'll believe it when i see it, regardless canada will very likely follow the US
+[15:36:30] <alyssa> tlwoerner: IIRC Ontario voted to change when New York and Quebec change, here's hoping :p
+[15:36:53] <Lyude> danvet: is there an unfixed UTC?
+[15:37:04] <danvet> well utc is always fixed
+[15:37:21] <Lyude> ahhhh ok yeah, it's fixed UTC then (we also have a google calendar event for this iirc with the corret timezone)
+[15:37:31] <danvet> and europe/us can't agree when to do dst switching, so those are lolz
+[15:37:45] <danvet> Lyude, oh right do you know how to update that one?
+[15:38:00] <Lyude> I believe so, iirc I've done it in the past to cancel meetings on holidays
+[15:54:41] <mfilion> sorry lost track of the conversation - so what's the new time?
+[15:55:13] <mfilion> 3 hrs earlier than previously?
+[15:55:48] <Lyude> nah we went all in, 10 hours later. (yes-it is 3 hours earlier, and now on wednesday)
+[16:08:13] <mfilion> ha ok cool
+[16:43:03] [disconnected at Thu May 12 16:43:03 2022]
diff --git a/BoardOfDirectors/MeetingSummaries/2021.mdwn b/BoardOfDirectors/MeetingSummaries/2021.mdwn
index 1925fc46..1b53425e 100644
--- a/BoardOfDirectors/MeetingSummaries/2021.mdwn
+++ b/BoardOfDirectors/MeetingSummaries/2021.mdwn
@@ -20,3 +20,4 @@
* [[Oct. 14|BoardOfDirectors/MeetingSummaries/2021/10-14]]
* [[Oct. 28|BoardOfDirectors/MeetingSummaries/2021/10-28]]
* [[Nov. 11|BoardOfDirectors/MeetingSummaries/2021/11-11]]
+* [[Dec. 09|BoardOfDirectors/MeetingSummaries/2021/12-09]]
diff --git a/BoardOfDirectors/MeetingSummaries/2021/12-09.mdwn b/BoardOfDirectors/MeetingSummaries/2021/12-09.mdwn
new file mode 100644
index 00000000..536a6711
--- /dev/null
+++ b/BoardOfDirectors/MeetingSummaries/2021/12-09.mdwn
@@ -0,0 +1,70 @@
+Summary of the 09 December 2021 meeting of the [[X.Org Foundation|XorgFoundation]] [[Board of Directors|BoardOfDirectors]]
+Full IRC meeting logs are posted at [[BoardOfDirectors/IrcLogs/]]
+## Attendees
+Daniel Vetter (ish),
+Samuel Iglesias Gonsálvez,
+Lyude Paul,
+Emma Anholt,
+Harry Wentland,
+Manasi Navare,
+Keith Packard,
+Mark Filion,
+## Summary
+Agenda: Treasurer's report for 2020, XDC2021 invoices status, XDC2022, domain status, GSoC/Outreachy/EVoC, MIPI Alliance and CSI,
+donation to Asahi Linux
+## Items discussed
+[[!format txt """
+ITEM: XDC2020 treasurer's report
+Emma wrote up a draft for the 2020 treasurer's report
+STATUS: Pending
+ITEM: XDC2021 invoices status
+Only one sponsor awaiting being invoiced now
+STATUS: Pending
+ITEM: XDC2022
+No updates on XDC2022. Samuel will be stepping down from being the sole
+organizer for XDC next year, but may be at least partially involved when time
+STATUS: Pending
+ITEM: GSoC/Outreachy/EVoC
+No updates
+STATUS: Pending
+ITEM: domain status
+2x domain transfer from keithp is stuck, danvet told emersion to drop until
+keithp figured it out. 3x domains confirmed owner/contact info and they're
+happy with the current situation. That leaves 2x other domains to figure out
+the owner of, and then of course
+STATUS: Pending
+ITEM: MIPI Alliance and CSI
+No updates
+ACTIONS: Lyude to poke partners again
+STATUS: Pending
+ITEM: Donation to Asahi Linux
+The organizers for XDC2021 asked that instead of us rewarding them with dinner
+that we instead make a donation to Asahi Linux. Board voted to approve this, and
+voted to make the donation amount $200.
+ACTIONS: Emma will contact SPI about getting them to pay for this
diff --git a/BoardOfDirectors/MeetingSummaries/2022.mdwn b/BoardOfDirectors/MeetingSummaries/2022.mdwn
new file mode 100644
index 00000000..6400d550
--- /dev/null
+++ b/BoardOfDirectors/MeetingSummaries/2022.mdwn
@@ -0,0 +1,8 @@
+* [[Jan. 20|BoardOfDirectors/MeetingSummaries/2022/01-20]]
+* [[Feb. 03|BoardOfDirectors/MeetingSummaries/2022/02-03]]
+* [[Feb. 17|BoardOfDirectors/MeetingSummaries/2022/02-17]]
+* [[Mar. 03|BoardOfDirectors/MeetingSummaries/2022/03-03]]
+* [[Mar. 17|BoardOfDirectors/MeetingSummaries/2022/03-17]]
+* [[Mar. 31|BoardOfDirectors/MeetingSummaries/2022/03-31]]
+* [[Apr. 28|BoardOfDirectors/MeetingSummaries/2022/04-28]]
+* [[May. 12|BoardOfDirectors/MeetingSummaries/2022/05-12]]
diff --git a/BoardOfDirectors/MeetingSummaries/2022/01-20.mdwn b/BoardOfDirectors/MeetingSummaries/2022/01-20.mdwn
new file mode 100644
index 00000000..c4d451c0
--- /dev/null
+++ b/BoardOfDirectors/MeetingSummaries/2022/01-20.mdwn
@@ -0,0 +1,67 @@
+Summary of the 20 January 2022 meeting of the [[X.Org Foundation|XorgFoundation]] [[Board of Directors|BoardOfDirectors]]
+Full IRC meeting logs are posted at [[BoardOfDirectors/IrcLogs/]]
+## Attendees
+Daniel Vetter,
+Samuel Iglesias Gonsálvez,
+Lyude Paul,
+Mark Filion,
+Keith Packard,
+Emma Anholt,
+Harry Wentland,
+Manasi Navare,
+## Summary
+Agenda: domain status, XDC2022, GSoC/Outreachy/EVoC, MIPI Alliance and CSI, Election Season, treasurer report for 2021 and SPI
+## Items discussed
+[[!format txt """
+ITEM: domain status
+No updates yet
+STATUS: Pending
+ITEM: XDC2022
+No updates
+STATUS: Pending
+ITEM: GSoC/Outreachy/EVoC
+GSoC recently changed their program guidelines in order to make things more
+flexible and allow for projects with longer timelines - so it would be a good
+time for us to consider getting involved with GSoC again. Because of the issues
+with finding volunteers, there's been some discussion regarding simply making
+it a board responsibility. We'll figure out details post-election.
+STATUS: Pending
+ITEM: MIPI Alliance and CSI
+No updates yet
+ACTIONS: Lyude to poke partners again
+STATUS: Pending
+ITEM: Election season
+Elections are coming up soon, and the people who currently aren't up for
+re-election are Lyude, Manasi and Daniel. Currently Lyude and Daniel have
+volunteered to help run the election.
+STATUS: Pending
+ITEM: Treasurer report for 2021 and SPI
+Currently because of continued issues with getting SPI to be responsive, which
+came up while discussing the treasurer report for last year (which is currently
+delayed as a result of this), the board is considering alternative organizations
+to propose joining. We'll likely be targeting the election after this one (so,
+next year) for this to provide members with a chance to vote on such a decision.
+ACTIONS: Lyude to start poking around with alternative organizations
+STATUS: Pending
diff --git a/BoardOfDirectors/MeetingSummaries/2022/02-03.mdwn b/BoardOfDirectors/MeetingSummaries/2022/02-03.mdwn
new file mode 100644
index 00000000..8d2772f4
--- /dev/null
+++ b/BoardOfDirectors/MeetingSummaries/2022/02-03.mdwn
@@ -0,0 +1,76 @@
+Summary of the 03 February 2022 meeting of the [[X.Org Foundation|XorgFoundation]] [[Board of Directors|BoardOfDirectors]]
+Full IRC meeting logs are posted at [[BoardOfDirectors/IrcLogs/]]
+## Attendees
+Daniel Vetter,
+Lyude Paul,
+Manasi Navare,
+Mark Filion,
+Keith Packard,
+Harry Wentland,
+Samuel Iglesias Gonsálvez,
+Emma Anholt,
+## Summary
+Agenda: domain status, XDC2022, XDC2023,
+GSoC/Outreachy/EVoC, MIPI Alliance and CSI, searching for new parent
+organization, elections + election schedule
+## Items discussed
+[[!format txt """
+ITEM: domain status
+Daniel sent some emails around for and, no replies
+quite yet. Will be looking into
+STATUS: Pending
+ITEM: XDC2022
+Samuel will be pinging organizers to start working on the website to have it on
+time for opening the CfP.
+ACTIONS: Pinging
+STATUS: Pending
+ITEM: XDC2023
+Samuel will soon be starting to nag European companies about organizing
+XDC2023. The idea is the same as last year: give them enough time for internal
+discussions, so at the same time that RFP is open we know if there is anyone
+really interested in submitting a proposal.
+STATUS: Pending
+ITEM: GSoC/Outreachy/EVoC
+No updates
+STATUS: Pending
+ITEM: MIPI Alliance and CSI
+No updates from Lyude
+ACTIONS: Lyude to make time to poke partners if they're still interested in
+STATUS: Pending
+ITEM: Treasurer report for 2021
+No updates
+ACTIONS: Emma to continue waiting for SPI
+STATUS: Pending
+ITEM: Searching for new parent organizations
+Lyude hasn't had a chance to get started with this quite yet.
+ACTIONS: Lyude to make time to poke organizations
+STATUS: Pending
+ITEM: Elections + election schedule
+Elections mailing list and membership website have permissions setup, and Daniel
+just updated the wiki with the details on the new election along with the
+election schedule.
+ACTIONS: Lyude will be sending out a membership reminder and election
+announcement sometime today.
diff --git a/BoardOfDirectors/MeetingSummaries/2022/02-17.mdwn b/BoardOfDirectors/MeetingSummaries/2022/02-17.mdwn
new file mode 100644
index 00000000..853c02af
--- /dev/null
+++ b/BoardOfDirectors/MeetingSummaries/2022/02-17.mdwn
@@ -0,0 +1,66 @@
+Summary of the 17 February 2022 meeting of the [[X.Org Foundation|XorgFoundation]] [[Board of Directors|BoardOfDirectors]]
+Full IRC meeting logs are posted at [[BoardOfDirectors/IrcLogs/]]
+## Attendees
+Daniel Vetter,
+Lyude Paul,
+Manasi Navare,
+Mark Filion,
+Emma Anholt,
+Harry Wentland,
+Trevor Woerner
+Samuel Iglesias Gonsálvez,
+Keith Packard,
+## Summary
+Agenda: domain status, XDC2022, GSoC/Outreachy/EVoC, MIPI
+alliance and CSI, election season, treasurer report for 2021, finding new parent
+## Items discussed
+[[!format txt """
+ITEM: domain status
+Daniel vetter managed to wrangle down the rest of the remaining domains, and
+we've begun the process with
+ITEM: XDC2022
+Samuel was absent so no updates
+STATUS: Pending
+ITEM: GSoC/Outreachy/EVoC
+We managed to find a new GSoC admin, and have also found GSoC mentors! Thanks to
+Rodrigo, Melissa and Daniel!
+ACTIONS: Admin to fill out paper work for to participate in GSoC
+STATUS: Pending
+ITEM: MIPI alliance and CSI
+No updates, Lyude had to take some unexpected time off work
+STATUS: Pending
+ITEM: Election season
+Nominations begin next week
+ACTIONS: Lyude and Mark filion to send out membership renewal reminders
+STATUS: Pending
+ITEM: Treasurer report for 2021
+No updates from SPI on this yet
+ACTIONS: Anholt to continue waiting for SPI
+STATUS: Pending
+ITEM: Finding new parent foundation
+No updates on this yet due to Lyude being out last week
+ACTIONS: Lyude to poke around next time she gets a chance
+STATUS: Pending
diff --git a/BoardOfDirectors/MeetingSummaries/2022/03-03.mdwn b/BoardOfDirectors/MeetingSummaries/2022/03-03.mdwn
new file mode 100644
index 00000000..21b020a7
--- /dev/null
+++ b/BoardOfDirectors/MeetingSummaries/2022/03-03.mdwn
@@ -0,0 +1,77 @@
+Summary of the 03 March 2022 meeting of the [[X.Org Foundation|XorgFoundation]] [[Board of Directors|BoardOfDirectors]]
+Full IRC meeting logs are posted at [[BoardOfDirectors/IrcLogs/]]
+## Attendees
+Daniel Vetter,
+Samuel Iglesias Gonsálvez,
+Lyude Paul,
+Manasi Navare,
+Emma Anholt,
+Harry Wentland,
+Keith Packard,
+Trevor Woerner
+Mark Filion,
+## Summary
+Agenda: XDC2022, XDC2023, GSoC/Outreachy/EVoC, MIPI alliance, election
+season/extending nominations, treasurer report for 2021, new parent organization
+## Items discussed
+[[!format txt """
+ITEM: XDC2022
+Organizers started editing the website, and adapted the CFP text to include
+wineconf proposals. They are going to remove past year sponsors from the sponsor
+box but they plan to add the ones confirmed sponsorship soon. Organizers are
+looking into booking a good bunch of hotel rooms for the conference days and
+some days before and after. The idea is to have the majority (ideally all)
+attendees at the same hotel to increase hallway track and spontaneous
+activities. Note that locking the rooms in the hotel is not forever, and they
+will be available for normal booking at some point in September. The idea is
+that con attendees should be able to book rooms for a special price.
+STATUS: Pending
+ITEM: XDC2023
+No news here
+STATUS: Pending
+ITEM: GSoC/Outreachy/EVoC
+Trevor completed our application for GSoC and submitted it, and we'll know
+whether we've been accepted as an organization on March 7th. Also, they will be
+documenting the steps to do this for future admins.
+ACTIONS: Lyude to setup repo for Trevor to put documentation into.
+STATUS: Pending
+ITEM: MIPI Alliance
+No updates on this yet
+ACTIONS: Lyude to find the time to poke partners at work about this
+STATUS: Pending
+ITEM: Treasurer report for 2021
+We have draft 2021 data from SPI, so hopefully we will receive final books soon
+and Emma will then be able to put together the treasurer report.
+STATUS: Pending
+ITEM: New parent organization
+Lyude hasn't had the time to start looking into this yet, will likely start the
+process after elections.
+ACTIONS: Lyude to start lookng around after elections
+STATUS: Pending
+ITEM: Elections / extending nomination period
+Since we haven't received enough nominations for the election yet, we've voted
+to extend the election timeline by two weeks.
+ACTIONS: Lyude to update elections timeline on website, send out reminders +
+notice about change.
+STATUS: Pending
diff --git a/BoardOfDirectors/MeetingSummaries/2022/03-17.mdwn b/BoardOfDirectors/MeetingSummaries/2022/03-17.mdwn
new file mode 100644
index 00000000..7dadb385
--- /dev/null
+++ b/BoardOfDirectors/MeetingSummaries/2022/03-17.mdwn
@@ -0,0 +1,75 @@
+Summary of the 17 March 2022 meeting of the [[X.Org Foundation|XorgFoundation]] [[Board of Directors|BoardOfDirectors]]
+Full IRC meeting logs are posted at [[BoardOfDirectors/IrcLogs/]]
+## Attendees
+Daniel Vetter,
+Samuel Iglesias Gonsálvez,
+Lyude Paul,
+Manasi Navare,
+Mark Filion,
+Keith Packard,
+Emma Anholt,
+Trevor Woerner
+Harry Wentland,
+## Summary
+Agenda: MIPI Alliance and CSI, election season, treasurer report 2021, finding
+more sysadmins, new parent foundation, GSoC, XDC2022, XDC2022 sponsors
+## Items discussed
+[[!format txt """
+ITEM: MIPI Alliance and CSI
+No updates here
+ACTIONS: Lyude to find time to do this
+STATUS: Pending
+ITEM: New parent foundation
+No updates
+ACTIONS: Lyude to start search after elections
+STATUS: Pending
+ITEM: Finding more sysadmins
+While we're not in any immediate danger, there's definitely less time
+availability across our sysadmins in general. So we need to try to find
+additional volunteers to bring onto the team
+ACTIONS: Lyude to make announcements as needed about this after elections (to
+prevent us from putting too much noise on the related mailing lists)
+STATUS: Pending
+ITEM: XDC2022 sponsors
+Sponsor box on website is now ready
+STATUS: Pending
+ITEM: Treasurer report 2021
+At long last, we have 2021 data from SPI now
+ACTIONS: Emma to start coming up with treasurer report
+STATUS: Pending
+ITEM: XDC2022
+Samuelig Will be talking to organizers to prepare the CFP announcement for April
+STATUS: Pending
+Potential students start applying April 4th
+STATUS: Pending
+ITEM: Elections season
+We now have enough nominations to proceed with an election, so no need for
+timeline extension - the election can continue on schedule now. Candidates will
+be announced March 28th, member is March 31st and the current nomination period
+ends on March 20th.
+ACTIONS: Lyude to gather statements from current candidates
+STATUS: Pending
diff --git a/BoardOfDirectors/MeetingSummaries/2022/03-31.mdwn b/BoardOfDirectors/MeetingSummaries/2022/03-31.mdwn
new file mode 100644
index 00000000..e3abd1f9
--- /dev/null
+++ b/BoardOfDirectors/MeetingSummaries/2022/03-31.mdwn
@@ -0,0 +1,70 @@
+Summary of the 31 March 2022 meeting of the [[X.Org Foundation|XorgFoundation]] [[Board of Directors|BoardOfDirectors]]
+Full IRC meeting logs are posted at [[BoardOfDirectors/IrcLogs/]]
+## Attendees
+Daniel Vetter,
+Samuel Iglesias Gonsálvez,
+Lyude Paul,
+Manasi Navare,
+Mark Filion,
+Keith Packard,
+Harry Wentland,
+Trevor Woerner
+Emma Anholt,
+## Summary
+Agenda: XDC2022, GSoC/Outreachy/EVoC, MIPI Alliance and CSI, Election season,
+Treasurer Report for 2021, new parent organization, find more sysadmins
+## Items discussed
+[[!format txt """
+ITEM: XDC2022
+Contacted organizers to prepare the CFP. They are going to do a separate
+announcement for XDC and WineConf, but they will mention each other in the
+respective ones.
+ACTIONS: Samuel plans to send announcement next week
+STATUS: Pending
+ITEM: GSoC/Outreachy/EVoC
+Trevor was absent, so skipped. However, we did talk about advertising our
+involvement with GSoC more on's twitter.
+STATUS: Pending
+ITEM: MIPI Alliance and CSI
+No updates from Lyude's side
+ACTIONS: Lyude to try to find time for doing more poking in the near future
+STATUS: Pending
+ITEM: Election season
+Things are going well - we have a decent number of members registered now, and
+will be closing membership renewals on Friday. We ended up getting a total of 6
+candidates to run in this election.
+STATUS: Pending Done
+ITEM: Treasurer report for 2021
+Emma was absent, so skipped for this meeting
+STATUS: Pending Done
+ITEM: New parent organization
+No updates here
+ACTIONS: Lyude to start doing some poking after elections
+STATUS: Pending
+ITEM: Find more sysadmins could use more sysadmins! If you're interested, please contact
+the board via board AT foundation dot x dot org
+STATUS: Pending
diff --git a/BoardOfDirectors/MeetingSummaries/2022/04-28.mdwn b/BoardOfDirectors/MeetingSummaries/2022/04-28.mdwn
new file mode 100644
index 00000000..71f8321a
--- /dev/null
+++ b/BoardOfDirectors/MeetingSummaries/2022/04-28.mdwn
@@ -0,0 +1,118 @@
+Summary of the 28 April 2022 meeting of the [[X.Org Foundation|XorgFoundation]] [[Board of Directors|BoardOfDirectors]]
+Full IRC meeting logs are posted at [[BoardOfDirectors/IrcLogs/]]
+This was an eventful meeting, so there's a few more notes here then usual.
+## Attendees
+Daniel Vetter,
+Lyude Paul,
+Mark Filion,
+Emma Anholt,
+Alyssa Rosenzweig,
+Ricardo Garcia
+Trevor Woerner
+Daniel Stone
+Manasi Navare,
+Samuel Iglesias Gonsálvez,
+## Summary
+Agenda: Elections, XDC2022/XDC2023, GSoC/Outreachy/EVoC, MIPI alliance and
+CSI, treasurer report for 2021, new parent organization, sysadmins, rebranding,
+meeting over IRC
+## Items discussed
+[[!format txt """
+ITEM: Elections
+Elections happened, and we now have two new board members: welcome Alyssa and
+STATUS: Pending
+ITEM: XDC2022/XDC2023
+Lyude currently taking over XDC duties. Submitted the CFP for XDC2022 and the
+RFP for XDC2023 this week. As well, currently working with the LPC to come up
+with plans for shipping some throw mics so that we have them for this year's XDC.
+STATUS: Pending
+ITEM: GSoC/Outreachy/EVoC
+Contributor proposal period ended April 19th. Currently have 4 project
+proposals, and one spam proposal. Mentors have until May 12th to rank the 4
+proposals and put in our slot request. There is some confusion around the new
+rules regarding contributors being "new" though that we're still figuring out.
+STATUS: Pending
+ITEM: MIPI Alliance and CSI
+No updates here
+ACTIONS: Lyude to poke vendors at her work about this again soon
+STATUS: Pending
+ITEM: Treasurer report for 2021
+Emma was finally able to get the info she needed to complete this, and the
+report has been approved by the board.
+ACTIONS: Emma to send out treasurer report
+STATUS: Pending
+ITEM: New parent organization
+No updates on this yet
+ACTIONS: Lyude to start looking into this now that elections are over
+STATUS: Pending
+ITEM: Sysadmins
+We need new sysadmins!!!!!
+ACTIONS: Person reading these minutes, you, to consider volunteering as a sysadmin
+STATUS: Pending
+ITEM: Rebranding
+Following the turnouts from this election, some very good points were brought up
+about ensuring the continued relevance of Some of these topics included
+the value of being named in regards to how that reflects our involvement
+with related projects like gstreamer, along with ensuring that
+projects under the umbrella - which keeps us relevant - are
+receiving fair representation considering their involvement with the community
+at large.
+CONSENSUS/TAKEAWAYS: In regards to the drop in election turnout, it was brought
+up that such fluctuations in membership aren't unheard of and aren't necessarily
+a sign that the organization is doing better or worse. More often, they're a
+sign that we just needed to send more voting reminders to people. But regardless
+of the election outcome, it is still very much worth further discussing and
+looking at the various issues that were brought up regarding outreach and
+projects' representation. As well while the results of previous votes on whether should be represented as or not had indicated there wasn't
+that much interest, it was pointed out that isn't necessarily a reliable data
+point as it's entirely possible such votes were only really paid attention to
+within the immediate member base - and thus quite possibly just a source
+of how the main community feels about this issue as opposed to the community at large.
+The main reason this is important is that while the overall consensus is that in it's current state is healthy, we should be proactive to ensure this
+remains the case as opposed to being solely reactive if things look like they
+aren't going well. This includes things like updating our website, investigating
+whether groups under the umbrella feel they're represented properly and
+whether they have any feelings regarding's naming. Of course no major
+changes like renames will happen without a proper vote that members are
+given a chance to particpate in beforehand beforehand, most of this is just to
+gather data around how how the community feels about this.
+ACTIONS: Following the discussion, Mark offered to start discussions with
+various project leads (e.g. like Gstreamer) to get their thoughts on this.
+STATUS: Pending
+ITEM: Meeting over IRC
+Whether or not we should still be having meetings on IRC or another platform
+(such as Jitsi) was also brought up.
+ACTIONS: Didn't reach much of a consensus with this, also was pointed out that
+it would likely also be good to get member's input on this - since such a change
+would mean there wouldn't be IRC logs from meetings for users to go through.
+STATUS: Pending
diff --git a/BoardOfDirectors/MeetingSummaries/2022/05-12.mdwn b/BoardOfDirectors/MeetingSummaries/2022/05-12.mdwn
new file mode 100644
index 00000000..07410baa
--- /dev/null
+++ b/BoardOfDirectors/MeetingSummaries/2022/05-12.mdwn
@@ -0,0 +1,68 @@
+Summary of the 12 May 2022 meeting of the [[X.Org Foundation|XorgFoundation]] [[Board of Directors|BoardOfDirectors]]
+Full IRC meeting logs are posted at [[BoardOfDirectors/IrcLogs/]]
+## Attendees
+Daniel Vetter,
+Lyude Paul,
+Manasi Navare,
+Mark Filion,
+Emma Anholt,
+Alyssa Rosenzweig,
+Ricardo Garcia
+Trevor Woerner
+Samuel Iglesias Gonsálvez,
+## Summary
+Agenda: XDC2022, XDC2023, XDC sponsors, new parent organization, MIPI/DSI,
+GSoC/EVoC, changing meeting time
+## Items discussed
+[[!format txt """
+ITEM: XDC2022
+No updates here other then having sent out the CFP, no presentations received as
+of yet though but it's quite early
+STATUS: Pending
+ITEM: XDC2023
+No updates here, sent out RFP
+STATUS: Pending
+ITEM: XDC sponsors
+Danvet was able to get one more sponsor on board
+STATUS: Pending
+No updates yet, but a member of the community offered to get us some contacts
+for this so that should help!
+STATUS: Pending
+Today is slot request today, we've got 4 proposals ranked and ready to go. Will
+find out results May 20th. Leftover slots are likely to get moved to EVoC, which
+it sounds like we may actually be able to do this year after all!
+ACTIONS: Lyude to update EVoC page?
+STATUS: Pending
+ITEM: Changing meeting time
+Some folks requested we changed the meeting time, so we voted to move the
+meeting to every other wednesday at 16:00 UTC
+ACTIONS: Lyude to update calendar events
+STATUS: Pending
+ITEM: New parent organization
+Lyude still needs to find time to start this
+ACTIONS: Lyude to make time to poke organizations
+STATUS: Pending
diff --git a/Development/Security.mdwn b/Development/Security.mdwn
index fe0544f4..df95e347 100644
--- a/Development/Security.mdwn
+++ b/Development/Security.mdwn
@@ -10,6 +10,16 @@ See the [[Security Checklist|Development/Security/Checklist]] for the list of th
## X.Org 7.7
+* December 14, 2021 Multiple input validation failures in X server extensions
+ * CVE-2021-4008 / ZDI-CAN-14192 SProcRenderCompositeGlyphs out-of-bounds access
+ * CVE-2021-4009 / ZDI-CAN-14950 SProcXFixesCreatePointerBarrier out-of-bounds access
+ * CVE-2021-4010 / ZDI-CAN-14951 SProcScreenSaverSuspend out-of-bounds access
+ * CVE-2021-4011 / ZDI-CAN-14952 SwapCreateRegister out-of-bounds access
+ * Fixed in [[xwayland 21.1.4|]]
+ * Fixed in [[xorg-server 21.1.2|]]
+ * Fixed in [[xorg-server 1.20.14|]]
+ * Please see [[the advisory|]] for more information
* April 13, 2021 Input validation failures in X server XInput extension
* CVE-2021-3472 / ZDI CAN 12549 XChangeFeedbackControl Integer Underflow
* Fixed in [[xorg-server 1.20.11|]]
diff --git a/Events.mdwn b/Events.mdwn
index 85ac68a1..bd4df76d 100644
--- a/Events.mdwn
+++ b/Events.mdwn
@@ -1,26 +1,26 @@
## Upcoming Events
* <span itemscope itemtype="">
- <span itemprop="name">[[X.Org Developer's Conference: XDC2021|]]</span>,
+ <span itemprop="name"><a itemprop="url" href="">FOSDEM 2022</a></span>,
+ <span itemprop="location">Virtual</span>,
+ <span itemprop="startDate" content="2022-02-05">February 5</span> through
+ <span itemprop="endDate" content="2022-02-06">February 6, 2022</span>.
+* <span itemscope itemtype="">
+ <span itemprop="name">[[X.Org Developer's Conference: XDC2022|]]</span>,
<link itemprop="url" content="" />
- <span itemprop="location">Virtual (formerly Gdańsk, Poland)</span>,
- <span itemprop="startDate" content="2021-09-15">September 15th</span> through
- <span itemprop="endDate" content="2021-09-17">September 17th, 2021</span>.
+ <span itemprop="location">Minneapolis, Minnesota, USA</span>,
+ <span itemprop="startDate" content="2022-10-04">October 4th</span> through
+ <span itemprop="endDate" content="2022-10-06">October 6th, 2022</span>.
## Recent Events
* <span itemscope itemtype="">
- <span itemprop="name"><a itemprop="url" href=""> 2021</a></span>,
+ <span itemprop="name"><a itemprop="url" href=""> 2022</a></span>,
<span itemprop="location">Virtual</span>,
- <span itemprop="startDate" content="2021-01-23">January 23 through </span>
- <span itemprop="endDate" content="2021-01-25">January 25, 2021</span>.
+ <span itemprop="startDate" content="2022-01-14">January 14 through </span>
+ <span itemprop="endDate" content="2022-01-16">January 16, 2022</span>.
-* <span itemscope itemtype="">
- <span itemprop="name"><a itemprop="url" href="">FOSDEM 2021</a></span>,
- <span itemprop="location">Virtual</span>,
- <span itemprop="startDate" content="2021-02-06">February 6</span> through
- <span itemprop="endDate" content="2021-02-07">February 7, 2021</span>.
## Older Events
diff --git a/Events/History.mdwn b/Events/History.mdwn
index 61ea8789..524e3b86 100644
--- a/Events/History.mdwn
+++ b/Events/History.mdwn
@@ -1,5 +1,26 @@
A collection of older events that X.Org has held, presented at, or had significant presence at. Move things here from the [[current events page|Events]] when they get too old, and if possible, link to what we did there.
+## 2021
+* <span itemscope itemtype="">
+ <span itemprop="name">[[X.Org Developer's Conference: XDC2021|]]</span>,
+ <link itemprop="url" content="" />
+ <span itemprop="location">Virtual (formerly Gdańsk, Poland)</span>,
+ <span itemprop="startDate" content="2021-09-15">September 15th</span> through
+ <span itemprop="endDate" content="2021-09-17">September 17th, 2021</span>.
+ </span>
+* <span itemscope itemtype="">
+ <span itemprop="name"><a itemprop="url" href="">FOSDEM 2021</a></span>,
+ <span itemprop="location">Virtual</span>,
+ <span itemprop="startDate" content="2021-02-06">February 6</span> through
+ <span itemprop="endDate" content="2021-02-07">February 7, 2021</span>.
+* <span itemscope itemtype="">
+ <span itemprop="name"><a itemprop="url" href=""> 2021</a></span>,
+ <span itemprop="location">Virtual</span>,
+ <span itemprop="startDate" content="2021-01-23">January 23 through </span>
+ <span itemprop="endDate" content="2021-01-25">January 25, 2021</span>.
+ </span>
### 2020
* <span itemscope itemtype="">
diff --git a/Events/RFP.mdwn b/Events/RFP.mdwn
index f699a298..aee7fb59 100644
--- a/Events/RFP.mdwn
+++ b/Events/RFP.mdwn
@@ -151,7 +151,7 @@ whether to solicit more proposals.
## Process
After the final vote the board will inform all organizers. Announcing the
-conference, setting up the conference page on the [[Events Wiki|/Events/]] and
+conference, setting up the conference page on the [[Indico instance|]] and
running the CFP are all the organizers duties. The board will only serve as the
papers committee and for granting travel sponsorships.
diff --git a/GSoCApplication.mdwn b/GSoCApplication.mdwn
index b354ed62..37fa7b49 100644
--- a/GSoCApplication.mdwn
+++ b/GSoCApplication.mdwn
@@ -6,7 +6,7 @@ We expect more project proposals than Google will be able to fund. Here is our l
## Requirements
* Applicants meet [[Google's requirements|]] for participation in Summer of Code.
- * Applicants are in regular and close contact with their X.Org mentors and the community (IRC).
+ * Applicants are in regular and close contact with their X.Org mentors and the community (IRC). At a minimum applications should be subscribed to the dri-devel mailing list and should follow the #dri-devel IRC channel on OFTC.
* Applicants know their target programming language.
* Applicants has successfully upstreamed a simple patch to demonstrate they know the process.
* Applicants are willing to blog weekly and interact with the community (failure to do so will result in a fail at the next review)
diff --git a/RadeonFeature.mdwn b/RadeonFeature.mdwn
index 633a9673..328d7e63 100644
--- a/RadeonFeature.mdwn
+++ b/RadeonFeature.mdwn
@@ -77,7 +77,7 @@ Dynamic Power Management (DPM) || | N/A | N/A | N/A | N/A | [[!color backgro
**Other** || | **R100** | **R200** | **R300/R400** | **R500** | **R600/700** | **Evergreen** | **N.Islands** | **S.Islands**[<sup>1</sup>](#note_1) | **C.Islands** | **V.Islands** | **A.Islands**
Suspend Support || | [[!color background=palegreen text=DONE ]] | [[!color background=palegreen text=DONE ]] | [[!color background=palegreen text=DONE ]] | [[!color background=palegreen text=DONE ]] | [[!color background=palegreen text=DONE ]] | [[!color background=palegreen text=DONE ]] | [[!color background=palegreen text=DONE ]] | [[!color background=palegreen text=DONE ]] | [[!color background=palegreen text=DONE ]] | [[!color background=palegreen text=DONE ]] | [[!color background=palegreen text=DONE ]]
CrossFire (multi-card) || | N/A | N/A | N/A | [[!color background=red text=TODO ]] | [[!color background=red text=TODO ]] | [[!color background=red text=TODO ]] | [[!color background=red text=TODO ]] | [[!color background=red text=TODO ]] | [[!color background=red text=TODO ]] | [[!color background=red text=TODO ]] | [[!color background=red text=TODO ]]
-Compute (OpenCL)[<sup>33</sup>](#note_33) || | N/A | N/A | N/A | N/A | [[!color background=red text=TODO ]] | [[!color background=orange text=WIP ]] | [[!color background=orange text=WIP ]] | [[!color background=orange text=WIP ]] | [[!color background=palegreen text="DONE (ROCm)" ]] | [[!color background=palegreen text="DONE (ROCm)" ]] | [[!color background=palegreen text="DONE (ROCm)" ]]
+Compute (OpenCL)[<sup>33</sup>](#note_33) || | N/A | N/A | N/A | N/A | [[!color background=red text=TODO ]] | [[!color background=orange text=WIP ]] | [[!color background=orange text=WIP ]] | [[!color background=orange text=WIP ]] | [[!color background=orange text=WIP ]] | [[!color background=orange text=WIP ]] | [[!color background=orange text=WIP ]]
Asynchronous DMA || | N/A | N/A | N/A | N/A | [[!color background=palegreen text=DONE ]] | [[!color background=palegreen text=DONE ]] | [[!color background=palegreen text=DONE ]] | [[!color background=palegreen text=DONE ]] | [[!color background=palegreen text=DONE ]] | [[!color background=palegreen text=DONE ]] | [[!color background=palegreen text=DONE ]]
* [[AMD Volcanic Islands Series ISA|]]
* [[AMD "Vega" Series ISA|]]
* [[AMD "Vega" 7nm Series ISA|]]
+* [[AMD CDNA Series ISA|]]
+* [[AMD CDNA2 Series ISA|]]
* [[AMD RDNA Series ISA|]]
* [[AMD RDNA2 Series ISA|]]
diff --git a/SummerOfCodeIdeas.mdwn b/SummerOfCodeIdeas.mdwn
index 9fc82b76..f946cda0 100644
--- a/SummerOfCodeIdeas.mdwn
+++ b/SummerOfCodeIdeas.mdwn
@@ -6,37 +6,63 @@ NOTE: documentation-only tasks don't fall within the scope of GSoC, but if you'r
The board treats GSoC as an opportunity to teach new developers rather than a chance to get a pile of free code. With this perspective, if, in two months, the student actually has learned how to contribute to X Window System and its related projects, that's a huge step forward. Creating a project which guides this process with a maximal chance of success is the only tricky part.
-When writing a proposal, please remember to make it detailed. Include at least the information called for in "[[What should a student proposal look like?|]]", but including milestones and a project schedule is even better. See [[GSoCApplication|GSoCApplication]] for guidelines.
+When writing a proposal, please remember to make it detailed. Include at least the information called for in "[[Writing a proposal|]]", but including milestones and a project schedule is even better. See [[GSoCApplication|GSoCApplication]] for guidelines.
X.Org is a large and comprehensive project with a huge number of possible opportunities for interesting Google / X.Org Summer of Code projects. This list contains a few of those opportunities that are particularly interesting to X.Org developers and potential mentors. Please note that these are just suggestions; if you have an idea for something else please ask.
-If you have questions, feel free to contact us on the [[dri-devel mailing list|]] or the [[dri-devel IRC channel|irc://]].
+If you have questions, feel free to contact us on the [[dri-devel mailing list|]] or the [[dri-devel IRC channel|irc://]].
+## Potential Mentors
+Some projects have one or more specific potential mentor(s) who are listed as part of the project idea itself. Otherwise a potential mentor might be found in the following list:
+* [Martin Peres]( - Apitrace, Power Management in Nouveau, xf86-video-modesetting or EzBench-related projects
+* [Daniel Stone]( - Wayland/Weston, EGL, KMS
+* [Karol Herbst]( - Nouveau
+* [Julien Isorce]( - OpenMAX
+* [Christian König]( - AMDGPU
+* [Simon Ser]( - Wayland
+* [Daniel Vetter]( - DRM
## Ideas
Here are a list of projects proposed by X.Org developers. If you have ideas of your own, please post them on the relevant mailing lists.
+### add unit tests to AMDGPU
+* _Difficulty:_ Medium
+* _Expected Size:_ 350 hr
+* _Skils Required:_ moderate knowledge of C (working with pointers should not be an issue), comfortable using Linux on the command-line
+* _Useful skills:_ able to communicate on a public mailing list, able to work in a group and to help others
+* _Hardware/Software required:_ any Linux distribution
+_NOTE:_ the mentors for this project have a separate set of instructions regarding prerequisites and proposal guidelines which supersede all others. Please see [[this page|AMDGPU2022]] for details.
+Mentors: Rodrigo Siqueira, Melissa Wen
### Mesa
#### adriconf enhancements
* _Difficulty:_ Medium
+* _Expected Size:_ 350 hr
* _Skills Required:_ GUI programming
* _Useful skills:_ C/C++
* _Hardware/Software required:_ Any GPU working with Mesa
-* _Where to ask questions:_ [[|]], #dri-devel on
+* _Where to ask questions:_ [[|]], #dri-devel on
* _Description:_ Mesa users can set several driver options via an xml file in $HOME/.drirc or system /etc/drirc. With these files, the user can define behaviours for selected applications, like forcing vsync, picking a specific gpu in multi-gpu systems or enabling driver workarounds. [adriconf]( is a user-friendly GUI to set these options, and like all such tools it can always use improvement.
-Possible mentor: Nicolai Hähnle (nha on IRC/freenode)
+Possible mentor: Nicolai Hähnle (nha on IRC/OFTC)
#### Vulkan GPU preference tool
* _Difficulty:_ Medium
+* _Expected Size:_ 350 hr
* _Skills Required:_ Writing advanced GUI
* _Useful skills:_ C/C++
* _Hardware/Software required:_ A dual-GPU setup where both GPUs support Vulkan
-* _Where to ask questions:_ [[|]], #dri-devel on
+* _Where to ask questions:_ [[|]], #dri-devel on
* _Description:_ One of the problems facing users with multi-GPU setups on
Linux is the fact that applications choose a GPU either through their own
algorithm, by just selecting the first thing that comes up (which may not
@@ -55,65 +81,71 @@ Possible mentor: Nicolai Hähnle (nha on IRC/freenode)
KDE system settings. It would also be good if the GUI was the same as
the DriConf tool mentioned above.
-Possible mentors: Dave Airlie (airlied on IRC/freenode) Jason Ekstrand
-(jekstrand on IRC/freenode)
+Possible mentors: Dave Airlie (airlied on IRC/OFTC) Jason Ekstrand
+(jekstrand on IRC/OFTC)
#### OpenMAX HEVC
* _Difficulty:_ Medium
+* _Expected Size:_ 350 hr
* _Skills Required:_ C
* _Useful skills:_ Multimedia
* _Hardware/Software required:_ AMD Graphics Card supporting at least UVD6.0 or VCN (Fiji, Carrizo, Polaris, Vega, Raven) for HEVC decode, UVD6.3 or VCN for HEVC encode (Polaris, Vega, Raven)
-* _Where to ask questions:_, #dri-devel on
+* _Where to ask questions:_, #dri-devel on
* _Description:_ Recently Mesa's OMX gained support for Tizonia which one is an implementation of the OpenMAX IL 1.2.0 specification. It means that Mesa provides decoders and encoders in a form of components that can be used from an OpenMAX IL client (ex: gst-omx) by loading the Tizonia core library. The advantage of these components is that they are hardware accelerated by the GPU. The project goal is to add h265 support to Mesa's Tizonia components. Starting by the decoder for which some code can be taken from Mesa's omx Bellagio. The second task is to implement the h265 encoder, bridging the generic Mesa's PIPE VIDEO api to Tizonia. Depending on the progress the third task will be to add support for zero-copy in the h264 and h265 encoders taking reference from the Mesa Tizonia h264 decoder which supports OMX_UseEGLImage. Along the project, any code taken from Mesa's omx Bellagio will be refactored in Mesa omx common to be shared between Mesa Bellagio and Tizonia. For validation and testing the student will use gst-omx from the GStreamer project which already has wrappers for h265 decoder and encoder.
-Possible mentor: Julien Isorce (capOM on IRC/freenode)
+Possible mentor: Julien Isorce (capOM on IRC/OFTC)
#### OpenMAX DMA-BUF
* _Difficulty:_ Medium
+* _Expected Size:_ 350 hr
* _Skills Required:_ C
* _Useful skills:_ Multimedia
* _Hardware/Software required:_ AMD Graphics Card supporting UVD or VCN for decode and VCE or VCN for encode
-* _Where to ask questions:_, #dri-devel on
+* _Where to ask questions:_, #dri-devel on
* _Description:_ Add dmabuf support in Mesa's OpenMAX plugins for Tizonia. Thanks to a GSoC 2017 project, Mesa has now plugins for [[Tizonia OMX IL|]]. Currently it supports zero-copy using EGLImage but this is limited to the decoders. In order to handle more cases for zero-copy (example: encoders and transcoding) we need to add support for dmabuf. The ZynqUltraScale board from XILINK already supports dmabuf in its implementation of OpenMAX IL named Allegro and it works with the [[OMX GStreamer plugins|]]. The first part of this project is to define similar dma-buf API in [[Tizonia|]], then use it in Mesa's OMX to implement dma-buf support. The tests will be done using OMX GStreamer.
-Possible mentor: Julien Isorce (, capOM on IRC/freenode)
+Possible mentor: Julien Isorce (, capOM on IRC/OFTC)
#### OpenMAX MJPEG decode
* _Difficulty:_ Medium
+* _Expected Size:_ 350 hr
* _Skills Required:_ C
* _Useful skills:_ Multimedia
* _Hardware/Software required:_ AMD Graphics Card supporting UVD6.x from Carrizo, up to Polaris.
-* _Where to ask questions:_, #dri-devel and #radeon on
+* _Where to ask questions:_, #dri-devel and #radeon on
* _Description:_ The MJPEG codec was implemented to MESA VA state tracker based on VA-API spec. Add that functionality for OMX/Bellagio&Tizonia. The implementation would need to parse MJPEG bitstream and extract all the information HW requires. The MJPEG spec could be referred for bitstream structure, and the VA-API implementation in MESA could be referred for HW interface requirements.
#### Piglit for VA-API
* _Difficulty:_ Easy
+* _Expected Size:_ 350 hr
* _Skills Required:_ C, Python
* _Useful skills:_ Multimedia
* _Hardware/Software required:_ AMD Graphics Card supporting UVD or VCN for decode and VCE or VCN for encode
-* _Where to ask questions:_, #dri-devel and #radeon on
+* _Where to ask questions:_, #dri-devel and #radeon on
* _Description:_ Make mesa VA-API more robust with latest gstreamer-vaapi. The goal is to provide an automated test framework for a variety of gst vaapi pipelines to catch regressions and find new bugs using something like piglit. Use gst vaapi pipelines from popular apps such as vlc, mpv, mplayer, totem, and chromium as references. Fixing some of the bugs found could be an additional stretch goal.
#### Piglit for OpenMAX
* _Difficulty:_ Easy
+* _Expected Size:_ 350 hr
* _Skills Required:_ C, Python
* _Useful skills:_ Multimedia
* _Hardware/Software required:_ AMD Graphics Card supporting UVD or VCN for decode and VCE or VCN for encode
-* _Where to ask questions:_, #dri-devel and #radeon on
+* _Where to ask questions:_, #dri-devel and #radeon on
* _Description:_ Make mesa OpenMAX more robust with latest gstreamer-omx. The goal is to provide an automated test framework for a variety of gst omx pipelines to catch regressions and find new bugs using something like piglit. Use gst omx pipelines from popular apps as references. Fixing some of the bugs found could be an additional stretch goal.
#### Unit and performance tests for VA-API
* _Difficulty:_ Easy
+* _Expected Size:_ 350 hr
* _Skills Required:_ C, Python
* _Useful skills:_ Multimedia
* _Hardware/Software required:_ AMD Graphics Card supporting UVD or VCN for decode and VCE or VCN for encode
-* _Where to ask questions:_, #dri-devel and #radeon on
+* _Where to ask questions:_, #dri-devel and #radeon on
* _Description:_ Create a set of unit tests for VA-API to test all documented and undocumented details of the API and provide a set of performance tests for benchmarking.
@@ -123,9 +155,10 @@ See also our [Trello board](
#### Compiler: Spilling Registers
* _Difficulty:_ Difficult
+* _Expected Size:_ 350 hr
* _Skills Required:_ C, Compilers
* _Hardware/Software required:_ Adreno 3xx, 4xx, or 5xx GPU
-* _Where to ask questions:_ [[|]], #freedreno on
+* _Where to ask questions:_ [[|]], #freedreno on
* _Description:_ Shaders with high register usage (see shadertoy) may fail register allocation stage, in which case load/store instructions need to be added to "spill" register values to memory. This project would involve adding support to freedreno/ir3 compiler to determine which registers to spill, add necessary load/store instructions to save to local memory and restore from local memory (and then re-run scheduling and register allocation passes).
### Nouveau (Open Source NVIDIA driver)
@@ -135,101 +168,112 @@ A list of project is available on our [Trello board](
#### Instruction Scheduler
* _Difficulty:_ Difficult
+* _Expected Size:_ 350 hr
* _Skills Required:_ C++
* _Useful skills:_ Compilers
* _Hardware/Software required:_ NVIDIA Fermi or later
-* _Where to ask questions:_ [[|]], #nouveau on
+* _Where to ask questions:_ [[|]], #nouveau on
* _Description:_ Write an instruction scheduling pass for basic blocks in the nouveau codegen compiler. Create scheduling policies that improve performance.
#### Maxwell Accelerated Video Decoding
* _Difficulty:_ Medium
+* _Expected Size:_ 350 hr
* _Skills Required:_ C
* _Useful skills:_ Reverse Engineering, Video formats
* _Hardware/Software required:_ NVIDIA Maxwell GM107, GM200, GM204 or GM208 chip (a GM108 desktop card might works as well, the mobile one won't)
-* _Where to ask questions:_ [[|]], #nouveau on
+* _Where to ask questions:_ [[|]], #nouveau on
* _Description:_ RE the mechanism for video decoding in VP6 (the video engine iteration used in GM10x chips). Implement support for driving the engine.
#### Kepler Accelerated Video Encoding
* _Difficulty:_ Medium-Difficult
+* _Expected Size:_ 350 hr
* _Skills Required:_ C
* _Useful skills:_ Reverse Engineering, Video formats
* _Hardware/Software required:_ NVIDIA Kepler GKxxx chip
-* _Where to ask questions:_ [[|]], #nouveau on
+* _Where to ask questions:_ [[|]], #nouveau on
* _Description:_ RE the video encoding component of Kepler chips and produce sufficient documentation for an open source implementation (while reusing blob firmware). A stretch goal would be to integrate something into nouveau to be able to drive the engine, and a toy user-space application to encode a video.
#### Dynamic Reclocking
* _Difficulty:_ Medium-Difficult
+* _Expected Size:_ 350 hr
* _Skills Required:_ C
* _Useful skills:_ Modeling, control systems, and statistics
* _Hardware/Software required:_ A Kepler NVIDIA GPU with a super-reliable reclocking support and a power sensor
-* _Where to ask questions:_ [[|]], #nouveau on
+* _Where to ask questions:_ [[|]], #nouveau on
* _Description:_ Create a performance test rig that will test different use-cases we want to support for our dynamic reclocking.
This setup will need to be replicable and will serve as a benchmark for both power consumption and performance. The next step will be to experiment with different heuristics in the userspace that will poll the performance counters, and dynamically change the clocks to achieve the highest possible performance, at the lowest power consumption possible and with the simplest possible heuristic.
#### Enabling performance analysis on frameretracer
* _Difficulty:_ Medium
+* _Expected Size:_ 350 hr
* _Skills Required:_ C, C++
* _Useful skills:_ Qt, OpenGL, Apitrace
* _Hardware/Software required:_ Any NVIDIA Tesla or newer
-* _Where to ask questions:_ [[|]], #nouveau on
+* _Where to ask questions:_ [[|]], #nouveau on
* _Description:_ Frameretracer is a wonderful tool to find and debug performance bottlenecks. However, it has been designed for Intel GPUs and requires changes in both Frameretracer and Nouveau in order to get the maximum out of the tool. The project would be to make the necessary changes in both Nouveau and Frameretracer to enable performance analysis on Nouveau.
#### Initial Nouveau Vulkan driver
* _Difficulty:_ Very Difficult
+* _Expected Size:_ 350 hr
* _Skills Required:_ C, C++, Python
* _Useful skills:_ Vulkan
* _Hardware/Software required:_ Any NVIDIA Kepler or newer
-* _Where to ask questions:_ [[|]], #nouveau on
+* _Where to ask questions:_ [[|]], #nouveau on
* _Description:_ Write an initial vulkan driver, which should pass the most basic tests from the khronos CTS.
#### Helping out with Nouveau OpenCL driver
* _Difficulty:_ Very Difficult
+* _Expected Size:_ 350 hr
* _Skills Required:_ C++
* _Useful skills:_ OpenCL, Compiler
* _Hardware/Software required:_ Any NVIDIA Tesla or newer
-* _Where to ask questions:_ [[|]], #nouveau on
+* _Where to ask questions:_ [[|]], #nouveau on
* _Description:_ Helping Pierre Moreau to get his current OpenCL Nouveau code to a usable state. This will include working a lot on the Nouveau compiler and improving the OpenCL Gallium state tracker Clover.
#### Adding new compiler optimization Passes to Codegen
* _Difficulty:_ Easy to Difficult
+* _Expected Size:_ 350 hr
* _Skills Required:_ C++
* _Useful skills:_ Compiler Optimizations
* _Hardware/Software required:_ Any NVIDIA Tesla or newer
-* _Where to ask questions:_ [[|]], #nouveau on
+* _Where to ask questions:_ [[|]], #nouveau on
* _Description:_ Add new passes to Nouveaus codegen to improve the current generated code. This can mean adding a lot of trivial passes or a few complex one. A list of passes are in the "OpenGL Compiler Opts" list on the Nouveau Trello board:
#### Fixing outstanding reclocking issues on already reclockable GPUs
* _Difficulty:_ Medium-Difficult
+* _Expected Size:_ 350 hr
* _Skills Required:_ C
* _Useful skills:_ Reverse Engineering
* _Hardware/Software required:_ Any NVIDIA Tesla, Kepler or Maxwell GPU
-* _Where to ask questions:_ [[|]], #nouveau on
+* _Where to ask questions:_ [[|]], #nouveau on
* _Description:_ We already support a handful of chipsets quite well. Fixing last outstanding issues on those would take us a step forward to actually having dynamic reclocking enabled by default (which we don't implement yet though)
### Fixing eGPU hotplugging in Nouveau
* _Difficulty:_ Easy to Hard (depending on which scenario to fix)
+* _Expected Size:_ 350 hr
* _Skills Required:_ C
* _Useful skills:_ linux kernel programming
* _Hardware/Software required:_ Any Nvidia GPU and an eGPU case
-* _Where to ask questions:_ [[|]], #nouveau on
+* _Where to ask questions:_ [[|]], #nouveau on
* _Description:_ Using Nvidia GPUs through an eGPU case already works flawless. The only issue is, that unplugging the device causes the kernel to crash. The Nouveau driver needs to be taught to handle this situation. The easiest to fix is to unplug the GPU while no application is using it. The hardest scenario to fix is when X is doing reverse PRIME and an application is using the GPU for rendering.
### Fix outstanding tearing issues
* _Difficulty:_ Medium-Hard
+* _Expected Size:_ 350 hr
* _Skills Required:_ C
* _Useful skills:_ linux kernel programming, understanding of Xorg
* _Hardware/Software required:_ Any Nvidia GPU and two displays
-* _Where to ask questions:_ [[|]], #nouveau on
+* _Where to ask questions:_ [[|]], #nouveau on
* _Description:_ In a couple of cases with the nvidia driver tearing still happens. One of such situations is when the user has two displays plugged in, but some also see it happen with PRIME. In order to fix specific cases of tearing, the cause needs to be figured out and fixed accordingly, be it in the kernel and/or the Nouveau DDX or Mesa driver.
### Kernel
@@ -243,51 +287,51 @@ You may find multiple ideas from the the [DRM todo list](https://dri.freedesktop
#### Support for pressure-only bluetooth styli
* _Difficulty:_ Medium
+* _Expected Size:_ 350 hr
* _Skills Required:_ C
* _Useful skills:_ Reverse Engineering, knowledge about Bluetooth/bluez
* _Hardware/Software required:_ Touchscreen-capable laptop, bluetooth pen
-* _Where to ask questions:_ [[|]], #wayland on
+* _Where to ask questions:_ [[|]], #wayland on
* _Description:_ Pressure-senstive style are commonly used with iPads and tablets. These styli usually only provide pressure, relying on the touchscreen for coordinates. To present such a stylus to an application, the touchscreen data and the stylus data have to be combined to a single event from the stylus device. libinput is perfectly suited to do exactly that. This project requires work in bluez to implement the stylus-specific protocol as a bluez plugin so the device shows up as kernel device (and, depending on the device, reverse engineering the protocol). This project requires work in libinput to extract and combine the data from both devices into a single virtual device.
### Wayland
-#### LibWeston based console
+#### KMS terminal emulator
-* _Difficulty:_ Medium
+* _Difficulty:_ Hard
+* _Expected Size:_ 350 hr
* _Skills Required:_ C
-* _Useful skills:_ LibWeston, Wayland.
-* _Hardware/Software Required:_ Supports Wayland and KMS with open drivers
-* _Where to ask questions:_
-* _Description:_ Using libweston to write a "server" that only uses pixman-renderer and ensures there is always a terminal app running fullscreen at all times. When the console is inactive the terminals can be either terminated or made run in low resource mode so gfx resources can be freed.
+* _Useful skills:_ KMS
+* _Hardware/Software Required:_ Supports KMS with open drivers
+* _Where to ask questions:_ [[|]], #wayland-devel
+* _Description:_ Writing a KMS client which can act as a terminal emulator to replace the old fbcon module. Prior art: kmscon. Could build on top of kmscon, or add a KMS backend to an existing terminal emulator.
#### Weston support for multiple KMS devices
* _Difficulty:_ Medium
+* _Expected Size:_ 350 hr
* _Skills Required:_ C
* _Useful skills:_ KMS, Pixman/EGL
* _Hardware/Software Required:_ Supports Wayland and KMS with open drivers
-* _Where to ask questions:_
+* _Where to ask questions:_ [[|]], #wayland-devel
* _Description:_ Weston supports multiple outputs, but currently limits them to a single GPU. Add support to Weston's DRM backend to open several KMS devices, with the ability to use outputs from all of them. To sidestep the problem of allocating buffers suitable for hardware acceleration across different GPUs, restrict this to the Pixman software renderer.
-#### Improved Wayland timeline debugging
+#### Improved Weston timeline debugging
* _Difficulty:_ Medium
+* _Expected Size:_ 350 hr
* _Skills Required:_ C
* _Useful skills:_ Performance profiling (including timeline and sample-based profilers), Wayland, toolkits, EGL / Vulkan WSI
* _Hardware/Software Required:_ Supports Wayland and KMS with open drivers
* _Where to ask questions:_ [[|]], #wayland-devel
* _Description:_ Weston currently has built-in support for timeline debugging, dumping JSON files with a visual representation of the timeline for showing client content on screen. This has a small client named Wesgr to render these to SVG. This project is somewhat open-ended, but there are many possibilities to improve it, including: implementing this protocol through more clients, a better renderer / timeline viewer with programmatic filtering (e.g. 'show me all frames which were late'), and integration with kprobes to instrument timings within the kernel stack (hardware/fence completion).
+#### wlroots presentation scheduling
-## Potential Mentors
-Please add yourself below if you are willing to be a GSoC or EVoC mentor:
-* [Martin Peres]( - Apitrace, Power Management in Nouveau, xf86-video-modesetting or EzBench-related projects
-* [Daniel Stone]( - Wayland/Weston, EGL, KMS
-* [Karol Herbst]( - Nouveau
-* [Julien Isorce]( - OpenMAX
-* [Christian König]( - AMDGPU
-* [Adam Jackson]( - Xorg docs
-* [Simon Ser]( - Wayland
-* [Daniel Vetter]( - DRM
+* _Difficulty_: Hard
+* _Expected Size:_ 350 hr
+* _Skills Required_: C
+* _Useful skills:_ Wayland, KMS, OpenGL
+* _Hardware/Software Required_: Supports Wayland and KMS with open drivers
+* _Where to ask questions_: #sway-devel on Libera Chat
+* _Description_: At the moment wlroots-based compositors render right after the GPU displays a new frame on screen (vblank). This isn't great from a latency point of view, because all client surface updates will be 1 frame worth of time late. There are multiple ways to improve this (Weston and Sway have a configurable fixed delay, Mutter has an adaptive delay). Research and implement a good mechanism to reduce latency without missing frames.
diff --git a/XorgModuleABIVersions.mdwn b/XorgModuleABIVersions.mdwn
index ae1b186b..c6fc020d 100644
--- a/XorgModuleABIVersions.mdwn
+++ b/XorgModuleABIVersions.mdwn
@@ -33,9 +33,10 @@ ABI numbers may increment multiple times during Xorg server development cycles,
**1.18** | 0.4 | 20.0 | 22.1 | 9.0 | 0.6
**1.19** | 0.4 | 23.0 | 24.1 | 10.0 | N/A
**1.20** | 0.4 | 24.0 | 24.1 | 10.0 | N/A
+**21** | 0.4 | 25.2 | 24.4 | 10.0 | N/A
-When looking at Xserver source code, the ABI versions may be found as definitions of `ABI_VIDEODRV_VERSION`, `ABI_XINPUT_VERSION`, etc. in [[`hw/xfree86/common/xf86Module.h`|]].
+When looking at Xserver source code, the ABI versions may be found as definitions of `ABI_VIDEODRV_VERSION`, `ABI_XINPUT_VERSION`, etc. in [[`hw/xfree86/common/xf86Module.h`|]].
## Input ABI policy