Hi, On Fri, Sep 8, 2023 at 12:26 AM sebb <seb...@gmail.com> wrote: > ...I think it would be worth considering setting up a central store for > DOAPs...
As we require our projects to have a website anyway, wouldn't it be better to get that information from the project's homepage instead of a separate file ? As you mention, I think it's only the fields that rarely change that are actually useful: the project's description, a few useful URLs, programming language, communications channel URLs, project category, code repository and download URLs, that's probably all we need ? That info can be embedded in HTML, for example using <meta> elements, Open Graph [1] maybe, with some ASF-specific extensions such as og:asf:category ? This would put the information in a natural place for projects to maintain it, and Open Graph metadata has other benefits. OTOH this means writing a conversion layer that, starting from a list of *.apache.org subdomain names, grabs that data and converts it to a format that's useful for projects.a.o. Another option would be to embed the current DOAP format using a <script> element with a specific type, example at [2]. That simplifies the conversion layer but it's less convenient to manage at the website level. -Bertrand [1] https://ogp.me/ [2] https://gist.github.com/bdelacretaz/66b72523c15cc5d8cb28ae7eeac2b7c3 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
