| 1 |
On Mon, Oct 29, 2012 at 2:40 PM, Diego Elio Pettenò |
| 2 |
<flameeyes@×××××××××.eu> wrote: |
| 3 |
> You're free to disagree and not become a developer. But with commit |
| 4 |
> _rights_ come commit _responsibility_. If you commit something for |
| 5 |
> somebody else, you're still responsible if it breaks somebody else's |
| 6 |
> package, it doesn't exempt you from not doing _your_ work. |
| 7 |
|
| 8 |
++ |
| 9 |
|
| 10 |
We do have a trust with our users. It doesn't mean that non-devs |
| 11 |
don't write good code. They do. However, the purpose of vetted |
| 12 |
developers is to be a gatekeeper to what runs on our user's systems. |
| 13 |
|
| 14 |
Devs also should be good at spotting problems with ebuilds that cause |
| 15 |
issues that might not be apparent from simply running emerge. |
| 16 |
|
| 17 |
That's the value Gentoo adds as a distro. Anybody can publish an |
| 18 |
overlay, but devs are required to get stuff in the tree. |
| 19 |
|
| 20 |
All that said, anything we can do to lower barriers to contribution |
| 21 |
while maintaining quality is a good thing. I don't want devs to be |
| 22 |
afraid of committing things, but they should be making an honest |
| 23 |
effort to catch issues. |
| 24 |
|
| 25 |
Rich |
Archives