Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
Post History
A tag on the community meta should reflect the status as experienced by the community. A change in tag should communicate a change in experience. This allows users to provide feedback (it's working...
Answer
#2: Post edited
by
Sigma
·
2020-09-04T14:31:06Z (about 4 years ago)
- A tag on the community meta should reflect the status as experienced by the community. A change in tag should communicate a change in experience. This allows users to provide feedback (it's working, it's not) rather than being unsure whether or not the new functionality is live because it might still be living in deployment limbo.
- A tag on the community meta should reflect the status as experienced by the community. A change in tag should communicate a change in experience. This allows users to provide feedback (it's working, it's not) rather than being unsure whether or not the new functionality is live because it might still be living in deployment limbo.
- Comparing timestamps on deployment and update is non-intuitive. We should follow the principle of least astonishment and let status-complete mean complete from the view of the end user.
#1: Initial revision
by
Sigma
·
2020-09-04T14:28:16Z (about 4 years ago)
A tag on the community meta should reflect the status as experienced by the community. A change in tag should communicate a change in experience. This allows users to provide feedback (it's working, it's not) rather than being unsure whether or not the new functionality is live because it might still be living in deployment limbo.