From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Help maintaining dev-erlang and ejabberd
Date: Thu, 24 Aug 2017 02:33:24 +0000 (UTC) [thread overview]
Message-ID: <pan$82e5c$a93c1d13$ca579a8a$c73c8e0f@cox.net> (raw)
In-Reply-To: CAAD4mYgv4yOEfx=B1Jc9gWY2iEsZzgLNyefBHTxvXGqRM1tmBw@mail.gmail.com
R0b0t1 posted on Tue, 22 Aug 2017 21:46:09 -0500 as excerpted:
> On Tue, Aug 22, 2017 at 3:50 PM, <aidecoe@gentoo.org> wrote:
>>
>> Some time ago I've made an effort to split ejabberd into proper
>> dependencies handled by portage rather than repackaging bundle produced
>> by rebar. While I've found that easier to maintain, my lack of
>> knowledge about Erlang makes maintenanace quite difficult. I'd
>> appreciate if someone who actually has some experience in Erlang helps
>> maintaining it.
>
> I would like to see Erlang receive continued maintenance and may be
> able to help (note I am not as experienced as some). However this
> would be my first time working with portage at such a level.
>
> I apologize if my post is too forward for this list.
Wonderful, and not too forward at all. =:^)
The gentoo mechanism by which non-gentoo devs maintain or co-maintain
packages is called proxy maintenance:
https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers
For packages such as this one that you'd be co-maintaining along-side the
existing maintainer, you obviously work with them and have already
initiated contact there. You also need to contact the proxy-maintainer
project to initiate that angle. There's further details and additional
resources on the linked page, above.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2017-08-24 2:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 20:50 [gentoo-dev] Help maintaining dev-erlang and ejabberd aidecoe
2017-08-23 2:46 ` R0b0t1
2017-08-24 2:33 ` Duncan [this message]
2017-08-24 4:26 ` [gentoo-dev] " R0b0t1
2017-08-24 21:48 ` Amadeusz Żołnowski
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='pan$82e5c$a93c1d13$ca579a8a$c73c8e0f@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-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