On 04/26/2012 12:49 PM, Tanu Kaskinen wrote:
One of the [[Software/PulseAudio/GSoC2012|Google Summer of Code project
ideas for 2012]] was a "configuration system". The configuration system
was not among the selected projects, but the system was seen as a
priority,
While I believe that this will probably be something nice to have, on my
end I don't see this project as a priority.
For me, I would prioritise the stuff that's long overdue:
* Get 2.0 out the door
* Review/merge the UCM stuff
* Implement Colin's priority list routing
But if it's really a prerequisite to make the GSoC students productive,
I guess there isn't much choice than to get it up and working really fast...
so the plan now is to design and implement the important bits
(the client API and the server-side infrastructure) ourselves within May
2012 or so (the reason for the tight schedule is that we'd like the GSoC
students to benefit from this new system). Porting the existing
configuration to the new system is not a matter of urgency. All the
existing stuff has to be kept in mind while doing the design, though, so
that the porting work is possible to do when that time comes.
Is there a plan for making "when that times comes" != "never"? This is
not meaning to be sarcastic - more I'm being curious about your thoughts
on the topic.
--
David Henningsson, Canonical Ltd.
http://launchpad.net/~diwic
_______________________________________________
pulseaudio-discuss mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
