-
Notifications
You must be signed in to change notification settings - Fork 48
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
Detail maintenance a bit more #46
Comments
Merged
Hmm, in 69ed4a8 I let a signature change go through. I think that kind of thing should be OK... |
It makes it harder for someone doing IPR review I think as they cannot just look at the latest file, but maybe that's nonetheless the case. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In particular, we probably do not want folks to change the signature field. And definitely not the id field.
The verified field is up to maintainers.
So workstreams and info fields would be up for changes? Don't see anything there that is off limits.
Aside: while we track the initial signature, we don't track join/leave dates of Workstreams other than through
git blame
. Is that wise?cc @domenic @foolip
The text was updated successfully, but these errors were encountered: