Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
48 hours seems more reasonable
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Surely one of six of the Editors can check the occasional website suggestions once every 24 hours. Perhaps you could arrange it between yourselves to take turns so you only have to check once every six days.
If that's too much of a burden then an alternative could be to trust the Creators to review the website suggestions as long as they are technically in line with previously approved website suggestions. If suggestions are not technically in line with previously approved website suggestions then it could go to the Editors for review.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Several things are problematic with this, I will list the most important ones below:
The assumption that the problem would be related to editors reacting slowly. There seems to be plenty of evidence to the contrary, including https://github.com/solid/solidproject.org/pulls?q=is%3Apr+is%3Aclosed+reviewed-by%3Arubenverborgh
The assumption that there would be a trust problem, as opposed to a quality check that is very common in open-source projects (hence the built-in review functionality in GitHub).
As such, I propose that we first aim to understand what exactly is causing slowdowns, before trying to fix anything. Clearly, the two assumed causes (slow editors / lack of positive feedback) are not the correct ones; hence, this fix can't be the correct one either. Also, note that the issues in #217 are considered to be addressed by the existing process, which simply is not followed consistently. I have created and assigned this issue to identify the causes: #226