From: Andrew Gray <andrewg@gnu.org>
To: Chad Walstrom <chewie@wookimus.net>
Cc: help-gnats@gnu.org
Subject: Re: Call for new GNATS maintainer
Date: Wed, 14 Apr 2004 15:47:00 -0000 [thread overview]
Message-ID: <20040414115007.GC4381@nandakot.anu.edu.au> (raw)
In-Reply-To: <20040407154546.GA30144@wookimus.net>
On Wed, Apr 07, 2004 at 10:45:46AM -0500, Chad Walstrom wrote:
> I've talked with my supervisor about stepping up as GNATS maintainer.
> He is willing to allow 5% of my time at work to contintribute to the
> project.
Great, that is good news!
> However, there are a few hoops I have to jump through before
> anything is official:
OK, I hope that goes well.
> If all this goes well, that still means only 5% development time in a
> 40+ hr work week. Is two hours per week enough? Obviously, to make
> that an effective use of time, I'd have to block it off from other
> activities. I'm already adding personal time for the Debian packages
> (although I have the OK to work on software we use for purposes of
> installation and maintenance, it's not "officially" development time).
I agree with Yngve, I think two hours per week is enough, particularly
if it is regular (and it is more than I have been applying to GNATS).
> I'll keep you all posted.
Thanks.
--
Andrew Gray
GNU GNATS Maintainer
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats
prev parent reply other threads:[~2004-04-14 12:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-28 22:32 Andrew Gray
2004-03-30 19:04 ` Chad Walstrom
2004-03-30 23:44 ` Yngve Svendsen
2004-04-01 22:04 ` Andrew Gray
2004-04-02 4:11 ` Mel Hatzis
2004-04-07 17:00 ` Chad Walstrom
2004-04-07 18:30 ` Yngve Svendsen
2004-04-15 0:02 ` Chad Walstrom
2004-04-14 15:47 ` Andrew Gray [this message]
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=20040414115007.GC4381@nandakot.anu.edu.au \
--to=andrewg@gnu.org \
--cc=chewie@wookimus.net \
--cc=help-gnats@gnu.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).