Re: [Mtgvenue] issue #3: Too many mandatory

[Ted Hardie <[e-mail]>]

Howdy,

On Wed, Apr 5, 2017 at 1:24 PM, Dave Crocker <[e-mail]> wrote:

> On 4/5/2017 1:12 PM, Ted Hardie wrote:
>
>> move or cancel the meeting.
>>
>
>
> BTW, folk seem to have mostly missed that the title of the draft refers to
> 'selection', which is a particular step in the overall process. And the wg
> charter concerns "specification of the venue selection process."
>
>
In each of the categories I put forwarding, I used "scheduling", but I am
fine with replacing it with "selecting".  I've put language for that below,
shifting all of the things post-"selecting" into new sentences.  If those
sentences/instructions don't go in this draft, that's fine by me, provided
they are clear in the directions somewhere.

I personally hope that the categories end up somewhere along the lines:
>
> Mandatory:  If not met, don't schedule the meeting here and move or cancel
> the meeting if the requirement ceases to be met.
>
Mandatory:  Do not select this site for a meeting.  Move or cancel the
meeting if the requirement ceases to be met.

> Exception-required:  Confirm that these are met during scheduling or get
> community confirmation of the exception.
>
Exception-required: Confirm that these are met while considering a site for
selection or get community confirmation of the exception.  If they cease to
be met and will not be met at the time scheduled for the meeting, confirm
the exception with the community.

> Important:  Things we care about but which can be traded off if the
balance
> of requirements is met without confirmation by the full community.
>
Important:  Things we care about when selecting site but which can be
traded off if the balance of requirements is met without confirmation by
the full community.  If these cease to be met after selection, these is no
need for community confirmation unless the balance of requirements is no
longer met.

> Desired:  Things we like, but which can be dropped without having an
impact
> on the meeting's effectiveness.

Desired:  Things we like in sites, but which do not have an impact on a
meetings effectiveness and thus can be considered in site selection without
being true requirements.


> All sorts of things happen after a venue is 'selected'.  These things are
> quite distinct form 'selection'.
>
> Contracting is one of those steps.  Another is monitoring and
> re-evaluating if conditions change.  Those are, of course, essential.
>
>
The draft as currently constructed covers those as venue selection steps,
at least as I read Section 5.  If each of those steps needs a new document,
we may be here a while.

Ted



> They are also outside the formal scope of this effort, though everyone
> seems to prefer to conflate them, which is having the predictable effect of
> making discussion and wording considerably more complicated.
>
>
> d/
>
> --
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net
>