[00:03] <ScottL> reading troy_s' latest blog post i am reminded that i could have handled the website development much better :/
[00:05] <ScottL> but i hope to learn from the experience (and his blog posts) and manage the next situation in a better fashion :)
[00:08] <persia> If you aren't learning, it gets boring fast :)
[00:30] <ScottL> i agree persia about primary and alternate solutions
[02:31] <ScottL> i just learned about "jack sessions" last week, i wonder if we should be supporting it as we are with lashd in natty?
[02:31] <ScottL> or should we choose one over the other?
[02:31] <ScottL> and what we would need to do if we choose to support "jack sessions" 
[02:33] <persia> We probably ought involve ourselves in wider discussions so that we can have one method that users use to save full status of their work.
[02:34] <persia> Could be jack sessions triggering lashd saves, or lashd saving the current jack session, or something else entirely.
[02:36] <ScottL> how wide?  i would imagine this could include more than the ubuntu studio or ubuntu communities
[02:37] <persia> I think it probably needs discussion at the l-a-d@ level.
[02:37] <ScottL> right, that seems entirely sane
[02:38] <persia> From a quick glance at archives, seems there was some discussion on the topic from June.
[02:39] <persia> And I think that upstream is being sane about this sort of thing, but it may need some work, especially in terms of integrating patches into the applications.
[02:41] <persia> http://trac.jackaudio.org/wiki/WalkThrough/Dev/JackSession and http://trac.jackaudio.org/wiki/WalkThrough/User/jack_session keep failing to load for me, but are probably reasonable resources.
[02:41] <ScottL> stochastic, dave phillips discussed some recent news about xjadeo  http://www.linuxjournal.com/content/ecology-ardour
[02:42]  * persia hugs uzbl for loading all sorts of random stuff that doesn't work with regular browsers
[02:42] <ScottL> persia, those are the pages i read last week, i had no idea about jack sessions until i read those
[02:43] <ScottL> dave phillips also reports that blender is working on JACK support :)
[02:44] <persia> Looks a bit immature for natty, to me, but maybe we'll reach sufficient coverage before natty+1 that it would make sense to target doing local patches for the more important apps still unsupported.
[02:47] <ScottL> oh yeah, i don't expect this for natty, just pointing it out because i think it's awesome
[02:48] <ScottL> persia, which browser are you trying to use to open the jack sessions pages?
[02:49] <persia> I was using epiphany.
[02:52] <persia> But my quest for a light-weight browser that does what I want is likely to end up with some custom luakit arrangement
[16:21] <scott-work> stochastic:  i think we may also be able to use wordpress for the website update
[16:22] <scott-work> i've noticed many, many new official ubuntu web pages that are "Powered by WordPress", e.g. http://uds.ubuntu.com/
[16:30] <scott-work> persia: i forgot if you had confirmed this or not, do we need to remove the mscore package from the natty seeds and replace it with musescore?
[16:30] <scott-work> is there anything else we will need to do?  will someone else handle the actual transition package itself?
[18:16] <persia> scott-work, Oh, for seeds!  Yes, absolutely mscore needs to be removed and musescore placed.  The mscore package has to be left in the archive until squeeze release.
[18:18] <scott-work> persia: thank you, i'll update my branch of the seeds then
[23:29] <stochastic> ScottL, switching themes/layouts within Drupal is an easy task; switching entire cms systems is much more involved.  I'm also not familiar with wordpress, so I wouldn't be much help in that situation.
[23:31] <stochastic> essentially, my view is that the site runs on drupal, there's nothing that wordpress can do that drupal can't, so there's no purpose to switching
[23:32] <persia> I'll argue that there are N things wordpress can do that drupal can't, and vice versa, and neither are important in the slightest: the decision ought be made based on the capabilities of the administrators, rather than for a feature, as it's vanishingly rare that either can't do something that is important for most sites.