[00:14] <zequence> hmm, I see I have access to change some teams now :P
[00:15] <zequence> This is as far as I got with the team structure page. Hard to condense that stuff to take smaller amount of space https://wiki.ubuntu.com/UbuntuStudio/TeamStructure
[02:06] <len-nb> micahg, -settings change done.
[02:07] <len-nb> zequence, Thunar is now default, Nautilus is removed, gnome-system-monitor has been replaced with xfce4-taskmanager
[02:10] <len-nb> zequence, this will show up on an update as the addition of xfce4-taskmanager. The two removed apps will be gone on the ISO, but not on an upgrade. The default will not change except for a new user.
[02:13] <micahg> len-nb: need a meta upload?
[02:14] <len-nb> That too :)
[02:14] <micahg> ok
[02:35] <micahg> len-nb: meta upload, will have to find time for -settings
[02:35] <micahg> *uploaded
[02:53] <len-nb> micahg, Thank you
[07:14] <zequence> len-nb: I'm thinking that if we ever do start doing multiple desktop metas for Ubuntu Studio, this one could be called Xubuntu Studio :P
[07:14] <zequence> Still just my brainchild, and I have not spoken with Scott about it
[07:16] <len-nb> Enough people install the metas over another DE to make it worth making the settings work as wide as possible.
[07:16] <zequence> I think that already happens
[07:17] <zequence> And those who know Linux audio don't even bother with US metas
[07:17] <zequence> Everyone has their own favorite setup
[07:17] <zequence> I think the crucial part, if we ever get our custom tools setup for workflows and everything, is that it'll work on any desktop system
[07:19] <len-nb> Anyway, I'm off to bed. C Ya
[07:20] <zequence> len-nb: GN
[08:49] <ttoine> hi guys
[08:50] <ttoine> I just discovered that Stephane Letz, one of the most contributive to jackdmp is working at the Grame, an institution in my area
[08:50] <ttoine> so
[08:50] <ttoine> I will try to make an interview
[08:50] <ttoine> would you have some questions ?
[08:52] <falktx> isn't he leaving?
[08:52] <falktx> I got that impression at least...
[09:01] <ttoine> http://lite.framapad.org/p/5n3kYagDQA
[09:01] <ttoine> falktx, perhaps, but he is still an important audio scientist in France
[09:01] <ttoine> maybe he can give us some impressions, and some interesting clues about the perfect setup
[09:01] <ttoine> zequence, http://lite.framapad.org/p/5n3kYagDQA
[09:02] <falktx> ttoine: note that his latest work has not been for linux, but for Windows and Mac
[09:03] <ttoine> the Grame is mainly working on Mac
[09:03] <ttoine> I know one of the sound tech working on some projects there
[09:03] <ttoine> they have intensive use of maxmsp
[09:04] <ttoine> anyway, the link to the question pad is on the misc blueprint whiteboard
[09:05] <ttoine> falktx, don't hesitate to add some questions, I would be happy to translate them
[09:05] <falktx> when is jack3 coming? ;)
[09:05] <falktx> I have questions, but they are all too technical...
[09:11] <ttoine> falktx, please, write your questions on the pad, even if it is technical
[09:11] <ttoine> I will do my best to get answers
[09:11] <ttoine> just follow the link and the howto
[09:11] <ttoine> it is very simple
[09:12] <ttoine> well, I need to go
[09:16] <zequence> Ah, I missed that
[09:16] <zequence> Great idea for an interview
[10:26] <zequence> Just got a surge warning from wiki.ubuntu.com. Telling me to slow down, or I might get locked out for a while
[10:26] <zequence> Apparently, there's a limit to how fast you are allowed to work on the wiki
[10:59] <astraljava> Unsurprising, considering how slow the wiki has been throughout its history. :)
[11:03] <zequence> I was working on multiple pages at once, open in different tabs. Started saving them one after the other. That didn't sit well with the wiki engine
[11:05] <astraljava> Heheh. Probably took that as DOS attack. :)
[11:23] <zequence> Things are really getting pretty organized now. Each team has their own wiki page. Some teams have blueprints, and are subscribed to them. 
[11:23] <zequence> Waiting for Scott to come online so I can discuss changing a few more things. 
[11:24] <zequence> I updated the team structure page again today https://wiki.ubuntu.com/UbuntuStudio/TeamStructure
[11:24] <zequence> Soon all that is missing is team members
[11:25] <zequence> ..well, a bunch of docs too before that
[13:57] <scott-work> good morning everyone :)
[13:58] <zequence> scott-work: Hi manm
[13:58] <zequence> man*
[13:58] <zequence> I've been busy all day writing wiki pages
[13:58] <zequence> scott-work: Have a look at https://wiki.ubuntu.com/UbuntuStudio/TeamStructure
[13:59] <scott-work> wow! that's looking really good. you have a much better eye for presentation that i do :)
[14:00] <smartboyhw> Hello:)
[14:00] <scott-work> good job, zequence
[14:00] <scott-work> morning smartboyhw 
[14:02] <smartboyhw> zequence, you do really know how to plan things:)
[14:03] <zequence> Thanks. There's still plenty to do, but I'm finding the format falling into place now
[14:04] <zequence> scott-work: I started subscribing teams to their correct blueprints. Started linking it all up, so to speak
[14:04]  * smartboyhw got at least 3 subscribing emails today
[14:04] <zequence> scott-work: I'd like to remove the mail list for ~ubuntustudio-testers, and have them not subscribe to bugs anymore. 
[14:05]  * smartboyhw agrees
[14:05] <zequence> scott-work: I have the ~ubuntustudio-bugs team for that. I'm thinking it doesn't need to be a workitem/blueprint based theme, but just a nice way to subscribe to Ubuntu Studio related bugs. YOu become a member, you get bug reports.
[14:05] <zequence> not theme. team
[14:06] <scott-work> zequence: i agree with moving that over
[14:06] <smartboyhw> :)
[14:07] <zequence> scott-work: Also, I think we should create a core team, which has power of adjusting teams. The -dev team I think should only be used for getting privelege to branches
[14:07] <zequence> So, the core team would own or manage all the other teams. The -dev team would only have priveleges inside itself
[14:11] <zequence> I went ahead and created a documentation team today. We still need to create "contributors team" and "PR/Support" team. I also think we should create a "Art" launchpad team which would own branches for art stuff
[14:11] <smartboyhw> zequence, will there be too many teams?
[14:12] <zequence> smartboyhw: No
[14:12] <smartboyhw> zequence, eh?
[14:12] <zequence> We should use the launchpad teams functionality more. Each team will have privileges, or be subscribed to relevant material
[14:13] <zequence> Each team is a sort of portal to that specific area of responsibilies
[14:14] <zequence> Subscribing teams to blueprints is actually a very good method for making sure team members are made aware of what's going on
[14:15] <zequence> Some teams don't have blueprints though. It all depends on what the team is doing
[14:15] <zequence> The nightly team does seem like a strange team to me. That could just as well be the -dev team. All it does is has a PPA
[14:22] <zequence> smartboyhw: The idea is we get more people involved. Each team needs to be able to operate independently as much as possible. If we don't have a good structure in place, with clear communications, it's hard to get that working
[14:24] <zequence> As soon as all of this structuring and doc writing is at a stage when someone could more or less jump in and start working - getting info, news and docs easily for what they want to work on, we could start announcing for participants on our different channels
[14:24] <zequence> With all these billions of people in the world, surely there must be a few wanting to participate
[14:25] <smartboyhw> zequence, I think that the -nightly team should get killed. The PPA isn't used anymore anyway
[14:26] <zequence> smartboyhw: It's being used, but not for us
[14:26] <smartboyhw> zequence, the old days:P
[14:27] <zequence> Last build attempt was 4 weeks ago
[14:27] <smartboyhw> zequence, oh?
[14:27]  * smartboyhw goes to see why:P
[14:27] <smartboyhw> And failed
[14:27] <zequence> But, I agree. I don't see a point in having that team. Those builds could be done on any PPA
[14:31]  * smartboyhw agrees
[14:39] <astraljava> I think I removed something that had been failing for the past couple of years or so. I'm fairly sure rexbron was the sole users who had set up anything there. He said he had no use for at least that one failing build anymore. Not sure about the rest.
[14:40] <zequence> smartboyhw: I'm looking to try get more testers. At least, we need to have a good quatily Beta testing period. Until then, we are a little lacking in docs. 
[14:40] <zequence> ISO testing is not required that often
[14:40] <smartboyhw> zequence, I will post something soon about 12.04.2 testing
[14:40] <zequence> But, we could use more workflow testing.
[14:41] <zequence> smartboyhw: Not just for a short period, but really try to get people join our testing team, and communicate directly with us
[14:43] <zequence> smartboyhw: I'm not saying you should try to get more testers right now, or anything. Just telling you in advance what my plans are, and that I plan to write docs for this to happen
[14:44] <zequence> If you have any ideas about docs and whatelse, just let me know
[14:44] <smartboyhw> good
[14:59] <zequence> Going home. bb in a couple of hours
[15:01] <smartboyhw> zequence, see ya
[15:30] <ttoine> scott-work, http://lite.framapad.org/p/5n3kYagDQA
[15:42] <scott-work> zequence: smartboyhw : we are not in control of that team, rexbron is. but i *do* want to get ubuntustudio-dev not a member of that team though
[15:43] <scott-work> ttoine: that would be exceedingly exciting to interview stephane
[15:43] <scott-work> i presume you want me to add some questions. i'll see what i can do throughout my work day
[15:45] <smartboyhw> scott-work, ok
[15:46] <scott-work> smartboyhw: i'm just saying we can't nuke (delete or terminate) this team as it isn't ours, but we can sever ties with it
[15:47] <smartboyhw> scott-work, ok
[16:22] <ttoine> scott-work, yes, the aim is that the team ad some questions
[16:22] <ttoine> I will see him next week, but the date is not fixed
[17:07] <zequence> scott-work: So, what do you think of adding a core team? It would make sense to have one team only for administering other teams
[17:45] <scott-work> zequence: i'm not sure. what sort of admin activities would they do? should we make an unofficial "core team" and have them as admin members across all teams?
[17:46] <scott-work> i don't feel strongly one way or the other, just talking outloud right now
[17:59] <zequence> scott-work: I don't think the -dev team is supposed to be admin of other teams. And members of -dev don't need access to lot's of other stuff
[17:59] <zequence> scott-work: -core would administer other teams, register blueprints, etc
[17:59] <zequence> It would function as the Ubuntu Studio launchpad admin team
[18:00] <zequence> I'm suggesting to create one, and make it owner of all other teams
[18:00] <zequence> Then add those people to the -core team that have it as their duty to administer those teams. Currently, it would be you and me
[18:04] <zequence> All of the teams should be separate what privileges are concerned. If you're a member of -dev, you don't get access to -kernel-team or -website. It would just be a cleaner way to administer rights
[19:21] <zequence> scott-work: In short, my vision of the launchpad team structure is: -core would own all official teams. No other teams would have privileges outside their own team
[19:21] <zequence> Each team, other then -core, would only have prileges related to the team
[19:22] <zequence> -core members do blueprint drafting, and administer the teams.
[20:19] <zequence> scott-work: Logging off. Will look at logs tomorrow, and continue working on the wiki.
[20:20] <scott-work> zequence: sorry, webchat died on me and then i got busy at work
[20:20] <scott-work> i'll check the logs myself and respond. have a good night :)