Orphaned Articles [modified]
-
There's been a lot of discussion over the years about updating articles not written by yourself, taking over old articles, and collaborating to keep old articles relevant. I figured it would be good to discuss this here in order to have the most people contribute. What would you like to see if an article is "abandoned" and the author can no longer be contacted? 1. The ability to create a new superceding article and have a formal link mechanism back to the old. 2. The ability to edit the article while keeping the original author 3. The ability to add your name to the article and edit it from there 4. The ability to take over the article completely 5. ...? [Edit] No one wants the ability to jump on to an article and make updates directly to the article itself?? (ie #3 or #4)
cheers, Chris Maunder
CodeProject.com : C++ MVP
modified on Monday, January 12, 2009 5:12 AM
-
There's been a lot of discussion over the years about updating articles not written by yourself, taking over old articles, and collaborating to keep old articles relevant. I figured it would be good to discuss this here in order to have the most people contribute. What would you like to see if an article is "abandoned" and the author can no longer be contacted? 1. The ability to create a new superceding article and have a formal link mechanism back to the old. 2. The ability to edit the article while keeping the original author 3. The ability to add your name to the article and edit it from there 4. The ability to take over the article completely 5. ...? [Edit] No one wants the ability to jump on to an article and make updates directly to the article itself?? (ie #3 or #4)
cheers, Chris Maunder
CodeProject.com : C++ MVP
modified on Monday, January 12, 2009 5:12 AM
1. but also with a link from the old one to the new one
-
There's been a lot of discussion over the years about updating articles not written by yourself, taking over old articles, and collaborating to keep old articles relevant. I figured it would be good to discuss this here in order to have the most people contribute. What would you like to see if an article is "abandoned" and the author can no longer be contacted? 1. The ability to create a new superceding article and have a formal link mechanism back to the old. 2. The ability to edit the article while keeping the original author 3. The ability to add your name to the article and edit it from there 4. The ability to take over the article completely 5. ...? [Edit] No one wants the ability to jump on to an article and make updates directly to the article itself?? (ie #3 or #4)
cheers, Chris Maunder
CodeProject.com : C++ MVP
modified on Monday, January 12, 2009 5:12 AM
1. The old article remains, but also with links forward to the new article - I hate stuff that's been deprecated / superseded but you can never tell because there's no forward reference.
I just love Koalas - they go great with Bacon.
-
There's been a lot of discussion over the years about updating articles not written by yourself, taking over old articles, and collaborating to keep old articles relevant. I figured it would be good to discuss this here in order to have the most people contribute. What would you like to see if an article is "abandoned" and the author can no longer be contacted? 1. The ability to create a new superceding article and have a formal link mechanism back to the old. 2. The ability to edit the article while keeping the original author 3. The ability to add your name to the article and edit it from there 4. The ability to take over the article completely 5. ...? [Edit] No one wants the ability to jump on to an article and make updates directly to the article itself?? (ie #3 or #4)
cheers, Chris Maunder
CodeProject.com : C++ MVP
modified on Monday, January 12, 2009 5:12 AM
Option 1 as well. And probably for the new superseding article to appear first on the search result instead of the old one, or even for the old article to not appear in the search result unless an option is specified.
"A democracy is nothing more than mob rule, where fifty-one percent of the people may take away the rights of the other forty-nine." - Thomas Jefferson "Democracy is two wolves and a lamb voting on what to have for lunch. Liberty is a well-armed lamb contesting the vote." - Benjamin Franklin Edbert Sydney, Australia
-
There's been a lot of discussion over the years about updating articles not written by yourself, taking over old articles, and collaborating to keep old articles relevant. I figured it would be good to discuss this here in order to have the most people contribute. What would you like to see if an article is "abandoned" and the author can no longer be contacted? 1. The ability to create a new superceding article and have a formal link mechanism back to the old. 2. The ability to edit the article while keeping the original author 3. The ability to add your name to the article and edit it from there 4. The ability to take over the article completely 5. ...? [Edit] No one wants the ability to jump on to an article and make updates directly to the article itself?? (ie #3 or #4)
cheers, Chris Maunder
CodeProject.com : C++ MVP
modified on Monday, January 12, 2009 5:12 AM
1 is probably best. 4 is a really bad idea: there are plenty here already hijacking co-authors, a curse you suffer from more than most: imagine the chaos if I could just take over and claim credit for an existing article. Just my tuppence worth.
-
There's been a lot of discussion over the years about updating articles not written by yourself, taking over old articles, and collaborating to keep old articles relevant. I figured it would be good to discuss this here in order to have the most people contribute. What would you like to see if an article is "abandoned" and the author can no longer be contacted? 1. The ability to create a new superceding article and have a formal link mechanism back to the old. 2. The ability to edit the article while keeping the original author 3. The ability to add your name to the article and edit it from there 4. The ability to take over the article completely 5. ...? [Edit] No one wants the ability to jump on to an article and make updates directly to the article itself?? (ie #3 or #4)
cheers, Chris Maunder
CodeProject.com : C++ MVP
modified on Monday, January 12, 2009 5:12 AM
1 - the original work ought to be preserved, IMO. But if an article could be marked as a successor to the original article, you could automatically inject links in the original indicating the new one?
-
There's been a lot of discussion over the years about updating articles not written by yourself, taking over old articles, and collaborating to keep old articles relevant. I figured it would be good to discuss this here in order to have the most people contribute. What would you like to see if an article is "abandoned" and the author can no longer be contacted? 1. The ability to create a new superceding article and have a formal link mechanism back to the old. 2. The ability to edit the article while keeping the original author 3. The ability to add your name to the article and edit it from there 4. The ability to take over the article completely 5. ...? [Edit] No one wants the ability to jump on to an article and make updates directly to the article itself?? (ie #3 or #4)
cheers, Chris Maunder
CodeProject.com : C++ MVP
modified on Monday, January 12, 2009 5:12 AM
A simple copy and paste from the suggestions forum :) I think it's important to have additions etc stay within the same article. Even if you have a link pointing to an updated article people will still miss it. I do see a problem that the person who takes over the article might screw it up. Maybe the contributions of the new owner can be clearly delineated within the original article and have an option for the community to rate the new owner's contribution so that if it falls below a certain rating then the added section gets removed from the original article. So the 4th option.
Cheers Garth If Jesus played guitar, he would play it like Clapton and the devil would play it like Hendrix
-
There's been a lot of discussion over the years about updating articles not written by yourself, taking over old articles, and collaborating to keep old articles relevant. I figured it would be good to discuss this here in order to have the most people contribute. What would you like to see if an article is "abandoned" and the author can no longer be contacted? 1. The ability to create a new superceding article and have a formal link mechanism back to the old. 2. The ability to edit the article while keeping the original author 3. The ability to add your name to the article and edit it from there 4. The ability to take over the article completely 5. ...? [Edit] No one wants the ability to jump on to an article and make updates directly to the article itself?? (ie #3 or #4)
cheers, Chris Maunder
CodeProject.com : C++ MVP
modified on Monday, January 12, 2009 5:12 AM
#1 But only when the original author does not disagree. (In other words, you should attempt to contact him.)
Cheers, Vıkram.
I don't suffer from insanity, I enjoy every moment of it.
-
There's been a lot of discussion over the years about updating articles not written by yourself, taking over old articles, and collaborating to keep old articles relevant. I figured it would be good to discuss this here in order to have the most people contribute. What would you like to see if an article is "abandoned" and the author can no longer be contacted? 1. The ability to create a new superceding article and have a formal link mechanism back to the old. 2. The ability to edit the article while keeping the original author 3. The ability to add your name to the article and edit it from there 4. The ability to take over the article completely 5. ...? [Edit] No one wants the ability to jump on to an article and make updates directly to the article itself?? (ie #3 or #4)
cheers, Chris Maunder
CodeProject.com : C++ MVP
modified on Monday, January 12, 2009 5:12 AM
I vote for #1 with the comment that a simple statement be inset (appropriately visually distinguished) at the top of the new article that says "This article is based on, or extends, or usess source code taken from ... link(s) to old article)s) ... It would be really nice in reading such a "derivative" article to have a clear statement by the author as to why they used to "old" articles, exactly what they took from them. And let the old article go to some kind of "heaven" (archive) with a link to the new, as others have suggested. I trust the "screeners" can recognize when a "new" article has not really added something new to the old article. And I trust that there is enough "collective intelligence" in this hive to raise hell if a "new" article doesn't measure up. I think the "sticky" part could be if I used some code from one or two other articles which are "abandoned" (let's assume, for this discussion, my "new" article has added something of real value) : the author of the "new" then has what responsibility to correct issues with the "borrowed" code ? This may be a moot issue since many authors of articles here (including some of the most excellent) do, after a while, cease responding to queries on their articles. So I don't mean to imply that there's some "'til death do us part" sub-text I have in mind here. best, Bill
"Many : not conversant with mathematical studies, imagine that because it [the Analytical Engine] is to give results in numerical notation, its processes must consequently be arithmetical, numerical, rather than algebraical and analytical. This is an error. The engine can arrange and combine numerical quantities as if they were letters or any other general symbols; and it fact it might bring out its results in algebraical notation, were provisions made accordingly." Ada, Countess Lovelace, 1844
-
There's been a lot of discussion over the years about updating articles not written by yourself, taking over old articles, and collaborating to keep old articles relevant. I figured it would be good to discuss this here in order to have the most people contribute. What would you like to see if an article is "abandoned" and the author can no longer be contacted? 1. The ability to create a new superceding article and have a formal link mechanism back to the old. 2. The ability to edit the article while keeping the original author 3. The ability to add your name to the article and edit it from there 4. The ability to take over the article completely 5. ...? [Edit] No one wants the ability to jump on to an article and make updates directly to the article itself?? (ie #3 or #4)
cheers, Chris Maunder
CodeProject.com : C++ MVP
modified on Monday, January 12, 2009 5:12 AM
-
There's been a lot of discussion over the years about updating articles not written by yourself, taking over old articles, and collaborating to keep old articles relevant. I figured it would be good to discuss this here in order to have the most people contribute. What would you like to see if an article is "abandoned" and the author can no longer be contacted? 1. The ability to create a new superceding article and have a formal link mechanism back to the old. 2. The ability to edit the article while keeping the original author 3. The ability to add your name to the article and edit it from there 4. The ability to take over the article completely 5. ...? [Edit] No one wants the ability to jump on to an article and make updates directly to the article itself?? (ie #3 or #4)
cheers, Chris Maunder
CodeProject.com : C++ MVP
modified on Monday, January 12, 2009 5:12 AM
I agree #1 - seems the most fair - credit where credit is due. There may be some old articles out there where the author can be contacted and is even active on CP still but for some reason no longer wishes to maintain the article. I know I don't use MFC/ATL anymore and so I don't keep those types articles up to date.
I'll be more enthusiastic about encouraging thinking outside the box when there's evidence of any thinking going on inside it. - pTerry
BizSquawk -
There's been a lot of discussion over the years about updating articles not written by yourself, taking over old articles, and collaborating to keep old articles relevant. I figured it would be good to discuss this here in order to have the most people contribute. What would you like to see if an article is "abandoned" and the author can no longer be contacted? 1. The ability to create a new superceding article and have a formal link mechanism back to the old. 2. The ability to edit the article while keeping the original author 3. The ability to add your name to the article and edit it from there 4. The ability to take over the article completely 5. ...? [Edit] No one wants the ability to jump on to an article and make updates directly to the article itself?? (ie #3 or #4)
cheers, Chris Maunder
CodeProject.com : C++ MVP
modified on Monday, January 12, 2009 5:12 AM
-
There's been a lot of discussion over the years about updating articles not written by yourself, taking over old articles, and collaborating to keep old articles relevant. I figured it would be good to discuss this here in order to have the most people contribute. What would you like to see if an article is "abandoned" and the author can no longer be contacted? 1. The ability to create a new superceding article and have a formal link mechanism back to the old. 2. The ability to edit the article while keeping the original author 3. The ability to add your name to the article and edit it from there 4. The ability to take over the article completely 5. ...? [Edit] No one wants the ability to jump on to an article and make updates directly to the article itself?? (ie #3 or #4)
cheers, Chris Maunder
CodeProject.com : C++ MVP
modified on Monday, January 12, 2009 5:12 AM
Option #1 seems to be most popular and rightly so. So long as the mechanism for moving an article to abandoned is safe, it should not cause too much grief. I can even see the case for an active member not wanting to continue updating an existing article they own and allowing someone else to take it over.
Panic, Chaos, Destruction. My work here is done.
-
There's been a lot of discussion over the years about updating articles not written by yourself, taking over old articles, and collaborating to keep old articles relevant. I figured it would be good to discuss this here in order to have the most people contribute. What would you like to see if an article is "abandoned" and the author can no longer be contacted? 1. The ability to create a new superceding article and have a formal link mechanism back to the old. 2. The ability to edit the article while keeping the original author 3. The ability to add your name to the article and edit it from there 4. The ability to take over the article completely 5. ...? [Edit] No one wants the ability to jump on to an article and make updates directly to the article itself?? (ie #3 or #4)
cheers, Chris Maunder
CodeProject.com : C++ MVP
modified on Monday, January 12, 2009 5:12 AM
I think #1, I like Bill Woodruff's points as well 'g'
-
There's been a lot of discussion over the years about updating articles not written by yourself, taking over old articles, and collaborating to keep old articles relevant. I figured it would be good to discuss this here in order to have the most people contribute. What would you like to see if an article is "abandoned" and the author can no longer be contacted? 1. The ability to create a new superceding article and have a formal link mechanism back to the old. 2. The ability to edit the article while keeping the original author 3. The ability to add your name to the article and edit it from there 4. The ability to take over the article completely 5. ...? [Edit] No one wants the ability to jump on to an article and make updates directly to the article itself?? (ie #3 or #4)
cheers, Chris Maunder
CodeProject.com : C++ MVP
modified on Monday, January 12, 2009 5:12 AM
I like option 1.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001 -
There's been a lot of discussion over the years about updating articles not written by yourself, taking over old articles, and collaborating to keep old articles relevant. I figured it would be good to discuss this here in order to have the most people contribute. What would you like to see if an article is "abandoned" and the author can no longer be contacted? 1. The ability to create a new superceding article and have a formal link mechanism back to the old. 2. The ability to edit the article while keeping the original author 3. The ability to add your name to the article and edit it from there 4. The ability to take over the article completely 5. ...? [Edit] No one wants the ability to jump on to an article and make updates directly to the article itself?? (ie #3 or #4)
cheers, Chris Maunder
CodeProject.com : C++ MVP
modified on Monday, January 12, 2009 5:12 AM
-
There's been a lot of discussion over the years about updating articles not written by yourself, taking over old articles, and collaborating to keep old articles relevant. I figured it would be good to discuss this here in order to have the most people contribute. What would you like to see if an article is "abandoned" and the author can no longer be contacted? 1. The ability to create a new superceding article and have a formal link mechanism back to the old. 2. The ability to edit the article while keeping the original author 3. The ability to add your name to the article and edit it from there 4. The ability to take over the article completely 5. ...? [Edit] No one wants the ability to jump on to an article and make updates directly to the article itself?? (ie #3 or #4)
cheers, Chris Maunder
CodeProject.com : C++ MVP
modified on Monday, January 12, 2009 5:12 AM
Gotta be option 1. Dickens still wrote David Copperfield, regardless of how many TV/Film scriptwriters have a go at c*&king it up. [Mod] I also second the forward link proposition. VOTE FOR PROPOSITION 1! [/Mod]
Henry Minute If you open a can of worms, any viable solution *MUST* involve a larger can.
-
There's been a lot of discussion over the years about updating articles not written by yourself, taking over old articles, and collaborating to keep old articles relevant. I figured it would be good to discuss this here in order to have the most people contribute. What would you like to see if an article is "abandoned" and the author can no longer be contacted? 1. The ability to create a new superceding article and have a formal link mechanism back to the old. 2. The ability to edit the article while keeping the original author 3. The ability to add your name to the article and edit it from there 4. The ability to take over the article completely 5. ...? [Edit] No one wants the ability to jump on to an article and make updates directly to the article itself?? (ie #3 or #4)
cheers, Chris Maunder
CodeProject.com : C++ MVP
modified on Monday, January 12, 2009 5:12 AM
The forward link could also be solved by a "People who viewed this article also looked at ..." section that is displayed at the bottom of each article, similar to Amazon.
Best wishes, Hans
[CodeProject Forum Guidelines] [How To Ask A Question] [My Articles]
-
There's been a lot of discussion over the years about updating articles not written by yourself, taking over old articles, and collaborating to keep old articles relevant. I figured it would be good to discuss this here in order to have the most people contribute. What would you like to see if an article is "abandoned" and the author can no longer be contacted? 1. The ability to create a new superceding article and have a formal link mechanism back to the old. 2. The ability to edit the article while keeping the original author 3. The ability to add your name to the article and edit it from there 4. The ability to take over the article completely 5. ...? [Edit] No one wants the ability to jump on to an article and make updates directly to the article itself?? (ie #3 or #4)
cheers, Chris Maunder
CodeProject.com : C++ MVP
modified on Monday, January 12, 2009 5:12 AM
-
There's been a lot of discussion over the years about updating articles not written by yourself, taking over old articles, and collaborating to keep old articles relevant. I figured it would be good to discuss this here in order to have the most people contribute. What would you like to see if an article is "abandoned" and the author can no longer be contacted? 1. The ability to create a new superceding article and have a formal link mechanism back to the old. 2. The ability to edit the article while keeping the original author 3. The ability to add your name to the article and edit it from there 4. The ability to take over the article completely 5. ...? [Edit] No one wants the ability to jump on to an article and make updates directly to the article itself?? (ie #3 or #4)
cheers, Chris Maunder
CodeProject.com : C++ MVP
modified on Monday, January 12, 2009 5:12 AM
#1 It would be nice to have a banner on the original article state that it is no longer supported. While I think this is understood by most people, someone may be in such need that they try to contact anyway and get frustrated.
Anyone who thinks he has a better idea of what's good for people than people do is a swine. - P.J. O'Rourke