All times shown according to UTC.
| Time | Nick | Message |
|---|---|---|
| 00:19 | uwe_mobile joined #miro-hackers | |
| 00:23 | uwe_ joined #miro-hackers | |
| 00:47 | maggie_s joined #miro-hackers | |
| 01:09 | ajonas joined #miro-hackers | |
| 02:40 | janet1 joined #miro-hackers | |
| 03:45 | maggie_s_ joined #miro-hackers | |
| 04:04 | maggie_s_ joined #miro-hackers | |
| 07:29 | Jarrhead joined #miro-hackers | |
| 07:43 | janet joined #miro-hackers | |
| 07:46 | janet joined #miro-hackers | |
| 07:46 | janet joined #miro-hackers | |
| 07:47 | janet1 joined #miro-hackers | |
| 07:53 | janet joined #miro-hackers | |
| 08:46 | glee joined #miro-hackers | |
| 09:27 | arpu joined #miro-hackers | |
| 09:35 | maggie_s joined #miro-hackers | |
| 11:46 | Jarrhead joined #miro-hackers | |
| 11:46 | willkg joined #miro-hackers | |
| 11:50 | willkg | hi! |
| 11:51 | zanoi | willkg: i just noticed you grabbed the winsparkle binary kit bug, but I'm fixing it right now. do you mind if i take it? |
| 11:57 | willkg | zanoi: nope. the way we left it yesterday suggested you were done and i was going to do the work. but if you want to do it, that's fine with me. |
| 11:57 | zanoi: do you understand what needs to be done? | |
| 11:58 | zanoi | yes, you want a tarball and patches instead of full source |
| 11:59 | willkg | and a README that covers how to build it. |
| 11:59 | zanoi | and more focus on how to build that instead of how to reproduce it from repositories |
| 11:59 | willkg | and it probably should have a COPYING, too, so we know under what permissions we're distributin git. |
| 12:00 | zanoi | i had considered doing it this way but ended up deciding that it would be unnecessarily confusing |
| 12:00 | ok, sure, i'll copy the winsparkle COPYING up one directory | |
| 12:02 | do you want me to copy the WinSparkle build instructions up one level as well? | |
| 12:02 | instead of writing that one should follow the WinSparkle README | |
| 12:03 | willkg | if it walks through how to apply the patches and in what order, then that's fine. |
| 12:04 | zanoi | well they are numbered, but I can add explicit commands |
| 12:04 | willkg | like i said before, you should mimic what we do with libtorrent and vlc. |
| 12:04 | so, here's what it needs to do. someone should read the README and know exactly how to reproduce the binaries that you built. | |
| 12:05 | does that make sense? | |
| 12:06 | take a look at the README in the libtorrent directory. mimic that. | |
| 12:06 | zanoi | yeah i know that README |
| 12:07 | willkg | cool. mimic that and ping me if you have questions. |
| 14:12 | ajonas joined #miro-hackers | |
| 14:15 | arpu joined #miro-hackers | |
| 15:05 | bendk joined #miro-hackers | |
| 15:26 | glee joined #miro-hackers | |
| 15:52 | CarlFK joined #miro-hackers | |
| 16:12 | arpu joined #miro-hackers | |
| 16:16 | melinath | ajonas: Are there already plans in the works to make mc work with django 1.3? Or explicit plans not to? |
| 16:17 | ajonas: On a related note, is there a backwards-compatibility policy? | |
| 16:18 | ajonas | melinath: i don't think we'd planned yet, though i do think it came up once. backwards-compatibility for people who have built custom themes? |
| 16:18 | melinath | Or in general. |
| 16:19 | ajonas | melinath: looks like it was discussed by paulproteus here - http://bugzilla.pculture.org/s[…]_bug.cgi?id=16177 |
| 16:19 | *refreshes memory* | |
| 16:19 | melinath: is it out of beta now? | |
| 16:21 | melinath | ajonas: Very much so, yes. |
| 16:22 | ajonas | melinath: we update non-custom themes automatically, so for those as long as the features still work, i don't think it should be an issue, but maybe you can tell me more about what some of the concerns would look like? for updating to 1.3 in specific - sounds like it makes sense, if you and z3p are both on board i'm cool with it |
| 16:22 | melinath | ajonas: do you happen to know how many people are using django 1.1/1.2? |
| 16:22 | paulproteus | melinath: You mean, on deployed MC instances? |
| 16:22 | I would say 1-10. | |
| 16:22 | Feel free to force an upgrade to Django 1.3, I would say. | |
| 16:22 | * paulproteus | vanishes for lunch |
| 16:23 | melinath | paulproteus: ooh, yay. |
| 16:25 | ajonas | melinath: just so i understand - would that likely be for people who made custom themes before we switched to a more recent version? |
| 16:25 | melinath | ajonas: updating to 1.3 would probably not affect people's custom themes, unless they are relying on an obscure behavior of callables in templates. |
| 16:26 | ajonas | melinath: awesome |
| 16:26 | melinath | ajonas: sorry, was just going over the release notes to make sure that I didn't miss anything. |
| 16:26 | ajonas | melinath: no problem at all! |
| 16:27 | melinath: are there any ays that you see an upgrade being likely to negatively impact users? | |
| 16:28 | melinath | ajonas: There could be some problems with csrf protection if the themes allow people to override the actual forms on pages, but they probably shouldn't be able to do that anyway. |
| 16:29 | ajonas | melinath: cool, sounds like a reasonable risk to take |
| 16:29 | melinath | ajonas: 1.3 is more secure and generally cleaner. I do think we should be slightly cautious just in case. |
| 16:29 | but that goes for any change. | |
| 16:29 | ajonas | melinath: *nod* |
| 16:29 | melinath: is this something we'll be able to test out on the dev sites first? | |
| 16:30 | melinath | The biggest concern is that people would need to upgrade to 1.3, but if there are only a few people using custom installations then that isn't a problem |
| 16:30 | I guess I should say, it's probably something we can afford to force them to do. | |
| 16:31 | yes, we should be able to test it on the dev sites first | |
| 16:31 | I haven't looked at the exact server setup, but if they're running a different version of miro than other sites, they can also run a different version of django. | |
| 16:33 | ajonas | melinath: *nod* |
| 16:34 | melinath | I probably won't do this immediately |
| 16:34 | *I won't | |
| 16:35 | but soonish, perhaps. We'll see how things go. | |
| 16:35 | I guess I should open a ticket | |
| 16:35 | ajonas | melinath: that sounds like a good plan |
| 16:39 | melinath | General question: Why is miro community called localtv instead of, say, mirocommunity? |
| 16:41 | ajonas | melinath: it changed names early on, to express the wider options for use |
| 16:41 | melinath | ajonas: So it used to be called mirocommunity? |
| 16:41 | ajonas | melinath: it used to be localtv |
| 16:41 | melinath: and is now miro community | |
| 16:41 | melinath: which is still confusing for a lot of people :( | |
| 16:42 | melinath | ajonas: ahh... that makes sense. Confusing how? |
| 16:42 | ajonas | melinath: we've discussed the possibility of changing again to decrease confusion with miro desktop |
| 16:42 | melinath: but changing names is always hard, so thus far we've stuck with it | |
| 16:43 | melinath: a lot of people just say "miro" when they mean miro community, or "miro site," or contact miro community people about miro (desktop) stuff | |
| 16:43 | willkg | people keep telling me i work for miro, too. |
| 16:43 | i'm going to miss working for miro. | |
| 16:44 | melinath | ajonas: If we're sticking with miro community, another change that we could consider would be renaming the python package to miro community. That would be a much more invasive change than upgrading to django 1.3 |
| 16:44 | ajonas: but if we did it right, it again wouldn't affect end users. | |
| 16:44 | willkg: where are you going? | |
| 16:45 | willkg | my last day is september 2nd. i took a job at mozilla. |
| 16:45 | ajonas | melinath: i'm definitely open to it - we do have a (sadly little used, currently) miro-developers listserv that it might make sense to contact to feel out how folks would feel about these changes |
| 16:45 | willkg: so soon! | |
| 16:46 | willkg | ajonas: yeah... but i'll be hanging out here. |
| 16:46 | melinath | ajonas: kk. Do we want to try to drum up more developers? |
| 16:47 | ajonas | melinath: it would certainly be great to have folks contributing if we can commit to having the capacity to manage and support them. i know it's something paulproteus worked on some - the challenge is just finding the time to do it right |
| 16:49 | melinath | ajonas: such as right after a release? Or the time in terms of hours of work? |
| 16:49 | ajonas | melinath: the latter |
| 16:57 | melinath | ajonas: Right now it also would not be particularly easy to contribute. |
| 16:57 | ajonas | melinath: *nod* |
| 16:57 | melinath | ajonas: If we want to make some sort of announcement about "come contribute" we would want to make it easier |
| 16:58 | ajonas | melinath: let's see if we can figure out some ways to make the process better in the coming months |
| 16:58 | melinath | ajonas: Also, it should be after renaming the package and upgrading to django 1.3 |
| 16:58 | ajonas | melinath: totally |
| 16:58 | melinath | ajonas: sounds good. |
| 17:22 | ajonas: I'm going to update the tests; should I just assume that whatever is happening now is what's supposed to happen? | |
| 17:22 | ajonas | melinath: hmm, i don't know - i think it's likely that there are things wrong |
| 17:22 | melinath | ajonas: for the failures, that is |
| 17:22 | ajonas: kk. | |
| 17:23 | ajonas | melinath: http://bugzilla.pculture.org/s[…]_bug.cgi?id=17561 |
| 17:23 | melinath: so i think it's worth looking at them a little more deeply, i just don't trust that we have everything right and the tests are wrong | |
| 17:25 | melinath | ajonas: will do. |
| 17:25 | Do I need to fill out a contributor form? | |
| 17:25 | I'd imagine yes? | |
| 17:46 | willkg | hrm... i can't seem to get the downloader to not crash. |
| 17:46 | something about a typeerror in the environment. | |
| 17:49 | glee: i just saw your unicodedecodeerror fix. that's something i pointed out in the peer review a while back, right? | |
| 17:50 | glee | willkg: Yes, it was |
| 17:50 | willkg | that stuff is such a pain in the ass. |
| 17:51 | glee | willkg: Yeah, I've been dealing with locale issues for 10+ years and it's gotten a bit better with people having switched to using unicode mostly, but things are still not completely right. Disappointing. |
| 17:51 | willkg | totally. |
| 17:51 | but, i think this is more a problem with our code. the whole str/unicode pathname problem is such a pain in the ass. | |
| 17:52 | there was a point in time where i was cleaning up unicodedecodeerrors in logging statements which is stupid because it's a _logging_ statement causing miro crashes. | |
| 17:52 | anyhow, we had dozens of them. so irritating. | |
| 17:52 | argh. i can't use miro in master because i've got a different build environment. how frustrating. | |
| 18:35 | janet1 joined #miro-hackers | |
| 18:36 | janet joined #miro-hackers | |
| 19:38 | arpu joined #miro-hackers | |
| 21:26 | willkg | dev call notes posted: http://bluesock.org/~willg/blo[…]all_20110817.html |
| 21:39 | DGMurdockIII joined #miro-hackers | |
| 22:20 | maggie_s joined #miro-hackers |