public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Georgi Georgiev <chutz@gg3.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  Re: Removal of articles.xml from website
Date: Fri, 10 Jun 2005 12:26:41 +0900	[thread overview]
Message-ID: <20050610032641.GA6359@ols-dell.gg3.net> (raw)
In-Reply-To: <pan.2005.06.10.03.14.33.87595@cox.net>

[-- Attachment #1: Type: text/plain, Size: 1534 bytes --]

maillog: 09/06/2005-20:14:33(-0700): Duncan types
.. snip  ..
> ....
> 
> That said, there remains the practical issue of keeping links updated.  I
> see a couple possibilities.
> 
> One, there's the idea others floated -- note on the page the problem of
> keeping links updated as to why links aren't provided, and suggest
> searching on the titles listed, possibly with IBM DeveloperWorks listed
> specifically, or otherwise with publisher or original source acknowledged,
> to ease the search.
> 
> Two, keep the links, but again, specifically acknowledge some of them move
> from time to time, list them as last verified links, and display a
> feedback mechanism (email, or web form based to prevent email harvesting,
> or whatever) prominently asking for reader link update submissions.  If a
> reader says a link doesn't work and it's verified, with no new link
> immediately available, simply note that it has been verified dead and ask
> for updates.  The idea here is to leave the links as well as acknowledging
> they may be outdated, but leave the work of providing updates to the
> readers.

Three, keep a local copy of the articles unless you're forbidden to.

Four, provide a link to a cached copy, e.g.,
http://web.archive.org/web/*/http://www-106.ibm.com/developerworks/linux/library/l-fs.html

-- 
\    Georgi Georgiev   \  I hate mankind, for I think myself one of    \
/     chutz@gg3.net    /  the best of them, and I know how bad I am. - /
\   +81(90)2877-8845   \  - Samuel Johnson                             \

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-06-10  3:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-09  8:45 [gentoo-dev] Removal of articles.xml from website Sven Vermeulen
2005-06-09 13:24 ` Lance Albertson
2005-06-09 16:35 ` Donnie Berkholz
2005-06-09 16:55   ` Sven Vermeulen
2005-06-09 17:40     ` Donnie Berkholz
2005-06-09 17:56       ` Olivier Crete
2005-06-09 18:05         ` Donnie Berkholz
2005-06-10  3:14           ` [gentoo-dev] " Duncan
2005-06-10  3:24             ` Shyam Mani
2005-06-10  9:39               ` Sven Vermeulen
2005-06-10  8:19                 ` Shyam Mani
2005-06-10 12:28                 ` [gentoo-dev] " Sven Vermeulen
2005-06-11  7:14                   ` Duncan
2005-06-14 14:07                     ` Shyam Mani
2005-06-10  3:26             ` Georgi Georgiev [this message]
2005-06-10  5:12           ` [gentoo-dev] " Martin Skjöldebrand
2005-06-09 22:59   ` Alec Warner
2005-06-09 23:14     ` David Morgan
2005-06-10 15:13 ` Donnie Berkholz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050610032641.GA6359@ols-dell.gg3.net \
    --to=chutz@gg3.net \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox