99:
original PHG arbitration was precisely crafted, a good piece of work, in my opinion, but I think that, even then, too little attention was paid to the positive side, and, as well, to other problems in the community which PHG faced. If it helps keep the peace in the community, then the continuation of a more precisely defined restriction is reasonable, which should be, properly construed and with the positive findings, practically harmless. Where new conflicts arise, I would advise PHG to back off, and act *as if* there were some restriction, a voluntary 1RR restriction (0RR if the dispute has become clear and remains unresolved, even a single revert should be used only with some reasonable expectation of acceptance by other editors). Sophisticated and collaborative editors tend to do this anyway. We'd be fools to not use the best of what he does, because we fear (or even see) problems with some of it. On the other hand, PHG should not take up his own cause but get help, when conflicts arise.
95:
arbitration was presented to the community, as if it had been a finding of bad faith, deception, and ongoing danger to the project, rather than merely the kind of misrepresentation of sources that is not uncommon among experts (or knowledgeable amateurs) when they read into sources what is not there. We *all* need fact-checking, none of us are totally free of bias in reading sources. PHG was also blocked as the result of a translation error, the kind of error which could afflict any of us. (Even within our own language, we may construe words with unintended meanings.) Expecting a highly productive editor to never make mistakes, I am sure, wasn't the intention of ArbComm; rather, reasonable caution was intended.
76:.) Blocks should be reserved for true disruption and lack of response to warnings. While an ArbComm sanction may be considered a strong warning, a "general" warning may still need specific application before the warned person understands the immediate application. "Construed broadly" may have opened a door to practically ridiculous extensions.
102:
I have no experience drafting ArbComm "remedies" or statements, but I suppose I should try if someone else doesn't get to it before me. We need to provide the other side, the carrot, not just the stick, even if we more precisely aim that stick. I'd claim that we may not have needed the stick in the
90:
Editors, familiar with this case, concerned about future behavior of PHG, should now consider contacting PHG's mentor or his advisors; I'm one of the latter. I did *not* advise him to file this case, I wasn't asked, though I was informed of it. Had I not been busy at the time, I might have advised
59:
Some editors seem to have become over-involved, at points, in "restraining" or "sanctioning" or "enforcing sanctions against" PHG, to the extent of harassment. He was blocked for allegedly violating his ban, when, in fact, he had not violated it. Claims were made that he had been sanctioned for
98:
What I'd like to see a statement by ArbComm affirming clearly that PHG is an extraordinarily valuable editor, that we are grateful for his contributions, and grateful as well for his persistence even in the face of adversity (many editors might simply have gone away, given what he faced). The
63:
I do not doubt their good faith; however, PHG is also an extraordinarily valuable editor on the creation and writing side, even though he may need fact-checking and other editorial support. My observation and expectation is that if there is a genuine problem, a friendly warning would now be
94:
It is not that I object to the substance of his request, but he might more simply obtain what he needs. ArbComm never confirmed a truly serious charge against him (such as deliberate insertion of false material or willful falsification of sources); the problems I saw had to do with how the
64:
sufficient; he would cease the behavior and seek consensus or other resolution with the assistance of other editors. Given that, blocking him seems excessive, especially if a violation isn't clear or egregious, especially if it is doing no harm (such as creating an article on
35:
FYI, I will be out of the U.S. for the next week, and probably won't have internet access. I should be back online by
January 5, 2009. My apologies for any delays that this may cause in the current case.
118:
As someone who has recently collaborated with PHG on edits, I find these suggestions very helpful. I agree that he is enthusiastic, resourceful and has a lot to offer WP.
134:
137:
about PHG. Please use some of the evidence and create a nice, tasty, crispy, orange carrot, or even more than one carrots. Proposal for titles based in your text here:
21:
60:"falsifying sources," which implies intentional misrepresentation, whereas the committee formally concluded that it could continue to assume good faith.
17:
65:
43:
160:
127:
112:
46:
156:
79:
Some of what PHG faced, as a result of how the original ArbComm ruling was taken, may be seen at
123:
40:
152:
108:
119:
37:
104:
72:
contained a fact dating back to medieval times, which it did not). (See
81:
Arbitration enforcement discussion cited in PHG's last block
84:
80:
73:
144:Advice to PHG for self-imposed engagement rules
56:I don't know where to put this, so ... here.
18:Knowledge (XXG) talk:Requests for arbitration
8:
52:About Enforcement of Sanctions against PHG
141:PHG is an extraordinarily valuable editor
103:first place, but what is done is done. --
133:I think that we have enough positive
66:France-Japan relations (19th century)
7:
28:
1:
161:20:12, 30 December 2008 (UTC)
147:PHG contributes in good faith
128:21:55, 29 December 2008 (UTC)
113:21:23, 29 December 2008 (UTC)
91:him to withdraw his request.
47:07:11, 28 December 2008 (UTC)
176:
85:block log for PHG
83:. For reference,
167:
175:
174:
170:
169:
168:
166:
165:
164:
54:
33:
26:
25:
24:
12:
11:
5:
173:
171:
149:
148:
145:
142:
131:
130:
53:
50:
32:
29:
27:
15:
14:
13:
10:
9:
6:
4:
3:
2:
172:
163:
162:
158:
154:
151:Thank you. --
146:
143:
140:
139:
138:
136:
129:
125:
121:
117:
116:
115:
114:
110:
106:
100:
96:
92:
88:
86:
82:
77:
75:
71:
68:, even if it
67:
61:
57:
51:
49:
48:
45:
42:
39:
30:
23:
19:
150:
132:
101:
97:
93:
89:
78:
74:block notice
69:
62:
58:
55:
34:
153:FocalPoint
31:Wikibreak
135:evidence
20: |
120:Mathsci
16:<
157:talk
124:talk
109:talk
105:Abd
70:had
22:PHG
159:)
126:)
111:)
87:.
44:ka
41:on
38:El
36:--
155:(
122:(
107:(
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.