[mythtv-users] Spilt Myth mailing list?

[Henk Poley]

>Van: steve at nexusuk.org
>
>On Wed, 11 Feb 2004, Henk Poley wrote:
>
>> I hope this split looks pretty obvious. Maybe the non-US seems akward,
>> but all kinds of things (XMLTV for example) behave just a bit different
>> outside of the US.
>
> If you're going to go down that route you need a separate list for each 
> part of the world - stuff like XMLTV works differently with practically 
> every grabber.  Splitting the list by country seems downright daft, and 
> most people won't know what works differently in different parts of the 
> world or not (so won't know what should go in the users list and what 
> should go in the nonus list).  Besides, if you're going down that route 
> you should have "mythtv-us" instead (believe it or not, the US is not
> the centre of the universe :)

Hmm, yes I see the problem of "the never ending splitup". It's just that I
have the feeling that most people who are using MythTV live in the US, so
non-US posts get dropped sometimes (or even bashed: "That's not my
problem!").

See how long it took to get manual recording in for example (both planning,
implementing and getting it in the tree), or auto shutdown (some kind of
non-issue in the US?). See how akward the frequency entries in the database
are for non-US people (just as if you would standardise on _exact_
frequencies and waste valuable bandwith?).

[so yes, my problem it indeed that most US people have the implicit
assumption that the US is the 'center of the universe', or even that it
_is_ the world.]

Most of the time these things are slow because it seems like nobody is
interested, most of the time because of a chicken and egg problem ("Hmm, no
power saving? Well never mind, I'll use my old style VCR.", you get it).

I _think_  having some kind of group of 'non-standardees' might help to get
some things of the ground. For example PDS/VPS pops up now and then (about
once a week!). So there are people who want it, and I know it is possible.
'Only' the scheduler needs to have some notice of it and you need to have a
way to grab that data of VBI. Yes, I know there's more about it, and
because of the current scheduler overhaul it would be a good time to do it
_now_, but well 'time the final frontier'.

And for example the frequency stuff is as easy as making the string size
big enough to hold "100000MHz" and add a line to the frequency parser to
interpret this correctly. I think 6 lines of code (MythTV even calculates
the MHz value from the frequency column, you now only need to 'read' it).
But my estimate is that it will take me at least a full day to pinpoint
_where_  I must look and how to change it. I don't have that time
currently. Somehow OSS defines this as 'I see no code from anyone, so it's
a non-issue'. 

End of rant, sorry... pfff...

	Henk Poley <><


PS: The answer "why don't you set up you own list then" isn't appreciated.