From: Mark Wielaard <mark@klomp.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: "Frank Ch. Eigler" <fche@redhat.com>,
pono@sfconservancy.org, Marc <dkm@kataplop.net>
Subject: Re: proposing Sourceware as Software Freedom Conservancy member project
Date: Fri, 02 Sep 2022 13:10:31 +0200 [thread overview]
Message-ID: <330c51b943d7cfc9921da9adcda9e5181e28024b.camel@klomp.org> (raw)
In-Reply-To: <20220901194716.GA19631@redhat.com>
Hi Marc,
On Thu, 2022-09-01 at 15:47 -0400, Frank Ch. Eigler via Overseers
wrote:
> > I guess this will be discussed during the upcoming Cauldron during
> > Mark's presentation?
>
> I believe so.
Frank (virtually) and I (in person) will give a presentation on:
Sourceware GNU Toolchain Infrastructure and beyond
https://gcc.gnu.org/wiki/cauldron2022#cauldron2022talks.sourceware_gnu_toolchain_infrastructure_and_beyond
The Sourceware infrastructure is continually improving. Just like
our other services, such as bugzilla, mailinglists and git repos,
we like to provide zero maintenance infrastructure for tracking and
automation of patches, testing and analyzing testresults.
This BoF is for everybody who likes to discuss (and wants to help
with) automating the infrastructure to make contributing to our
projects more fun and more productive.
Topics to discuss include the shared buildbot. Whether we need
more/other arches/distro support. Which builders are most beneficial
to projects. How buildbot should report issues. Whether to use the
buildbot to automate other tasks like updating documentation,
websites, generate release tars or updating bugzilla. How to use git
user try branches. Taking advantage of the Bunsen testrun cluster
analysis, per-testrun testcase search/browse engines, search
operators, testsuite summary (vs detail) grids. Patch tracking using
patchwork integrated with buildbot and the CICD trybot. How to use
the sourcehut mirror. And anything else that would make you more
productive and happy contributing.
(I see the official description doesn't mention public-inbox, but I
prepared some examples and would love to discuss whether and how people
are using it.)
So we really want to concentrate on discussing having fun contributing
to the various sourceware projects. But if the sourceware application
to be a Conservancy member project is approved by then we can also
discuss that (not implying that fiscal sponsorship isn't a fun topic,
but I suspect most hackers will be interested in discussing technical
stuff).
Cheers,
Mark
next prev parent reply other threads:[~2022-09-02 11:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 19:18 Marc
2022-09-01 19:47 ` Frank Ch. Eigler
2022-09-01 20:47 ` Christopher Faylor
2022-09-02 11:10 ` Mark Wielaard [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-30 18:03 Frank Ch. Eigler
2022-09-01 14:19 ` Elena Zannoni
2022-09-01 18:10 ` Christopher Faylor
2022-09-02 10:14 ` Mark Wielaard
2022-09-01 18:45 ` Corinna Vinschen
2022-09-01 18:54 ` Frank Ch. Eigler
2022-09-02 10:51 ` Mark Wielaard
2022-09-02 11:47 ` Mark Wielaard
2022-09-05 12:20 ` Dodji Seketeli
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=330c51b943d7cfc9921da9adcda9e5181e28024b.camel@klomp.org \
--to=mark@klomp.org \
--cc=dkm@kataplop.net \
--cc=fche@redhat.com \
--cc=overseers@sourceware.org \
--cc=pono@sfconservancy.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).