public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Seemant Kulleen <seemant@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Gentoo-Status
Date: Mon, 21 Aug 2006 19:27:44 -0400	[thread overview]
Message-ID: <1156202864.10125.2.camel@localhost> (raw)
In-Reply-To: <44EA3A0B.7000401@gentoo.org>

Your concerns are well noted. The trustees in general are quiet even
amongst themselves, but I hope this changes with the new board coming in
next week (ish?).  It's been my idea to propose that someone (tsunam was
in my head) publish a trustee monthly news or something. 

The one I'm curious about is the council -- the council posts to -dev
before and after every meeting (and puts meeting logs up on the website
within days of a meeting).  I suppose the webpage itself could be
updated, but I'm unsure what else the council can do.  Perhaps you have
some ideas?

Thanks!
-- 
Seemant Kulleen <seemant@gentoo.org>
Gentoo Foundation / Gentoo Linux

-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2006-08-21 23:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-21 22:56 [gentoo-dev] Gentoo-Status Alec Warner
2006-08-21 23:27 ` Seemant Kulleen [this message]
2006-08-22  0:12   ` Joshua Jackson
2006-08-21 23:51 ` Kevin F. Quinn
2006-08-22  0:13   ` Alec Warner
2006-08-22  0:06 ` Ciaran McCreesh
2006-08-22  0:21   ` Alec Warner
2006-08-22  0:27     ` Ciaran McCreesh
2006-08-22 13:20   ` Lance Albertson
2006-08-22 14:33     ` Simon Stelling
2006-08-22 14:40       ` Ciaran McCreesh
2006-08-22 14:45         ` Elfyn McBratney
2006-08-22 14:52           ` Ciaran McCreesh
2006-08-22 14:45       ` Lance Albertson
2006-08-22 15:10         ` Simon Stelling
2006-08-22 15:17           ` Lance Albertson
2006-08-23 17:18   ` Sune Kloppenborg Jeppesen
2006-08-22  6:09 ` Marius Mauch
2006-08-22 12:57   ` Alec Warner

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=1156202864.10125.2.camel@localhost \
    --to=seemant@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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