discussion#555 should be made to look like it's no longer active, with more blatant link to current "project"16
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- html
- Domain
- documentation
Research direction
Start with discussion #555 and inspect its current closed notice and table presentation. Compare it with project 16, then make the obsolete content visibly inactive and add a prominent link to the current project; done means a returning reader can immediately understand that #555 is no longer active and where current information lives.
Written by the indexing model from the issue text.
Description
Originally posted by @TallTed in https://github.com/solid/specification/pull/633#pullrequestreview-1920706382
Note that #555 still looks alive. Someone coming back to it, to see the latest addition to the bottom of the table, won't necessarily see the top-posted notice that it's been closed with new info being posted at https://github.com/orgs/solid/projects/16. I suggest adding <strike> or similar markup to make clear what is no longer valid.
Also note that https://github.com/orgs/solid/projects/16 requires more thinking, parsing the date column which is no longer in ISO-numerics, figuring out that "status — done" means the meeting has been held... and now, it's even more challenging, because the last dated entry is (was) March 5 (which is now in the past) and shows status "discussed" instead of "done" or at least "scheduled" which seem to make more sense for a date in the past....
attn @csarven @VirginiaBalseiro
- Dominant language
- HTML
- Stars
- 563
- Forks
- 111
- Avg merge
- 5d 7m
- Merged PRs (30d)
- 3
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from solid/specification
-
new-work-item
Difficulty 5/5 Over a week Newbie friendliness 25/100
solid/specification#806 · 11 comments · 4 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
solid/specification#804 · 9 comments · 2 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
solid/specification#799 · 1 reaction ·
-
topic: resource access
Difficulty 5/5 Over a week Newbie friendliness 30/100
solid/specification#797 · 4 comments · 2 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
solid/specification#788 · 4 comments · 1 reaction ·
All issues in solid/specification
Similar issues
-
sync-en
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
sync-en
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 3 days
-
bug developer portal
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
discord/discord-api-docs#8645 ·
Maintainers usually reply within 1 day
-
Form
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
symfony/symfony-docs#23159 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day