public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Rick Moseley <rmoseley@redhat.com>
To: frysk <frysk@sourceware.org>
Subject: Re: user discussion & meeting and more meetings
Date: Wed, 14 Feb 2007 19:41:00 -0000	[thread overview]
Message-ID: <45D365F4.7010608@redhat.com> (raw)
In-Reply-To: <45D34165.7090300@redhat.com>

Andrew Cagney wrote:
> lets throw this open for debate;
>
> On Wednesday's @9:30 CA-EST is a discussion about UI aspects of 
> frysk.  The discussion ranges from utilities through to the gnome 
> components.  The discussion has the following goals:
> -> focus on end user experience
> -> be focused - very limited topic list, shorter meeting
> -> have clear outcomes, and follow them through
> -> occasionally, the opportunity to explore new ideas
> At the moment I'm picking things driven largely by active work that 
> I'm aware of.  Going forward, I hope this will evolve into more of a 
> weekly show-n-tell - an opportunity to highlight progress and gain 
> quick feedback on new work.  The discussion is proving to be largely 
> non-technical.
>
> Elena is asking that there also be made available time where non user 
> issues can be addressed:
> -> a free technical exchange
> -> co-operative planning and administration
> (At present there's an internal meeting that touches on this).
>
> 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
I vote for this.  Having weekly UI stuff does not allow time to 
necessarily implement changes.  Maybe it was good here at the first 
because the UI had not been reviewed in a while, but now that it has 
moving to a less-than-weekly review would be best, IMHO.
> -> 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.
>
> Andrew
>

  reply	other threads:[~2007-02-14 19:41 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 [this message]
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
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=45D365F4.7010608@redhat.com \
    --to=rmoseley@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).