[Management] [Product Council] Attending calls
eli at media.berkeley.edu
Thu May 13 15:49:14 PDT 2010
+1. Open, unless there is a *very* compelling reason not to.
On May 13, 2010, at 12:04 PM, Nate Angell wrote:
> +1 for generally open Product Council calls unless there is a
> compelling reason to have a closed call, which should be so stated in
> the agenda in advance.
> - Nate
> On Thu, May 13, 2010 at 11:58 AM, Clay Fenlason
> <clay.fenlason at et.gatech.edu> wrote:
>> Someone's asked whether anyone is welcome to sit in on Product Council
>> calls. I have my own opinion, but thought I should get other thoughts
>> in the open.
>> My opinion is that as a general rule this is fine, and in fact in
>> keeping with our goal of taking in and reflecting community will on
>> questions of product standards. I also think that there may be rare
>> occasions (eg. a meeting about a final set of release determinations)
>> for which it could be better to have a closed meeting than risk a need
>> for strong facilitation, but we could announce those ahead of time.
>> management mailing list
>> management at collab.sakaiproject.org
>> TO UNSUBSCRIBE: send email to management-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
> management mailing list
> management at collab.sakaiproject.org
> TO UNSUBSCRIBE: send email to management-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
. . . . . . . . . . . . . . . . . . .
manager of user experience design
ETS, UC Berkeley
"The opportunity lost by increasing the amount of blank space is gained back with enhanced attention to what remains."
- John Maeda
More information about the management