From: Elena Zannoni <elena.zannoni@oracle.com>
To: Stan Cox <scox@redhat.com>
Cc: Frysk List <frysk@sourceware.org>
Subject: Re: user discussion & meeting and more meetings
Date: Tue, 20 Feb 2007 21:37:00 -0000 [thread overview]
Message-ID: <45DB6800.7020503@oracle.com> (raw)
In-Reply-To: <1171998220.14902.25.camel@multics.rdu.redhat.com>
Stan Cox wrote:
> On Wed, 2007-02-14 at 12:05 -0500, Andrew Cagney wrote:
>
>> -> Cycle the Wednesday meeting so that it alternates between user /
>> technical / co-op focused
>>
>
> I vote for cycling the meetings, with week 1 for
> planning/administration/idea exchange and week 2 for technical
> discussion.
>
>
>
>
A project management meeting every 2 weeks is not going to cut it
unfortunately,
given the scope and the size of the project it needs to be done every week.
Doing UI every 2 weeks is reasonable.
next prev parent reply other threads:[~2007-02-20 21:37 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
2007-02-20 19:09 ` Stan Cox
2007-02-20 21:37 ` Elena Zannoni [this message]
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=45DB6800.7020503@oracle.com \
--to=elena.zannoni@oracle.com \
--cc=frysk@sourceware.org \
--cc=scox@redhat.com \
/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).