/srv/irclogs.ubuntu.com/2013/12/02/#ubuntustudio-devel.txt

OvenWerk1cub ping14:21
OvenWerk1cub re: languages.... c c++ python  would be my guesses14:22
OvenWerk1it depends on the lib the dev wishes to use14:23
OvenWerk1gtk is c and qt is c++14:23
OvenWerk1we were trying to avoid kde apps for a while but that was to ship less libs.14:25
OvenWerk1in the end we want the best or most used apps to be included.14:25
cubah, I'm trying to convince a friend who is a developer to participate in ubuntu studio14:29
cubI think he mostly work with c and c++14:29
OvenWerk1we don't do that much coding ourselves.14:29
cubno but it would not hurt to have someone who knows some about it?14:30
OvenWerk1Most of what we do is with script like python or perl14:30
OvenWerk1The big use we would have fopeople who know code is bug fixing.14:30
cubyeah14:30
cubbut 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 time14:31
OvenWerk1Our direction seems to be changing some. The focus seems to be moving towards making the workflow metas really good.14:32
OvenWerk1Once in a while work is good too. as you have probably seen there are no real dead lines14:32
zequencecub: 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 yet14:36
zequenceOur other applications, the installer, and ubuntustudio-controls could both be coded in any language with either GTK or QT14:36
zequencecurrently, -installer is in perl? and -controls is python/GTK14:37
zequenceWe do have deadlines. But, we don't get serious consequences in not making them, as we are not a business.14:38
cubI was looking at the work flow page last week, but unsure on how to proceed14:48
cubit feels like april 2014 is quite soon. :P14:48
cubthis one: https://wiki.ubuntu.com/UbuntuStudio/PackageListSaucy14:49
zequencecub: categories needs to be established, and then, each application needs to be put into a category14:51
zequenceIt would be good to add all that data to a searchable database14:51
zequenceWe don't need to do it all over again for each release either14:51
zequenceJust update it14:51
zequenceThe categories should follow existing freedesktop and Debian categories as much as possible14:53
zequenceThat means, one needs to understand what those are first14:53
zequencewell, Debian has sections. Not sure about the details myself, actually14:53
zequenceSorry, packages need to be tagges with one or more categories. Not applications, as that is not the same thing14:56
cubthe current list, is that everything that is available or is it what's actually included in an default installation?14:58
cubhm should be all available, as I understand it14:59
zequenceall available under the "sound" section of Ubuntu15:07
zequencenot nessecarily all that should be included under the audio workflow, since there might be non-"sound" packages that belong there too15:08
cubyup15:08
zequenceperhaps we should use a calc document for this?15:09
zequenceone that we can share and use as basis for a searchable database15:09
zequenceor what's the term, calc sheet?15:10
cubspread sheet15:19
cubbut most people sadly call it "Excel sheet"15:19
cubwhat's a good way to share it? Ubuntu One?15:20
zequenceSure15:36
knomezequence, spreadsheet15:37
zequenceit'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 format15:37
knomewell CSV usually works15:37
knomeoh, heh, didn't notice cub already said that ;)15:38

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!