Skip to content

Fix a dead repository URL, an unresolvable homepage, and four stale project links - #31

Open
asish-singh wants to merge 1 commit into
aaif:mainfrom
asish-singh:fix/stale-and-broken-landscape-urls
Open

Fix a dead repository URL, an unresolvable homepage, and four stale project links#31
asish-singh wants to merge 1 commit into
aaif:mainfrom
asish-singh:fix/stale-and-broken-landscape-urls

Conversation

@asish-singh

Copy link
Copy Markdown

What

Fixes one repository URL that returns 404, one homepage that no longer resolves, and four links pointing at organisation or domain names the projects have moved away from.

How these were found

I requested every homepage_url and repo_url in landscape/landscape.yml, 51 URLs across 33 items, following redirects and recording the final URL.

Item Field Was Now Reason
A2A Protocol repo_url github.com/Agent2Agent/specification github.com/a2aproject/A2A 404. a2aproject/A2A is also what the published aaif/aaif-landscape uses
A2A Protocol homepage_url github.com/Agent2Agent a2a-protocol.org pointed at a GitHub organisation page that holds one unrelated repository
OpenHands homepage_url openhands.ai www.openhands.dev no DNS record
OpenHands repo_url All-Hands-AI/OpenHands OpenHands/OpenHands repository moved
CrewAI repo_url joaomdmoura/crewAI crewAIInc/crewAI owner renamed
NeMo Guardrails repo_url NVIDIA/NeMo-Guardrails NVIDIA-NeMo/Guardrails owner renamed
NeMo Guardrails homepage_url same value as repo_url docs.nvidia.com/nemo/guardrails/ the entry carried the repository URL in both fields
Braintrust homepage_url www.braintrustdata.com www.braintrust.dev domain moved
Meta Llama Guard homepage_url ai.meta.com/llama/ developer.meta.com/ai/llama-protections/ the old link now lands on a generic page rather than the protections page

All nine replacement URLs return HTTP 200 with no redirect.

The four renames still redirect, so those four are about the data being current rather than about a broken link. The A2A repository URL and the OpenHands homepage are the two that genuinely do not work.

Left alone deliberately

Six cosmetic redirects (adding www, adding a trailing slash, a deeper docs path) still resolve correctly, so changing them would add churn without adding accuracy.

The ISO 42001 link returns 403 to any automated request, including with a browser user agent. It works for a human, so it is not a broken link and I have not touched it.

One thing for the editors rather than for this PR

A2A carries project: external here, while aaif/project-proposals#37 shows the A2A proposal as TC Approved with the contribution agreement signed. Whether that changes the marker is an editor call, so this PR only fixes the URLs.

Validation

landscape/landscape.yml still parses, and every item across all categories keeps its required name, homepage_url, description and project fields, with project within the allowed values. Nine lines changed in one file, no entries added or removed.

Verified every homepage_url and repo_url in landscape/landscape.yml by
request. Two entries no longer resolve and four point at organisation or
domain names the projects have since moved away from.

A2A: repo_url github.com/Agent2Agent/specification returns 404, and
homepage_url pointed at a GitHub organisation page rather than the
project site. The project lives at a2aproject/A2A with the site at
a2a-protocol.org, which is also what the published aaif/aaif-landscape
entry uses.

OpenHands: openhands.ai does not resolve (no DNS record), and the
repository moved from All-Hands-AI/OpenHands to OpenHands/OpenHands.

CrewAI, NeMo Guardrails: repository owners renamed to crewAIInc and
NVIDIA-NeMo. The old paths still redirect, so this is about the data
being current rather than about a broken link.

Braintrust, Meta Llama Guard: homepage domains moved to braintrust.dev
and to the Llama protections page on developer.meta.com.

NeMo Guardrails also carried the same URL in homepage_url and repo_url,
so homepage_url now points at the documentation site.

All nine replacement URLs return HTTP 200 without a redirect. The file
still parses and every item keeps its required fields.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants