[kde-community] Our new project metadata system

Jaroslaw Staniek staniek at kde.org
Thu Mar 31 10:44:00 UTC 2016


+1 for using wider accepted standards, whatever they are, and making life
of distros easier too.

On 31 March 2016 at 12:06, Luigi Toscano <luigi.toscano at tiscali.it> wrote:

> On Thursday 31 of March 2016 13:55:03 Boudhayan Gupta wrote:
> > Hi all,
> >
> > Over the last few weekends we've been doing some spring-cleaning to
> > our infrastructure. You may have noticed that we've killed off
> > projects.kde.org, and we have new scripts that generate our
> > kde_projects.xml without having to depend on ChiliProject now. We're
> > also planning to deprecate kde_projects.xml itself, and to that effect
> > we've started setting up a JSON/REST API at
> > https://apps.kde.org/api/v1/.
> >
> > The same infrastructure that is used to generate data for our API and
> > the XML file can be used to generate a HTML website with landing pages
> > for our applications, and this is something we intend to do in the
> > coming months as a replacement for the outdated kde.org/applications
> > site. To achieve that, however, we're going to need some help from
> > you.
> >
> > Our project metadata is currently held in the sysadmin/repo-metadata
> > repository. We currently hold data about the project name, repository
> > and a one-line description of each project. We would like maintainers
> > and anyone who can help to provide us with three things for every
> > project - a *description.md* file with a bigger description of each
> > project that appears on the website, and for applications with a GUI,
> > a *screenshot.png* file with a screenshot of the app and two icons (a
> > 256 * 256 px icon.png and a 512 * 512px icon_2x.png).
>
> I don't think we need to do this; we have AppStream metadata.
>
> Long time ago it was in fact discussed how to not duplicate the information
> between the json on the website and the AppStream metadata. There was some
> idea on how to generate one from the other. Check this old thread on
> kde-core-
> devel, from November 2013 ("Adopting AppData in KDE?
> http://marc.info/?l=kde-core-devel&m=138348776618380&w=2
> http://marc.info/?l=kde-core-devel&m=138349411519937&w=2
>
> And also, more recent:
> https://mail.kde.org/pipermail/kde-community/2015q4/002132.html
>
> Now, whether we like them or not, those metadata are already available and
> going to stay. I don't think we want to duplicate again the same set of
> data
> for the website.
>
> I would say then to use them for the website, adding the missing files in
> the
> process (most of applications are already covered).
>
> Ciao
> --
> Luigi
> _______________________________________________
> kde-community mailing list
> kde-community at kde.org
> https://mail.kde.org/mailman/listinfo/kde-community
>



-- 
regards, Jaroslaw Staniek

KDE:
: A world-wide network of software engineers, artists, writers, translators
: and facilitators committed to Free Software development - http://kde.org
Calligra Suite:
: A graphic art and office suite - http://calligra.org
Kexi:
: A visual database apps builder - http://calligra.org/kexi
Qt Certified Specialist:
: http://www.linkedin.com/in/jstaniek
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-community/attachments/20160331/e4762a80/attachment.html>


More information about the kde-community mailing list