| 1 |
On 10/11/2015 09:19 AM, Sven Vermeulen wrote: |
| 2 |
> |
| 3 |
> This is good news. There are quite a few developers that manage a small |
| 4 |
> subset of packages while doing tremendous work for Gentoo within that |
| 5 |
> community. For instance, they focus on particular deliverables in |
| 6 |
> repositories which eventually get packaged, or on integration of certain |
| 7 |
> components which have a strong, broader community coverage. |
| 8 |
> |
| 9 |
> These developers will certainly welcome any helping hand (even post-commit) |
| 10 |
> in keeping packages of high quality. |
| 11 |
> |
| 12 |
> I hope you will also focus on the documentation side. Certain processes that |
| 13 |
> we follow within Gentoo (for commits, for instance the Git workflow) would |
| 14 |
> benefit from a good document *set* (yes, set, as you'll definitely want such |
| 15 |
> processes to have both a single-screen version as well as an elaborate |
| 16 |
> version). |
| 17 |
> |
| 18 |
> I've also found myself often looking for similar ebuilds in which a certain |
| 19 |
> problem would already have been implemented. For instance, ebuilds with an |
| 20 |
> optional python part using the python-r1 eclass. Do you think it is |
| 21 |
> worthwhile to have a number of packages assigned as good examples? |
| 22 |
> |
| 23 |
|
| 24 |
Those are great ideas, unfortunately we currently don't have a wiki guru |
| 25 |
in the team ;) |
Archives