497:
standards. Fairly inexperienced staff still sometimes move to a position when they'll be working with servers, so theres likely a great many readers that might find the article useful. Im only voting a weak keep as while its well above the typical standard we see from a new user, it will admittedly be challenging to clarify the articles scope and would take a long time to bring up to the quality of say the excellent
381:, and then cleanup the article to meet WP standards. Worst-case, the text that you object to could be removed and the article returned much to it's original more NPOV state. We would then still have at least a stub that others can expand on for this important topic as well as an edit history. Given the importance of
279:. It seems that many vendors are now using the term "Infrastructure 2.0". Perhaps that's a better name for a cleaned up version of the article that might have a section specifically on Dynamic Infrastructure. While I appreciate your contributions to Knowledge (XXG), you are throwing a lot of stones at
496:
Its the way all the big boys are heading, Im not aware of any serious enterprise class org that isnt at least investigating these models. Granted its not the most notable topic but then recent technologies that arent user facing rarely are, there's enough coverage in the IT press to pass our
477:— there seem to be plenty of references and external links, not just IBM, establishing notability. The tone of the article should be improved, but that does not mean it should be deleted. I have improved the references and done a little bit if tidying. More is needed! —
373:. However, it seems to me that any subject containing the words "Next generation" is doomed to have a very short shelf-life in the IT world. With IBM enforcing it's trademark on Dynamic Infrastructure, it's more likely that others will jump on the
275:. I assume that terminating the cancelation proceeding for the trademark on 24 August 2009 means that the term is now completely in the hands of IBM. However, the term may still be notable in its own right and deserves some discussion. See
165:
365:
should redirect to a new section of the moved article that presents the history of the terms, including IBM's trademark on
Dynamic Infrastructure. I do note that Google shows close to 20M hits for
323:
I agree with you on the trademark issue. We should first decide if we want to keep the article under this name, merge it into another IBM product article, or rework it into an article on
287:. Since IBM is pushing Dynamic Infrastructure as part of their Cloud Computing solution, there's a chance that you work for a direct competitor of IBM in this field. If so, it would be a
126:
159:
448:
309:. Discussing an IBM trademark in a generic context makes the article even more problematic and if it is to remain then it should at least explain the trademark situation.
291:
that I think you should disclose when proposing to delete an article related to IBM. Disclaimer: I have never worked for IBM or any Cloud
Computing vendor.
393:, I'm interested to hear your take on this. Can you see two such articles compliment each other, or do you prefer to delete this article outright and bury
93:
88:
97:
80:
252:
which removed my dated prod *and* forward-dated two article issues templates (confusing & cleanup) while adding a raft of problematic text.
361:
to it. Both names are already referenced in the first sentence of the article. There are currently no redlinks to either topic. The new
180:
17:
147:
228:* (per edit logs). With sections like "Need for a holistic approach" and "Benefits of having a dynamic infrastructure" and no
272:
141:
525:
36:
510:
486:
466:
428:
410:
336:
318:
300:
261:
229:
84:
62:
137:
386:
366:
358:
52:
that have no bearing on a topic's suitability for inclusion. The threshold for inclusion in the encyclopaedia is
524:
Subsequent comments should be made on the appropriate discussion page (such as the article's talk page or in a
314:
257:
35:
Subsequent comments should be made on the appropriate discussion page (such as the article's talk page or in a
187:
305:
And while I appreciate your right to an opinion you are wrong with your accusations and perhaps should try
506:
424:
406:
362:
332:
296:
76:
68:
416:
394:
382:
378:
374:
370:
354:
324:
244:
created for the purpose of editing this article) it is clear that
Knowledge (XXG) is being abused as a
49:
225:
463:
267:
It seems that other companies may have been counting on overturning the IBM trademark since googling
276:
245:
153:
310:
280:
253:
237:
173:
57:
213:
502:
482:
420:
402:
328:
292:
29:
The following discussion is an archived debate of the proposed deletion of the article below.
209:
306:
288:
241:
53:
498:
455:
398:
390:
221:
205:
201:
478:
114:
48:. Issues with verifiability, neutrality, tone and other inappropriate content are
197:
353:
OK, I've looked into it. I think the current article should be moved to
377:
band wagon. I propose that we close this AfD, open a move proposal to
327:. I need to look into it a bit deeper before making a recommendation.
518:
The above discussion is preserved as an archive of the debate.
56:, and there is consensus here that this topic has reached that.
419:
might be best if they have any success enforcing the patent.
284:
249:
233:
217:
121:
110:
106:
102:
172:
415:
That's a bit sharp of IBM! I agree that redirects to
54:
significant coverage in independent reliable sources
186:
39:). No further edits should be made to this page.
528:). No further edits should be made to this page.
449:list of Computing-related deletion discussions
8:
443:
447:: This debate has been included in the
18:Knowledge (XXG):Articles for deletion
7:
24:
283:when you seem to have your own
511:18:05, 11 September 2009 (UTC)
487:11:49, 11 September 2009 (UTC)
429:18:05, 11 September 2009 (UTC)
63:14:19, 12 September 2009 (UTC)
1:
467:23:49, 5 September 2009 (UTC)
411:09:27, 6 September 2009 (UTC)
337:02:32, 6 September 2009 (UTC)
319:16:31, 5 September 2009 (UTC)
301:08:58, 5 September 2009 (UTC)
269:"Dynamic Infrastructure" -IBM
262:07:14, 5 September 2009 (UTC)
248:. Most problematic though is
208:issues, little in the way of
387:Next generation data center
367:Next generation data center
359:Next generation data center
545:
521:Please do not modify it.
369:and just over 100K for
212:and it has read like an
32:Please do not modify it.
363:Dynamic Infrastructure
77:Dynamic Infrastructure
69:Dynamic Infrastructure
357:with a redirect from
232:whatsoever (beyond a
210:neutral point of view
289:conflict of interest
204:, there are serious
307:assuming good faith
50:resolvable problems
417:Infrastructure 2.0
395:Infrastructure 2.0
383:Infrastructure 2.0
379:Infrastructure 2.0
375:Infrastructure 2.0
371:Infrastructure 2.0
355:Infrastructure 2.0
325:Infrastructure 2.0
216:ever since it was
44:The result was
469:
452:
536:
523:
461:
453:
191:
190:
176:
124:
118:
100:
60:
34:
544:
543:
539:
538:
537:
535:
534:
533:
532:
526:deletion review
519:
499:cloud computing
459:
399:Cloud Computing
391:Cloud Computing
133:
120:
91:
75:
72:
58:
37:deletion review
30:
22:
21:
20:
12:
11:
5:
542:
540:
531:
530:
514:
513:
490:
489:
479:Jonathan Bowen
471:
470:
440:
439:
438:
437:
436:
435:
434:
433:
432:
431:
344:
343:
342:
341:
340:
339:
311:CloudComputing
254:CloudComputing
194:
193:
130:
71:
66:
42:
41:
25:
23:
15:
14:
13:
10:
9:
6:
4:
3:
2:
541:
529:
527:
522:
516:
515:
512:
508:
504:
500:
495:
492:
491:
488:
484:
480:
476:
473:
472:
468:
465:
462:
458:
450:
446:
442:
441:
430:
426:
422:
418:
414:
413:
412:
408:
404:
400:
396:
392:
388:
384:
380:
376:
372:
368:
364:
360:
356:
352:
351:
350:
349:
348:
347:
346:
345:
338:
334:
330:
326:
322:
321:
320:
316:
312:
308:
304:
303:
302:
298:
294:
290:
286:
282:
281:User:Kbrhouse
278:
274:
270:
266:
265:
264:
263:
259:
255:
251:
247:
243:
239:
238:User:Kbrhouse
235:
234:pronouncement
231:
227:
223:
220:*from an IBM
219:
215:
211:
207:
206:verifiability
203:
199:
189:
185:
182:
179:
175:
171:
167:
164:
161:
158:
155:
152:
149:
146:
143:
139:
136:
135:Find sources:
131:
128:
123:
116:
112:
108:
104:
99:
95:
90:
86:
82:
78:
74:
73:
70:
67:
65:
64:
61:
55:
51:
47:
40:
38:
33:
27:
26:
19:
520:
517:
503:FeydHuxtable
493:
474:
456:
444:
421:FeydHuxtable
403:UncleDouggie
329:UncleDouggie
293:UncleDouggie
268:
195:
183:
177:
169:
162:
156:
150:
144:
134:
45:
43:
31:
28:
401:somewhere?
273:68,500 hits
202:not notable
160:free images
285:SPA issues
277:WP:PRODUCT
230:discussion
59:Skomorokh
494:Weak Keep
250:this edit
226:trademark
198:neologism
271:returns
127:View log
246:soapbox
218:created
166:WP refs
154:scholar
94:protect
89:history
464:(talk)
222:patent
214:advert
138:Google
122:delete
98:delete
460:cobra
457:Cyber
236:from
196:This
181:JSTOR
142:books
125:) – (
115:views
107:watch
103:links
16:<
507:talk
483:talk
475:Keep
445:Note
425:talk
407:talk
333:talk
315:talk
297:talk
258:talk
240:- a
224:and
174:FENS
148:news
111:logs
85:talk
81:edit
46:keep
501:.
397:in
389:to
242:SPA
200:is
188:TWL
509:)
485:)
454:--
451:.
427:)
409:)
335:)
317:)
299:)
260:)
168:)
113:|
109:|
105:|
101:|
96:|
92:|
87:|
83:|
505:(
481:(
423:(
405:(
385:/
331:(
313:(
295:(
256:(
192:)
184:·
178:·
170:·
163:·
157:·
151:·
145:·
140:(
132:(
129:)
119:(
117:)
79:(
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.