Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce the field 'state.lastreviewed' #157

Open
christian-weiss opened this issue Sep 10, 2019 · 0 comments
Open

Introduce the field 'state.lastreviewed' #157

christian-weiss opened this issue Sep 10, 2019 · 0 comments

Comments

@christian-weiss
Copy link
Contributor

We have a field state.lastchanged. Which is some times updated automatically (e.g. when a script updates the state.nodes. For automating quality checks, and alerting / notifications this field can be used to detect problems with auto-update-scripts (e.g. if it stops to update the file each day ), but this field do not help if we want to detect potential for semantically problems.

For automating quality checks, and alerting / notifications, it would be very helpful to know when a community file was last reviewed for semantical errors by a human - e.g. outdated contact details (old, but syntactially valid e-mail address). With that field we could implement a "Review Reminder Service".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant