[14:21] <OvenWerk1> cub ping
[14:22] <OvenWerk1> cub re: languages.... c c++ python  would be my guesses
[14:23] <OvenWerk1> it depends on the lib the dev wishes to use
[14:23] <OvenWerk1> gtk is c and qt is c++
[14:25] <OvenWerk1> we were trying to avoid kde apps for a while but that was to ship less libs.
[14:25] <OvenWerk1> in the end we want the best or most used apps to be included.
[14:29] <cub> ah, I'm trying to convince a friend who is a developer to participate in ubuntu studio
[14:29] <cub> I think he mostly work with c and c++
[14:29] <OvenWerk1> we don't do that much coding ourselves.
[14:30] <cub> no but it would not hurt to have someone who knows some about it?
[14:30] <OvenWerk1> Most of what we do is with script like python or perl
[14:30] <OvenWerk1> The big use we would have fopeople who know code is bug fixing.
[14:30] <cub> yeah
[14:31] <cub> but we'll see, he's quite busy with work, family and music...as most of us so he wasn't sure he would have the time
[14:32] <OvenWerk1> Our direction seems to be changing some. The focus seems to be moving towards making the workflow metas really good.
[14:32] <OvenWerk1> Once in a while work is good too. as you have probably seen there are no real dead lines
[14:36] <zequence> cub: There's perhaps only one project that might need C/C++ coding - a workflow manager, most likely in the form of a panel. It's a loose concept that has not been deeply developed yet
[14:36] <zequence> Our other applications, the installer, and ubuntustudio-controls could both be coded in any language with either GTK or QT
[14:37] <zequence> currently, -installer is in perl? and -controls is python/GTK
[14:38] <zequence> We do have deadlines. But, we don't get serious consequences in not making them, as we are not a business.
[14:48] <cub> I was looking at the work flow page last week, but unsure on how to proceed
[14:48] <cub> it feels like april 2014 is quite soon. :P
[14:49] <cub> this one: https://wiki.ubuntu.com/UbuntuStudio/PackageListSaucy
[14:51] <zequence> cub: categories needs to be established, and then, each application needs to be put into a category
[14:51] <zequence> It would be good to add all that data to a searchable database
[14:51] <zequence> We don't need to do it all over again for each release either
[14:51] <zequence> Just update it
[14:53] <zequence> The categories should follow existing freedesktop and Debian categories as much as possible
[14:53] <zequence> That means, one needs to understand what those are first
[14:53] <zequence> well, Debian has sections. Not sure about the details myself, actually
[14:56] <zequence> Sorry, packages need to be tagges with one or more categories. Not applications, as that is not the same thing
[14:58] <cub> the current list, is that everything that is available or is it what's actually included in an default installation?
[14:59] <cub> hm should be all available, as I understand it
[15:07] <zequence> all available under the "sound" section of Ubuntu
[15:08] <zequence> not nessecarily all that should be included under the audio workflow, since there might be non-"sound" packages that belong there too
[15:08] <cub> yup
[15:09] <zequence> perhaps we should use a calc document for this?
[15:09] <zequence> one that we can share and use as basis for a searchable database
[15:10] <zequence> or what's the term, calc sheet?
[15:19] <cub> spread sheet
[15:19] <cub> but most people sadly call it "Excel sheet"
[15:20] <cub> what's a good way to share it? Ubuntu One?
[15:36] <zequence> Sure
[15:37] <knome> zequence, spreadsheet
[15:37] <zequence> it's nice if the data can easily be transferred to other form of databases easily. I suppose there's a way to save in a common format
[15:37] <knome> well CSV usually works
[15:38] <knome> oh, heh, didn't notice cub already said that ;)