Re: Defining a developer name for our applications metadata

2024-02-02 Thread Johannes Zarl-Zierl
Hi Albert,

Am Dienstag, 30. Jänner 2024, 22:27:22 CET schrieb Albert Astals Cid:
> "The KDE Community" is like "ATM Machine", KDE is *already* the community.

I have to say this is definitely *not* like "ATM Machine". At least I hope 
nobody is saying "the C in KDE stands for Community"... ;-)

Apart from that nitpick, no objection from me on either variant.

Cheers,
  Johannes






Re: Defining a developer name for our applications metadata

2024-02-02 Thread Timothée Ravier
On Fri, Feb 2, 2024 at 5:08 PM Johnny Jazeix  wrote:

> Hi,
>
> Just to be sure, do we know which appstream version do we use to validate
> our appdata files (
> https://invent.kde.org/frameworks/extra-cmake-modules/-/blob/master/kde-modules/appstreamtest.cmake)
> and if the deprecated tag will issue a warning, an error or nothing in it?
>
> Cheers,
>
> Johnny
>

I've tested that `appstreamcli validate` gives no error/warning for this
tag on Fedora 39 & Rawhide (appstream 0.16.1 & 1.0.1) and Ubuntu 20.04
(0.12.10). The deprecation is only an info (not a warning) on appstream
1.0.1.

See also the Developer section from
https://planet.kde.org/matthias-klumpp-2023-11-11-appstream-1-0-released/.

-- 

Timothée Ravier

CoreOS co-Team Lead

Red Hat 

trav...@redhat.com



Re: Defining a developer name for our applications metadata

2024-02-02 Thread Johnny Jazeix
Hi,

Just to be sure, do we know which appstream version do we use to validate
our appdata files (
https://invent.kde.org/frameworks/extra-cmake-modules/-/blob/master/kde-modules/appstreamtest.cmake)
and if the deprecated tag will issue a warning, an error or nothing in it?

Cheers,

Johnny


Le ven. 2 févr. 2024 à 16:56, Timothée Ravier  a écrit :

> Hi everyone,
>
> Following suggestions in the thread, I'll start updating our AppStream
> metadata with:
>
> ```
> KDE
> ```
>
> Thanks
> --
>
> Timothée Ravier
>
> CoreOS co-Team Lead
>
> Red Hat 
>
> trav...@redhat.com
> 
>


Re: Defining a developer name for our applications metadata

2024-02-02 Thread Nate Graham

Sounds good! Thanks for tackling this, Timothée.

Nate



On 2/2/24 08:55, Timothée Ravier wrote:

Hi everyone,

Following suggestions in the thread, I'll start updating our AppStream 
metadata with:


```
KDE
```

Thanks
--

Timothée Ravier

CoreOS co-Team Lead

Red Hat

trav...@redhat.com 





Re: Defining a developer name for our applications metadata

2024-02-02 Thread Timothée Ravier
Hi everyone,

Following suggestions in the thread, I'll start updating our AppStream
metadata with:

```
KDE
```

Thanks
-- 

Timothée Ravier

CoreOS co-Team Lead

Red Hat 

trav...@redhat.com



Re: Automation & Systematization sprint in Berlin in late April

2024-02-02 Thread Méven
I am interested as well.

Le jeu. 1 févr. 2024 à 23:55, Albert Astals Cid  a écrit :

> El dijous, 1 de febrer de 2024, a les 0:26:05 (CET), Nate Graham va
> escriure:
> > 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.
> >
> > Let me know if you're interested so I can get a sense of the level of
> > attendance!
>
> I am tentatively interested.
>
> Cheers,
>   Albert
>
> >
> >
> > Nate
>
>
>
>
>

-- 
Méven