solid / solid/specification

discussion#555 should be made to look like it's no longer active, with more blatant link to current "project"16

Open
#635 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
563
Forks
108
Avg merge
4d 13h
Merged PRs (30d)
3

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

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.

Assessment

Tech stack
html
Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.