| sakrecoer | nice eylul !! :) | 19:03 |
|---|---|---|
| eylul | krytarik | 19:57 |
| eylul | sakrecoer | 19:57 |
| eylul | you have been formally tagged. | 19:57 |
| krytarik | :D | 19:57 |
| sakrecoer | pong | 19:57 |
| eylul | heh | 19:57 |
| sakrecoer | topic: website i suppose | 19:58 |
| eylul | ok so, just to clarify for everyone, this is not a formal meeting or anything but since we are all here.. might as well discuss this on the devel. and yes | 19:58 |
| eylul | ok so.. the situation is that sakrecoer poked in october we have not received an answer. right? | 19:58 |
| sakrecoer | correct | 19:58 |
| sakrecoer | tbh, i have a fair bit confusion about what is wrong and with what... | 19:59 |
| eylul | ok so the main problem is this | 19:59 |
| sakrecoer | as far as i understand, the community theme is standard way of doing things with WP, but IS are not doing it the standard way... | 20:00 |
| eylul | wordpress's theme system has cascading styles. | 20:00 |
| eylul | so when you modify a theme, the common way to do so, is to create a child theme, that only includes parts that varies from the parent | 20:00 |
| eylul | this way the changes are modular, and you don't have any updates to parent theme erasing your work, | 20:01 |
| eylul | or being forced to stick to an old version of the theme you use, until you manually port the updates. | 20:01 |
| eylul | that is what we did to community theme | 20:01 |
| eylul | we added a bit of css and one new page type | 20:01 |
| eylul | by creating a child theme | 20:01 |
| eylul | this works in our stage. | 20:02 |
| eylul | but apparently ubuntu's wordpress install does something weird with the theme paths in the webserver | 20:02 |
| eylul | normally each theme sits at wp-themes/<theme name> | 20:02 |
| eylul | but in this case the themes sit at wp-themes/<theme name>/<theme name> | 20:03 |
| eylul | this causes the link from our child theme referring to our parent theme (community theme) to break | 20:03 |
| eylul | so we have several options: | 20:03 |
| eylul | 1) try to convince ubuntu IS to change to fix this to a normal wordpress setting. Pros: permanent solution that is best practice. Cons: it might not be possible since this is not our decision to make | 20:04 |
| eylul | (or at least take a long time to escalate our ticket to this) | 20:05 |
| * sakrecoer is quitely reading | 20:06 | |
| eylul | 2) we change the parent theme information in a way that it reflects the directory tree correctly Pro: keeps our child theme still separate, instant solution. Cons: pretty bad hack (the parent theme names aren't supposed to contain a path, just a name.), this will break if the directory structure changes on ubuntu side back to normal. | 20:06 |
| sakrecoer | ok.. thank you! | 20:07 |
| sakrecoer | what do you guys think is the best option? krytarik eylul ? | 20:07 |
| eylul | 3) we put all of the changes onto the community parent theme (so think we fork the community theme, rather than creating a child that appends it) Pros: will work whatever happens, again we can solve this on our end. Cons: not best practice, hard to split our changes out later in future, we don't get to benefit from updates to community theme | 20:07 |
| eylul | /done | 20:07 |
| sakrecoer | oh... | 20:07 |
| sakrecoer | sorry | 20:07 |
| eylul | (np) | 20:07 |
| eylul | my suggestion is to do either 2 or 3. (I did initially advocate for 3, but I concede to krytarik's point from our discussion yesterday that this is pretty bad down the line) | 20:08 |
| eylul | overall through I am ok to go with whatever you decide | 20:09 |
| eylul | (krytarik?) | 20:09 |
| krytarik | Well, I still want to push a little bit for the most proper solution at least (1.) - then if it becomes clear one way or another that it's not gonna happen, go with 2. | 20:10 |
| eylul | *nods* | 20:11 |
| * eylul just realizes she might have another idea. - krytarik do you have the link to knome's theme repo at hand? (the one they pull from?) | 20:12 | |
| sakrecoer | ok, i feel like 1) sounds the most proper! | 20:13 |
| krytarik | eylul: Not the upstream one, but the one they'd be pulling from: https://code.launchpad.net/~knome/ubuntu-community-wordpress-theme/trunk | 20:14 |
| sakrecoer | can we try to set a deadline for trying that push? | 20:14 |
| sakrecoer | like at some point, if nothing happens from IS side, we are going to need to go with another option | 20:14 |
| * eylul agrees with sakrecoer | 20:15 | |
| eylul | I think we MIGHT have a 4th option btw | 20:15 |
| eylul | sorry I just literally realized this | 20:15 |
| eylul | http://bazaar.launchpad.net/~knome/ubuntu-community-wordpress-theme/trunk/files | 20:16 |
| eylul | check the filestructure here | 20:16 |
| eylul | I think what is happening might be that, they are simply creating a folder for each theme and pulling it in, not realizing, the directory they pull has the folder in it | 20:16 |
| krytarik | Well, they *asked* him to do it that way.. | 20:16 |
| eylul | .... | 20:17 |
| eylul | ugh | 20:17 |
| eylul | oh well | 20:17 |
| eylul | nvm then | 20:17 |
| eylul | (I assume you knew what I was going to suggest) | 20:17 |
| eylul | ok so.. | 20:18 |
| eylul | back to 3 options. | 20:18 |
| sakrecoer | ok, so how do we go about 1) | 20:18 |
| sakrecoer | do you want to try stepping in the thread krytarik ? | 20:18 |
| krytarik | Not really. :P | 20:19 |
| eylul | oh-kay | 20:20 |
| sakrecoer | ok... the thing is, while eylul did a great job explaining the problem, my understanding is very superfecial. | 20:20 |
| sakrecoer | hehe | 20:21 |
| sakrecoer | *superficial | 20:21 |
| krytarik | And btw, they'd have to respond sometime either way.. :P | 20:24 |
| eylul | it doesn't hurt somebody who understands wordpress better being the lead on this through | 20:24 |
| sakrecoer | ok, so i will just write and see if i can get a response, maybe i may add you to CC? | 20:24 |
| eylul | rather than the telephone situation happening via sakrecoer. :) | 20:24 |
| sakrecoer | eylul is right | 20:24 |
| eylul | (not that sakrecoer has been awesome about it) | 20:24 |
| sakrecoer | but i could just poke this time. like "hello wassap?" | 20:25 |
| eylul | and while sakrecoer and I suppose I can take the initiative on this, it would be really great (if you have the time/energy to do so), as the person who has put most of the work on the theme | 20:25 |
| eylul | but no pressure. | 20:26 |
| eylul | *gives krytarik a few moments to think* | 20:27 |
| krytarik | Well, I'd really like to avoid being 'another person that isn't the project lead' there. | 20:27 |
| eylul | oh-kay. putting on my (relatively) newbie hat here | 20:28 |
| sakrecoer | but, you sort of are the website lead krytarik :) | 20:28 |
| * eylul agrees with sakrecoer | 20:28 | |
| eylul | krytarik would it help if you were the designated website lead? | 20:29 |
| krytarik | How about sakrecoer just follows up on his last post there, and links back to knome's? It's that easy. | 20:30 |
| sakrecoer | link back to knome's? | 20:31 |
| sakrecoer | knome's what? | 20:31 |
| krytarik | Post - they've been outright ignoring that one. | 20:31 |
| sakrecoer | ok i get it. | 20:31 |
| sakrecoer | i can do that? | 20:31 |
| sakrecoer | i mean | 20:31 |
| sakrecoer | i can do that *! | 20:32 |
| krytarik | :D | 20:32 |
| krytarik | Also, could link the logs of this discussion, if it helps. | 20:33 |
| sakrecoer | you mean, this diskussion? | 20:34 |
| sakrecoer | like, here in IRC now | 20:34 |
| krytarik | Yep. | 20:34 |
| krytarik | The options are all listed up there. | 20:34 |
| eylul | (it might be easier to copy paste it from the logs, rather than have them dig through trying to figure out what part we refer to. support people deal with a lot of tickets) | 20:35 |
| krytarik | eylul: Thanks for putting that together so nicely, btw! | 20:37 |
| eylul | no problem at all :) | 20:37 |
| sakrecoer | ok. so i will do that :) | 20:37 |
| eylul | \o/ | 20:39 |
| eylul | alright so.. shall we touch base on this next week? | 20:40 |
| sakrecoer | ok! | 20:40 |
| sakrecoer | i'm up for that! | 20:40 |
| eylul | this works for me. krytarik? | 20:41 |
| krytarik | Well, I think I'll be around then anyway.. :P | 20:41 |
| eylul | heh ok | 20:41 |
| eylul | alright then | 20:41 |
| eylul | off with the website issue | 20:41 |
| eylul | sakrecoer, before I forget. I know you have been traveling, so not sure if you saw, but chimois had a new version of the boot image | 20:42 |
| eylul | maybe one of us could also work with him, regularly, every 2 weeks or so, to touch base? | 20:42 |
| sakrecoer | eylul: no i missed that... | 20:42 |
| eylul | let me see if I can find the link. one sec | 20:42 |
| eylul | *chamois | 20:43 |
| eylul | I keep mistyping | 20:43 |
| krytarik | \o/ | 20:44 |
| sakrecoer | \o/ | 20:44 |
| sakrecoer | cool guys! | 20:44 |
| sakrecoer | and gals! | 20:44 |
| sakrecoer | and robots! | 20:44 |
| sakrecoer | i have to log off! thanks eylul and krytarik ! :) | 20:45 |
| sakrecoer | read you soon! | 20:45 |
| eylul | (12:41:14 AM) chamois: Hello everyone! http://pasteall.org/pic/index.php?id=108733 | 20:45 |
| eylul | there | 20:45 |
| eylul | and bye sakrecoer | 20:45 |
| sakrecoer | thanks! | 20:46 |
| eylul | np. alright guys see you next week, if not before | 20:46 |
| sakrecoer | bye! \o | 20:47 |
| eylul | bye. | 20:47 |
| OvenWerks | Hmm, well that time certainly didn't work for me... won't ever for that matter. | 22:52 |
| OvenWerks | Not that I have been able to contribute much anyway. | 22:54 |
| eylul | OvenWerks: is there a time range that works better for you? | 23:24 |
| eylul | (and again this was more of an impromptu thing mostly to figure out what to do about the website issue, but all the same. :)) | 23:25 |
| OvenWerks | I would say just about anything... Sunday mornings I am always out till about 2pm here (-700... or is it -800 now?) | 23:26 |
| eylul | Alright. (Sakrecoer, Krytarik, see above) | 23:27 |
| OvenWerks | I have weekdays from utc 1200ish till 14 ish I am getting kids out to school (7am till 830 here) | 23:28 |
| eylul | I'd say UTC early evenings have the most chance to work overall when we want to get most people together. anything earlier people are generally sleeping in USA side (or have work) | 23:29 |
| eylul | (family stuff etc) | 23:29 |
| OvenWerks | I'm retired, so my "busy" times are when someone else in the family needs me :) | 23:30 |
| eylul | :D | 23:30 |
| eylul | that's fair | 23:30 |
| OvenWerks | I do sleep | 23:30 |
| eylul | I think we all do | 23:31 |
| OvenWerks | but generally get up around 6am | 23:31 |
| eylul | ok so anytime that is not sunday mornings and not early afternoon european time. | 23:31 |
| OvenWerks | Robin from Ardour seems to never sleep | 23:31 |
| eylul | hahah | 23:31 |
| OvenWerks | I often see him around at 3am his time | 23:32 |
| eylul | I am fairly certain 6am your time might be too early for krytarik. I rarely see him around before evenings (EU ones) | 23:32 |
| eylul | :D they might simply be a nightowl | 23:32 |
| eylul | I am usually up and about at 3am my time ;) | 23:32 |
| OvenWerks | By about 10pm I stop making too much sense anyway... | 23:33 |
| eylul | :D | 23:33 |
| OvenWerks | I was thinking my wake up time could relax a bit when I retired, but my wife gets up at 530... | 23:34 |
| eylul | :) | 23:34 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!