From: Mark Wielaard <mark@klomp.org>
To: gdb@sourceware.org
Subject: Re: Sourceware Survey 2026
Date: Mon, 30 Mar 2026 17:42:48 +0200 [thread overview]
Message-ID: <c0090b9228b0be4f9152836afcfb3ccfb8ed4466.camel@klomp.org> (raw)
In-Reply-To: <20260320112416.GM344@gnu.wildebeest.org>
On Fri, 2026-03-20 at 12:24 +0100, Mark Wielaard wrote:
> It is time for our yearly Sourceware Survey. The Sourceware Project
> Leadership Committee would like to know who our users are, which
> hosted projects they feel part of, what services they rely on and what
> the priorities should be for our budget and new initiatives.
>
> https://nextcloud.sfconservancy.org/apps/forms/s/rtRRt8nA6fCY7zD2zBG3dBMR
Reminder: The Survey runs till this Friday
https://sourceware.org/survey-2026
> The survey will run for two weeks and contains 20 quick questions.
> Please feel free to skip any question, for example if you don't use a
> service or are not interested in a specific service or topic. Each
> question has an "Other" option where you can add any suggestion you
> have about improving the Sourceware services.
>
> The overview page (where we will also publish the summary/results) is
> here https://sourceware.org/survey-2026 the direct link to the form is
> https://nextcloud.sfconservancy.org/apps/forms/s/rtRRt8nA6fCY7zD2zBG3dBMR
>
> This survey is one way to give (anonymous) feedback on Sourceware. For
> other ways to participate or to ask more specific questions see the
> Sourceware organization contact options:
> https://sourceware.org/mission.html#organization
>
> Thanks,
>
> Frank Ch. Eigler, Ian Kelling, Ian Lance Taylor, Tom Tromey,
> Jon Turney, Mark J. Wielaard and Elena Zannoni
prev parent reply other threads:[~2026-03-30 15:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 11:24 Mark Wielaard
2026-03-30 15:42 ` Mark Wielaard [this message]
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=c0090b9228b0be4f9152836afcfb3ccfb8ed4466.camel@klomp.org \
--to=mark@klomp.org \
--cc=gdb@sourceware.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