From: Lance Albertson <ramereth@gentoo.org>
To: gentoo-trustees@lists.gentoo.org
Subject: [gentoo-trustees] Recent issues (funding/etc)
Date: Sat, 17 Jun 2006 12:33:33 -0500 [thread overview]
Message-ID: <44943CED.4080805@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2241 bytes --]
Its becoming more evident that some of us are lacking on sufficient time
for this council. I'm curious what we should do to help that situation.
One of the major issues so far has the been the extremely slow responses
to funding requests (I admit, I'm slow too). And after they're approved,
we're still stuck waiting on someone to actually make the transaction.
There's just too many bottlenecks and its really starting to annoy some
of our developers. I understand that we're all volunteers and only have
so much time to deal with this stuff, but we really need to try and do
something to deal with that. We were elected in our position so that
means we should put more effect in what we do.
Do we need to make the process better, easier on us? I think we've
actually past the deadline on having another election for trustees
(which I'm surprised no one has complained about yet). Should we just
have another election for this year and get new people on board that
have the sufficient time, or do we need to look at another alternative
to that?
The main example I'd like to point out is the recent AMD64 request. Its
been sitting on our table for a *long time*. And once it got approved
the transaction of funds for it never happened (I'm not trying to attack
anyone that was in charge of that). Then osprey had issues, then
suddenly everyone was on board to fund that too (within 48 hours). And
since then, we're still waiting on funding to actually get moved.
Either we need to hand over duties to people who do have the time, or we
need to do something else about it. Its really becoming frustrating and
apparent to our developers that we don't move very fast at all.
I know from my side of things I've been busy with work related stuff and
other real-life stuff. I've tried my best to keep up on things with the
foundation, but its hard to do sometimes with all the other noise I see
in email.
Ok, thats the end of my ranting. :-)
Thanks-
--
Lance Albertson <ramereth@gentoo.org>
Gentoo Infrastructure | Operations Manager
---
GPG Public Key: <http://www.ramereth.net/lance.asc>
Key fingerprint: 0423 92F3 544A 1282 5AB1 4D07 416F A15D 27F4 B742
ramereth/irc.freenode.net
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 186 bytes --]
next reply other threads:[~2006-06-17 17:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-17 17:33 Lance Albertson [this message]
2006-06-17 20:55 ` [gentoo-trustees] Recent issues (funding/etc) Jason Huebel
2006-06-17 21:53 ` Lance Albertson
2006-06-18 1:21 ` Seemant Kulleen
2006-06-18 1:21 ` Donnie Berkholz
2006-06-18 1:27 ` Lance Albertson
2006-06-20 21:58 ` Lars Weiler
2006-06-21 13:51 ` Donnie Berkholz
2006-06-20 19:43 ` Sven Vermeulen
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=44943CED.4080805@gentoo.org \
--to=ramereth@gentoo.org \
--cc=gentoo-trustees@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