| *** mralex has quit IRC | 00:19 | |
| *** JED3 has quit IRC | 00:33 | |
| *** michi_ has joined #cc | 00:37 | |
| *** JED3 has joined #cc | 00:39 | |
| *** JED3 has quit IRC | 00:45 | |
| *** Danny_B has joined #cc | 00:50 | |
| *** JoiIto has joined #cc | 00:50 | |
| *** tvol has joined #cc | 01:22 | |
| *** michi_ has quit IRC | 01:51 | |
| *** Kaetemi has quit IRC | 02:34 | |
| *** JED3 has joined #cc | 02:58 | |
| *** JED3 has quit IRC | 03:06 | |
| *** tvol has quit IRC | 03:17 | |
| *** mralex has joined #cc | 04:18 | |
| *** mralex has quit IRC | 04:19 | |
| *** balleyne has joined #cc | 04:26 | |
| *** balleyne has quit IRC | 05:32 | |
| *** JED3 has joined #cc | 05:43 | |
| *** mralex has joined #cc | 06:00 | |
| *** JED3 has quit IRC | 06:24 | |
| *** mralex1 has joined #cc | 06:41 | |
| *** JoiIto has quit IRC | 06:56 | |
| *** mralex has quit IRC | 07:04 | |
| *** jgay has joined #cc | 07:34 | |
| *** mralex1 has quit IRC | 07:45 | |
| *** Kaetemi has joined #cc | 08:50 | |
| *** Kaetemi__ has joined #cc | 08:52 | |
| *** Kaetemi has quit IRC | 09:10 | |
| *** Kaetemi__ is now known as Kaetemi | 09:12 | |
| *** cc has joined #cc | 11:06 | |
| *** cc has quit IRC | 11:07 | |
| *** JoiIto has joined #cc | 11:41 | |
| *** papyromancer has quit IRC | 11:53 | |
| *** papyromancer has joined #cc | 11:53 | |
| *** michi_ has joined #cc | 12:04 | |
| *** JoiIto has quit IRC | 12:30 | |
| *** michi_ has quit IRC | 12:58 | |
| *** michi_ has joined #cc | 13:34 | |
| *** tvol has joined #cc | 13:47 | |
| *** nkinkade has joined #cc | 14:29 | |
| paroneayea | morning #cc! | 15:21 |
|---|---|---|
| tvol | morning paroneayea, #cc | 15:26 |
| greg-g | morning all around | 16:13 |
| *** michi_ has quit IRC | 16:16 | |
| *** paroneayea has left #cc | 16:17 | |
| *** paroneayea has joined #cc | 16:17 | |
| *** Kaetemi has quit IRC | 16:29 | |
| *** stevel has joined #cc | 16:41 | |
| *** nathany has joined #cc | 16:44 | |
| *** tvol has quit IRC | 16:52 | |
| *** tvol has joined #cc | 16:53 | |
| nathany | nkinkade, someone called saying the captcha on the wiki isn't working | 16:53 |
| nathany | can you poke that? | 16:53 |
| nkinkade | nathany: I'll take a look. | 16:54 |
| nathany | thanks | 16:54 |
| nkinkade | nathany: Did they say where? For registration? For including external links? | 16:54 |
| nathany | they were trying to add a Salon | 16:54 |
| nathany | so presumably for an external link? | 16:54 |
| *** jgay has joined #cc | 16:55 | |
| paroneayea | this is maybe a dumb question, but does anyone know if there is a "nice" way to prevent os.path.abspath(os.path.join('/path/to/static', '../../../var/')) in python? | 16:58 |
| paroneayea | this is for lazy static-serving resources in development mode, so probably shouldn't matter, but I guess I should look into the right way to do it anyway :) | 16:58 |
| greg-g | nathany: they *called*? :) | 16:59 |
| nathany | greg-g, unfortunately | 17:00 |
| nathany | with a baby crying for attention on their other knee | 17:00 |
| paroneayea | one way is os.path.abspath(os.path.join('/path/to/static', '../../../var/'.replace('..', ''))) | 17:00 |
| paroneayea | but that is hacky | 17:00 |
| greg-g | nathany: ugh | 17:00 |
| nathany | paulproteus, iirc, one way is to do your abspathing before you join | 17:01 |
| nathany | er, sorry, that doesn't make much sense; | 17:01 |
| * paulproteus blinks. | 17:01 | |
| nathany | obviously this is my first day back | 17:01 |
| paroneayea | paulproteus: I think that was meant for me :) | 17:02 |
| paulproteus | Morning, nathany (-: | 17:02 |
| paroneayea | pa* | 17:02 |
| nathany | :) | 17:02 |
| *** JED3 has joined #cc | 17:06 | |
| paroneayea | sensible solution served for my static serving development hackiness: | 17:09 |
| paroneayea | <asl2> you could call os.normpath on the result, then check that it starts w/ /path/to/static | 17:10 |
| paroneayea | <asl2> that disallows symlinks out of static, which may or may not be what you want. | 17:10 |
| nkinkade | nathany: The reCaptcha works for me. I just added an edit to /Salon with an external link, the captcha was displayed, I filled it in and the edit was made. | 17:21 |
| nathany | nkinkade, thanks, i'll email her | 17:21 |
| *** akozak has joined #cc | 17:37 | |
| nkinkade | nathany: Do we have any information on the FSF and metadata, as it relates to our wrappers and GPLv3, etc? | 17:42 |
| nkinkade | I have got 2 emails about it in the past couple days. | 17:42 |
| nathany | nkinkade, what sort of information? | 17:43 |
| nathany | they're not doing deeds, they have done RDF, we're not doing 3.0 deeds | 17:43 |
| nkinkade | Back in April you sent an email mentioning that we were working with the FSF to include metadata. | 17:43 |
| nathany | right; they're publishing RDF now | 17:43 |
| nkinkade | That works. Thanks. | 17:43 |
| nathany | sure | 17:43 |
| *** mralex has joined #cc | 17:47 | |
| nkinkade | Ah, I see they are using ccREL as well. | 17:49 |
| paroneayea | nathany: got a second? | 18:22 |
| nathany | paroneayea, sure | 18:22 |
| paroneayea | so I'm trying to understand how cc.engine's static stuff works, what its history is or whatever | 18:23 |
| paroneayea | I see that in the old setup it seems to be pulling things from: | 18:24 |
| paroneayea | engine/skin/resources/ext-2.0/resources/ | 18:24 |
| paroneayea | and etc | 18:24 |
| paroneayea | although there are some things at just the ext-2.0 level | 18:24 |
| nathany | paroneayea, are you referring to things like the CSS, javascript,e tc? | 18:25 |
| paroneayea | what I suspect is that there's some history here that I should be aware of | 18:25 |
| paroneayea | yes, exactly | 18:25 |
| nathany | paroneayea, iirc we used to use ext for our popups and we now just use YUI and pull it from their CDN | 18:25 |
| nathany | i think the things we should care about are the stylesheets, etc, | 18:25 |
| nathany | the only reason we pull them into the cc.engine source code is so we can see them at development time | 18:26 |
| nathany | on staging and production those never get hit for the actual resources -- Apache rewrites them to the versions in the main www directory that it serves and caches | 18:27 |
| paroneayea | ah right, so currently those are pulled in from git submodules right? | 18:27 |
| paroneayea | from the cc wordpress setup or something | 18:27 |
| nathany | paroneayea, yeah, either a submodule or svn:external | 18:27 |
| mralex | svn:external | 18:27 |
| paroneayea | svn:external, right :) | 18:28 |
| nathany | one way i can see this working with the new version is: | 18:28 |
| *** JoiIto has joined #cc | 18:28 | |
| nathany | since this is a wsgi/paster app now, we have two different .ini files -- one for production, one for development | 18:28 |
| nathany | the development version sets up a static serving directory that mirrors the /includes directory on the production deployment | 18:28 |
| nathany | and the URLs in the templates just refer to those paths | 18:29 |
| nathany | the production ini file doesn't bother with that (and probably eventually also grows the caching support) | 18:29 |
| nathany | does that make sense? | 18:29 |
| paroneayea | yes I think so | 18:29 |
| nathany | so it wouldn't be anything in the cc/engine/ source tree specifically | 18:30 |
| paroneayea | does this mean we need to make a ccwordpress git mirror? | 18:30 |
| nathany | hrm, probably | 18:30 |
| nathany | nkinkade, can probably help you with that | 18:30 |
| nkinkade | paroneayea: Do we really need a full ccwordpress git-svn clone? | 18:32 |
| paroneayea | I don't know? :) | 18:32 |
| nkinkade | I didn't read back through the whole conversation. | 18:32 |
| paroneayea | we just need whatever has the static resources (js/images/css) | 18:32 |
| nathany | nkinkade, we'd just like to be able to pull things in using a submodule | 18:32 |
| paroneayea | so if we want to do a shallow clone that is fine | 18:32 |
| nathany | paroneayea, you know, maybe there's a buildout recipe that can help with this | 18:32 |
| nkinkade | I don't think git can do that. | 18:32 |
| nathany | and just do a subversion checkout | 18:32 |
| nathany | of the part we care about | 18:32 |
| nathany | (into a predetermined path) | 18:32 |
| nkinkade | With git it's all or nothing, unlike subversion, at least as far as I know. | 18:33 |
| nathany | paroneayea, http://pypi.python.org/pypi/infrae.subversion | 18:33 |
| nathany | let's just do that -- we don't need full version history | 18:33 |
| nkinkade | nathany: paroneayea: Does this mean that you'll get back to me about the ccwordpress git clone? | 18:33 |
| nathany | nkinkade, this means don't worry about it right now | 18:34 |
| paroneayea | :) | 18:34 |
| nkinkade | That's what I wanted to hear. :-) | 18:34 |
| paroneayea | ok, thx nathany, I'll pull from that. | 18:34 |
| *** Kaetemi has joined #cc | 19:14 | |
| *** michi_ has joined #cc | 19:41 | |
| *** Kaetemi has quit IRC | 20:00 | |
| *** Kaetemi has joined #cc | 20:01 | |
| *** michi_ has quit IRC | 20:12 | |
| *** mlinksva has joined #cc | 21:19 | |
| paroneayea | nathany: all resources cc.engine uses are mounted under: http://creativecommons.org/@@/cc/ | 21:20 |
| paroneayea | is this correct? | 21:20 |
| nathany | paroneayea, mounted by... apache? | 21:23 |
| nathany | zoep? | 21:23 |
| nathany | zope, that is? | 21:23 |
| paroneayea | oh, are those served by zope? | 21:24 |
| paroneayea | the reason I ask is I set up this system to either static-serve itself or | 21:24 |
| paroneayea | you give a url where everything is served from | 21:24 |
| paroneayea | so if the file is c4/css/style.css, and you set the media prefix to http://creativecommons.org/@@/cc/ | 21:25 |
| nathany | paroneayea, they're only served by zope in development mode right now (well, they're actually always served, but that's the only time requests make it there) | 21:25 |
| paroneayea | it'll serve from there | 21:25 |
| nathany | the prefix should be something like /include | 21:25 |
| nathany | look @ /var/www/creativecommons.org/www/include[s?] on a5 | 21:25 |
| nathany | that's the actual checkout of ccwordpress that we serve up | 21:25 |
| paroneayea | okay | 21:25 |
| paroneayea | looking at http://creativecommons.org/licenses/, I see lines like: | 21:26 |
| paroneayea | <script src="http://creativecommons.org/@@/cc/includes/license-results.js" | 21:26 |
| nathany | that's just a zope-ism | 21:26 |
| nathany | we can eliminate it in this version of the code | 21:26 |
| paroneayea | oh | 21:26 |
| nathany | (the "@@/cc" part, in particular) | 21:27 |
| paroneayea | okay, I think I might be a little bit confused | 21:27 |
| paroneayea | if we *want* to point it at the apache-served version | 21:27 |
| nathany | right | 21:27 |
| nathany | (we do) | 21:27 |
| paroneayea | why is the current version of cc.engine that is running serving up a url like http://creativecommons.org/@@/cc/includes/license-results.js, which is apparently run by zope and not apache | 21:27 |
| paroneayea | because that is what the live cc.engine appears to be using | 21:27 |
| nathany | it's doing that for hysterical, er, historical, reasons -- | 21:28 |
| nathany | that *url* is a zope-ism | 21:28 |
| paroneayea | okay :) | 21:28 |
| nathany | varnish/apache is configured to intercept those requests before they hit zope | 21:28 |
| nathany | so they actually are served by apache, with a bit of indirection | 21:29 |
| nathany | by eliminating the @@ url, we can eliminate the indirection as well | 21:29 |
| paroneayea | okay, so main question I meant by all this :) | 21:29 |
| paroneayea | well I guess it is answered | 21:30 |
| nathany | i think the answer is "eliminate '@@/cc' and you're good" ;) | 21:30 |
| paroneayea | what I meant was, should we expect all the apache-served media to be under one directory like: | 21:30 |
| paroneayea | hm | 21:30 |
| nathany | oh | 21:30 |
| paroneayea | so, things will *not* be all under one url | 21:30 |
| paroneayea | er, under one main path | 21:30 |
| nathany | uh, i think they are, aren't they? | 21:31 |
| nathany | aren't they all @@/cc/includes? | 21:31 |
| paroneayea | there are two types: | 21:31 |
| paroneayea | <script src="http://creativecommons.org/@@/cc/includes/license-results.js" | 21:31 |
| paroneayea | <script src="http://creativecommons.org/@@/cc/cc5/site.js" | 21:31 |
| paroneayea | cc[1-5] | 21:31 |
| paroneayea | what's the canonical urls for those? maybe I should look at the actual apache config :) | 21:32 |
| nathany | ah, sigh, those | 21:32 |
| nathany | they're CC theme files for Wordpress :( | 21:32 |
| nathany | they're in ccwordpress in wp-content/themes/cc5, etc | 21:33 |
| nathany | so right, there's not just one top level directory | 21:33 |
| nathany | although... | 21:33 |
| nathany | mralex, what would you think about adding symlinks in includes to cc{3-5} | 21:34 |
| nathany | and using the /includes version in deeds, etc | 21:34 |
| nathany | we'd just need to make sure apache is set up to follow symlinks | 21:34 |
| mralex | sounds fine to me | 21:34 |
| paroneayea | hm, that may make the svn checkout difficult | 21:34 |
| nathany | what may? | 21:34 |
| nathany | adding symlinks? | 21:35 |
| paroneayea | so this buildout thing we just did :) | 21:35 |
| paroneayea | currently we are checking out /includes and etc like: | 21:35 |
| paroneayea | http://code.creativecommons.org/svnroot/ccwordpress/trunk/www/wp-content/themes/cc5 cc5 | 21:35 |
| paroneayea | http://code.creativecommons.org/svnroot/ccwordpress/trunk/www/images images | 21:35 |
| paroneayea | http://code.creativecommons.org/svnroot/ccwordpress/trunk/www/includes includes | 21:35 |
| paroneayea | 21:35 | |
| nathany | yeah, don't do that | 21:35 |
| nathany | er, nevermind | 21:36 |
| nathany | sorry | 21:36 |
| paroneayea | well we won't be able to check out the cc5 into the includes | 21:36 |
| nathany | if we add the symlinks, that just collapses to: | 21:36 |
| nathany | oh, got it | 21:36 |
| nathany | nevermind | 21:36 |
| nathany | any reason we should just checkout the whole thing? | 21:36 |
| paroneayea | I heard you like vcs so I checked out into your checkout | 21:36 |
| paroneayea | hm, well I think I can actually support a kind of hashmap setup | 21:37 |
| paroneayea | where you can load_resource('cc3', 'site.js') | 21:37 |
| nathany | i don't know what that means, but it sounds like more work than we need | 21:37 |
| nathany | (ok, i sort of know what load_resource means) | 21:37 |
| paroneayea | possibly :) | 21:37 |
| nathany | my suggestion: | 21:37 |
| nathany | let's check out ccwordpress in the buildout so we have those files | 21:38 |
| nathany | let's refer to our resources in /includes/ for production; you or mralex can add symlinks to ccwordpress | 21:38 |
| nathany | if we're running in development, let's serve up the appropriate directory in the buildout as /includes/ | 21:38 |
| nathany | (where everything will be served from) | 21:38 |
| nathany | for constructing URLs, that should mean the only part that changes is the root... we could even ignore that for the moment if we wanted to and just construct them as "/includes/cc5/..." | 21:39 |
| nathany | does that make sense? | 21:39 |
| paroneayea | I'm trying to figure out how the symlinks would work | 21:41 |
| paroneayea | since buildout is checking stuff out *into* the resources directory... do we need to extend the buildout script to then add symlinks after svn checkout? | 21:41 |
| paroneayea | that also seems confusing | 21:41 |
| nathany | no | 21:41 |
| paroneayea | ok :) | 21:42 |
| nathany | svn supports symlinks | 21:42 |
| paroneayea | oh | 21:42 |
| nathany | so we just add relative symlinks to the repo | 21:42 |
| paroneayea | oic | 21:42 |
| paroneayea | you are suggesting we check out all of http://code.creativecommons.org/svnroot/ccwordpress/trunk/www/ ? | 21:42 |
| nathany | yes | 21:42 |
| paroneayea | okay, that makes a lot more sense now :) | 21:42 |
| nathany | awesome :) | 21:43 |
| paroneayea | so out of curiosity... you are deferring to mralex | 21:43 |
| *** michi_ has joined #cc | 21:43 | |
| paroneayea | does that mean mralex is lord and master of the ccwordpress kingdom | 21:43 |
| nathany | lol | 21:44 |
| nathany | something like thta | 21:44 |
| nathany | that | 21:44 |
| paroneayea | okay, good to know :) | 21:44 |
| nathany | at the very least he's the one who has to maintain things | 21:44 |
| paroneayea | heh | 21:44 |
| nathany | so i want to keep him happy | 21:44 |
| mralex | ;) | 21:44 |
| mralex | nkinkade: have you upgraded WP to the latest release yet? | 21:46 |
| *** michi_ has quit IRC | 21:51 | |
| nkinkade | mralex: Not yet. I'm got held up because Simple Tags wasn't 2.9 compatible (yet). | 21:56 |
| mralex | ahh | 21:58 |
| mralex | nkinkade: is there any reason we aren't using the built-in tagging functionality? i don't remember why we went with a plugin instead. | 22:02 |
| nkinkade | mralex: I'm not sure. I think Fred had me install those plugins. | 22:05 |
| mralex | i wonder if it's a pain in the arse to convert over to WP tags | 22:06 |
| nkinkade | But if WP has built in tagging support that does what we need them I'm all for ditching Simple Tags ... assuming we can migrate existing tags. | 22:06 |
| nkinkade | Yeah. | 22:06 |
| nkinkade | I guess these are things that I'll be looking into this week. | 22:06 |
| nkinkade | mralex: Is there something in 2.9 that you'd like to use? | 22:07 |
| mralex | nkinkade: it appears to have actual image editing (scaling! rotating!) and better video embedding support. all good things our users would like. | 22:09 |
| *** mlinksva has quit IRC | 22:13 | |
| *** {newbie} has joined #CC | 23:02 | |
| *** {newbie} has left #CC | 23:02 | |
| JED3 | nathany: ping | 23:07 |
| nathany | pong | 23:07 |
| JoiIto | pung | 23:10 |
| nkinkade | nathany: Is the campaign banner on the Deeds inserted with some javascript? Should we disable that soon? | 23:48 |
| nathany | nkinkade, yes, javascript; ask mlinksva/mralex | 23:49 |
| nkinkade | Just sent an email. Thanks. | 23:51 |
| mralex | it is disabled | 23:54 |
| mralex | cached JS perhaps? | 23:54 |
Generated by irclog2html.py 2.6 by Marius Gedminas - find it at mg.pov.lt!