| 1 |
On Mon, 29 Oct 2012 19:30:40 +0100 |
| 2 |
Peter Stuge <peter@×××××.se> wrote: |
| 3 |
|
| 4 |
> Diego Elio Pettenò wrote: |
| 5 |
> > the understanding of "you're responsible for whatever you commit". |
| 6 |
> |
| 7 |
|
| 8 |
>> Outrageours rant deleted << |
| 9 |
|
| 10 |
> Isn't it outrageous to claim that people who create and |
| 11 |
> contribute to and around Gentoo without being developers |
| 12 |
> are any less responsible for what they do than devs are? |
| 13 |
|
| 14 |
I guess Diego's response is rooted in seeing bug reports about or |
| 15 |
finding bugs in ebuilds that have been tagged with "proxymaint". I've |
| 16 |
recently seen quite a few things with the same label that should not |
| 17 |
have been committed in the first place. |
| 18 |
|
| 19 |
> I have personal experience from several cases of the reverse, |
| 20 |
> but that doesn't make me think that it's the norm for devs to |
| 21 |
> behave irresponsibly. |
| 22 |
|
| 23 |
That's good to hear, but it says nothing about the (arguably) fringe |
| 24 |
cases of bad commits. |
| 25 |
|
| 26 |
> Diego, what you wrote does nothing other than make it seem like you |
| 27 |
> have a personal agenda against Arfrever. |
| 28 |
|
| 29 |
I don't normally agree with anything Diego says, mind you. |
| 30 |
|
| 31 |
> I expect that anyone and everyone who contribute to any open source |
| 32 |
> project will do their damndest to contribute only "perfect" work. |
| 33 |
|
| 34 |
Yes. And everyone makes mistakes when they fail to spot the |
| 35 |
imperfections. That's just human. But no one should ever hide behind |
| 36 |
the lame excuse that it was somebody else's work when it obviously was |
| 37 |
not the contributor/proxy developer who did the commit. |
| 38 |
|
| 39 |
At the other end of the spectrum, recently some people like to tie red |
| 40 |
tape around everything, hold up progress for months, and call that "QA". |
| 41 |
|
| 42 |
> I know that this is a pipe dream, but it does happen. I think the way |
| 43 |
> to make it happen more often is education, but not everyone is able |
| 44 |
> to educate and so, there is a gap.. |
| 45 |
> |
| 46 |
> Threats aren't an excellent way to try to close any gap IMO. WTF. |
| 47 |
|
| 48 |
Since it is a pipe dream, you have to expect and deal with careless |
| 49 |
commits as and when they occur, and keeping people on their toes is one |
| 50 |
way to help prevent it, rather than fix the mess afterwards. |
| 51 |
|
| 52 |
|
| 53 |
jer |
Archives