public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ben de Groot <yngwin@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] introduce a soft-limit policy for changing other developers ebuilds
Date: Thu, 6 Dec 2012 18:53:34 +0800	[thread overview]
Message-ID: <CAB9SyzQ1U3_obHPZKiC1ZfPSTDHsnRdSwwYPVcyamdVxPB48xQ@mail.gmail.com> (raw)
In-Reply-To: <CAG2jQ8gneVurgN5Pyy8EUQY1G6C=yaS6FKWDkgb149+tMsFwdw@mail.gmail.com>

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

On 4 December 2012 17:19, Markos Chandras <hwoarang@gentoo.org> wrote:

> On 4 December 2012 01:18, Ben de Groot <yngwin@gentoo.org> wrote:
> > In my opinion we should limit the amount of places where we document
> > policies and best practices. I suggest we keep only devmanual and PMS as
> > authoritative documents.
> >
> > In that case we should go forward and add these kind of policies to the
> > devmanual.
> >
> > --
> > Cheers,
> >
> > Ben | yngwin
> > Gentoo developer
> > Gentoo Qt project lead, Gentoo Wiki admin
>
> As I said, the only drawback is that devmanual will become huge and
> without a proper "search" functionality, it will be a real pain to
> search
> for something quickly. Especially for new developers who are not
> familiar with how devmanual is structured.
>
> --
> Regards,
> Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2
>
>
Except the situation now is worse. Things are spread over multiple
documents, and we don't have a proper site search.

Even so, 1) Google is your friend, and 2) a single document with a good
index would be a step forward.

-- 
Cheers,

Ben | yngwin
Gentoo developer
Gentoo Qt project lead, Gentoo Wiki admin

[-- Attachment #2: Type: text/html, Size: 1777 bytes --]

  parent reply	other threads:[~2012-12-06 10:54 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-02 15:21 [gentoo-dev] introduce a soft-limit policy for changing other developers ebuilds hasufell
2012-12-02 15:38 ` Rich Freeman
2012-12-02 19:30   ` Markos Chandras
2012-12-04  1:18     ` Ben de Groot
2012-12-04  7:43       ` Ian Whyman
2012-12-04  9:19       ` Markos Chandras
2012-12-04 15:42         ` Alec Warner
2012-12-04 18:54           ` Markos Chandras
2012-12-06 10:53         ` Ben de Groot [this message]
2012-12-04  8:10 ` Rick "Zero_Chaos" Farina
2012-12-04  9:23   ` Markos Chandras
2012-12-04 16:01     ` Rick "Zero_Chaos" Farina
2012-12-04 17:06       ` Proxy maintainers in metadata.xml (was Re: [gentoo-dev] introduce a soft-limit policy for changing other developers ebuilds) Diego Elio Pettenò
2012-12-04 17:28         ` Rick "Zero_Chaos" Farina
2012-12-04 18:35           ` Sergey Popov
2012-12-04 18:48             ` Diego Elio Pettenò
2012-12-04 18:51           ` Markos Chandras
2012-12-06 11:02             ` Ben de Groot
2012-12-06 13:28               ` Markos Chandras
2012-12-06 15:27                 ` Peter Stuge
2012-12-06 15:54                   ` Ian Stakenvicius
2012-12-06 16:04                     ` Peter Stuge
2012-12-06 19:07                   ` Markos Chandras
2012-12-08 17:48             ` Jeroen Roovers
2012-12-04 17:01   ` [gentoo-dev] introduce a soft-limit policy for changing other developers ebuilds hasufell
2012-12-04 17:17     ` Rick "Zero_Chaos" Farina
2012-12-04 17:32       ` hasufell
2012-12-04 17:46         ` Rick "Zero_Chaos" Farina
2012-12-04 18:17           ` hasufell

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=CAB9SyzQ1U3_obHPZKiC1ZfPSTDHsnRdSwwYPVcyamdVxPB48xQ@mail.gmail.com \
    --to=yngwin@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