| 1 |
Alec Ten Harmsel <alec <at> alectenharmsel.com> writes: |
| 2 |
|
| 3 |
|
| 4 |
> There is a large discussion on the Spark mailing list right now about |
| 5 |
> having groups of maintainers for different areas: |
| 6 |
|
| 7 |
> |
| 8 |
http://apache-spark-developers-list.1001551.n3.nabble.com/VOTE-Designating-maintainers-for-some-Spark-components-td9115.html |
| 9 |
|
| 10 |
|
| 11 |
This is an excellent link and model for a "hi profile" software. |
| 12 |
It is a very open and accountable model for code development, reviewing |
| 13 |
patches, including patches and in general code maintenance and bug |
| 14 |
fixes. |
| 15 |
|
| 16 |
> I'm not sure how relevant that is, but it's interesting. |
| 17 |
|
| 18 |
It is relevant to very large and important codes. I do believe that |
| 19 |
most of the gentoo ebuilds (packages) will not be afforded this |
| 20 |
level and number of devs. As the gentoo distro grows, it is a model |
| 21 |
for the devs and the council to keep in mind for those critically |
| 22 |
important packages... |
| 23 |
|
| 24 |
|
| 25 |
James |
Archives