You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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....
Thanks for this. I marked #555 as ARCHIVED, and deleted the "Discussed" status from the board as it is indeed confusing. You're right we need to think of improvements to it, perhaps we can discuss in a meeting.
Originally posted by @TallTed in #633 (review)
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
The text was updated successfully, but these errors were encountered: