[03:50] hey stochastic [03:50] hey smartboyhw [03:54] I see a bunch of re-organization took place lately [03:54] I was removed from a handful of groups, but didn't have time to dig in to understand why [03:55] what exactly went down? [04:00] stochastic, ask zequence :P [04:01] He's the vice project lead now :P [04:01] okay [04:05] zequence, ? === micahgmobile is now known as micahg_mobile [06:31] stochastic: Didn't you get a message in your mail about that? [06:32] stochastic: We've reaorganized the launchpad teams. For practical reasons. Privileges, blueprints and bug subscriptions per team [06:34] stochastic: ubuntustudio-dev has been removed from some groups, but I don't think you were removed from any? [06:34] zequence, do you have a document I can overview of these changes or the subject of the best e-mail to read on the subject? [06:34] stochastic: https://wiki.ubuntu.com/UbuntuStudio/TeamStructure [06:35] I'm reworking the wiki too. [06:35] Writing dev docs for all the tams [06:35] teams* [06:35] okay [06:36] sounds good, I just get concerned when I see messages like "stochastic deactivated from X" without prior knowledge (maybe I missed the prior memo) [06:38] :). I guess I should have made an announcement, but I did message everyone who were directly being moved between groups. I haven't removed anyone directly from any group. Only moved a couple of our active members from one group to another, retaining the purpose of the membership [06:38] I will make an announcement once it's all done though [06:39] Perhaps deactivating ubuntustudio-dev from some groupts caused those messages to show? [06:39] It was a member of many groups. We've now made ubuntustudio-core the manager of the launchpad teams, and ubuntustudio-dev is just for development. Owns branches [06:41] yeah, in review of the changes you've made all the message make sense now [06:42] web-team is deleted thus there were a few deactivation messages, also dev group general messages of deactivation, there were about five in a row of similar nature. Just all housekeeping stuff :) [06:43] next time it'd be great to e-mail out to the two lists (users & dev) directly before or after any major launchpad reorg just to briefly explain what's happening [06:45] zequence, why was I deactivated from the website team? [06:46] stochastic: -website team is now only for developing the website. It seems I moved you to the PR team, which has editor rights on the main site, so full control of content [06:47] I think I messaged you about that [06:47] * stochastic looks for that message [06:47] Should be in the same message where you are shown to be deactivated from -website [06:48] I should be asking you if this was a correct move, or not [06:48] ..in the message [06:48] oh [06:48] I'd still like to retain website development work if that's okay [06:49] I know I've been quite inactive as of late, but have been very involved with that in the past [06:50] stochastic: Done [06:50] zequence, thank you [06:50] That team owns the website theme code, and gets messages of changes to the -website blueprint [06:50] yes, makes sense [06:51] I think that clears everything up. Thanks for taking this re-org on zequence I know scott was wanting to clean up our launchpad presence for a long time now [06:52] stochastic: Thanks. I've been working with Scott on this, all though he has had less time than me to work out the details [06:53] One reason for the change is to make it easier for new contributors to get connected to information. [06:53] And I really want to start hunting for contributors, as soon as the Wiki is in better shape too. [17:36] this guy has an interesting icon for music made with linux: http://audio-and-linux.blogspot.com/2013/02/music-made-with-linux.html [17:37] i wonder if there is a "standard" icon for this [18:15] scott-work: nice entry and some real interesting music out there [18:56] scott-work: If not, maybe we should lobby for one [18:57] Or, one could discuss this on LAU === TheDrums_ is now known as TheDrums [19:01] scott-work: We should post about projects made using Linux Audio too [19:02] Something to add for the PR team [19:02] scott-work: btw, I was playing around with a format for the header https://wiki.ubuntu.com/UbuntuStudio/TeamStructure [19:03] scott-work: I'm thinking we should have one for wiki.ubuntu.com/UbuntuStudio, and the same design, but with perhaps another color and also another content for help.ubuntu.com/community/UbuntuStudio [19:05] We should profile one to be for development, and the other for users, but keep a close tie, so that it's easy to orientate. One should really find everything else from anywhere, whether one is at the website or one of the wikis [19:05] Particularly having different sets of colors makes it easy to see the difference [19:06] I'm planning to make navigation easy also for all the pages that become the backbone for docs, both dev and user [19:07] By either using another form of the header, or use trails back to the root [19:14] zequence: definitely i think we should post about some of this stuff [19:15] zequence: i like the look of the header [19:16] one thing i've thought about is that perhaps some open teams should have a time limit on members [19:16] for example, i'm okay with ~ubuntustudio being open and no time limits, there really isn't an responsibility for that team [19:17] however for -testing, i would like to have a mechanism that automatically drops people who aren't active anymore or willing to reply to the 'renew membership' email [19:18] scott-work: Sure, we could add a time limit to that sort of teams. -documentation and -contributors are similar [19:18] ..as they are open [19:19] I guess there's no reason to add that to moderated teams [19:19] Few members, and we know them all, pretty much [19:25] Or, you think we should add that to moderated teams as well? [19:26] It's not a big deal to renew ones membership every once a year, or whatever period one chooses [19:30] I saw that Xubuntu had different icons for teams, depending on how restricted they are. I was thinking of doing that for us too. I was using another form of the logo for some teams before [19:38] No, forget I said anything about the moderated teams. [19:39] scott-work: So, for the open teams, except for ~ubuntustudio, and ~ubuntustudio-bugs(which is more of a bug subscription team), what time period do you like? I'm thinking one year is not too short anyway [19:42] zequence: that sounds good. i just worry about these teams where anyone can join but we don't get any benefit from them even though a bazillion people are on the team [19:43] (and webchat dropped me again :( ) [19:44] scott-work_: Yeah. Ok, I'll set that up then === scott-work_ is now known as scott-work [19:50] I'm making the subscription period 365 days, and the self renewal period 30 days. But, this only affects new members. The existing ones keep their settings [19:50] -testing had 3000 days [19:51] I could change that, but would need to do that for each user. [19:51] I could do that, and send a message about the change, so no one is surprised by the change [22:14] zequence, I was this week-end at azarecord [22:14] I followed the record of 9 track of a jazz band on the workstation I builded for them [22:14] now, I am waiting for the mix and master, so I can let you listen [22:20] ttoine Great [22:21] ttoine: You should post about that too [22:21] zequence, yep, I think I will do a case study about azarecord, and translate it in english [22:22] and wednesday, I interview Stephange Letz [22:22] stephane [22:23] the mastering session is scheduled at the end on february