public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tom Wijsman <TomWij@gentoo.org>
To: dolsen@gentoo.org
Cc: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Commit Policy
Date: Wed, 15 Jan 2014 04:17:26 +0100	[thread overview]
Message-ID: <20140115041726.3219f64f@TOMWIJ-GENTOO> (raw)
In-Reply-To: <1389350112.7103.133.camel@big_daddy.dol-sen.ca>

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

On Fri, 10 Jan 2014 02:35:12 -0800
Brian Dolbec <dolsen@gentoo.org> wrote:

> First off.  Welcome and than you for responding to help with portage.
>
> With this many people, we should be able to make good progress without
> overloading any one person.

Thank you for taking the step forward to look for them and lead them.
 
> General rule is to submit all patches to this list for review and
> approval before committing.
> 
> Remember to do these always:
>  1) run pyflakes on your changes to check for faults, misssing
> imports, variables undefined,...
> 
> 2) run the testsuite to check for breakage.  It is in the base
> directory called runtests.sh.  Please try to test it with all minimum
> supported python versions, but if you have pypy, and some others,
> then great.
> 
> 3) any new code that could break things, make a test for it if at all
> possible.
> 
> 
> The general exception for patch submittal is for trivial changes such
> as typo fixes, etc..
> 
> It will take a bit of time for everyone to acclimate themselves into
> our new team.  So, I was thinking we give it 2 months, then hold an
> election for lead in March.  Is that alright with everyone?

Looks good; 2 months is indeed also handy to get to learn each other,
as well as for people to consider whether they want to nominate.

-- 
With kind regards,

Tom Wijsman (TomWij)
Gentoo Developer

E-mail address  : TomWij@gentoo.org
GPG Public Key  : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2  ABF0 95B2 1FCD 6D34 E57D

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

      parent reply	other threads:[~2014-01-15  3:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-10 10:35 [gentoo-portage-dev] Commit Policy Brian Dolbec
2014-01-10 17:24 ` Matthew Thode
2014-01-10 18:13 ` Pavel Kazakov
2014-01-11  3:01 ` Alexander Berntsen
2014-01-13  6:43 ` Sebastian Luther
2014-01-13  7:29   ` Brian Dolbec
2014-01-15  2:19     ` Yixun Lan
2014-01-13 16:37   ` [gentoo-portage-dev] " W. Trevor King
2014-01-15  3:22   ` [gentoo-portage-dev] " Tom Wijsman
2014-01-15  8:42     ` Alexander Berntsen
2014-01-15  3:17 ` Tom Wijsman [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=20140115041726.3219f64f@TOMWIJ-GENTOO \
    --to=tomwij@gentoo.org \
    --cc=dolsen@gentoo.org \
    --cc=gentoo-portage-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