nzTiVo effort and state

[DJC]

I've noted posts here (and on the other thread) wanting to know who, what, why and seeking explanations ...

A couple of things need to be made clear from prior exposure to decentralised structures like this:-

1. The nzTiVo setup is not a commercial service ... far from it ... never intended to be ... its a volunteer best endeavors setup which may or may not work, but has worked pretty well in the past. But of course as various people move on numbers need to be kept up, otherwise EOL will come sooner rather than a planned date.

If you don't agree with that SLA, ie there is not a service level agreement - you still have the simple alternative to set up your own system and to get it to work the way you need, this is what the original team did to evolve from the old VCR manual record and then loadguide methods.

2. If members of the nzTiVo team choose not disclose their details or level of contribution, then that is really their decision. After all, they are volunteering their time to help others and are not accountable for doing so or not doing so, we just hope they do.

This is the nature of a loosely knit group of volunteers. Personally, I'm just thankful for the contributions that many have made in the past - its been a great service while it lasted.

[Schumi]

Hi guys,
I thought I better make it clear that it is my and presumably everyone elses view that you have done fantastic work to keep this going for as long as it has. From day one when I imported my TIVO from the US I have always viewed this as a volunteer service with a no-guarantees-attached policy. I have often pondered where to help, but since I have no experience in java programming and have done little perl scripting my assistance is probably only minimal; I could update an html page with an FAQ if that skill was required. I have no problem if the guide creation process is not published or members don't want to reveal some of their personal "tricks", but if that's the case where is the rest supposed to pick up? No one is asking for the inner workings of it all, but if we are supposed to contribute we need to know what needs doing. I don't believe you will get like for like replacements for the team members who have moved on. The way I see it the jobs that need to be done are not bite size, so some just shy away because they are overwhelmed, which is why they need to be made small and overseeable so when someone can't do it any longer a replacement is easily found. Someone who knows the systems needs to take the lead. If this isn't possible then maybe it is best to say thanks for the good time and move on.