meeting coverage of weekly agenda

[Kevin Cole]

Jane Weideman wrote:

> My 2c...

Don't know where the U.S. is on the exchange rate, but my $0.02 isn't worth
what it used to be.  In any case, I've added mine to yours.

> 1) We need to keep the meeting format a little tighter (less general
> chatter).

Guilty as charged Your Honor, but Flint incites it. ;-)  Seriously, I will
attempt to curtail.

> 2) We need to have updated prepared in advance - as per the Ubuntu
> dapper Status Update meeting. This makes the update post quicker and
> allows for a brief on topic discussion as necessary afterwards. If a
> long discussion is required, like Drupal vs Moin. This should be
> deferred to a separate meeting, or for discussion at the end of the
> meeting, or to the mailing list.

IIRC, since joining, I don't know if I've seen any meeting agenda
pre-meeting. Is there one that I miss? Is it worth having?  (It seems to help
in some meetings.)

Much as I consider myself to be disinclined to IRC, Discussions like the
decent Drupal vs. Moin seem to flow better in IRC, provided people have time
after the meetings.  (Unfortunately, I run for a train into work after the
meetings. But there's always the logs and post-log e-mail follow-up, I
suppose.)

> 3) We also need to keep focused on the goal of this meeting which is
> really a Dapper Development Status meeting. Post Dapper topics and nice
> to haves etc should be discusses in the #edubuntu channel outside the
> meeting.

Although I don't think I added much to post-Dapper discussion, it was probably
by sheer luck: Where do I find the "boundaries" on what's appropriate? (Study
Launchpad specs?)  Another part of the problem -- for me at least: High degree
of overlap between the Edubuntu team, documentation team, and accessibility
team. Often it feels like I need to ask or report back similar things in all
meetings.  (I'm not complaining.  I think it's a GOOD thing to think about
the same issues with a different crowd and focus. But it does steal time.)

> 4) Each of the key areas (Tech, Doc, Artwork) should have an owner who
> will represent that area for the week, this doesn't have to be the same
> person each week, but they should arrive prepared.

Although it seems unnatural for the IRC crowd, perhaps also waiting for the
end of a report before opening it up to any Q&A follow-up would be good.  It
felt like, in some cases, we'd go off on tangents before the person reporting
was finished, which made the discussion a bit like herding cats.  I'm all for
the free-for-all but as you said, we've only got approximately an hour.

> 5)I also need to try to get my ADSL line not to rest at the crucial time
> as the meeting starts!

Anyone you trust as a proxy in case of continued difficulties?

-- 
 Kevin Cole                    |  Key ID: 0xE6F332C7
 Gallaudet University          |     WWW: http://gri.gallaudet.edu/~kjcole/
 Hall Memorial Bldg  S-419     |   V/TTY: (202) 651-5135
 Washington, D.C.  20002-3695  |     FAX: (202) 651-5746

 "Using vi is not a sin. It's a penance." -- St. IGNUcious, Church of Emacs
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ubuntu.com/archives/edubuntu-devel/attachments/20051201/1dd56c63/attachment.pgp>