From kde-devel Thu Feb 01 09:46:58 2024 From: Ben Cooksley Date: Thu, 01 Feb 2024 09:46:58 +0000 To: kde-devel Subject: Re: Automation & Systematization sprint in Berlin in late April Message-Id: X-MARC-Message: https://marc.info/?l=kde-devel&m=170678075925396 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--0000000000000df97006104ee131" --0000000000000df97006104ee131 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Feb 1, 2024 at 12:26=E2=80=AFPM Nate Graham wrote: > Hello folks! > > I'd like to gauge interest in an in-person sprint supporting the > Automation & Systematization goal. Right now we are targeting Berlin on > April 19th - April 24th. KDE e.V. has budget available to help with > travel and lodging costs. > > This will be a triple-threat sprint, with the Accessibility and > Sustainability sprints co-located. People interested in multiple topics > will be able to jump between them if they want. > > Topics for the Automation & Systematization sprint might include: > - Writing tests > - Fixing failing tests > - Making tests mandatory to pass > - Documenting how to write good tests > - Updating outdated documentation > - Transition documentation to code (e.g. making kdesrc-build or the new > kde-builder tool do more itself, so we don't have to write so much about > it in our documentation) > - Make a push for enabling clang-format for more repos > - Make a push to put release notes in AppStream metadata > - Improve our AppStream CI job to require or recommend more things - Make a CI job to enforce as much of the onboarding/new repo checklist > as possible, and make enabling it be a part of the process > > These are just ideas; the folks who attend will be the ones who guide > the agenda. > If this ends up happening, please do keep me in the loop on what you're thinking of building so I can provide the necessary guidance to make it easy to deploy things that are built :) > > Let me know if you're interested so I can get a sense of the level of > attendance! > > > Nate > Cheers, Ben --0000000000000df97006104ee131 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, Feb 1, 2024 at 12:26=E2=80=AFPM N= ate Graham <nate@kde.org> wrote:<= br>
Hello folks!

I'd like to gauge interest in an in-person sprint supporting the
Automation & Systematization goal. Right now we are targeting Berlin on=
April 19th - April 24th. KDE e.V. has budget available to help with
travel and lodging costs.

This will be a triple-threat sprint, with the Accessibility and
Sustainability sprints co-located. People interested in multiple topics will be able to jump between them if they want.

Topics for the Automation & Systematization sprint might include:
- Writing tests
- Fixing failing tests
- Making tests mandatory to pass
- Documenting how to write good tests
- Updating outdated documentation
- Transition documentation to code (e.g. making kdesrc-build or the new kde-builder tool do more itself, so we don't have to write so much abou= t
it in our documentation)
- Make a push for enabling clang-format for more repos
- Make a push to put release notes in AppStream metadata
- Improve our AppStream CI job to require or recommend more things
- Make a CI job to enforce as much of the onboarding/new repo checklist as possible, and make enabling it be a part of the process

These are just ideas; the folks who attend will be the ones who guide
the agenda.

If this ends up happening, = please do keep me in the loop on what you're thinking of building so I = can provide the necessary guidance to make it easy to deploy things that ar= e built :)
=C2=A0

Let me know if you're interested so I can get a sense of the level of <= br> attendance!


Nate

Cheers,
Ben=C2=A0
<= /div>
--0000000000000df97006104ee131--