[vdr] VDR Development

syrius.ml at no-log.org syrius.ml at no-log.org
Sun Sep 7 00:47:58 CEST 2008


Udo Richter <udo_richter at gmx.de> writes:

> Lets think this through: An open VDR repository for everyone to get in 
> their personal 'I want this' patches. Surely this will lead to chaos, 

indeed.

> since no one really oversees the needs of all VDR users. (Take 
> sourcecaps vs. lnbsharing as example.)

> So we have to restrict things. Only a few trusted dev's getting write 
> access. In any case changes that go beyond simple bug fixing would 
> require discussions about whether things go into the right direction, 
> and I'm pretty sure that none of the trusted dev's would ever check in 
> any changes without a previous ack by Klaus anyway.
>
> So if Klaus ack's anything anyway, why does anyone except Klaus actually 
> need write access?

And what about global warming ?
What if germany gets sunny summer weather for the next 24 months ? :)
no talk, no commit, nothing for 24 months ? 

I insist because I'd like to know where things go.
I tend to think Klaus won't have as much time as he had in the past.
And it's obviously not funny to developp features you're not
interested in.
So what's vdr future with only one developper ?


[snip]
> - With a distributed repository system like Mercurical, it would also 
> easily be possible to do external user branches to support more 
> cutting-edge features, as long as some other maintainer keeps them up to 
> date. Think of it as something like the -mm kernels, or as the bigpatch 
> / extensions-patch. And if things get Klaus' approval, they can be 
> easily merged back into main VDR too.

indeed !
would linuxtv.org be interested in hosting it ?

-- 



More information about the vdr mailing list