(mark@radagast)-(02:41-:-07/20)-]-
(2008)diff psarc_2008_575_draft_opinion.txt.orig psarc_2008_575_draft_opinion.txt
11c11
< Date:         July 9th, 2009.
---
> Date:         July 20th, 2009.
49c49
<        posix-spaw(3C),spawn.h  Committed
---
>        posix-spawn(3C),spawn.h  Committed
55c55
<        SIOCILB                  Private              ilbd daemon uses this
---
>        SIOCILB                  Project Private      ilbd daemon uses this
72c72
< regression of performance occurs. The committee noted that there does not exist
---
> regression of performance occurs. Members noted that there does not exist
78c78
< The committee's concern is that these features are adding branches in the
---
> The member's concern is that these features are adding branches in the
86c86
< The committee would offer advice to the project management organization that it
---
> The committee members offer advice to the project management organization that it
96c96
< Additionally, the committee noted that this case causes an overlap in
---
> Additionally, members of the committee noted that this case causes an overlap in
100c100
< exist for both to be enabled at the same time. The team advised the team that
---
> exist for both to be enabled at the same time. The members advised the team that
105,112c105,112
< choose to enable both tools. The committee would also advise the same
< organization as mentioned in the preceding paragraph that it seems that some
< sort of diagnostic tool seems warranted here. The committee cautioned against
< creating too much coupling between subsystems, especially where subsystem
< functionality may overlap, and by extension, configuration may overlap or be
< contentious. Embedding knowledge of each tool's capability for overlap in each
< other tool would cause a mushrooming amount of complexity and coupling. The
< committee does advise the project management team that it should consider
---
> choose to enable both tools. The members also advise the same organization as
> mentioned in the preceding paragraph that it seems that some sort of diagnostic
> tool seems warranted here. The members cautioned against creating too much
> coupling between subsystems, especially where subsystem functionality may
> overlap, and by extension, configuration may overlap or be contentious.
> Embedding knowledge of each tool's capability for overlap in each other tool
> would cause a mushrooming amount of complexity and coupling. The members of the
> committee also advise the project management team that it should consider
115c115
< as a whole, including all possible paths through integrated tools.
---
> as a whole, including all possible paths through integrated subsystems.
121,123c121,123
< Finally, as noted in the advisory information section, the committee noted that
< the use of the "persist=<netmask>" would more useful if it did not use any
< netmask as a default.  The committee advised the team that the "persist"
---
> Finally, as noted in the advisory information section, members of the committee
> noted that the use of the "persist=<netmask>" would more useful if it did not
> use any netmask as a default. The members advised the team that the "persist"
126c126
< This advice is noted in the Advisory Section (section 6.3).
---
> This advice is noted in the Technical Changes Advised Section (section 7.2).
136c136
< As previously mentioned in the Opinion section 4.1, the committee would advise
---
> As previously mentioned in the Opinion section 4.1, the committee members advise
147c147
< As mentioned in the Opinion section 4.2, the committee would also advise the
---
> As mentioned in the Opinion section 4.2, the committee members also advise the
153,155c153,155
< could address diagnosing these overlaps (and the potential misconfiguration
< that could result). Such architecture would prevent requiring each project to
< build in knowledge of every other potentially conflicting subsystem, thus also
---
> could address diagnosing these overlaps (and the potential misconfiguration that
> could result). Such architecture would prevent requiring each project to build
> in knowledge of every other potentially conflicting subsystem, thus also
159,165d158
< 6.3.  Make "Persist" Netmask Optional
<
< The committee advises the team that the netmask parameter for the "Persist"
< keyword should be optional. By default, then, this persistence, if specified,
< would apply to all hosts for the rule in which the "Persist" keyword was
< applied.
<
174,177c167,170
< As mentioned in the Opinion section 4.3 and Advisory section 6.3, the committee
< advised the project team that it should change the specification so that the
< "persist" option should allow the netmask parameter to be optional, thereby
< implying all hosts by default.
---
> As mentioned in the Opinion section 4.3, the committee members advised the
> project team that it should change the specification so that the "persist"
> option should allow the netmask parameter to be optional, thereby implying all
> hosts by default.
193,195d185
< 4    Issues
<      File: issues
<