1 |
On Wed, Aug 23, 2017 at 9:33 PM, Duncan <1i5t5.duncan@×××.net> wrote: |
2 |
> R0b0t1 posted on Tue, 22 Aug 2017 21:46:09 -0500 as excerpted: |
3 |
> |
4 |
>> On Tue, Aug 22, 2017 at 3:50 PM, <aidecoe@g.o> wrote: |
5 |
>>> |
6 |
>>> Some time ago I've made an effort to split ejabberd into proper |
7 |
>>> dependencies handled by portage rather than repackaging bundle produced |
8 |
>>> by rebar. While I've found that easier to maintain, my lack of |
9 |
>>> knowledge about Erlang makes maintenanace quite difficult. I'd |
10 |
>>> appreciate if someone who actually has some experience in Erlang helps |
11 |
>>> maintaining it. |
12 |
>> |
13 |
>> I would like to see Erlang receive continued maintenance and may be |
14 |
>> able to help (note I am not as experienced as some). However this |
15 |
>> would be my first time working with portage at such a level. |
16 |
>> |
17 |
>> I apologize if my post is too forward for this list. |
18 |
> |
19 |
> Wonderful, and not too forward at all. =:^) |
20 |
> |
21 |
> The gentoo mechanism by which non-gentoo devs maintain or co-maintain |
22 |
> packages is called proxy maintenance: |
23 |
> |
24 |
> https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers |
25 |
> |
26 |
> For packages such as this one that you'd be co-maintaining along-side the |
27 |
> existing maintainer, you obviously work with them and have already |
28 |
> initiated contact there. You also need to contact the proxy-maintainer |
29 |
> project to initiate that angle. There's further details and additional |
30 |
> resources on the linked page, above. |
31 |
> |
32 |
|
33 |
Hello, |
34 |
|
35 |
I am waiting to forward this comment chain to proxy-maint@g.o |
36 |
pending a reply from aidecoe, or waiting for him to do the same at his |
37 |
leisure. It is possible someone else may reply that is a better fit. I |
38 |
am not very smart, sir, and I do not want to disappoint the Gentoo |
39 |
project. |
40 |
|
41 |
The developer's manual was easy enough to find |
42 |
(https://devmanual.gentoo.org/). Are there subsections of that manual |
43 |
or related documents you (or aidecoe) would suggest I read in their |
44 |
entirety before starting? I am vaguely aware of standards documents |
45 |
and style guidelines that are important for code committed to the main |
46 |
portage tree. |
47 |
|
48 |
Respectfully, |
49 |
R0b0t1 |