All times shown according to UTC.
| Time | Nick | Message |
|---|---|---|
| 00:21 | uwe_ joined #miro-hackers | |
| 02:39 | janet1 joined #miro-hackers | |
| 03:30 | uwe_mobile joined #miro-hackers | |
| 06:15 | glee joined #miro-hackers | |
| 06:55 | Jarrhead joined #miro-hackers | |
| 08:28 | maggie_s joined #miro-hackers | |
| 08:52 | Dawnrell joined #miro-hackers | |
| 10:41 | janet joined #miro-hackers | |
| 11:04 | Stefan_ joined #miro-hackers | |
| 11:29 | janet left #miro-hackers | |
| 11:43 | Jarrhead joined #miro-hackers | |
| 11:57 | willkg joined #miro-hackers | |
| 12:00 | willkg | hi! |
| 13:51 | janet joined #miro-hackers | |
| 14:08 | ajonas joined #miro-hackers | |
| 14:08 | ajonas | morning all |
| 14:08 | willkg | ajonas: hi! |
| 14:10 | bendk: you on? | |
| 14:19 | paroneayea joined #miro-hackers | |
| 14:25 | jamessan joined #miro-hackers | |
| 14:25 | jamessan joined #miro-hackers | |
| 15:05 | Stefan_ joined #miro-hackers | |
| 15:14 | paroneayea joined #miro-hackers | |
| 15:38 | paroneayea joined #miro-hackers | |
| 15:59 | CarlFK joined #miro-hackers | |
| 15:59 | arpu joined #miro-hackers | |
| 16:15 | paroneayea joined #miro-hackers | |
| 16:25 | arpu joined #miro-hackers | |
| 17:00 | paulproteus | melinath: Hi there. I'd probably rather answer questions here, unless they're about private stuff. |
| 17:05 | melinath | paulproteus: sounds good. I do actually have one that's been knocking around. Why is mc GPL? It's not a usual license for django projects. |
| 17:05 | paulproteus | It's AGPLv3, not GPL. |
| 17:05 | That's a variant of the GPL. | |
| 17:05 | Depends on your perspective as to why it's that way. | |
| 17:06 | Nicholas Reville or paroneayea (who were there at the start) can say for sure. | |
| 17:06 | paroneayea | hiya. |
| 17:06 | paulproteus | I'd guess that it has to do with the fact that if other people use the MC code and make improvements, the AGPLv3 makes sure that pculture.org (and the rest of the community) can get those improvements back into the main codebase. |
| 17:06 | paroneayea | yup, there you go |
| 17:07 | we didn't want someone to proprietize miro community and not give things back. | |
| 17:09 | paulproteus | BTW paroneayea, you may or may not know that melinath is the new MC lead developer. |
| 17:09 | (as I understand things) | |
| 17:10 | And melinath may or may not know that paroneayea is the famous Christopher A. Webber. | |
| 17:10 | paroneayea | hiya melinath! |
| 17:10 | Welcome to the project :) | |
| 17:10 | melinath | paroneayea: Hi, thanks. |
| 17:12 | I was under the impression that e.g. the BSD license would also prevent proprietization | |
| 17:13 | but my legalese is not that great. | |
| 17:13 | paulproteus | Nope. There's this concept called 'copyleft' that is necessary to avoid that (if you want to let (C) law help avoid that), and BSD falls squarely on the "no" side, whereas GPL-type things fall squarely on the "yes" side. |
| 17:14 | It's often possible to avoid proprietarization through non-copyright-law means, like by asking people nicely to please share, but the request is toothless without copyleft. | |
| 17:16 | melinath | I am familiar with copylefting. ;-) I'm just still trying to get a grasp on the specific licenses. |
| 17:16 | http://www.youtube.com/watch?v=vhuF0oalOi8 | |
| 17:19 | paulproteus | (-: |
| 17:25 | melinath | Here's another: What doc format is being used in the docstrings? |
| 17:27 | paulproteus | I don't think there's anything super consistent. |
| 17:27 | The Miro style guidelines are things we should follow (even though MC != Miro; the Miro guidelines are still good ones), but I don't know if they say anything about that, or if MC does. | |
| 17:28 | melinath | are the guidelines on the wiki? |
| 17:30 | Hmm... I don't seem to be able to find them there. | |
| 17:32 | testz0r joined #miro-hackers | |
| 17:34 | paroneayea joined #miro-hackers | |
| 17:44 | paulproteus | http://develop.participatorycu[…]p/CodingStandards |
| 17:44 | Kind of hard to find. | |
| 17:44 | I had to poke around a bit. I got to it from http://develop.participatorycu[…]dex.php/MiroStart from the front page. | |
| 17:47 | melinath | Hmm. Thanks |
| 17:55 | paulproteous: What's the branching policy/convention for mc? It doesn't seem to be included in the Coding Standards. | |
| 17:55 | i.e. for philo, we (try to) use http://nvie.com/posts/a-succes[…]-branching-model/ | |
| 17:56 | (philo being another project I work on.) | |
| 18:03 | bendk joined #miro-hackers | |
| 18:19 | bendk | hey willkg |
| 18:19 | thanks for the feedback on the extensions stuff, I totally agree about using a single argument for load() | |
| 18:19 | I just updated the itemfilter branch with that change, and also one more that adds a hook for context menus | |
| 18:19 | can you take a look when you get the chance? | |
| 18:28 | willkg | bendk: totally can do. |
| 18:31 | ajonas joined #miro-hackers | |
| 18:34 | willkg | as a side note, i feel awful. i went to rest my eyes because my backup glasses are giving me a headache and then woke up two hours later. |
| 18:34 | now i've really got a headache. | |
| 18:34 | plus i feel like someone replaced my brain with molasses. | |
| 18:40 | afk a smidge. | |
| 19:34 | bendk: i'm going to push my gstreamer branch to github. i want to see how all the peer review stuff works. | |
| 19:35 | bendk | sounds good to me |
| 19:35 | do we have a repository on github? | |
| 19:35 | willkg | no. we don't need one, though. i'll just put a fork of miro there in my account. |
| 19:35 | er, we don't need one for my testing. | |
| 19:46 | there. i've set it up: https://github.com/willkg/miro | |
| 20:00 | DGMurdockIII joined #miro-hackers | |
| 20:02 | DGMurdockIII joined #miro-hackers | |
| 20:54 | willkg | bendk: i'm tweaking setup.py so that it's easier to put the miro-binary-kit-win directory in tv/windows/ and have it just work without having to deal with tarballs and stuff. |
| 21:01 | bendk: zanoi's winsparkle stuff was done in his github account clone. we need to move that to a PCF area. | |
| 21:01 | bendk: he should have done it, but i think he's done now. | |
| 21:03 | zanoi | ? |
| 21:04 | willkg | zanoi: you put the winsparkle changes you made in your github account. it should have been put on git.participatoryculture.org like all our other code. |
| 21:05 | zanoi | willkg: I can move it there but it works really badly with the different patches that need to be applied and updated |
| 21:05 | I guess we can have it in both places | |
| 21:06 | willkg | zanoi: what do you mean "it works really badly"? what is "it" in that sentence? |
| 21:06 | zanoi | well there is the official winsparkle, then there is a fork with the downloading patch and a push request to the original. We fork the fork and then apply our own patches |
| 21:07 | but when push request goes through we can directly fork the original | |
| 21:08 | it seems to me that doing this on github is much less chaotic, but i could be wrong | |
| 21:08 | willkg | zanoi: then what you should have done was create a tarball of the patched code and put that in the binary kit. |
| 21:09 | zanoi: i'm looking at what's in the binary kit now and the docs you wrote don't make any sense. VERSIONS say the code is from your github fork. README.backup talks about patches from another fork. but then there's a winsparkle directory with code in it. | |
| 21:09 | what did you check in? | |
| 21:10 | zanoi | well i didn't do the tarball but I added the source directly |
| 21:10 | or did something go wrong? | |
| 21:11 | sorry. no idea how README.backup ended up there | |
| 21:11 | willkg | i have no idea. the VERSIONS file and README docs don't say what's in winsparkle/ . is that the actual code? the patched code? |
| 21:11 | zanoi | it's the code that is compiled to get the WinSparkle.dll |
| 21:11 | willkg | is it the patched code? |
| 21:11 | zanoi | yes |
| 21:11 | and also the code you get if you follow the instructions in the README | |
| 21:11 | willkg | ok. so what you should have done is more atomic and easier to reproduce. |
| 21:12 | if you look at how we did vlc and libtorrent, we have the original source tarball and the patches we apply. | |
| 21:12 | then the README walks through how to build everything. | |
| 21:12 | does that make sense? | |
| 21:12 | zanoi | yes, but to me that seems in no way easier |
| 21:13 | I'll change winsparkle to be that way then | |
| 21:13 | willkg | "easier" in what way? |
| 21:13 | zanoi | easier to reproduce |
| 21:13 | willkg | it's way easier to understand what happened documentation wise. |
| 21:13 | it's easier to reproduce, too, because you have all the original bits: the source tarball, the patches to apply, ... | |
| 21:13 | zanoi | to me it is easier to look at github. It would be quite confusing to have the stuff as separate patches |
| 21:13 | do you want it based on the original or the fork? | |
| 21:14 | willkg | and all of it is easily available in the same repository rather than sending someone on a wild goose chase across the internet to places that may or may not be there tomorrow. |
| 21:14 | which fork are you referring to? there are at least two forks referred to in your docs. | |
| 21:15 | zanoi | well to understand what is happening it is easiest to look at github |
| 21:15 | there is the official winsparkle, then there is a fork with the downloading patch and a push request to the original. We fork the fork and then apply our own patches | |
| 21:16 | willkg | so which fork were you referring to? |
| 21:16 | zanoi | the downloading fork. |
| 21:17 | willkg | mmm... neither fork looks like it's named "downloading fork". so i don't know what that refers to. |
| 21:17 | are you talking about the zanoi fork or the vslavik fork? | |
| 21:18 | zanoi | the one with the commit "use application icon & managed download" by vveloso |
| 21:18 | willkg | which fork is that? |
| 21:19 | zanoi | the that's the fork we base our winsparkle patches on |
| 21:19 | * willkg | sighs. |
| 21:19 | willkg | nevermind. i'll figure this all out and fix it later. it's taking too much energy to understand what you're talking about. |
| 21:19 | afk a bit. | |
| 22:21 | janet joined #miro-hackers | |
| 22:22 | maggie_s joined #miro-hackers | |
| 22:24 | jamessan joined #miro-hackers | |
| 22:24 | jamessan joined #miro-hackers | |
| 23:04 | mattjohnson joined #miro-hackers |