Posts: 6,563
Joined: Apr 2008
Reputation:
160
natethomas
Enjoying Retirement by Staying Busy
Posts: 6,563
MediaPortal is a pretty good warning example against complete feature freeze. They announced the "new" media portal something like 4 years ago and STILL haven't gotten it out. Keeping each feature of XBMC in its own API'd silo is a great idea. Amazon did it years ago and has been experiencing benefits ever since. But actually doing the work sucks and is boring and, most importantly, isn't an assignable task. If devs want to do it, awesome. Montellese did just this recently with settings. But telling people they HAVE to do the work (or else work on nothing) is a guaranteed way to end development of XBMC forever.
Posts: 1,483
Joined: Aug 2010
(2013-07-30, 13:41)pecinko Wrote: (2013-07-30, 13:05)da-anda Wrote: pecinko - in general yes, but one of the XBMC instances will act as "master" (auto negotiated) - and if you have one instance up all the time it could be your permanent master -> server
There's no problem running it 24/7; main drawback is it still won't be headless server.
I believe Montelesse once wrote how this could look like. I thought improving UPNP server is an important part. As for the headless approach; this is quite use able already altough it still needs work.
Posts: 1,483
Joined: Aug 2010
@pecinclo: Theuni committed PR1049 last year.
Posts: 1,483
Joined: Aug 2010
(2013-07-30, 16:53)Martijn Wrote: (2013-07-30, 16:51)Robotica Wrote: @pecinclo: Theuni committed PR1049 last year.
That is far from complete.
Nobody said it was complete. But I think pecinko is right; this project needs more cooperation to be completed.