public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: python@gentoo.org
Subject: [gentoo-dev] Python project is looking for a new PyPy maintainer/hacker
Date: Mon, 6 Jan 2014 19:36:45 +0100	[thread overview]
Message-ID: <20140106193645.701b6467@gentoo.org> (raw)

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

Hello, all.

We've been slacking for some time and we're two versions of PyPy behind
already. Therefore, I've opened a staffing need [1] for a new PyPy
package maintainer and hacker.

We specifically need someone who knows the basics of Python ecosystem
and is able to hack on PyPy's code. The work involves:

- checking our existing patchset and updating it for future versions
  of PyPy,

- hacking PyPy to be compatible with common Python install layout
  as outlined in bug #465546 [2],

- updating PyPy ebuilds and building binary packages [3].

We will offer all help we can. We can help with ebuild-related issues
and understanding of Python ecosystem in Gentoo. We can provide
some infrastructure to build PyPy if that is necessary.

However, we don't know the PyPy internals, so that's what the candidate
will need to face alone. Hopefully, it will be just a one-time effort.

If you are interested in helping out, please contact us at
#gentoo-python (freenode) or python@gentoo.org. We appreciate all
the help you can give us.

[1]:https://wiki.gentoo.org/wiki/Project:Gentoo/Staffing_Needs/PyPy_hacker
[2]:https://bugs.gentoo.org/show_bug.cgi?id=465546
[3]:https://bugs.gentoo.org/show_bug.cgi?id=479832

-- 
Best regards,
Michał Górny

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

             reply	other threads:[~2014-01-06 18:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-06 18:36 Michał Górny [this message]
2014-01-07  1:56 ` [gentoo-dev] Python project is looking for a new PyPy maintainer/hacker Alice Ferrazzi
2014-03-12 12:28   ` Michał Górny

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=20140106193645.701b6467@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=python@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