1 |
On Sat, 16 Dec 2017 14:38:58 +0100 |
2 |
Toralf Förster <toralf@g.o> wrote: |
3 |
|
4 |
> On 12/16/2017 09:34 AM, Daniel Campbell wrote: |
5 |
> > I learned from this experience that |
6 |
> > I don't need to be a member of a distribution to contribute |
7 |
|
8 |
> So there's no need to become a dev to just contribute - but shouldn't |
9 |
> make it that task easier? |
10 |
|
11 |
I guess not if your ndewly gained title makes some other developers |
12 |
think they can treat you as trash, and that yet more developers |
13 |
entirely fail to stop those few nasties. You might just become more |
14 |
timid, distrust your own contributions, retreat into a niche where no |
15 |
one might bother you. That's where the fun stops. I should know. I've |
16 |
been retreating there for years.[1] |
17 |
|
18 |
> Therefore my (naive) question - what is the advantage to give away the |
19 |
> dev status ? |
20 |
|
21 |
Daniel quite adequately explains that the balanced tipped to the side |
22 |
of the bad stuff. His story suggests to me that "giving away the dev |
23 |
status" isn't an apt paraphrasing. |
24 |
|
25 |
|
26 |
|
27 |
jer |
28 |
|
29 |
|
30 |
|
31 |
[1] Even more so this year, when some of the younger developers |
32 |
invested in several important teams started teaming up and bullying |
33 |
most other developers in the name of mostly their own cleverness but |
34 |
also QA, CI and something still ironically called Community Relations. |