public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: How to contribute ebuilds?
Date: Sun, 24 Apr 2016 17:11:54 +0000 (UTC)	[thread overview]
Message-ID: <loom.20160424T185859-563@post.gmane.org> (raw)
In-Reply-To: 20160424144252.26640c73@probook

Victor <victor <at> enise.org> writes:


> I have a couple of ebuilds for some software not in main tree, mainly
> emacs and python modules.
> What is the preferred way to contribute them without becoming a Gentoo
> Developer?

I think the preferred method (it takes time to go down the gentoo-dev or
gentoo-proxy-maintainer pathways) is to setup a github acccount and post your 
body of work there because github makes it easy for folks to collaborate
with you and your work.

Who knows, maybe you'll also want to bring turbogears2 to gentoo? That would
be very, bery cool!   Turbogears1 use to be part of the packages available.
Turbogears2 is very cool [1]. 

> 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?

Yes, that way, we get immediate access to the ebuilds to test them out and
give you feedback. Put up some details, related to these packages, either in
bgo or a github/blog, particularly if they are part of a theme you are pursuing.


hth,
James

[1] http://www.turbogears.org/current-status.html#




  parent reply	other threads:[~2016-04-24 17:12 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
2016-04-24 21:11   ` Victor
2016-04-24 17:11 ` James [this message]
2016-04-24 21:20   ` [gentoo-user] " 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=loom.20160424T185859-563@post.gmane.org \
    --to=wireless@tampabay.rr.com \
    --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