From: Lyude Paul <lyude@redhat.com>
To: xorg@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
events@lists.x.org, xorg-devel@lists.freedesktop.org,
wayland-devel@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, mesa-dev@lists.freedesktop.org,
amd-gfx@lists.freedesktop.org, etnaviv@lists.freedesktop.org,
freedreno@lists.freedesktop.org, nouveau@lists.freedesktop.org,
intel-gfx@lists.freedesktop.org,
libre-soc-dev@lists.libre-soc.org
Cc: board@x.org
Subject: [Intel-gfx] [Important!] 2022 X.Org Foundation Membership deadline for voting in the election
Date: Thu, 17 Feb 2022 15:08:18 -0500 [thread overview]
Message-ID: <db5decb525e7ab36cd4875ef5c6bba942b46d7c7.camel@redhat.com> (raw)
The 2022 X.Org Foundation elections are rapidly approaching. We will be
forwarding instructions on the nomination process to membership in the
near future.
Please note that only current members can vote in the upcoming election,
and that the deadline for new memberships or renewals to vote in the
upcoming election is March 17th 2022 at 23:59 UTC.
If you are interested in joining the X.Org Foundation or in renewing
your membership, please visit the membership system site at:
https://members.x.org/
You can find the current election schedule here:
https://www.x.org/wiki/BoardOfDirectors/Elections/2022/
Lyude Paul,
On behalf of the X.Org elections committee
next reply other threads:[~2022-02-17 20:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 20:08 Lyude Paul [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-04 17:40 [Intel-gfx] [Important!] 2022 X.Org Foundation Membership deadline for voting in the election Lyude Paul
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=db5decb525e7ab36cd4875ef5c6bba942b46d7c7.camel@redhat.com \
--to=lyude@redhat.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=board@x.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=etnaviv@lists.freedesktop.org \
--cc=events@lists.x.org \
--cc=freedreno@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=libre-soc-dev@lists.libre-soc.org \
--cc=mesa-dev@lists.freedesktop.org \
--cc=nouveau@lists.freedesktop.org \
--cc=wayland-devel@lists.freedesktop.org \
--cc=xorg-devel@lists.freedesktop.org \
--cc=xorg@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox