[00:48] <Pendulum> o/
[16:07]  * micahg waves
[16:24]  * ScottL waves at micahg 
[16:27]  * micahg is available on IRC for Xubuntu related questions
[16:29] <micahg> Perhaps having the flavors having their own langpacks might be beneficial, we certainly don't want to bloat the main langpacks with stuff for all th eflavors
[16:30] <micahg> that should be the best of both worlds (flavors get to translate in LP, no extra bloat for anyone), I just have no idea how much work it is to generate those (dpm and pitti would be the people to discuss with)
[16:38] <tgm4883> we need more devs!
[16:38] <highvoltage> DEVELOPERS! DEVELOPERS! DEVELOPERS!
[16:38] <tgm4883> FWIW, it's difficult for me to make the Mythbuntu release notes on our own page
[16:41] <tgm4883> that might be something Mario took care of for us, is there a link that I can see for that?
[16:42] <tgm4883> ok
[16:42] <highvoltage> here's the edubuntu one, for an example... https://wiki.ubuntu.com/PrecisePangolin/ReleaseNotes/Edubuntu
[16:42]  * highvoltage checks if there's a template somewhere
[16:42] <tgm4883> highvoltage, thanks
[16:42] <highvoltage> well I guess https://wiki.ubuntu.com/PrecisePangolin/ReleaseNotes contains all you need
[16:42] <tgm4883> and this is what was autogenerated from blueprints?
[16:47] <tgm4883> sweet
[16:49] <udsbotu> uds-gb-b: 5 minutes left in this session!
[16:51] <udsbotu> uds-gb-b: 4 minutes left in this session!
[16:51] <udsbotu> uds-gb-b: 3 minutes left in this session!
[16:52] <udsbotu> uds-gb-b: 2 minutes left in this session!
[16:53] <udsbotu> uds-gb-b: 1 minute left in this session!
[16:54] <udsbotu> uds-gb-b: This session has ended.
[17:09] <mpt> Each of these items isn't just a matter of designing and implementing a setting, it also requires designing and implementing what happens when a user tries the thing that has been locked down
[17:09] <mpt> (e.g. what happens when they try to drag an application into the launcher)
[17:12] <mpt> Another example, if a System Settings panel is hidden, any button somewhere else that would open that panel should also be greyed out
[17:15] <mpt> dbarth, I'm not sure what you meant by a template, but it would make sense to have template for a mini-specification for each setting: * Where and how an admin changes the setting * How existing user accounts behave when the setting is changed * What happens when the user tries the disallowed thing
[17:18] <mpt> desrt, for example, if someone has added applications X, Y, and Z to the launcher, and then the admin allows X and Z but not Y, X and Z should still appear, and there shouldn't be a [?] tile left where Y used to be. Things like that.
[17:22] <mpt> This could be a whitelist that included X and Z, not necessarily a blacklist that included Y
[17:27] <mpt> ---
[17:27] <mpt> The UI for setting the configuration is what really interests me
[17:29] <mpt> If you just implement the dconf keys and do nothing else, what percentage of admins would discover them?
[17:29] <mpt> If you implement them and document them on ubuntu.com somewhere, that percentage increases, but not by much
[17:29] <mpt> If you have an admin control panel of some sort, the settings become much more useful
[17:31] <mpt> desrt, that would be a good start -- even better if it was inside a window rather than in a whole separate session
[17:31] <mpt> (I think Unity can do that already?)
[17:32] <mpt> There would be some settings that couldn't be expressed in that way
[17:32] <mpt> searchable list, sure
[17:33] <mpt> I see "Ability to hide some System Settings items" in this table, and I immediately think, oh, that should be a copy of the System Settings home screen with a checkbox next to each icon
[17:40] <mpt> In some cases you want something more general, e.g. "Users in this group can: [/] Change the sound volume"
[17:40] <udsbotu> uds-gb-b: 5 minutes left in this session!
[17:40] <mpt> and if that's unchecked it affects not just the sound menu, but the volume keys etc as well
[17:41] <udsbotu> uds-gb-b: 4 minutes left in this session!
[17:42] <udsbotu> uds-gb-b: 3 minutes left in this session!
[17:42] <mpt> I really think each of these settings should be considered as its own design+implementation task, because it touches varying bits of UI
[17:42] <mpt> "[shell-team] implement lock-down support" would turn into a fuzzy endless task
[17:43] <udsbotu> uds-gb-b: 2 minutes left in this session!
[17:44] <mpt> ok
[17:44] <udsbotu> uds-gb-b: 1 minute left in this session!
[17:45] <mpt> sure, thanks dbarth
[17:45] <udsbotu> uds-gb-b: This session has ended.
[17:46] <mpt> Another thing to consider is whether the admin UI for all these settings should ship by default, or whether it should be something you install separately
[17:46] <mpt> given that there are a few user permission settings in the User Accounts panel of System Settings already
[17:47] <dbarth> mpt: yeah, it could live there you're proposing?
[17:47] <mpt> maybe
[17:48] <dbarth> i would see it stay outside of the CD for now, as it's quite specific though
[17:48] <dbarth> if only to save space
[18:49] <udsbotu> uds-gb-b: 5 minutes left in this session!
[18:51] <udsbotu> uds-gb-b: 4 minutes left in this session!
[18:51] <udsbotu> uds-gb-b: 3 minutes left in this session!
[18:52] <udsbotu> uds-gb-b: 2 minutes left in this session!
[18:54] <udsbotu> uds-gb-b: 1 minute left in this session!
[18:55] <udsbotu> uds-gb-b: This session has ended.
[19:03] <cr3> hello everyone!
[19:19] <brendand> 5 minutes
[19:19] <brendand> it runs for 300 seconds
[19:20] <cr3> brendand: I wonder what would be the difference between running for 5 minutes or 5 times for 1 minute
[19:20] <brendand> cr3 - that's effectively what it does
[19:21] <brendand> 5 * 60 seconds
[19:21] <cr3> perhaps if we calculate the median, removing the highest and smallest values, rather than just an average would make a difference
[19:21] <brendand> we could process the numbers in a more statistically meaningful way
[19:21] <brendand> it would be nice if iperf could do that for us (maybe it does)
[19:27] <brendand> cr3 - remember the maverick headless problem?
[19:30] <cr3> brendand: nope, my memory doesn't go further back than precise
[19:30] <cr3> ironically, my memory is inprecise
[19:43] <brendand> in the sru?
[19:43] <brendand> it's never failed
[19:44]  * brendand wants to check it's there )
[19:44] <brendand> no, it's not
[19:44] <brendand> we just need to add it then. it's an easy win
[19:45] <brendand> i'm not sure it's in the sru suite yet
[19:45] <brendand> we were waiting for hardware to arrive in taipei
[19:45] <brendand> ctf has cards now?
[19:46] <brendand> another easy win  (hopefully!)
[19:55] <udsbotu> uds-gb-b: 5 minutes left in this session!
[19:56] <udsbotu> uds-gb-b: 4 minutes left in this session!
[19:57] <udsbotu> uds-gb-b: 3 minutes left in this session!
[19:58] <udsbotu> uds-gb-b: 2 minutes left in this session!
[19:59] <udsbotu> uds-gb-b: 1 minute left in this session!
[20:00] <udsbotu> uds-gb-b: This session has ended.
[22:34] <SpamapS> o/
[22:34] <SpamapS> I missed the first 30 min...
[22:35] <SpamapS> no notes in etherpad
[22:35] <SpamapS> Serge, anything I should know?
[22:36] <SpamapS> You know I'm all about whats cool
[22:55] <udsbotu> uds-gb-b: 5 minutes left in this session!
[22:55] <udsbotu> uds-gb-b: 4 minutes left in this session!
[22:57] <udsbotu> uds-gb-b: 3 minutes left in this session!
[22:58] <udsbotu> uds-gb-b: 2 minutes left in this session!
[22:59] <udsbotu> uds-gb-b: 1 minute left in this session!
[23:00] <udsbotu> uds-gb-b: This session has ended.
[23:10] <NMinker> hello
[23:55] <udsbotu> uds-gb-b: 5 minutes left in this session!
[23:56] <udsbotu> uds-gb-b: 4 minutes left in this session!
[23:56] <mika__> Greeter doc http://goo.gl/ImT7O
[23:57] <mika__> Greeter visuals http://goo.gl/5G2VZ
[23:57] <udsbotu> uds-gb-b: 3 minutes left in this session!
[23:58] <udsbotu> uds-gb-b: 2 minutes left in this session!
[23:59] <udsbotu> uds-gb-b: 1 minute left in this session!