public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Dolbec <dolsen@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Re: [gentoo-dev] Portage team, Zac's development break and stepping down as lead
Date: Tue, 07 Jan 2014 20:02:20 -0800	[thread overview]
Message-ID: <1389153740.5407.11.camel@big_daddy.dol-sen.ca> (raw)
In-Reply-To: <52CCA16E.2000504@gentoo.org>

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

On Tue, 2014-01-07 at 16:53 -0800, Pavel Kazakov wrote:
> Hi everyone,
> 
> I saw the email sent to the dev mailing list asking for help on portage.
> I'm not sure how much interest the post has generated, but if help is
> still needed, I'd be more than willing to help out. I have good
> familiarity with bash and python (I use both extensively at work). I'm
> not too familiar with portage's internals but willing to learn.
> 
> If help is still needed, is there any documentation for starting
> development or any good pointers for me to get started?
> 
> Regards,
> Pavel
> 

Welcome.  There have been several so far, but, the more the better.
It will take the load off any one individual.  We all (well, most) have
real lives that we also need to attend to.  ;)

For best the best documentation, enable the epydoc use flag and
re-emerge portage.  

There are several bugs to start working on.  Also there are some gleps
that need to be attended to.  See the email Sebastian has sent out with
a number of open bugs.  

I will be laying out a plan for the sync operations change I am
proposing to do.  If we can come to an agreement on that, then there
will also be that to implement.

So for now, join, start delving into the code, see what you can do.
Ask questions...

We will need to establish some meetings after some newcomers have had a
bit of time to see what needs doing.  We can start making some decisions
then.

Thank you.
-- 
Brian Dolbec <dolsen@gentoo.org>

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

  reply	other threads:[~2014-01-08  4:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-08  0:53 [gentoo-portage-dev] Re: [gentoo-dev] Portage team, Zac's development break and stepping down as lead Pavel Kazakov
2014-01-08  4:02 ` Brian Dolbec [this message]
2014-01-08  5:51   ` [gentoo-portage-dev] " Pavel Kazakov
  -- strict thread matches above, loose matches on Subject: below --
2014-01-06  5:33 Brian Dolbec
2014-01-13  3:07 ` [gentoo-portage-dev] Re: [gentoo-dev] " Brian Dolbec

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=1389153740.5407.11.camel@big_daddy.dol-sen.ca \
    --to=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