[mythtv] Development of MythTV

Paul Woodward paul_woodward at fastnet.co.uk
Wed May 19 11:05:29 EDT 2004


Quoting Kirby Vandivort <kvandivo at ks.uiuc.edu>:

> 
> On Wed, May 19, 2004 at 01:59:31PM +0200, Henk Poley wrote:
> > In response to some possible troll on the Wiki (don't flame, this mail is
> not 
> > in any way related to that) I have the following question.
> > 
> > What are the plans/ideas/roadmap IRT MythTV?
> > 
> > The troll(?) said there is no need for, a show mouse cursor toggle,
> FireWire 
> > support (think home videos), a C# client running on other operating systems
> 
> > than linux and some other things. 
> > 
> > What is the 'official' stance on this by 'the developers'?
> 
> I think that it is safe to say the following (and I'm not being critical
> or harsh, or responding about any wish in particular... just stating
> reality as I've observed it over the past year or so):
> 
> For the most part, each developer has their own ideas of what they want
> mythtv to do for them.  There is no official roadmap.  Each developer
> (the people who are willing to actually write the code) decides what
> they want to spend their own time on.  Random users can make up wish
> lists from now until 2030, but someone has to be willing to write the
> code, and the developers aren't (in general; there are exceptions)
> in the business of writing code that they don't personally care about.
> 
> Isaac obviously has the final word on what actually goes into CVS, but
> the bottom line is that the developers are writing code to satisfy their
> own itches.
> 
> Due to the beauty of Open Source, anyone that wants feature X is
> completely free to download the source and start writing.  Once they have
> the feature working as they wish, they are free to send it mythtv-dev's
> way for inclusion into the CVS tree.  If it makes it, great.  If not,
> they've got the feature themselves and are free to do with it as they
> wish.
> 

That being said, any code providing new functionality and committed into CVS has
to be maintained, something which the core developers may not want to be
responsible for.


More information about the mythtv-dev mailing list