Update Apache Thrift DOAP metadata - #3707
Open
kpumuk wants to merge 1 commit into
Open
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Updates Apache Thrift’s DOAP project metadata (doap.rdf) to use canonical HTTPS URLs (and non-trailing-slash paths where appropriate) so the Apache Projects directory links resolve correctly, while keeping the project’s published metadata accurate.
Changes:
- Switched DOAP project identifiers/links from
http://to canonicalhttps://for the project, homepage, and PMC URLs. - Updated mailing list and download page URLs to the canonical non-trailing-slash forms.
- Added
Rubyto the explicitprogramming-languagelist and normalized maintainer contact indentation.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Co-Authored-By: OpenAI Codex (GPT-5.6) <codex@openai.com>
kpumuk
force-pushed
the
rb-update-doap-metadata
branch
from
August 8, 2026 20:37
5dd1eb0 to
288f480
Compare
Contributor
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.
Suppressed comments (1)
doap.rdf:65
- The change from
<release rdf:parseType="Collection">to many standalone<release>elements materially changes the RDF structure for releases (RDF list vs repeated properties) and isn’t mentioned in the PR description. This could affect how downstream consumers (e.g., projects.apache.org tooling) interpret ordering or select the “latest” release. Either revert this structural change (keep the existingrdf:parseType="Collection"form) or explicitly justify it in the PR description with evidence that consumers still parse releases correctly.
<release>
<Version>
<name>Apache Thrift</name>
<created>2026-07-11</created>
<revision>0.24.0</revision>
</Version>
</release>
<release>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The mailing-list and download links currently published through the Apache Projects entry for Thrift resolve to 404 pages because the old DOAP values redirect to trailing-slash HTTPS URLs.
The releases section also shows only
0.2.0even though the DOAP file contains 30 releases. Apache Projects collapses the collection-style release block to its final entry instead of preserving each version.This update uses the canonical HTTPS project links and represents every version with a separate DOAP
releaseelement, allowing Apache Projects to publish the complete history from0.24.0through0.2.0. It also includes Ruby in the programming-language list and aligns the maintainer contact indentation. These metadata corrections do not change runtime code.Release structure rationale
The DOAP XML schema defines
releaseas a repeatable property, with each occurrence containing exactly oneVersion. Apache Projects' own DOAP generator emits the same structure.Although
rdf:parseType="Collection"is valid RDF/XML syntax, it givesdoap:releasea single RDF-list value. That is semantically different from defining 30doap:releaserelationships to 30 individualVersionresources. Apache Projects does not expand that RDF list: its DOAP-to-JSON parser indexes the nested elements by tag name, so eachVersionreplaces the previous one and only the final0.2.0entry survives.Representing each version with a separate
<release><Version>...</Version></release>element follows the DOAP schema, matches Apache Projects' supported input format, and produces all 30 release records without changing any release names, versions, or dates.[skip ci]anywhere in the commit message to free up build resources.