Skip to content

docs: replace dead references in Ideas-2026 with live links#290

Open
shivv23 wants to merge 1 commit intosugarlabs:masterfrom
shivv23:fix-ideas-2026-broken-reference-links
Open

docs: replace dead references in Ideas-2026 with live links#290
shivv23 wants to merge 1 commit intosugarlabs:masterfrom
shivv23:fix-ideas-2026-broken-reference-links

Conversation

@shivv23
Copy link
Copy Markdown

@shivv23 shivv23 commented Mar 9, 2026

Summary

This updates dead references in Ideas-2026.md to currently reachable links.

What was fixed

  • Replaced three dead GTK4 "great headway" links (www.sugarlabs.org/news/...) with the existing Sugar GTK4 migration PR reference:
    • https://github.com/sugarlabs/sugar/pull/1019
  • Replaced one dead AI Reflection reference link (www.sugarlabs.org/news/...) with a live Music Blocks meeting reference that documents the reflection work:
    • https://wiki.sugarlabs.org/go/Music_Blocks/2025-03-16-meeting

Why

The previous URLs returned 404, which can confuse applicants reading project references.

Scope

  • Content-only docs change in Ideas-2026.md
  • No workflow/CI/infrastructure changes

@quozl
Copy link
Copy Markdown
Contributor

quozl commented Mar 9, 2026

The argument is a bit weak. URLs returning 404 should not confuse applicants of the quality we seek.

@shivv23
Copy link
Copy Markdown
Author

shivv23 commented Mar 9, 2026

Fair point — “confuse applicants” was overstated.

My goal here is simple documentation hygiene: the current references in Ideas-2026.md return 404, so readers can’t verify the claims or follow the context. Even strong applicants will just hit a dead end and waste time looking for the right material, and broken links also make the Ideas page look outdated.

This PR is content-only and replaces the dead news URLs with currently reachable references that document the same work (GTK4 migration progress via sugarlabs/sugar#1019, and the reflection work via https://wiki.sugarlabs.org/go/Music_Blocks/2025-03-16-meeting). If you’d prefer, I can remove the references instead of replacing them, but I thought keeping a working pointer was more useful.

@chimosky
Copy link
Copy Markdown
Member

chimosky commented Mar 9, 2026

Firstly, the reference isn't dead as the links load just fine.

Secondly, the context in which it is used is the right context for it, the replacement you've chosen isn't the right one for that context.

@quozl
Copy link
Copy Markdown
Contributor

quozl commented Mar 11, 2026

Eh, the links you are replacing are not 404. Please check your diffs.

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.

3 participants