Weblog entry #1 for niol
See all weblog entries made by niol.
I was just wondering how do you think I should handle howto updates on an article I wrote for the site.
As said in a comment, this is completely deprecated due to the new work that the wpa_suplicant maintainers have put into the packaging.
I have updated the original article with the new stuff on my wiki.
How should this be handled? Should I submit a new update article and ask Steve to put an "Update warning" on the old one? Ultimately, I do not need to host that stuff as long as I can easily maintain it. Should this stuff go in the Debian Wiki?
Another weblog post seems to raise the same questions.
Comments on this Entry
[ Send Message | View Steve's Scratchpad | View Weblogs ]
In general I suggest people only update articles in place :
- To fix obvious errors.
- To fix typos.
If an article is completely obsolete by now then I'd suggest the comments should make that obvious, and my preferred solution would be to see a new article submitted which is current.
With the tagging system in place it should be possible to tag articles "Sarge", "Etch", "obsolete", etc appropriately. I did make a start at doing that myself, but I got a bit bored of it. Certainly users are welcome to tag things like that - and indeed that is half the reason for user tagging in the first place!
[ Parent | Reply to this comment ]
I need to update some of mine too...
--
"It's Not Magic, It's Work"
Adam
[ Parent | Reply to this comment ]
The answer to some of my questions changed at Perl 5.6 and 5.8, and at various other minor changes over the course of history, which means there are a lot of "stale" comments and articles out there.
In comparison Debian articles that often mention the release used, are much easier to follow.
I don't think there is one solution, but there presumably are ways to do a more general solution which might be a business opportunity...
[ Parent | Reply to this comment ]