1 |
> > > Bug reports need to be thorough. If they do not provide enough |
2 |
> > > information to reproduce a bug, or at least explain exactly what is |
3 |
> > > going on, then it is hard for the developers and bug |
4 |
> > squashers to do |
5 |
> > > anything about it. |
6 |
> > |
7 |
> > Sometimes, as the reported, you miss some important things. Okay. |
8 |
> > Then the wrangler (or whom else works onthr bug) simply |
9 |
> > should ask for more information. |
10 |
> > |
11 |
> > But if your bugs are always marked as invalid, you loose any |
12 |
> > motiviation for further contributions. Bug reports are also |
13 |
> > contribution. |
14 |
|
15 |
Imo, provide as much information as possible, describe all paths of |
16 |
logic, dont assume bugwranglers are psychic. Verbosity can be your |
17 |
friend. |
18 |
If its marked invalid, then either they've given a damn good reason, |
19 |
or you've not given them a better one not to mark it invalid. In |
20 |
either case, if its invalid, keep posting as much information as |
21 |
possible on the subject, not just the what, but the why. |
22 |
I'm still at a loss why theres any need for symlinks to the coda FS |
23 |
when you could just tell firefox to build a profile /directly/ on that |
24 |
coda-fs. |
25 |
Im not saying there is no valid reason, just there has yet to be a |
26 |
good explanation as to why. |
27 |
If you can't on your own convince a dev to change a bugs status, find |
28 |
other people with similar problems to increase the validity of your |
29 |
claim. Bugs can be like a court room. No witnesses & no good evidence, |
30 |
a poor testimony, and you end up in jail. So you get all the evidence |
31 |
you can, get your witnesses, make a nice logical argument, and with |
32 |
any luck, the wrangler might reinstate its free status ( cos being |
33 |
invalid dosn't mean that the CC list will suddenly stop working afaik |
34 |
) |
35 |
|
36 |
> I can't really argue that one. I would also admit that I personally |
37 |
> tend to be a lot more patient in weedling information out of an |
38 |
> end user. Comes from tech support training. Do remember though that |
39 |
> a lot of techies are not people persons (I know that is not a great |
40 |
> excuse, or even good grammar). The founders of the open source movement |
41 |
> were notorious jerks. :P It is a matter of recorded fact. They |
42 |
> Focused more on the software and let their friends handle the people. |
43 |
|
44 |
I sympathize with them. The reason devs often tend to be jerks, is |
45 |
because people of lesser understanding often be as big a jerk when |
46 |
they envisage a problem which is really a case of "problem exists |
47 |
between keyboard and chair" or a case of "its not our fault, its |
48 |
somebody elses", and sadly for devs, there are an awful lot of people |
49 |
who know very little yet profess to know very much. ( Evidence? in |
50 |
high school i had one teacher tell me off for doing on a computer |
51 |
something another teacher had told me to do, because the one of |
52 |
lesser understanding didn't obviously have a clue what i was doing, |
53 |
and thus made drastic assumptions that i was 'writing viruses and |
54 |
hacking' .... and that was before I ever did any /real/ programming |
55 |
work :/ ... work in a company where you have customers, you'll |
56 |
probably find complications with 'customer doesn't understand, and |
57 |
thus we have to start again to fix a non-problem' ) |
58 |
|
59 |
|
60 |
> > > if the idea of creating a new profile would not work for you, |
61 |
> > > then recreating your firefox directory, with "physical" copies |
62 |
> > > of the symlinked files would do the trick as well. |
63 |
> > |
64 |
> > Not really. The symlinks are no problem for FF, it works perfectly |
65 |
> > well. And I *need* them to store temporary stuff locally. |
66 |
> > It's mozilla-launcher which artificially breaks if it |
67 |
> > *thinks* something could be wrong. |
68 |
> |
69 |
> |
70 |
> Personally, I don't realy know WHAT mozilla-launcher is I think. :P |
71 |
> I have always just created shortcuts to firefox directly, and let it |
72 |
> handle everything itself. |
73 |
> |
74 |
> > > Imagine if you just sunk three years into a project, and suddenly |
75 |
> > > someone started attacking you because it didn't work perfectly on |
76 |
> > > their system. |
77 |
> |
78 |
> > Well, I'm working on lots of OSS projects for many many |
79 |
> > years. But I never ever felt being attacked by an bug report. |
80 |
> |
81 |
> It is not the bug report that is the attack. It is the angry |
82 |
> declarations |
83 |
> of incompetense. The insistance that because you do not agree, that |
84 |
> something |
85 |
> must be wrong with the developers. The fact that in just a handful of |
86 |
> hours |
87 |
> working with a complicated issue, you declared the community at large to |
88 |
> be hostile and ignorant. |
89 |
|
90 |
Community is developer oriented, and thus, nasties and arrogance will abound =). |
91 |
Just look in -dev for your daily dose of flame war/soap opera. ( if |
92 |
your going to have a 100+ message flamewar that started from somebody |
93 |
complaining and missunderstanding an 'inside' joke, it looks kinda |
94 |
evident that some devs love arguing for the sake of it... so with that |
95 |
in mind, play safe, be nice :) ) |
96 |
|
97 |
> |
98 |
> That is just what I have seen from this situation. It is not the fact |
99 |
> that |
100 |
> you submit bugs, it is the way in which you do it. |
101 |
> |
102 |
> |
103 |
> -- |
104 |
> gentoo-user@g.o mailing list |
105 |
> |
106 |
> |
107 |
|
108 |
In favour of what Enrico did, although for all the world it seems like |
109 |
he fought a bit and went against advice, he found a problem, and |
110 |
provided the means for a solution, and placed it in bugzilla. Despite |
111 |
it being marked invalid, that bug will remain in there for the rest of |
112 |
the natural life of bugzilla, and if anyone else out there /does/ have |
113 |
the misfortune of having the same problem later, they'll find it ( cos |
114 |
they look hard ), try it, see it work, and say 'thanks enrico for |
115 |
fixing my problem' on the bottom. When that happens, maybe it might |
116 |
get migrated from being invalid, and somebody may consider changing it |
117 |
for the better, which is one of the fundemental benefits of OSS. You |
118 |
dont have to actually commit the bugfix into upstream to do a world of |
119 |
difference :) |
120 |
|
121 |
-- |
122 |
Kent |
123 |
ruby -e '[1, 2, 4, 7, 0, 9, 5, 8, 3, 10, 11, 6, 12, 13].each{|x| |
124 |
print "enNOSPicAMreil kdrtf@×××.com"[(2*x)..(2*x+1)]}' |
125 |
-- |
126 |
gentoo-user@g.o mailing list |