[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Automation & Systematization sprint in Berlin in late April
From:       Ben Cooksley <bcooksley () kde ! org>
Date:       2024-02-01 9:46:58
Message-ID: CA+XidOHVbECLdos3eBePaPr0WdVmpPmirMgc+_AO-PeGRdi=hA () mail ! gmail ! com
[Download RAW message or body]

On Thu, Feb 1, 2024 at 12:26 PM Nate Graham <nate@kde.org> 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

[Attachment #3 (text/html)]

<div dir="ltr"><div dir="ltr">On Thu, Feb 1, 2024 at 12:26 PM Nate Graham &lt;<a \
href="mailto:nate@kde.org">nate@kde.org</a>&gt; wrote:<br></div><div \
class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello folks!<br> <br>
I&#39;d like to gauge interest in an in-person sprint supporting the <br>
Automation &amp; Systematization goal. Right now we are targeting Berlin on <br>
April 19th - April 24th. KDE e.V. has budget available to help with <br>
travel and lodging costs.<br>
<br>
This will be a triple-threat sprint, with the Accessibility and <br>
Sustainability sprints co-located. People interested in multiple topics <br>
will be able to jump between them if they want.<br>
<br>
Topics for the Automation &amp; Systematization sprint might include:<br>
- Writing tests<br>
- Fixing failing tests<br>
- Making tests mandatory to pass<br>
- Documenting how to write good tests<br>
- Updating outdated documentation<br>
- Transition documentation to code (e.g. making kdesrc-build or the new <br>
kde-builder tool do more itself, so we don&#39;t have to write so much about <br>
it in our documentation)<br>
- Make a push for enabling clang-format for more repos<br>
- Make a push to put release notes in AppStream metadata<br>
- Improve our AppStream CI job to require or recommend more \
things</blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px \
                0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
- Make a CI job to enforce as much of the onboarding/new repo checklist <br>
as possible, and make enabling it be a part of the process<br>
<br>
These are just ideas; the folks who attend will be the ones who guide <br>
the agenda.<br></blockquote><div><br></div><div>If this ends up happening, please do \
keep me in the loop on what you&#39;re thinking of building so I can provide the \
necessary guidance to make it easy to deploy things that are built :)</div><div>  \
</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px \
solid rgb(204,204,204);padding-left:1ex"> <br>
Let me know if you&#39;re interested so I can get a sense of the level of <br>
attendance!<br>
<br>
<br>
Nate<br></blockquote><div><br></div><div>Cheers,</div><div>Ben  </div></div></div>



[prev in list] [next in list] [prev in thread] [next in thread]