From: Alex Legler <a3li@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] RFC: moving API-related DTDs into api.gentoo.org
Date: Tue, 24 Mar 2015 13:52:22 +0100 [thread overview]
Message-ID: <55115E06.3040705@gentoo.org> (raw)
In-Reply-To: <20150324103736.2a43eb85@pomiot.lan>
[-- Attachment #1: Type: text/plain, Size: 1348 bytes --]
On 3/24/15 at 10:37 AM, Michał Górny wote:
> […]
> - metadata.dtd -- since it's used by different repositories and not
> really www.gentoo.org sites. It would be better if it had permanent
> api.gentoo.org URI for apps to fetch.
But neither has it really something to do with a file on api.g.o.
Its current URL on gentoo.org is just as permanent (even more so if it
isn't moved).
I fail to see the actual gain in moving it.
>
> - mirrors.dtd -- used for mirror XML files stored in api.gentoo.org,
...and on the main website still.
>
> - repositories.dtd -- used for repository XML files stored in a.g.o.
>
That is the one fitting addition from your examples.
> And we should move more DTD as soon as respective XML files are moved
> to api.gentoo.org.
Quickly looking through the current DTDs, none belong to any files or
services that should be moving to the api site, except maybe glsa.dtd,
but that has its own site now anyway.
>
> Thoughts?
>
Taking into account that not everything belonging to these DTDs is on
api.g.o, we would be even hurting permanence of the URLs by moving them,
and the overall lack of a clear gain, I'd keep them on gentoo.org in one
central DTD location, i.e. the current gentoo.org/dtd/.
That being said, I'm all for having a separate git hosting them.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2015-03-24 12:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 9:37 [gentoo-project] RFC: moving API-related DTDs into api.gentoo.org Michał Górny
2015-03-24 11:14 ` Ben de Groot
2015-03-24 12:52 ` Alex Legler [this message]
2015-06-02 15:38 ` Mike Frysinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55115E06.3040705@gentoo.org \
--to=a3li@gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox