[Community] requirements and meeting schedules

[Joaquin Miller]

> >> It is my recollection that we not only agreed a quarterly 
> meeting (telephone conference) of the Steward's Council would be a 
> good thing, I believe we agreed and >>stipulated that a quarterly 
> meeting of the council was a requirement we placed upon ourselves, 
> albeit with the proviso that we could meet more often when needed.

That's right.  We did.

And what is written below is (as we used to say) righteous.

>About the terminology of 'requirement, 'rules,' and the like.  It is 
>my impression that there is a fundamental spirit of both seriousness 
>and simultaneously non-formal or non-legalistic in the comments 
>everyone tends to make.  Therefore I would suggest that the notion 
>of a serious and yet not legally rigid way of thinking about the 
>concept of a requirement would be something like this:
>
>A requirement that we place upon ourselves is something we agree as 
>a council (and [each] individually as council members) is important 
>and that we take on as a group obligation [and each as an individual 
>obligation].  In that case of a "requirement" that we meet once 
>every three months, at a minimum, I think that it could take the 
>form of an agreement that remember and keep track of through your 
>keeping track of the date of the most recent meeting.  The idea 
>could be as simple as we project a date 90 days out as the default 
>date for the next meeting, unless there is a call for a meeting at 
>an earlier date.  Does that make sense?

It does make sense.

And there is no reason we can't schedule the date of the next 
quarterly meeting three months in advance, even a year in advance.

Cordially, Joaquin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.idcommons.net/pipermail/community/attachments/20061018/8aa2c73e/attachment.htm