From: Mart Raudsepp <leio@gentoo.org>
To: gentoo devs <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] How to speed up maintenance and other Gentoo work?
Date: Wed, 04 Mar 2009 04:01:36 +0200 [thread overview]
Message-ID: <1236132096.2522.4.camel@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 1255 bytes --]
Hello,
I'm collecting ideas from the wider development and contributing
community on how to help maintainers and contributors get work done
quicker, or rephrased - how to get more done in the limited time we
have.
This basically means ideas for tools, scripts, or functionality in some
hypothetical centralized maintainer helper website or GUI/CLI program
that would help save time in taking care of some of the gruntwork that
gets done by maintainers right now manually or by scripts that don't get
shared and re-used and generalized as much as they could.
Then afterwards I can sort through the suggestions/ideas, try to make a
summary and arrange some of them to actually happen.
If things get done quicker, there is theoretically more available time,
which hopefully would translate into being able to bring us back to the
bleeding edge in one hand, and high quality in another.
I have intentionally left out my own ideas at start to keep everyone's
mind open to various approaches to this.
Please share your thoughts and ideas as a reply here, on my matching
blog post as comments or via private e-mail!
--
Mart Raudsepp
Gentoo Developer
Mail: leio@gentoo.org
Weblog: http://planet.gentoo.org/developers/leio
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2009-03-04 2:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 2:01 Mart Raudsepp [this message]
2009-03-04 2:24 ` [gentoo-dev] How to speed up maintenance and other Gentoo work? Mike Frysinger
2009-03-04 5:37 ` Donnie Berkholz
2009-03-04 2:26 ` Peter Alfredsen
2009-03-04 2:51 ` Olivier Crête
2009-03-04 4:54 ` Josh Saddler
2009-03-04 5:36 ` Donnie Berkholz
2009-03-04 12:50 ` [gentoo-dev] " Nicolas Sebrecht
2009-03-07 7:22 ` Caleb Cushing
2009-03-07 11:21 ` Nicolas Sebrecht
2009-03-07 19:27 ` Alec Warner
2009-03-08 0:57 ` Caleb Cushing
2009-03-08 2:29 ` Robin H. Johnson
2009-03-08 14:10 ` Nicolas Sebrecht
2009-03-06 19:02 ` [gentoo-dev] " Petteri Räty
2009-03-07 1:44 ` [gentoo-dev] " Ryan Hill
2009-03-07 3:08 ` Duncan
2009-03-13 8:24 ` [gentoo-dev] " Thilo Bangert
2009-03-13 12:44 ` Grant Goodyear
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=1236132096.2522.4.camel@localhost \
--to=leio@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