Re: [gentoo-dev] Re: Help maintaining dev-erlang and ejabberd

[R0b0t1 <r030t1@gmail.com>]

On Wed, Aug 23, 2017 at 9:33 PM, Duncan <1i5t5.duncan@cox.net> wrote:
> 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.
>

Hello,

I am waiting to forward this comment chain to proxy-maint@gentoo.org
pending a reply from aidecoe, or waiting for him to do the same at his
leisure. It is possible someone else may reply that is a better fit. I
am not very smart, sir, and I do not want to disappoint the Gentoo
project.

The developer's manual was easy enough to find
(https://devmanual.gentoo.org/). Are there subsections of that manual
or related documents you (or aidecoe) would suggest I read in their
entirety before starting? I am vaguely aware of standards documents
and style guidelines that are important for code committed to the main
portage tree.

Respectfully,
     R0b0t1