> On a related note, we need to come up with a way to transfer "ownership" of
> handlers. I know there are a lot of handlers that I've written that I never
> use. It seems to me that someone who does use a handler would be better
> suited to maintain it. I'm worried that people will stop maintaining their
> handlers, and the responsibility will fall on me.
I agree. There's no need for you to maintain handlers, especially if you don't
use them. Maybe you could have a web page or something, where people
that don't want to maintain anymore, can hook up with people that might want to
take over. An "Adopt a Handler" page. Or maybe just do that through this list.
> One way to handle this would be to ask someone to take it over, and if no one
> does, I remove it from the database when it breaks. (Or maybe have it say
> "Sorry this content is not available. It will become available when someone
> adopts this handler.") Anyone have any ideas?
That is a good idea. Perhaps you could make that show up on the resulting web
page, with a link to NewsClipper. That might get someone's attention. I tend
to check my news pages everyday, a couple times a day to make sure nothings
broken., and because I enjoy reading the news links available. So I know when
one doesn't work, and if it doesn't show, I run it again (this time by hand- I
have it set on a cron job) to make sure. ( I use it statically) . If it happens
two days in a row, or happens more than once during the day, I will presume the
web page has changed, and go investigate. I will also do this on other
handlers that I didn't write, but use., and if it's easy, I fix it locally.
my 2cents;
LP
-
If you would like to unsubscribe from this mailing list send an email to
[EMAIL PROTECTED] with the body "unsubscribe newsclipperlist
YOUR_EMAIL_ADDRESS" (without the quotes) or use the form provided at
http://www.NewsClipper.com/TechSup.htm#MailingList.
