public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sam Jorna <wraeth@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How to contribute ebuilds?
Date: Sun, 24 Apr 2016 21:54:25 +1000	[thread overview]
Message-ID: <20160424115424.GB3792@nemesis.wraeth.lan> (raw)
In-Reply-To: <20160424115056.GA3792@nemesis.wraeth.lan>

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

On Sun, Apr 24, 2016 at 09:50:57PM +1000, Sam Jorna wrote:
> On Sun, Apr 24, 2016 at 02:42:52PM +0300, Victor wrote:
> > What is the preferred way to contribute them without becoming a Gentoo
> > Developer?
> > 
> > Should I post them to bugzilla or maybe send to `python' and `emacs'
> > overlays (if so, how?), or `sunrise' overlay? Or create my own overlay?
> 
> Hi!
> 
> You can file a "New Ebuild" request on Bugzilla (go to "New" -> "Gentoo
> Linux" and select the component "New Ebuilds"), or you can fork the
> Portage tree on GitHub[0] and submit a Pull Request.
> 
> If you're interested, you can also become a proxy-maintainer for the
> package - you would be responsible for bugs and version-bumps, and while
> you wouldn't have commit/push access to the development Portage tree,
> the members of the Proxy Maintainers project[1] are there to help
> prepare and commit ebuilds and patches.
> 
> Thanks in advance for the contribution!

One day I will remember to include my references the first time
around... Today is not that day...

0: https://github.com/gentoo/gentoo/
1: https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers

--
Sam Jorna (wraeth)
GnuPG Key: D6180C26

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 951 bytes --]

  reply	other threads:[~2016-04-24 11:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-24 11:42 [gentoo-user] How to contribute ebuilds? Victor
2016-04-24 11:50 ` Sam Jorna
2016-04-24 11:54   ` Sam Jorna [this message]
2016-04-24 21:11   ` Victor
2016-04-24 17:11 ` [gentoo-user] " James
2016-04-24 21:20   ` Victor

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=20160424115424.GB3792@nemesis.wraeth.lan \
    --to=wraeth@gentoo.org \
    --cc=gentoo-user@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