<div dir="ltr"><div dir="ltr">On Thu, Dec 19, 2024 at 7:11 PM Justin Zobel <<a href="mailto:justin@1707.io">justin@1707.io</a>> wrote:</div><div class="gmail_quote gmail_quote_container"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><u></u>
<div>
<p>Hey Everyone,</p>
<p>Thanks for all the input. Sorry I've been out for a few days, my
wife and I were busy and welcomed into our life our baby girl
Isla.</p>
<p>I would like to propose the following based on all of the
feedback and my own thoughts:</p>
<p>- Main page of <a href="http://apps.kde.org" target="_blank">apps.kde.org</a> it will by default only show apps
that are active. This data will come from the lifecycle status in
repo metadata.</p>
<p>- A filter on the front page of <a href="http://apps.kde.org" target="_blank">apps.kde.org</a> with tickboxes:
Status: [x] Active [ ] Beta [ ] Archived(Unmaintained)</p>
<p>- On each app page it will show the status of the app: Actively
Developed, Beta or Archived so users know what to expect if they
do try it.</p></div></blockquote><div><br></div><div>These all sound good to me.</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"><div>
<p>- Add appstream metadata file location to the repo metadata. For
example org.kde.kate: utilities/kate/org.kde.kate.appdata.xml<br></p></div></blockquote><div><br></div><div>Where is this location relative to sorry?</div><div>Note that some repositories have multiple appstream files in them due to providing separate plugins or multiple versions of their application (which distros ship as separate packages)</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"><div><p>
</p>
<p>- Encourage developers to use our mailing lists or KDE Discuss to
announce the new app they're working on and intending to be part
of the KDE umbrella.</p>
<p><br>
</p>
<p>Specific replies:<br>
</p>
<p>> I'll also note that user namespaces are not writable to all
developers<br>
<br>
Anyone can still fork pubic repositories if they wish to
contribute.<br>
<br>
> Probably I'm one of the reasons this discussion started.<br>
<br>
This did prompt the discussion but it wasn't the trigger, I had
been thinking about this for a while.</p>
<p>Regards, </p></div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
<p>Justin<br></p></div></blockquote><div><br></div><div>Cheers,</div><div>Ben</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"><div><p>
</p>
<div>On 9/12/24 01:50, Phu Hung Nguyen
wrote:<br>
</div>
<blockquote type="cite">
<blockquote type="cite">
<pre>Date: Sun, 08 Dec 2024 12:36:26 +0100
From: Albert Astals Cid <a href="mailto:aacid@kde.org" target="_blank"><aacid@kde.org></a>
To: Ben Cooksley <a href="mailto:bcooksley@kde.org" target="_blank"><bcooksley@kde.org></a>
Cc: <a href="mailto:kde-devel@kde.org" target="_blank">kde-devel@kde.org</a>
Subject: Re: New Application Status
Message-ID: <9526941.xt29fcdmcD@xps15>
Content-Type: text/plain; charset="utf-8"
El divendres, 6 de desembre del 2024, a les 19:27:32 (Hora estàndard del
Centre d’Europa), Ben Cooksley va escriure:
</pre>
<blockquote type="cite">
<pre>On Fri, Dec 6, 2024 at 9:37 AM Albert Astals Cid <a href="mailto:aacid@kde.org" target="_blank"><aacid@kde.org></a> wrote:
</pre>
<blockquote type="cite">
<pre>El dijous, 5 de desembre del 2024, a les 13:57:26 (Hora estàndard del
Centre
d’Europa), Ingo Klöcker va escriure:
</pre>
<blockquote type="cite">
<pre>On Donnerstag, 5. Dezember 2024 10:27:13 Mitteleuropäische Normalzeit
Ben
Cooksley wrote:
</pre>
<blockquote type="cite">
<pre>Trying to coming full circle on this here, but in summary sounds like
there
are a couple of things to change going forward:
* For <a href="http://apps.kde.org" target="_blank">apps.kde.org</a>, we should flag applications in accordance with
</pre>
</blockquote>
</blockquote>
<pre>their
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre>Lifecycle status in the metadata (ie. unmaintained and those yet to
</pre>
</blockquote>
</blockquote>
<pre>pass
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre>KDE Review should be flagged in some form or another)
</pre>
</blockquote>
<pre>Yes. For beta apps. I'd say for unmaintained apps there shouldn't be a
</pre>
</blockquote>
<pre>page
</pre>
<blockquote type="cite">
<pre>on <a href="http://apps.kde.org" target="_blank">apps.kde.org</a>. Given that there won't be build artifacts for
</pre>
</blockquote>
<pre>unmaintained
</pre>
<blockquote type="cite">
<pre>apps (at least not for long) there is anyway no AppStream data for
</pre>
</blockquote>
<pre>creating
</pre>
<blockquote type="cite">
<pre>such a page.
</pre>
</blockquote>
<pre>In my opinion once a page exists it needs to exist forever.
Imagine Okular goes unmaintained, I don't want the lots of pages pointing
to
<a href="https://apps.kde.org/okular/" target="_blank">https://apps.kde.org/okular/</a> to suddenly point to a 404
I want to see a page that says "This is unmaintained" but still has the
old
contents.
</pre>
</blockquote>
<pre>Continuing to have pages for unmaintained applications sounds okay, subject
to appstream metadata being available (not a given as we source them from
CI artifacts right now).
We probably wouldn't want to list unmaintained applications on say the
front page of <a href="http://apps.kde.org" target="_blank">apps.kde.org</a> or the category lists though?
</pre>
</blockquote>
<pre>Clearly not on the front page, probably not on category lists though (Maybe
having their own "unmaintained category" in case people want to adopt them?)
</pre>
</blockquote>
<span style="white-space:pre-wrap">
</span>
<p><span style="white-space:pre-wrap">We are already having a "Unmaintained" category page, <a href="https://apps.kde.org/categories/unmaintained/" target="_blank">https://apps.kde.org/categories/unmaintained/</a> or <a href="https://apps.kde.org/unmaintained/" target="_blank">https://apps.kde.org/unmaintained/</a>. This isn't linked to from the page of categories <a href="https://apps.kde.org/categories/" target="_blank">https://apps.kde.org/categories/</a>, it's only linked to from pages of unmaintained apps, e.g. <a href="https://apps.kde.org/choqok/" target="_blank">https://apps.kde.org/choqok/</a></span></p>
<p><span style="white-space:pre-wrap">For apps that don't have their artifacts and repos available anymore, we store their appdata and desktop files inside the repo <a href="https://invent.kde.org/websites/apps-kde-org/-/tree/master/appdata-extractor/appdata-unmaintained?ref_type=heads" target="_blank">https://invent.kde.org/websites/apps-kde-org/-/tree/master/appdata-extractor/appdata-unmaintained?ref_type=heads</a>
</span></p>
</blockquote>
</div>
</blockquote></div></div>