300:
edited text. The GFDL generally requires a record of contributions be kept in order to keep compliant with the license, and that's why in cases where you merge something, you usually do a redirect. The only way you could get around it would be if you were the only significant contributor, which I assume is not the case. I'm also not sure if it's the case that you're copying mission notes directly from NASA, which would also be acceptable. In terms of reducing clutter on
Knowledge (XXG), it's really not worth worrying about, as the storage requirements are too vast for the individual to matter with the aggregate. Let's assume it takes 1 megabyte of space to keep this page around. Last year about this time, the database was 1.2 Terabytes
303:. Since one terabyte is one million megabytes, that means we could have over a million copies of this one article and still have room for well...a lot. It's not worth worrying about for that reason. (Especially since in reality, the page probably takes up a tenth or less of that size). Yes, eventually there will be problems with the size of Knowledge (XXG), but it's not going to be handled by boiling tea cups of the ocean with a candle.
318:
It was just a mistake on my part for not thinking it through, again my most abject apologies. I'd appreciate if someone could handle the redirect, and remove the AFD notice, and feel free to remove my addition, and I'll just try and find a way to re-word everything, without losing all the NASA URL references while doing it. So much for my first foray into AfD, lol.
327:
The thing is, if there's any significant edits done (even formatting) once it gets away from NASA (which is a federal agency and thus public domain), you'd run afoul of the GFDL attribution. Since there are in-line references, I'd say that is your problem, and as such, the best thing to do is to use
317:
Understood, and of course, I knew that copying and pasting entire articles is a no-no, but basically this is a list of activities as stated from NASA's end of day Status
Reports, nothing changed in what the crew did, or how they did it, so it makes it quite difficult to even attempt to "rewrite" it.
282:
I actually had nearly half of the mission notes written up by hand, and then I found the timeline page, so yes I transferred it as written. However, when pages are merged that contain timeline information that didn't change between the versions, how is the merge handled? I apologize if I merged it
299:
If you want something deleted in its current form, but used elsewhere, the appropriate way to do it is to work from the actual sources involved, and to not involve any other edits on
Knowledge (XXG). Though you can get information such as a list of those references from it, you shouldn't copy the
337:
I agree with you FrozenPurpleCube, and I completely understand. Again my apologies for handling it in the wrong way. I'd appreciate anyone who can take care of the redirect/merge, as I guess I still don't understand: If you redirect, are you allowed to "copy/paste" merge, or do you still have to
283:
wrong, and I'd be happy to learn the proper way to merge information such as this. Also, it seems that a redirect is the most appropriate choice, so my apologies for not considering that, I was thinking more of reducing "clutter" from
Knowledge (XXG), and I apologize. Thanks.
382:
Yeap. If you copy/paste stuff, the edit history has to be preserved. Leave a note on the talk page of the new page as to where to find the edit history. As of now, this cannot be closed because there is still a "Delete" vote on the board and thus, would not qualify for a
344:
When I redirect/merge, what I do is make sure to note it in the edit summary that I'm copying from a given location, both when I'm pasting over and I'm making the redirect. There is no need to further rewrite it (except for whatever cleanup issues are appropriate). See
289:
Basically you cannot copy content from article to another. This is because the revision history must be maintained, otherwise the GFDL is being violated. The 'merge' is handled by re-writing the data yourself from the external sources and deleting the original
156:
is working to standardize all the mission articles into the same format, so the timeline should remain with the mission page, not as a separate article. While STS-115 will need pruning, this orphaned article can probably be purged. Notices placed on
268:
How was the merge done? Did you copy from this page? That's the way it looks to me, in which case, a deletion is not appropriate, but rather a redirect in order to satisfy the attribution requirements of the GFDL.
395:
Actually, I think it can, since the delete argument can be dismissed as ignorant of the merge. But I'll ask that person to strike their comment unless they feel it doesn't belong as part of STS-115.
121:
338:
re-write the entire thing? If someone would like to remove the AfD, and do whatever is needed, I'll be happy to attempt to rewrite it, if that's required.
162:
94:
89:
153:
98:
81:
239:
17:
222:
444:
36:
180:. Since you've merge the articles, I don't see how this article serves a purpose. It's far from encyclopedic, anyway
429:
400:
390:
373:
353:
339:
332:
319:
307:
294:
284:
273:
256:
242:
226:
197:
170:
63:
328:
the merge/redirect solution. It's far less work, and there's no real benefit from doing things the harder way.
443:
Subsequent comments should be made on the appropriate discussion page (such as the article's talk page or in a
85:
35:
Subsequent comments should be made on the appropriate discussion page (such as the article's talk page or in a
397:
350:
329:
304:
270:
422:
238:. That way if something is missed, others can still look over the information, if they try hard enough. --
190:
58:
218:
148:, and this page can be deleted. It has been orphaned since March 2007. The only link to the page is
141:
77:
69:
369:
Since info is merged - Stuff like this has historic notability and is covered by reliable sources
346:
415:
183:
29:
The following discussion is an archived debate of the proposed deletion of the article below.
149:
210:
384:
48:
for GFDL compliance as information from this article had been substantially merged into
166:
158:
414:
The only reason I said "Delete" is because the OP had already merged the subject.
251:
Good idea, there is one other "Timeline" article that could use that as well, for
115:
291:
53:
387:
370:
301:
52:
prior to nomination and to retain any information for future reference.
252:
235:
206:
145:
137:
133:
129:
49:
437:
The above discussion is preserved as an archive of the debate.
111:
107:
103:
39:). No further edits should be made to this page.
447:). No further edits should be made to this page.
8:
154:Knowledge (XXG):WikiProject_Space_missions
128:To standardize shuttle missions, (see
18:Knowledge (XXG):Articles for deletion
7:
24:
240:Richard Arthur Norton (1958- )
1:
430:15:52, 10 August 2007 (UTC)
401:05:24, 10 August 2007 (UTC)
391:05:12, 10 August 2007 (UTC)
374:04:54, 10 August 2007 (UTC)
354:06:02, 10 August 2007 (UTC)
340:05:05, 10 August 2007 (UTC)
333:04:52, 10 August 2007 (UTC)
320:04:20, 10 August 2007 (UTC)
308:03:18, 10 August 2007 (UTC)
295:03:09, 10 August 2007 (UTC)
285:02:05, 10 August 2007 (UTC)
274:01:57, 10 August 2007 (UTC)
257:01:25, 10 August 2007 (UTC)
243:01:21, 10 August 2007 (UTC)
227:01:16, 10 August 2007 (UTC)
198:00:32, 10 August 2007 (UTC)
171:00:25, 10 August 2007 (UTC)
152:which can also be removed.
64:19:17, 10 August 2007 (UTC)
464:
255:. Thanks for the input!
440:Please do not modify it.
32:Please do not modify it.
169:(current flight).
142:Timeline of STS-115
78:Timeline of STS-115
70:Timeline of STS-115
163:Project talk page
455:
442:
426:
419:
398:FrozenPurpleCube
351:FrozenPurpleCube
349:for the steps.
330:FrozenPurpleCube
305:FrozenPurpleCube
271:FrozenPurpleCube
214:
213:Dennis The Tiger
194:
187:
150:STS-115 Timeline
140:) I have merged
119:
101:
34:
463:
462:
458:
457:
456:
454:
453:
452:
451:
445:deletion review
438:
424:
417:
212:
192:
185:
92:
76:
73:
44:The result was
37:deletion review
30:
22:
21:
20:
12:
11:
5:
461:
459:
450:
449:
433:
432:
408:
407:
406:
405:
404:
403:
377:
376:
363:
362:
361:
360:
359:
358:
357:
356:
315:
314:
313:
312:
311:
310:
297:
277:
276:
262:
261:
260:
259:
246:
245:
229:
200:
126:
125:
72:
67:
42:
41:
25:
23:
15:
14:
13:
10:
9:
6:
4:
3:
2:
460:
448:
446:
441:
435:
434:
431:
428:
427:
421:
420:
413:
410:
409:
402:
399:
394:
393:
392:
389:
386:
381:
380:
379:
378:
375:
372:
368:
365:
364:
355:
352:
348:
343:
342:
341:
336:
335:
334:
331:
326:
325:
324:
323:
322:
321:
309:
306:
302:
298:
296:
293:
288:
287:
286:
281:
280:
279:
278:
275:
272:
267:
264:
263:
258:
254:
250:
249:
248:
247:
244:
241:
237:
233:
230:
228:
224:
220:
216:
215:
208:
204:
201:
199:
196:
195:
189:
188:
181:
179:
175:
174:
173:
172:
168:
164:
160:
155:
151:
147:
143:
139:
135:
131:
123:
117:
113:
109:
105:
100:
96:
91:
87:
83:
79:
75:
74:
71:
68:
66:
65:
62:
61:
57:
56:
51:
47:
40:
38:
33:
27:
26:
19:
439:
436:
423:
416:
411:
366:
316:
265:
231:
211:
202:
191:
184:
177:
176:
167:Talk:STS-118
159:Talk:STS-115
127:
59:
54:
45:
43:
31:
28:
385:speedy keep
165:, and on
412:Redirect
367:Redirect
347:WP:MERGE
266:Question
232:Redirect
203:Redirect
122:View log
46:redirect
290:page.--
253:STS-121
236:STS-115
207:STS-115
146:STS-115
138:STS-118
134:STS-117
130:STS-116
95:protect
90:history
50:STS-115
425:Luftan
292:Dacium
193:Luftan
178:Delete
161:, the
99:delete
418:James
388:Corpx
371:Corpx
223:stuff
209:. --
186:James
144:into
116:views
108:watch
104:links
16:<
221:and
219:Rawr
112:logs
86:talk
82:edit
234:to
205:to
120:– (
60:ʏɑɴ
55:ɑʀк
225:)
182:.
136:,
132:,
114:|
110:|
106:|
102:|
97:|
93:|
88:|
84:|
217:(
124:)
118:)
80:(
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.