Gentoo Archives: gentoo-project

From: Steve Long <slong@××××××××××××××××××.uk>
To: gentoo-project@l.g.o
Subject: [gentoo-project] Re: Re: Re: Re: Plan, then communicate (no-list)
Date: Wed, 23 Jan 2008 19:40:34
Message-Id: fn852g$m9o$1@ger.gmane.org
In Reply to: Re: [gentoo-project] Re: Re: Re: Plan, then communicate (no-list) by "Wulf C. Krueger"
1 Wulf C. Krueger wrote:
2
3 >>> I'd wait for the bugs to come. If there are problems, we have Bugzilla
4 >>> to use for that.
5 >> That's fine for technical problems: it's a lot harder to use that to deal
6 >> with social problems.
7 >
8 > I've written it before (in the context of some discussions on the -dev
9 > mailinglist): People need to grow a thicker skin. If people are scared
10 > by "fighting" among the developer's I can't really help it. We have
11 > quarrels just like anyone else. We will piss each other off sometimes
12 > and either work it out or agree that we consider each other idiots.
13 > That's fine, that's life.
14
15 Agreed; I don't have an issue with disagreement: I have just seen too much
16 *nastiness* (especially on the dev m-l.) And it really annoys me that it
17 goes unremarked from devs, since they have signed up to _represent_ Gentoo.
18 Go and have the flamewar off-list, or on IRC. If it's someone you can't
19 speak with, deal with it professionally on-list by sticking to the topic at
20 hand (as far as possible.) Yeah there'll be times where that doesn't work,
21 but they should be exceptional, not commonplace.
22
23 > Most users I've heard or seen so far aren't even really concerned with
24 > social stuff but (semi-) technical things - no 2007.1 release
25 > (technical issue), GWN (semi-technical; lack of manpower and user
26 > contributions), quality of the tree (technical) and the Foundation
27 > bullshit (non-technical and without any real relevance for our users).
28 >
29 > If those are addressed (and all of them are), most of the discontent
30 > will either disappear or at least things will calm down again.
31 >
32 Yeah I don't think that addresses the issue of involvement though, and it is
33 a central problem for devs as well as users, since you are overstretched.
34 I've spoken to too many user who've complained, with good reason, to accept
35 that technical problems, especially lack of manpower, don't sometimes have
36 social causes.
37
38 >> would take a very brave user indeed to file a {user,dev}rel bug.
39 >
40 > (That would be a UserRel bug.) Why? How many people have been eaten by
41 > UserRel so far? ;-)
42 >
43 > Furthermore, seeing all those comments on Robbins' blog and from brief
44 > looks at the Forums, I'd say we have (more than ;->) enough brave users.
45 >
46 Heh, maybe so; thing is if someone's nasty to you (wherever it is) and
47 no-one else comments, you just assume that's the culture. If you then act
48 similarly, you will be flamed. That just leads to confusion and
49 ill-feeling, for zero benefit to anyone. And often that person will just
50 walk away (no need to show them the door) and you've lost an advocate and
51 gained a detractor.
52
53 > Yes, it will need some maturity but, yes, I *do* expect that from
54 > people who want to be taken seriously.
55 >
56 Sure, but devs have to show just as much, if not more, maturity; or we won't
57 take your claims to be snowed-under seriously. "You haven't got enough
58 people? Hmm I wonder why.."
59
60 >> what I am getting at is that users need to be molly-coddled to a certain
61 >> extent:
62 >
63 > We've had that. It was called User Representatives and it failed
64 > because the representatives decided not to represent anyone by either
65 > not showing up or simply doing next to nothing. I'm not into
66 > baby-sitting; I've three kids of my own. :-)
67 >
68 Hehe I know what you mean (not as many kids though.) I actually feel that
69 way about the devs (collectively.) I don't care how much you whinge about
70 being over-worked, you're doing it out of your own self-interest; you can
71 quit whenever you want, and some of you even think it acceptable to treat
72 Gentoo as your own "private playground." If you want more help, ask
73 *nicely* and *behave* nicely or no-one will want to play with you.
74
75 > Nevertheless, whenever a user approaches me with a minimum (!) of
76 > politeness by mail, in the Forums or on IRC, I treat him/her like
77 > that, too.
78 >
79 >> they're in a position of less power and not so comfortable with the
80 >> processes.
81 >
82 > Maybe but we need a certain degree of processes and people *will* have
83 > to follow them just like I have to as well.
84 >
85 Sure; but if you look at users as potential future devs, it's worthwhile
86 helping them when they are clearly out of their depth. A quiet bit of help
87 at the beginning makes the world of difference, and brings you a "convert."
88 There've been a few times in #friendly-coders when someone has asked a
89 really stupid question, and I really haven't been in the mood to deal with
90 them. The times when I've bit my tongue and just pointed them in the right
91 direction, have pretty much always ended up positively.
92
93 There's been the odd time that hasn't worked, but others have stepped in to
94 explain (usually after I've hit !diy, !ego and !igli ;) and only once have
95 we had to kb someone (after days of problems; he's come back a bit wiser,
96 finally.)
97
98 >>> No, really. I don't want anyone to leave but if someone really thinks
99 >>> Gentoo is going down the drain (which it isn't), I can't do much about
100 >>> it.
101 >> Sure; but if they're going to leave that's up to them. Scaring em off
102 >> (which is how "if you don't like it, there's the door" sounds) isn't in
103 >> Gentoo's interest imo.
104 >
105 > Sometimes, that's the only reasonable answer, though.
106 >
107 Well it's the answer I'd personally give to the drobbins ultimatum, but I'd
108 never say that to my users for any software I've ever written. I might
109 say "I don't want/have the time to add that, feel free to patch it, and
110 [maybe] I'll help you with it." If you don't see users as your client, you
111 won't get anywhere with software development ime. You might get paid, but
112 you won't be asked back; the best software is always the stuff that
113 end-users (be that admins, end-users or other coders) feel ownership of,
114 because it's been developed in response to their needs. No user buy-in, no
115 use of your code, as many large organisations have found (usually just
116 after they rolled out their new EIS that was a year late and /way/
117 over-budget, only for everyone to ignore it.)
118
119 Yeah devs are users too; but imo please the users and the devs will be happy
120 (if they're not they can change it) since they get more kudos as everyone
121 wants to use it. Please the devs only, and all you get is technically nice
122 software that no-one else knows how to use, and frankly you code yourself
123 into irrelevance since everyone's using the other software that makes them
124 *feel good* about wastin^W spending all their time on a computer.
125
126 Devs are just as susceptible to the "ooh, shiny" bit as well; it's human
127 nature. Many books have been written on HCI and they overlap with
128 psychology (although the resultant doctoral students annoy the hell out of
129 me, as they have nfc when it comes to implementation and they claim to know
130 CS.) It's not something a coder typically worries about, but we like the
131 same interfaces, especially for apps we don't know.
132
133 To be an effective coder, imo, you have be able to think like a user (which
134 is why it's fun: you see what happens in all the other industries close up
135 at a data-level.) Spending your days sneering at users is not a good career
136 move, and imo Gentoo should stamp on it-- hard.
137
138 NB: None of this means entertaining unreasonable demands or tolerating
139 discourteous behaviour.
140
141 > "TF"? :-)
142 >
143 /me looks innocent: Thank Freitag! ;p
144
145
146 --
147 gentoo-project@l.g.o mailing list