95:
lists and most of the people involved over the years have never met each other as it really was a multinational team. These days I defer all decisions to Bart and I did to Tim when he was lead developer. So really I have no provable COI above that of a knowledgeable user as anyone who had a clue about the subject would know, and which bart did point out. Personally I believe that the "obsessive interest" some parties have shown in controlling the edits to the
22:
89:
and before that being a test user of the application. I am now trying to rewrite the K-3D wikipedia page. There may be even earlier references, will add them if found, they may go back to the late 1990s! Since then I have not owned or used a computer with anything but some form of Linux or BSD unix
108:
demonstrates. The same interfering parties have put a lot of effort into destroying that image file, one of those accounts is now blocked from wikipedia. The
Luxrender output was a great example of how Tim's C++ code was designed well, to allow multiple input and output formats to be easily plugged
103:
These days I only use K-3D if my kids want help with something that they find it is useful for, but it is far from dead and runs fine on the latest hardware and Linux operating systems (Manuel A. Fernandez
Montecelo maintains the Debian build, which is also used by many derivatives such as Mint and
94:
page about that. I have certainly played around with the application a lot in the process of the
Windows support role, one that was entirely voluntary and from which I have derived no benefit. Each new feature was tested by me. Almost all of the work was managed in the public eye via the mailing
150:
Oh well that didn't work out well, somebody really badly wanted to hide the history of that page so destroying it was the only choice they and their supporters considered despite there being alternatives which were pointed out to them. They even hit me with a bogus block that prevented me
69:
and has not and will not make any edits associated with that specific aspect of the topic of K-3D on
Microsoft Windows. Any other edits will be on the basis of knowledge gained from reading the publicly available mailing lists associated with the topic, and therefore
171:
It would appear that the individual who initiated the destruction of the K-3D page as finally succeeded in destroying themselves. Time will tell if this is permanent. It would be nice to think that we can get back to doing good without further interference. See:
99:
page is simply malicious interference motivated by their sense of self importance. They could have made the improvements themselves, but didn't, they just delete, revert, or resort to "interference by abuse of procedure".
117:
page has "deleted" status the the deleter is justifying it a way that I have questioned on ethical grounds. I have highlighted the problem with what happened and also requested help with the ethics issue.
109:
into the core architecture of the applications graphics pipeline. Ultimately, if the interference continues, it is all the people who may miss out on learning how to use K-3D that will suffer, not I.
137:
155:, and was just as toxic. So now I have to rebuild the entire page and then update it, using similar free open source software pages as rough template/example.
65:
Dsmatthews was, over ten years ago responsible for the compilation, packaging and testing of the
Microsoft Windows version of the software
128:
User talk:L235#Assistance required to resolve ethical problem with User talk:Sandstein#Request to restore page K-3D
104:
Ubuntu), even the rendering export modules for
Luxrender work, as the linked file at the bottom of the
180:
160:
144:
75:
54:
122:
218:
49:
people in total actually, will add them to the template above if they get their own logins.
266:
242:
194:
114:
105:
96:
91:
83:
66:
127:
32:
151:
participating in the discussion. What happened stinks worse than a bucket full of
90:
on it (yeehah!). Supporting
Windows was a PITA, not that I'd say anything on the
134:
I have requested a Review of the
Deletion, on ethical and technical grounds.
28:
173:
152:
174:https://en.wikipedia.org/User_talk:Codename_Lisa
123:User talk:Sandstein#Request to restore page K-3D
138:Knowledge:Deletion review/Log/2018 January 13
8:
186:
82:Having handled the Windows builds of
7:
16:
219:"Re: [K-3D dev] K-3D news!"
14:
27:This user may sometimes share an
20:
163:) 10:40, 24 January 2018 (UTC)
147:) 10:17, 14 January 2018 (UTC)
78:) 10:40, 24 January 2018 (UTC)
57:) 06:14, 24 January 2018 (UTC)
1:
183:) 02:22, 16 March 2018 (UTC)
297:
61:Declarations of interest
267:"K-3D / Mailing Lists"
243:"K-3D / Mailing Lists"
195:"K-3D / Mailing Lists"
113:As things stand the
39:
38:
288:
281:
280:
278:
277:
263:
257:
256:
254:
253:
239:
233:
232:
230:
229:
215:
209:
208:
206:
205:
191:
24:
23:
17:
296:
295:
291:
290:
289:
287:
286:
285:
284:
275:
273:
271:sourceforge.net
265:
264:
260:
251:
249:
247:sourceforge.net
241:
240:
236:
227:
225:
217:
216:
212:
203:
201:
199:sourceforge.net
193:
192:
188:
169:
133:
112:
80:
63:
58:
42:
40:
21:
12:
11:
5:
294:
292:
283:
282:
258:
234:
210:
185:
168:
165:
131:
130:
125:
87:many years ago
62:
59:
44:
37:
36:
25:
15:
13:
10:
9:
6:
4:
3:
2:
293:
272:
268:
262:
259:
248:
244:
238:
235:
224:
223:lists.gnu.org
220:
214:
211:
200:
196:
190:
187:
184:
182:
178:
175:
166:
164:
162:
158:
154:
148:
146:
142:
139:
135:
129:
126:
124:
121:
120:
119:
116:
110:
107:
101:
98:
93:
88:
85:
79:
77:
73:
68:
60:
56:
52:
48:
43:
34:
30:
26:
19:
18:
274:. Retrieved
270:
261:
250:. Retrieved
246:
237:
226:. Retrieved
222:
213:
202:. Retrieved
198:
189:
176:
170:
156:
149:
140:
136:
132:
111:
102:
86:
81:
71:
64:
50:
46:
41:
70:verifiable.
276:2018-01-10
252:2018-01-10
228:2018-01-10
204:2018-01-10
177:Dsmatthews
157:Dsmatthews
141:Dsmatthews
72:Dsmatthews
51:Dsmatthews
29:IP address
33:QuietOwl
153:skatole
167:Karma
47:seven
31:with
181:talk
161:talk
145:talk
115:K-3D
106:K-3D
97:K-3D
92:K-3D
84:K-3D
76:talk
67:K-3D
55:talk
45:Yup
269:.
245:.
221:.
197:.
279:.
255:.
231:.
207:.
179:(
159:(
143:(
74:(
53:(
35:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.