Don't know what was happening before but it seems to fixed now.
On Wed, Jun 26, 2019, 8:11 AM Michael Reeves wrote:
> Why does every page contain a self referential home page link. If no
> homepage is provided why make this a link at all.
>
> On Wed, Jun 26, 2019, 4:35 AM Kevin Funk wrote:
>
Why does every page contain a self referential home page link. If no
homepage is provided why make this a link at all.
On Wed, Jun 26, 2019, 4:35 AM Kevin Funk wrote:
> On Wednesday, 5 June 2019 13:07:35 CEST Jonathan Riddell wrote:
> > The new KDE Applications website is now up
> >
> >
On Wednesday, 5 June 2019 13:07:35 CEST Jonathan Riddell wrote:
> The new KDE Applications website is now up
>
> https://kde.org/applications/
>
> The old one was a manual task of keeping the metadata up to date while this
> one scans builds from build.kde.org and git in search of appstream
>
They are ignored if they are in Playground or KDE Review. Once past KDE
Review they will appear on that website as long as they have the required
appstream .xml and .desktop files.
(The site is updated nightly on the binary-factory job.)
Jonathan
On Thu, 6 Jun 2019 at 10:47, Alexander
Hi Jonathan,
How would you handle the apps being developed (thus, not
"unmaintained") that have a Git repository, but not released yet?
ср, 5 июн. 2019 г. в 14:08, Jonathan Riddell :
>
> The new KDE Applications website is now up
>
> https://kde.org/applications/
>
> The old one was a manual
Awesome! Having it automated goes a long way in helping it stay updated.
Thank you for your hard work!
--
Regards,
Juan Carlos Torres
Jucato
On Wed, 5 Jun 2019 12:07:35 +0100
Jonathan Riddell wrote:
> The new KDE Applications website is now up
>
> https://kde.org/applications/
>
> The old one was a manual task of keeping the metadata up to date while this
> one scans builds from build.kde.org and git in search of appstream
>
Great work!
On woensdag 5 juni 2019 13:07:35 CEST Jonathan Riddell wrote:
> The new KDE Applications website is now up
>
> https://kde.org/applications/
>
> The old one was a manual task of keeping the metadata up to date while this
> one scans builds from build.kde.org and git in search of
