public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Phil Muldoon <pmuldoon@redhat.com>
To: Andrew Cagney <cagney@redhat.com>
Cc: frysk <frysk@sourceware.org>
Subject: Re: user discussion & meeting and more meetings
Date: Wed, 14 Feb 2007 21:57:00 -0000	[thread overview]
Message-ID: <45D385B0.4010308@redhat.com> (raw)
In-Reply-To: <45D34165.7090300@redhat.com>

Andrew Cagney wrote:
>
> There are several ideas to kick around:
> -> expand Wednesday morning's meeting to include other matters
> -> add a second weekly meeting
> -> Cycle the Wednesday meeting so that it alternates between user / 
> technical / co-op focused
> -> have less regular technical/co-op focused meetings
> -> use mailing lists and irc for technical stuff
> -> ...
>
> I've two personal and strong preferences:
> -> not have too many meetings
> -> keep discussion focused, for instance, as been done with UI discussion
>
> Comments and suggestions.

Personally I find short meetings more productive than longer ones. So 
two 30 minute meetings, for me, are always invariably more productive 
that one hour long plus. This is especially true when the meetings 
require close following of both the speech on the phone, as well as 
following prompts on the vnc session.

That being said, I personally think the weekly UI meetings are just 
going to run into each other, as the deliverable from one meeting to the 
other take more than one week to complete.

My own personal preference would be cycle the Wednesday meeting, 
accordingly.

Regards

Phil
>
> Andrew
>

  parent reply	other threads:[~2007-02-14 21:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-14 17:31 Andrew Cagney
2007-02-14 19:41 ` Rick Moseley
2007-02-14 21:57 ` Phil Muldoon [this message]
2007-02-20 19:09 ` Stan Cox
2007-02-20 21:37   ` Elena Zannoni
2007-02-20 22:49     ` Andrew Cagney
2007-02-20 23:34       ` Kris Van Hees
2007-02-21  3:07       ` Elena Zannoni
2007-02-20 19:14 ` Mark Wielaard
2007-02-20 20:16 ` Nurdin Premji

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45D385B0.4010308@redhat.com \
    --to=pmuldoon@redhat.com \
    --cc=cagney@redhat.com \
    --cc=frysk@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).