dave2wave commented on issue #138:
URL:
https://github.com/apache/tooling-trusted-release/issues/138#issuecomment-2956356960
I agree that two locations are confusing. The other locations I meant are
the status quo. These are all variously advertised (or not) by PMCs. Having a
single place and switching switching silently could be confusing as well. I
suppose all the TLP websites content could be scanned for DOAP files or
references, and redirected or sent to PMCs respectively.
Also we could deprecate as Greg suggests.
Some possible locations:
1. d.a.o/projects/{committee}}/{{project}}.[yaml,xml]
2. d.a.o/{committee}}/{{project}}.[yaml,xml]
3. releases.a.o/{committee}}/{{project}}.[yaml,xml]
I think that `releases.apache.org` is best and really aligns as ATR metadata.
BTW - See https://en.wikipedia.org/wiki/DOAP
Other Foundations use DOAP so it's not just a question of the ASF's
consumption.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@tooling.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tooling.apache.org
For additional commands, e-mail: dev-h...@tooling.apache.org
