| 1 |
On 01/21/2017 12:12 AM, William L. Thomson Jr. wrote: |
| 2 |
> On Friday, January 20, 2017 10:27:34 PM EST Dean Stephens wrote: |
| 3 |
>> |
| 4 |
>> Just to point out, part of, why people are interpreting this as they |
| 5 |
>> are: you frame it as a requirement, even a "mandatory requirement", |
| 6 |
>> without specifying what recourse, if any, there is if such requirements |
| 7 |
>> are not met. |
| 8 |
> |
| 9 |
> I can understand that perspective. I am more of the mindset of not having |
| 10 |
> recourse. I am not a fan of punishment. If projects repeatedly do not do it, |
| 11 |
> oh well. That is their choice, just not encouraged. |
| 12 |
> |
| 13 |
>> This implicitly leaves the default mechanisms in place, as |
| 14 |
>> has been discussed elsewhere. A requirement with no enforcement, |
| 15 |
>> especially one which explicitly avoids enforcement is a suggestion, or |
| 16 |
>> request, not a requirement. |
| 17 |
> |
| 18 |
> By stating mandatory the idea is to encourage it to be considered something |
| 19 |
> that should be done and not ignored. I would think non-compliance to be more |
| 20 |
> egg on face of leaders or members. Not a punishable offense. |
| 21 |
> |
| 22 |
|
| 23 |
And let's take a very rigorous look back at this, since there seems to |
| 24 |
be a lack of uniformity in opinions. |
| 25 |
|
| 26 |
Definition(Requirement):a thing that is compulsory; a necessary condition. |
| 27 |
Definition(Compulsory):required by law or a rule; obligatory |
| 28 |
Definition(Obligatory):required by a legal, moral, or other rule; compulsory |
| 29 |
|
| 30 |
OK, so clearly, these are circular. The point is, a requirement, is |
| 31 |
compulsory and obligatory, ie you MUST do it, you are obligated, you are |
| 32 |
compelled to do so. But if you are told that you MUST do it, what |
| 33 |
happens if you opt not to? Well, one of two things, action must be |
| 34 |
undertaken to FORCE that behavior, or inaction allows that behavior to |
| 35 |
continue. If the former, one of two things may happen, positive |
| 36 |
reinforcement, or negative reinforcement. Positive reinforcement would |
| 37 |
most likely be things like a paycheck, you do your work, you get paid. |
| 38 |
Negative reinforcement is obviously punishment of some sort. If we are |
| 39 |
talking about the latter, inaction, the original condition is not being |
| 40 |
forced. Thus, it is not a REQUIREment as the individual is NOT REQUIRED |
| 41 |
to perform said action. |
| 42 |
|
| 43 |
Now, that takes us back to the points made by everyone else in this |
| 44 |
thread... All of which are stating that they do not want compulsory |
| 45 |
reporting actions, in part, because they don't like the premise of being |
| 46 |
punished for failure to perform such an activity. |
| 47 |
|
| 48 |
If you concede that you didn't intend to say compulsory, must do lest |
| 49 |
the person/project incur a punishment, then we aren't talking about |
| 50 |
requirements, we are talking about a suggestion. |
| 51 |
|
| 52 |
I hardly think anyone would complain at the suggestion of projects |
| 53 |
voluntarily reporting to the council for updates if they so wish, and |
| 54 |
that it might be useful for council to poke projects to remind them that |
| 55 |
they may exercise that right if they so choose. |
| 56 |
|
| 57 |
If your goal is to impose compulsory behavior that goes beyond QA and |
| 58 |
other similar necessities of development, I suspect that you will find |
| 59 |
almost no support anywhere. As cited before in this thread, we aren't |
| 60 |
paid to put up with requirements, there is no positive reinforcement, |
| 61 |
only negative reinforcement, so adding barriers to contributions is |
| 62 |
ill-advised and will not be well received. |
| 63 |
|
| 64 |
-- |
| 65 |
NP-Hardass |
Archives