| 1 |
Victor <victor <at> enise.org> writes: |
| 2 |
|
| 3 |
|
| 4 |
> I have a couple of ebuilds for some software not in main tree, mainly |
| 5 |
> emacs and python modules. |
| 6 |
> What is the preferred way to contribute them without becoming a Gentoo |
| 7 |
> Developer? |
| 8 |
|
| 9 |
I think the preferred method (it takes time to go down the gentoo-dev or |
| 10 |
gentoo-proxy-maintainer pathways) is to setup a github acccount and post your |
| 11 |
body of work there because github makes it easy for folks to collaborate |
| 12 |
with you and your work. |
| 13 |
|
| 14 |
Who knows, maybe you'll also want to bring turbogears2 to gentoo? That would |
| 15 |
be very, bery cool! Turbogears1 use to be part of the packages available. |
| 16 |
Turbogears2 is very cool [1]. |
| 17 |
|
| 18 |
> Should I post them to bugzilla or maybe send to `python' and `emacs' |
| 19 |
> overlays (if so, how?), or `sunrise' overlay? Or create my own overlay? |
| 20 |
|
| 21 |
Yes, that way, we get immediate access to the ebuilds to test them out and |
| 22 |
give you feedback. Put up some details, related to these packages, either in |
| 23 |
bgo or a github/blog, particularly if they are part of a theme you are pursuing. |
| 24 |
|
| 25 |
|
| 26 |
hth, |
| 27 |
James |
| 28 |
|
| 29 |
[1] http://www.turbogears.org/current-status.html# |
Archives