From: Mark Wielaard <mark@klomp.org>
To: frysk <frysk@sourceware.org>
Subject: Re: user discussion & meeting and more meetings
Date: Tue, 20 Feb 2007 19:14:00 -0000 [thread overview]
Message-ID: <1171998871.3587.56.camel@dijkstra.wildebeest.org> (raw)
In-Reply-To: <45D34165.7090300@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1214 bytes --]
On Wed, 2007-02-14 at 12:05 -0500, Andrew Cagney wrote:
> lets throw this open for debate;
>
> 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 like to see stuff pushed to the mailinglist as much as possible since
that means there is an automatic record and you can read/respond on your
own time.
The ui meetings are useful to explicitly focus on actual usage. But it
looks like doing that once a week is too much for all the feedback it
generates. It seems to take more than a week to actually change the code
based on all the feedback. So doing the ui reviews bi-weekly seems
better.
If we do want to have a phone meeting to sync technical,
who-works-on-what status reports than it seems a good idea to alternate
those on a weekly basis with a ui-review meeting to keep the meetings
short and focused. I kind of tune out after 30/60 minutes on the
phone...
Cheers,
Mark
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-02-20 19:14 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
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 [this message]
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=1171998871.3587.56.camel@dijkstra.wildebeest.org \
--to=mark@klomp.org \
--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).