=== jussi01 is now known as jussi [14:57] ScottL: ae you busy? [15:19] rlameiro: a couple of days you said you had wanted to talk about something, do you remember what it was? [15:22] yes [15:23] we need to make some kind of meeting [15:23] scott-work: to make the decitions to be made, and organize a team ASAP to start the maverick DEV [15:37] we should set some goals [15:44] rlameiro: i agree, we do need to start determining a direction and some definitive goals for maverick [15:44] but we may need to address some issues concerning Ubuntu Studio as a project first [15:45] finally addressing those issues (audience, goals) may have significant impact on maverick [15:47] exactly i mean that [15:47] after this isues are solved the faster we start on maverick [15:49] okay, so lets start planning the work [15:49] man, svn drives me nuts when it breaks [15:53] i would hope that we can make significant strides in the next few weeks to clarify the project, and provide a good springboard for moving into marverick [15:56] 'svn: Server sent unexpected return value (405 Method Not Allowed) in response to MKCOL request' -- I don't even know what this means [16:04] anyway, I'm hacking away at wordpress at the moment but maybe I'll have some time on the weekend to dump into building up some documentation to give examples for how I think applications should be organized / explained on the wiki [16:04] and as for the 'help' documentation... what's the strategy for expanding that? [16:05] do we wait until something in the wiki matures to the level of going into the help section or do we plan to write more user-end specific documentation for it? [16:05] I'm not really clear on that process [16:56] detrate-: perhaps i'm not understanding your suggestion about the 'help' documentation and using the wiki to mature [16:56] my feelings are that the wiki would be a tool for contributors to use to develop Ubuntu Studio [16:57] while the help documetnation would consist more of tutorials and explanations for users [16:57] others may have variences in this paradigm [16:57] though [17:13] detrate-: i also want you to know that i am eagerly looking forward to seeing what you come up with for the wordpress examples [17:43] well, I figured some of the developer documentation can be migrated to help after it's been built out a bit more [17:43] I figure it will just need some rewording and maybe some reorganization to make it more user-end [18:38] does the US project have any resources available somewhere other than the few graphics available in the wiki? [18:38] some stock photos and what not [18:39] also, does the website need to be licensed under the GPL? [18:40] or just GPL compatible? [18:41] detrate-: you might just search for "ubuntu studio art" in the wiki, there are numerous images throughout, although i don't know that i would consider any of them "stock photo" material [18:41] http://www.sxc.hu/browse.phtml?f=search&txt=sound+board&w=1&x=0&y=0 [18:41] might be better [18:41] but I need license clarification [18:41] as to licensing, i would defer to persia or TheMuso [18:42] lol @ this http://www.sxc.hu/photo/1046263 [18:42] I imagine CC-BY-SA would be okay but definitely want to know before getting started [18:44] who is the person in charge of the website again? was that cory? [18:44] who is my contact for getting the files on the server [18:45] I plan on developing it locally, worrying more about the technical, not so much on the theme which can be reconfigured later [18:48] I'm not sure if this license is GPL compatible, http://www.sxc.hu/help/7_2 [19:03] if you can do it locally, we can email cory if necessary with a link, that should bring his necessary involvement to the fore [19:29] any restrictions on the server I should be aware of? [19:29] I figure it's standard LAMP environment that can run WP without a problem [19:30] mod_rewrite needs to be enabled [19:31] doh, i don't know anything about the server detrate- , maybe persia has an idea or at least an idea of who would have an idea [22:57] Re: licensing: we'd do best to use the licenses cused for the contents at wiki.ubuntu.com and/or help.ubuntu.com [22:58] Note that when we document software, it's best to diverge from this, and use a license that is compatible with the software. [22:59] Re: server configuration: I have absoulutely no idea: this may require asking ckontrol [22:59] s/ol/os/