[16:03] <qense> hello
[16:11] <newz2000> hi qense
[16:13] <tannman> hello
[16:14] <tannman> this the correct room for assistance?
[16:42] <thorwil> hi newz2000. i still see the pixelated brainstorm logo on http://www.ubuntu.com/community/participate
[16:42] <newz2000> hi thorwil, that's on my list to do today
[16:42] <thorwil> ah, ok :)
[16:42] <newz2000> I had some time off last week and just didn't get that done before I left
[16:43] <nand> oh hai!
[16:44] <newz2000> hey nand
[16:44] <nand> newz2000: did I remember correctly that you were talking about a inter website navigation a while ago?
[16:44] <newz2000> I was talking about it but never came up with a solution
[16:46] <nand> okay. If you're interested, we may talk a bit about it at the UDS, I have some little ideas, but I need some background to see if they're feasible
[16:46] <newz2000> nand: I won't be a UDS, sending to the mailing list is probably the best way
[16:47] <nand> okay, I'll give my ideas there then (I'm at work right now)
[16:47] <newz2000> nand: will you be at UDS?
[16:47] <nand> yes
[16:48] <newz2000> make sure to introduce yourself to Julian, he's the guy Mark S hired to be in charge of Ubuntu's prettyness
[16:49] <newz2000> I know he's putting a lot of thought into the website's appearance
[16:49] <nand> Julian how?
[16:49] <newz2000> I don't understand that question
[16:50] <nand> his last name? :)
[16:50] <newz2000> Maybe Julian who?
[16:50] <nand> yah :)
[16:50] <newz2000> let me look it up
[16:50] <nand> (french deformation)
[16:50] <thorwil> nand: just think of the doctor ;)
[16:50] <newz2000> Julian Hubbard
[16:51] <nand> newz2000: okay thanks for the tip!
[16:51] <newz2000> my pleasure
[16:52] <newz2000> since I'm not going to UDS during that week I'll be at a drupal training conference www.doitwithdrupal.com
[16:52] <nand> you're a drupal fan?
[16:52] <newz2000> I'm hoping to learn how to improve the websit a lot
[16:52] <thorwil> that url sounds naughty
[16:52] <newz2000> nand: I wouldn't say a fan, but it's a tool I use to solve problems
[16:52]  * nand is currently working on the drupal powered www.france24.com
[16:53] <newz2000> I really wish there were better solutions out there but haven't found anything yet
[16:53] <nand> In my opinion, Drupal is really powerful, once you have spend months with it and you understand it
[16:54] <newz2000> I'd trade some of its power if it made life easier
[16:54] <newz2000> for example, a lady is updating www.canonical.com's landscape section on a staging server
[16:54] <thorwil> i still shudder when thinking of drupal css, after exposure to it because of ardour.org :)
[16:54] <newz2000> she has to upload the full content to staging but there's no way to go from staging to live without rebuilding it all a second time
[16:54] <nand> in fact, you can work with drupal in two ways : 1) by ignoring almost all his features : fast and easy, but harder to maintain or 2) longer to learn, but fast and easy to maintain :)
[16:55] <nand> newz2000: yeah the staging - production is also one of the main issue here
[16:56] <nand> but they got used to it : recording all changes done during dev, and they have two prod server : one act as the prod, the other as the preprod, with a replicated DB
[16:57] <nand> when we want to go live, we isolate preprod, we make the changes we made during dev, and preprod become prod. And prop become preprod.
[16:57] <newz2000> yuck
[16:57] <newz2000> I mean, it is an interesting solution
[16:58] <newz2000> but it assumes you deploy changes to a website like a software company deploys updates to software. All at once.
[16:59] <nand> well, preprod DB is disconnected from prod DB for less than 10mn, time during which we apply dev SQL changes, and then we switch
[17:00] <nand> and this time can be reduced to zero, if no manual sql changes
[17:02] <nand> and of course, all in SVN, so that code upgrade is as simple as a svn up
[17:02] <newz2000> A while back I created a python module that could publish or modify content on a drupal site using the xml-rpc api.
[17:02] <newz2000> I thought it would be nifty to create a django app that published content to a drupal site
[17:03] <newz2000> Use a django based web front end and it would publish to staging for approval and then after sign-off push the same content to live
[17:04] <nand> why not use a module that will by default set new content as not published?
[17:04] <newz2000> that doesn't allow you to make changes to content, it would only affect new pages
[17:04] <nand> ok