-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Rename FaceFaceConstraint #10769
Comments
You've opened up several tickets with really terse wording. Let's try to flesh these out a bit more, this would likely not stand up under an audit. The official requirements for these sections comes from NQA-1, but we've distilled it a bit in our PLN-4005 document in EDMS if you care to investigate what we are trying to do here. |
@permcody I added more words - I don't really know what to say. I just wanted to rename an object, I wasn't trying to be provocative here... just needed a simple ticket for renaming something. Not everything needs a large amount of prose.... |
Right, I'm just pointing out that making all issues into requirements is not the right idea. Some things are just simple actions that don't require a lot thought, bookingkeeping, prose, etc. They are useful to track work, but not necessarily to generate requirements. As soon as you say, well only a subset of the issues are requirements, then an auditor want to know, which subset... |
Hah - well - I still think each issue is a requirement... but not all
requirements are "large" requirements. I "require" that this file changed
names is still a requirement!
And as for subsetting - it could be easily done with a label.
But anyway: that ship has sailed... let's see how we do with our currently
agreed upon system! :-)
…On Tue, Feb 27, 2018 at 11:37 AM Cody Permann ***@***.***> wrote:
Right, I'm just pointing out that making all issues into requirements is
not the right idea. Some things are just simple actions that don't require
a lot thought, bookingkeeping, prose, etc. They are useful to track work,
but not necessarily to generate requirements. As soon as you say, well only
a subset of the issues are requirements, then an auditor want to know,
which subset...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#10769 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA1JMX2n-6sUYv4Yyiz9AuX40_dq0NUDks5tZEsIgaJpZM4SD_U9>
.
|
Closing as addressed by #10771 |
Rationale
FaceFaceConstraint is really a MortarConstraint so let's rename it.
Description
Name sounds more general than it is. We want to use the more general name for another object
Impact
Clearer naming
The text was updated successfully, but these errors were encountered: