[01:39] <ScottL> created a blueprint for updating the website:  https://blueprints.launchpad.net/ubuntustudio-resources/+spec/update-ubuntustudio-website
[01:39] <ScottL> knome, falktx ^^^
[01:39] <ScottL> holstein, ^^^ astraljava 
[01:40] <falktx> ScottL: joomla is also another nice CMS
[01:40] <falktx> opensource too
[01:41] <ScottL> please feel free to update it
[01:41] <ScottL> falktx, i'm not sure that joomla is acceptable to canonical
[01:41] <ScottL> maybe it is, i don't know
[01:42] <falktx> "acceptable to canonical" ?
[01:42] <falktx> canonical refuses opensource projects?
[01:43] <falktx> wiki seems stuck to me
[01:43] <falktx> ScottL: sorry, I can't login...
[01:45] <falktx> ah, now I'm on
[01:45] <falktx> ScottL: no idea how to edit this though
[01:45]  * falktx doesn't like the ubuntu wiki
[01:45] <falktx> arch wiki is much cleaner and easy to use
[01:48] <ScottL> falktx, i should have said "acceptable to canonical security"
[01:48] <falktx> security...?
[01:48] <ScottL> i think they have been quiet restrictive previously about which platforms can be used
[01:48] <falktx> not considered safe enough?
[01:49] <ScottL> it wasn't until recently that they started using wordpress i believe
[01:49] <ScottL> i.e. it was drupal or nothing for a while i believe
[01:51] <falktx> geez
[01:51] <falktx> canonical guys must be crazy 
[01:52] <falktx> ScottL: anyway, please try to speak with knome about the website
[01:52] <falktx> ScottL: if he can't do it, I'll be glad to take the task
[01:52] <falktx> just remember that I already have other things to do, so if he can do it, I'll be glad
[01:53] <falktx> in last case, I can drop my things to work with US website. getting this done is very important and I realy want to see it happening
[01:55] <ScottL> falktx, pushing the code to the bzr branch would be a huge help
[01:55] <falktx> code?
[01:55] <ScottL> i'll find the link...
[01:55] <ScottL> https://code.launchpad.net/~ubuntustudio-dev/ubuntustudio-resources/website
[01:56] <ScottL> as best as i can tell (and i'm far from a website expert) the base code (like newpage.php) is hosted in a bzr branch
[01:56] <ScottL> once it has been reviewed (pesumably by security) then it is pushed by others to the hosted site
[01:57] <ScottL> then someone who has access to the site can generate content
[01:57] <ScottL> this is how i _think_ it is handled but i haven't talked to anyone who has particular knowledge yet
[01:58] <falktx> ok, ScottL, I'll take a look tomoroow
[02:00] <falktx> I don't see an index.php
[02:00] <falktx> oh, ScottL, is this a wordpress theme?
[02:01] <falktx> ah, drupal
[02:01] <ScottL> falktx, it should be drupal6 (i think)
[02:01] <falktx> I'll install it later
[02:01] <ScottL> knome, mentioned migrating to wordpress perhaps
[02:01] <falktx> ScottL: what about the new proposal, do you got the code for it?
[02:01] <ScottL> i have it in my email somewhere, i can find it later tonight or tomorrow
[02:01] <ScottL> i need to update the spec more to include that and a few other things
[02:01] <falktx> ok, please forward it to me
[09:28] <astraljava> ScottL: I think the theming looks really sleek(?). Will check the blueprint for the webserver, but that's not really my field, and frankly I've got my hands full on other things. But will definitely read it through, anyway.
[10:55] <knome> falktx, hey!
[10:56] <falktx> knome: hey, finally!
[10:56] <knome> falktx, where should i start? :)
[10:56] <falktx> knome: ask ScottL
[10:56] <knome> well, to ScottL too, of course the theme is convertable to wordpress
[10:57] <falktx> ScottL: there's a blueprint for it
[10:57] <falktx> err
[10:57] <knome> hehe
[10:57] <falktx> knome: there's a blueprint for it
[10:57] <knome> yep, i read the backlog
[10:57] <knome> what do you think of wordpress as the platform?
[10:57] <falktx> never used it
[10:58] <falktx> only used joomla so far, oh, and mediawiki
[10:58] <knome> i've used it quite a lot, and it's way better than joomla or drupal
[10:58] <falktx> my kx site is done in mediawiki
[10:58] <knome> drupal is just a horror :(
[10:58] <knome> http://shimmerproject.org/,  http://open.knome.fi/
[10:59] <knome> done with WP
[10:59] <knome> and http://xubuntu.princessleia.com/ is WP also
[11:03] <falktx> knome: i'm working on this - http://distrho.sourceforge.net - although I did *not* made the base template
[11:03] <knome> falktx, mmyeah
[11:04] <knome> ScottL did say that many people liked the new site looks, so maybe we should keep that, or...?
[11:04] <knome> or was he referring to this site or yours? :)
[11:06] <falktx> the new US one
[11:06] <falktx> I like it too
[11:06] <falktx> ScottL: I'm still waiting on that email with source...
[11:07] <knome> i'm not sure if i'd need source. converting from drupal theme to WP theme (if we're going to do that) is not trivial, and really, some of the stuff need tweaking anyway
[11:07] <knome> :)
[11:19] <knome> okay, i'm going to cook some lunch now, bbl
[17:54] <scott-work> hi shnatsel|busy how are you doing today?
[17:54] <scott-work> i made a blueprint for the website update :)  although i'm still clarifying some points on it
[17:54] <scott-work> but it's a start
[17:54] <scott-work> i need to find an email for falktx_ as well on it
[17:55] <scott-work> knome: did you see the discussion about the website blueprint as well?
[17:55] <scott-work> knome: please let me know how i can improve it (please, please)
[17:55] <scott-work> i really want it to be as helpful as possible
[17:56] <knome> yeah, i read the discussion
[17:56] <knome> i can check that later, yeah
[17:58] <scott-work> thank you, i also got your email and i will give it attention tonight
[17:58] <shnatsel|busy> scott-work: I'm OK, messing with seeds. Canonical guys clearly never planned to export this system.
[17:58] <scott-work> knome: falktx_ would really like to help with the website as well, is there something he can do to assist as well?
[17:59] <falktx_> knome: do you think you got it?
[17:59] <falktx_> knome: you seem a lot more experienced on this than me
[17:59] <shnatsel|busy> hardly any docs and read/write locks required for seed branches and some branches can't even be branched without auth to canonical servers
[17:59] <falktx_> scott-work: thanks for the mail!
[18:00] <knome> falktx_, i can "lead" it, but i'll keep you informed on the progress :)
[18:00] <falktx_> knome: ah yes, let me know where I can help1
[18:00] <falktx_> *help!
[18:00] <knome> falktx_, okay, great, i'll do that once i get started
[18:01] <shnatsel|busy> scott-work: what blueprint? https://blueprints.launchpad.net/ubuntustudio still tells me that blueprints are disabled
[18:02] <scott-work> knome: i have the files for the http://myhaiku.org/ site if it helps you at all
[18:02] <knome> scott-work, https://blueprints.launchpad.net/ubuntustudio-resources/+spec/update-ubuntustudio-website
[18:02] <knome> err, shnatsel|busy 
[18:02] <scott-work> shnatsel|busy: i ended up created the bluprint under the code at the bzr branch
[18:02] <scott-work> shnatsel|busy:  i thought that the blueprints worked under ubuntustudio-dev before but i couldn't get them to work this time, maybe something has changed
[18:03] <knome> scott-work, sure, at least the artwork comes handy when i don't have to recreate it. btw, is there svg sourcer for the US logo?
[18:03] <scott-work> but even as project lead i couldn't find a way to enable them
[18:03] <falktx_> knome: will you keep the web structure or change to a cms?
[18:03] <scott-work> knome: i will have to find it
[18:03] <knome> scott-work, okay, no hurry :)
[18:04] <knome> falktx_, i'll create a wordpress theme
[18:04] <knome> scott-work, ^ that was okay, am i right? :)
[18:04] <shnatsel|busy> scott-work: go to https://blueprints.launchpad.net/ubuntustudio, there should be a "configure blueprints" link at the right
[18:06] <scott-work> knome: i think wordpress is good
[18:06] <knome> good!
[18:07] <knome> 3.x is wonderful as a CMS too
[18:07] <scott-work> knome: my only serious concern (which is platform independent) is getting the code into the bzr branch and then pushed to the site
[18:08] <scott-work> charlie-tca: did you have any involvement with coordinating the xubuntu website migration to wordpress or know who did?
[18:08] <scott-work> shnatsel|busy: done
[18:09] <knome> scott-work, this: https://launchpad.net/xubuntu-website-wordpress is how we did it, it's pushed into two separate branches (theme/plugins), and the canonical IS services staff is now reviewing it, and they'll handle uploading to production
[18:09] <knome> scott-work, pleia2 is working on that, but i'm aware of what has happened so far too :)
[18:09] <falktx_> it sucks when someone reviews your site. all the work and they simply say "no"
[18:09] <scott-work> knome: my apologies, i thought you weren't involved in that part
[18:10] <scott-work> falktx_: it is canonical hosting and i dont' begrudge them the right to protect their security
[18:10] <knome> scott-work, well, not exactly *involved*, but i'm getting all the CC's
[18:10] <shnatsel|busy> scott-work: it works! thanks!
[18:10] <charlie-tca> scott-work: pleia2 handled the IS requests, and knome and pleia2 did the actual layouts
[18:10] <scott-work> knome: ah, but sometimes that is enough as in cases like this :)
[18:10] <knome> "review" probably means they will tell to change something, or that they'll change something theirself, and then push it to production
[18:10] <falktx_> scott-work: so any change needs to be reviewed by canonical?
[18:11] <knome> falktx_, yes
[18:11] <scott-work> i have been told that they expressly forbid some plugins on security basis so we have to be selective sometimes about what functions we want
[18:11] <knome> falktx_, any change to the code, changes to content via WP admin (or any other tool) are of course manageable by yourself
[18:12] <knome> scott-work, you can do pretty much everything what myhaiku.org does with core WP, except the javascript slider on the front page
[18:21] <shnatsel|busy> scott-work: https://blueprints.launchpad.net/ubuntustudio/+spec/livedvd
[18:26] <shnatsel|busy> scott-work: I guess you can set general direction to approved in the livedvd blueprint
[18:34] <scott-work> shnatsel|busy: would it be beneficial to reassign the website-update to "ubuntustudio" instead of the bzr branch?
[18:35] <shnatsel|busy> scott-work: well, I think it should be linked to the branch containing the ongoing work described in the blueprint
[18:35] <shnatsel|busy> scott-work: I guess moving it to ubuntustudio project would be a good idea
[18:36] <shnatsel|busy> it would make it more visible
[18:36] <scott-work> okay, i'll reassign it to ubuntustudio and link the brank
[18:36] <scott-work> branch
[18:36] <shnatsel|busy> it's called "re-target blueprint"
[18:36] <shnatsel|busy> changing project
[18:38] <scott-work> i did it once already :)
[18:39] <shnatsel|busy> it took me a while to discover how to change project
[18:50] <scott-work> shnatsel|busy: when i did the update-website blueprint i re-targeted it once because i think i assigned it to ubuntustudio-dev the first time just to get it done
[18:57] <scott-work> re-targeted "update-website" blueprint:  https://blueprints.launchpad.net/ubuntustudio/+spec/update-ubuntustudio-website
[18:59] <shnatsel|busy> scott-work: awsum blueprint
[19:00] <scott-work> thanks :)  i still have some more to add to it though, some further clarifications and examples
[21:33] <scott-work> i think i'll also make a blueprint for the -lowlatency kernel