<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Le 31/03/2016 12:07, <a class="moz-txt-link-abbreviated" href="mailto:kde-community-request@kde.org">kde-community-request@kde.org</a> a écrit :<br>
<blockquote
cite="mid:mailman.86252.1459418836.22121.kde-community@kde.org"
type="cite">
<pre wrap="">Message: 8
Date: Thu, 31 Mar 2016 12:06:50 +0200
From: Luigi Toscano <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="mailto:luigi.toscano@tiscali.it"><luigi.toscano@tiscali.it></a>
To: <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:kde-community@kde.org">kde-community@kde.org</a>
Cc: <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:kde-devel@kde.org">kde-devel@kde.org</a>, KDE Sysadmin Help Desk <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="mailto:sysadmin@kde.org"><sysadmin@kde.org></a>
Subject: Re: [kde-community] Our new project metadata system
Message-ID: <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="mailto:5718636.mFtRzCLg3p@whitebase.usersys.redhat.com"><5718636.mFtRzCLg3p@whitebase.usersys.redhat.com></a>
Content-Type: text/plain; charset="us-ascii"
On Thursday 31 of March 2016 13:55:03 Boudhayan Gupta wrote:
</pre>
<blockquote type="cite" style="color: #000000;">
<pre wrap=""><span class="moz-txt-citetags">> </span>Hi all,
<span class="moz-txt-citetags">> </span>
<span class="moz-txt-citetags">> </span>Over the last few weekends we've been doing some spring-cleaning to
<span class="moz-txt-citetags">> </span>our infrastructure. You may have noticed that we've killed off
<span class="moz-txt-citetags">> </span>projects.kde.org, and we have new scripts that generate our
<span class="moz-txt-citetags">> </span>kde_projects.xml without having to depend on ChiliProject now. We're
<span class="moz-txt-citetags">> </span>also planning to deprecate kde_projects.xml itself, and to that effect
<span class="moz-txt-citetags">> </span>we've started setting up a JSON/REST API at
<span class="moz-txt-citetags">> </span><a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://apps.kde.org/api/v1/">https://apps.kde.org/api/v1/</a>.
<span class="moz-txt-citetags">> </span>
<span class="moz-txt-citetags">> </span>The same infrastructure that is used to generate data for our API and
<span class="moz-txt-citetags">> </span>the XML file can be used to generate a HTML website with landing pages
<span class="moz-txt-citetags">> </span>for our applications, and this is something we intend to do in the
<span class="moz-txt-citetags">> </span>coming months as a replacement for the outdated kde.org/applications
<span class="moz-txt-citetags">> </span>site. To achieve that, however, we're going to need some help from
<span class="moz-txt-citetags">> </span>you.
<span class="moz-txt-citetags">> </span>
<span class="moz-txt-citetags">> </span>Our project metadata is currently held in the sysadmin/repo-metadata
<span class="moz-txt-citetags">> </span>repository. We currently hold data about the project name, repository
<span class="moz-txt-citetags">> </span>and a one-line description of each project. We would like maintainers
<span class="moz-txt-citetags">> </span>and anyone who can help to provide us with three things for every
<span class="moz-txt-citetags">> </span>project - a <b class="moz-txt-star"><span class="moz-txt-tag">*</span>description.md<span class="moz-txt-tag">*</span></b> file with a bigger description of each
<span class="moz-txt-citetags">> </span>project that appears on the website, and for applications with a GUI,
<span class="moz-txt-citetags">> </span>a <b class="moz-txt-star"><span class="moz-txt-tag">*</span>screenshot.png<span class="moz-txt-tag">*</span></b> file with a screenshot of the app and two icons (a
<span class="moz-txt-citetags">> </span>256 * 256 px icon.png and a 512 * 512px icon_2x.png).
</pre>
</blockquote>
<pre wrap="">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?
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://marc.info/?l=kde-core-devel&m=138348776618380&w=2">http://marc.info/?l=kde-core-devel&m=138348776618380&w=2</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://marc.info/?l=kde-core-devel&m=138349411519937&w=2">http://marc.info/?l=kde-core-devel&m=138349411519937&w=2</a>
And also, more recent:
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://mail.kde.org/pipermail/kde-community/2015q4/002132.html">https://mail.kde.org/pipermail/kde-community/2015q4/002132.html</a>
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
<div class="moz-txt-sig">--
Luigi
</div></pre>
</blockquote>
<div class="moz-txt-sig">
</div>
Hi,<br>
<br>
During the CERN Sprint we worked with Alex Merry on something
similar, without knowing you were doing the same. Our idea is to
have all metadata to generate a comprehensive api.kde.org.<br>
<br>
You can see the notes here: <a class="moz-txt-link-freetext" href="https://notes.kde.org/p/apidox">https://notes.kde.org/p/apidox</a> (please
do not edit, even if I have a copy). I'm currently working on the
the script that could generate the doxygen documentation from this,
before releasing the proposition.<br>
<br>
These "config.apidox" files should just add infos that are not in
"metadata.yaml". Maybe we should work together to have one global
system, that can be used by everyone?<br>
<br>
If it's not related to the topic, then sorry for the noise :S<br>
<br>
Cheers,<br>
Olivier<br>
</body>
</html>