hboutemy commented on issue #138: URL: https://github.com/apache/tooling-trusted-release/issues/138#issuecomment-2956427863
DOAP or other format I don't care: I do care about the data that is carried DOAP being a standard format means we don't know who consumes it: we consume it in projects.a.o, but others may aggregate (I'd like to know, honestly, if where that semantic web idea went...) our current implementation of DOAP, by being overly flexible in the location for storage, creates an additional complexity: I'd be in favor of creating an ASF standard for location to avoid that and as written in #117, most [fields of DOAP](https://projects.apache.org/create.html) are static: there is only the release data that is updated on each release => having ATR, as THE source for release info, automatically inject releases to full DOAP would be a great win full DOAP info = base static DOAP info + release info (from ATR) with that equation: - base static DOAP info could be managed in .asf.yaml by PMCs (people will be happy: it's not XML :) ) - release info is lead by ATR - ATR could publish full DOAP files (this time in standard DOAP format) by merging the 2 sources to a formally structured download area, like everything related to releases -- 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
