public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Olivier Crête" <tester@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] How to speed up maintenance and other Gentoo work?
Date: Tue, 03 Mar 2009 21:51:22 -0500	[thread overview]
Message-ID: <1236135082.11937.35.camel@TesterTop3.tester.ca> (raw)
In-Reply-To: <20090304032640.4c4ca005@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1031 bytes --]

On Wed, 2009-03-04 at 03:26 +0100, Peter Alfredsen wrote:
> On Wed, 04 Mar 2009 04:01:36 +0200
> Mart Raudsepp <leio@gentoo.org> wrote:
> 
> > 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.
> 
> Something like what Debian does where a central service monitors
> upstream ftp and notifies you when a bump is available.
> 
> Per-package eclasses - eblits standardized.
> 
> Crazy idea: Not-quite-eclasses. Some way to share small bits of code
> between packages, though the code may not be eclass-worthy. We all know
> the use-cases:
> [[ -f ChangeLog ]] && \
>  { dodoc ChangeLog || die "ChangeLog exists but cannot be dodoc'ed" ; }
> 
> And bits of code of that ilk.

Maybe we could use the dev wiki for that kind of stuff?

Having a wiki.gentoo.org would be even better...

-- 
Olivier Crête
tester@gentoo.org
Gentoo Developer

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-03-04  2:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-04  2:01 [gentoo-dev] How to speed up maintenance and other Gentoo work? Mart Raudsepp
2009-03-04  2:24 ` Mike Frysinger
2009-03-04  5:37   ` Donnie Berkholz
2009-03-04  2:26 ` Peter Alfredsen
2009-03-04  2:51   ` Olivier Crête [this message]
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=1236135082.11937.35.camel@TesterTop3.tester.ca \
    --to=tester@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