David Crossley wrote:
>
> Diana Shannon wrote:
> > David Crossley wrote:
> > > Diana Shannon wrote:
> > > <snip/>
> > >> I also forgot to add the step of using Link Alarm
> > >> (http://reports.linkalarm.com/373104199608/) to test links, once the
> > >> site is live. This should be used primarily for bad external links.
> > >
> > > This is a step that only i can do. Our company pays for the
> > > LinkAlarm run. We schedule it on an irregular basis. In the
> > > past this has only been following an official code release,
> > > because that was the only time the website was updated.
> >
> > How generous!
>
> Just one more way that we can contribute. All contributers
> are generous with their time (= money).
>
> > > It looks like there will soon be regular updates of the
> > > website independent of code release. So we will schedule
> > > LinkAlarm to be regular.
> >
> > What does "regular" mean? If I update the live site, I feel somewhat
> > responsible for correcting link errors. How will I know when to check
> > LinkAlarm?
>
> I am not yet sure how often we will run it.
>
> I just scheduled LinkAlarm to do its work again and will tell
> the list when the report is finished.
>
> > I hope this doesn't drive up the costs to your company.
> > I certainly didn't mean to suggest that.
>
> At one cent per page it is not too bad. Last time there were
> 968 pages (it includes javadocs too). So that equates to about
> US$10 per run. We can cope with that.
>
> It is the javadocs that bumps up the page-count. We may decide
> to exclude them. We could then run LinkAlarm more often.
David,
while I've liked this resource contribution since they day it started, I
wonder if these resources (money == time) can't be used a little more
wisely.
Please, please, don't get me wrong: I'm not in PITA-mode, just trying to
solve potential problems.
If you point your CVS client to the scratchpad, you'll see something
called "LinkStatusGenerator". There is a sitemap in the
/mount/linkstatus area that explains its use. I've tried it and it
works. It might not be perfect, but it's pretty cool stuff.
LinkAlarm costs 10$ per run but has no initial costs. LinkStatus costs
0$ per run but has an initial cost of a few hours, probably more.
Depending on the value of your hours.
My suggestion is to concentrate on naving LinkStatus work with forrest
sooner rather than leter so that we reduce the 'per run' expenses as
close to zero as possible (which is the only way it can work in the
longer run for a volunteer no-profit community like this one).
Again, please understand I have nothing against your contribution, but
I'd like to find an approach that doesn't have per-run costs (neither
time nor money) associated with it.
comments/
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<[EMAIL PROTECTED]> Friedrich Nietzsche
--------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
