| 1 |
On Sun, Apr 12, 2015 at 5:59 AM, hasufell <hasufell@g.o> wrote: |
| 2 |
> On 04/11/2015 01:54 PM, Rich Freeman wrote: |
| 3 |
>> |
| 4 |
>> 1. What does proxy-maintainers lack in comparison to sunrise |
| 5 |
>> exclusively. The immediate question is whether sunrise should be |
| 6 |
>> migrated to proxy-maintainers, so this specific comparison is |
| 7 |
>> important. |
| 8 |
>> |
| 9 |
> |
| 10 |
> proxy-maintainers lack: |
| 11 |
> 1. a repository with a usable VCS |
| 12 |
|
| 13 |
proxy-maintainers is using git. Am I missing something? |
| 14 |
|
| 15 |
> 2. an actual review workflow... @proxy-maintainers are just some sort of |
| 16 |
> backup committers. it's not a hub for contributors to gather, discuss, |
| 17 |
> get reviews and improve skills |
| 18 |
|
| 19 |
My understanding is that github pull-requests are being used. I'll |
| 20 |
buy that the project is still fairly immature but it seems like they |
| 21 |
have a decent foundation for a review-oriented workflow. Perhaps you |
| 22 |
might consider getting involved and building improvements? |
| 23 |
|
| 24 |
> 3. means to ensure the tree doesn't break |
| 25 |
|
| 26 |
Well, we don't even do this well in the main repository. |
| 27 |
proxy-maintainers can use repoman, as can committers, but I'll buy |
| 28 |
that those aren't the best solution. There are already efforts to get |
| 29 |
travis-ci working on the main tree, and presumably this could be |
| 30 |
applied to proxy-maintainers as well. |
| 31 |
|
| 32 |
> 4. actively look for and educate potential developers, even before the |
| 33 |
> recruitment process |
| 34 |
|
| 35 |
Sure, but I don't see this as an issue with proxy-maintainers, but |
| 36 |
more of another layer to add. |
| 37 |
|
| 38 |
Honestly, I see many of the seeds of things that you're looking for in |
| 39 |
the project already. Change has been slow, but the number of people |
| 40 |
doing the work has also been small. We don't have a huge number of |
| 41 |
new devs in general, and most of those new devs are interested in |
| 42 |
being package maintainers, not "Gentoo Maintainers" helping to change |
| 43 |
how we do things. I'd be interested in suggestions as to how to |
| 44 |
recruit the latter, but I think the nature of our distro tends to |
| 45 |
appeal more to users who are more interested in the nuts and bolts |
| 46 |
than the organization. |
| 47 |
|
| 48 |
I get your frustration, but I think you should look more at the trend |
| 49 |
direction. Sure, we're not doing a lot in terms of a workflow not |
| 50 |
centered around having cvs commit rights, but we're doing a lot more |
| 51 |
than we were even a year ago. If there are others who would like to |
| 52 |
make it happen but see barriers to this, I'd be interested in hearing |
| 53 |
from them. |
| 54 |
|
| 55 |
-- |
| 56 |
Rich |
Archives