[02:01:20] petan: What was it that you told me to do yesterday? [08:20:21] [02huggle3-qt-lx] 07benapetr pushed 031 commit to 03master [+0/-0/±1] 13http://git.io/x7YlIA [08:20:22] [02huggle3-qt-lx] 07benapetr 038e7f3c2 - you have a message fix [08:55:08] Change on 12en_wikipedia a page Wikipedia:Huggle/Feedback was modified, changed by Banaticus link https://en.wikipedia.org/w/index.php?diff=603987360 edit summary: /* What are the possible other things for a Mac? Who wrote that? */ new section [09:12:08] Change on 12en_wikipedia a page Wikipedia:Huggle/Config was modified, changed by Petrb link https://en.wikipedia.org/w/index.php?diff=603988677 edit summary: /* Prediction */ nonsense [09:24:48] Change on 12en_wikipedia a page Wikipedia:Huggle/Feedback was modified, changed by Petrb link https://en.wikipedia.org/w/index.php?diff=603989598 edit summary: /* What are the possible other things for a Mac? Who wrote that? */ re [09:30:32] [02huggle3-qt-lx] 07benapetr pushed 031 commit to 03master [+0/-0/±7] 13http://git.io/igNwHw [09:30:33] [02huggle3-qt-lx] 07benapetr 03cfc191b - implemented ec now we have detailed information for every user [09:40:07] [02huggle3-qt-lx] 07benapetr pushed 031 commit to 03master [+0/-0/±1] 13http://git.io/3YhrOA [09:40:08] [02huggle3-qt-lx] 07benapetr 03c86d333 - suffixed top edits [11:13:50] [02huggle3-qt-lx] 07benapetr pushed 031 commit to 03master [+0/-0/±1] 13http://git.io/AmyeTQ [11:13:50] [02huggle3-qt-lx] 07benapetr 035478501 - bug decrement instead of increment [11:23:04] someone here got a mac? [11:33:55] [02huggle3-qt-lx] 07benapetr pushed 031 commit to 03master [+0/-0/±1] 13http://git.io/zvfOmA [11:33:56] [02huggle3-qt-lx] 07benapetr 036e6a70b - layout fix [13:12:46] [02huggle3-qt-lx] 07benapetr pushed 032 commits to 03master [+0/-0/±6] 13http://git.io/WUnxfQ [13:12:47] [02huggle3-qt-lx] 07benapetr 0364d7012 - implemented a check if user is blocked or not [13:12:48] [02huggle3-qt-lx] 07benapetr 039d2a534 - Merge branch 'user-block' [15:31:58] [02huggle3-qt-lx] 07benapetr pushed 031 commit to 03master [+0/-0/±6] 13http://git.io/LbsNEg [15:31:59] [02huggle3-qt-lx] 07benapetr 0395d83dd - Improved handling of new pages [17:54:48] [02huggle3-qt-lx] 07benapetr pushed 031 commit to 03master [+0/-0/±3] 13http://git.io/HR8Tyg [17:54:49] [02huggle3-qt-lx] 07benapetr 030e52502 - generic code optimizations [17:56:21] [02huggle3-qt-lx] 07benapetr pushed 031 commit to 03master [+0/-0/±1] 13http://git.io/MF3bLQ [17:56:22] [02huggle3-qt-lx] 07benapetr 03d578382 - typo [18:01:46] [travis-ci] huggle/huggle3-qt-lx#666 (master - 0e52502 : Petr Bena): The build has errored. [18:01:46] [travis-ci] Change view : https://github.com/huggle/huggle3-qt-lx/compare/95d83dd3df83...0e5250205f0a [18:01:46] [travis-ci] Build details : http://travis-ci.org/huggle/huggle3-qt-lx/builds/22895910 [18:38:39] [02huggle3-qt-lx] 07benapetr pushed 031 commit to 03master [+0/-0/±6] 13http://git.io/a2KK5w [18:38:39] [02huggle3-qt-lx] 07benapetr 03fbb9a5c - performance tweaks [18:45:46] [travis-ci] huggle/huggle3-qt-lx#668 (master - fbb9a5c : Petr Bena): The build has errored. [18:45:46] [travis-ci] Change view : https://github.com/huggle/huggle3-qt-lx/compare/d578382b3df9...fbb9a5c73c4a [18:45:46] [travis-ci] Build details : http://travis-ci.org/huggle/huggle3-qt-lx/builds/22897877 [18:45:59] [02huggle3-qt-lx] 07benapetr pushed 031 commit to 03master [+0/-0/±1] 13http://git.io/5A1Csg [18:46:00] [02huggle3-qt-lx] 07benapetr 0312f94fc - fixed CI and inserted 1 more test [18:50:10] addshore: is it better to use master for devel and have branch stable or use master for stable and have branch dev? :D [18:50:20] I am wondering how we maintain code after release [18:50:42] now master is good for anything, even untested code, but later we might want to keep untested code somewhere else [19:00:03] [travis-ci] huggle/huggle3-qt-lx#669 (master - 12f94fc : Petr Bena): The build failed. [19:00:03] [travis-ci] Change view : https://github.com/huggle/huggle3-qt-lx/compare/fbb9a5c73c4a...12f94fcc392a [19:00:03] [travis-ci] Build details : http://travis-ci.org/huggle/huggle3-qt-lx/builds/22898317 [19:04:33] [02huggle3-qt-lx] 07benapetr pushed 031 commit to 03master [+0/-0/±1] 13http://git.io/2LsEPw [19:04:34] [02huggle3-qt-lx] 07benapetr 03cca19c3 - rewrote ipv6 regex [19:06:41] petan, doesn't mediawiki core have a regex for ipv6? [19:06:50] Krenair: IDK [19:07:01] I think it uses some php function IMHO [19:08:09] petan, see includes/utils/IP.php [19:08:42] if it's better than this regex I will upload it to SO because there they think this one is best POSIX existing [19:09:04] I don't have core checked out [19:09:08] it's too huge git repo [19:09:18] I can't clone 8gb repository with my net [19:09:58] https://github.com/wikimedia/mediawiki-core/blob/master/includes/utils/IP.php [19:10:05] :o [19:10:44] You want the RE_IPV6_WORD and RE_IPV6_ADD constants and the isIPv6 function [19:10:48] php doesn't have namespaces? [19:10:57] MediaWiki core doesn't use them. [19:11:08] imho classes that just contain static public functions are a bit weird [19:11:11] Some extensions do [19:11:28] PHP has had namespaces since 5.3 [19:12:23] which was released 2009-06-30 [19:16:43] that is some "cute source" but if you merge all these defines to 1 regex, you will see it's even more long and complex [19:17:27] tbh regex is maybe not best performing solution for this, but I am lazy to write own function for this :P [19:18:43] hi petan [19:18:51] hey :D [19:19:01] petan: use master foe devel and make branch for stable [19:19:07] ok [19:19:14] but really master should be reasonably stable [19:19:17] I will do once we release first stable [19:19:34] yss, so make a branch for the first release, then you can always drop fix patches on to it [19:20:26] * addshore wonders if there is a free build service for open source projects [19:20:28] if you really want master to be stable we would need to create every change in separate branch, then have a merge request and have other devs review the change before merge [19:20:33] that isn't gonna work here [19:20:51] we have only 1 dev who is looking at code at least once a day and that is me :P [19:20:56] :P [19:21:00] indeed, thats fine, :P [19:21:05] itll get better with time im sure ;p [19:21:08] so if I had to wait for others to review and approve the code it wouldn't really work [19:21:12] as long as it compiles right? ;p [19:21:21] that we have travis for XD [19:21:37] we didn't have unit for ipv6 [19:21:49] I figured today that all time the regex we had was broken [19:21:56] so ipv6 never worked XD [19:22:17] :> [19:23:47] btw what you think about new fonts? I thought my browser is fucked up XD [19:23:59] then I saw that huge complaint thread on wikitech-l [19:24:06] people always complain about every change lol [19:24:31] maybe we should update css in huggle to new fonts? [19:24:47] that is some "cute source" but if you merge all these defines to 1 regex, you will see it's even more long and complex [19:24:54] they're all split up for this exact reason [19:25:05] yes I like the split up [19:25:13] but I doubt that regex is gonna perform better [19:25:40] petan: migyht look at setting up automated nigyhtly builds on cloudbees [19:25:58] linux nightly build is super easy we can do that on wmflabs [19:26:03] but regarding windows and mac :/ [19:26:16] there is mingw32 for linux [19:26:17] petan: on cloudbees we can do osx, windows and nix [19:26:36] mhm [19:26:48] currently we have no way to generate osx packages [19:26:55] I don't even know how it works I have no mac [19:27:01] xD [19:27:11] I just heard there are some .dmg files [19:27:27] anyway, this automation is something I can look at after the first release I guess [19:28:18] I prepared some scripts for ubuntu packaging so making packages is not so hard as it used to be, but still it requires some skills :D [19:28:37] like knowing what gpg is and how it works :P [19:34:14] :P [19:34:36] are they in the huggle 3 repo? [19:35:06] ubuntu branch [19:35:17] gpg keys of course not :D [19:35:34] they are in my PC only, but I can add you in huggle-devs on launchpad so that you can register your private key [19:36:16] but for that you need to have ubuntu it's not possible to upload packages even from other linux distro than ubuntu, definitely not different system [19:37:01] [02huggle3-qt-lx] 07addshore pushed 031 commit to 03master [+0/-0/±1] 13http://git.io/QQ918A [19:37:02] [02huggle3-qt-lx] 07addshore 03d2868a6 - Add License section to README [19:37:28] btw we have quite a mess in licenses [19:37:36] I still don't know which license I would prefer [19:37:51] GNU GPL3 seems to restrictive to me, I recently started using LGPL for everything [19:38:00] Ryan told me I should use BSD license though [19:38:30] hg3 core is GPLv3 but that ./configure script is BSD XD [19:44:51] How is GPL3 restrictive? [19:46:54] it requires derived work, even if it just links against the software that uses GPLv3 to be licensed under this as well [19:47:30] that kind of forces anyone who works with your code to make their code open source under GPL as well [19:47:43] which may not be always good thing [19:48:26] for example, if I wanted to reuse some of code I myself wrote in my own personal commercial project with closed source I would have problem [19:48:39] maybe [19:48:43] idk I am not a lawyer [19:55:42] petan, the dropdown button for revert or revert+warn doesn't bring up a dropdown [19:56:00] it does [19:56:04] you need to hold it [19:56:15] blame Qt XD [19:56:20] I hate it too [20:08:08] sigh [20:11:46] sign x2 [21:22:00] [02huggle3-qt-lx] 07benapetr pushed 0317 commits to 03ubuntu [+0/-0/±62] 13http://git.io/0Qho7w [21:22:01] [02huggle3-qt-lx] 07benapetr 03adc8418 - Merge branch 'master' into ubuntu Conflicts: README.md [21:22:48] [02huggle3-qt-lx] 07benapetr pushed 032 commits to 03ubuntu [+0/-0/±1] 13http://git.io/fDUmsQ [21:22:49] [02huggle3-qt-lx] 07benapetr 03a31834a - Merge branch 'master' into ubuntu Conflicts: README.md [21:23:32] [02huggle3-qt-lx] 07benapetr pushed 031 commit to 03ubuntu [+0/-0/±1] 13http://git.io/47R5wg [21:23:33] [02huggle3-qt-lx] 07benapetr 037bd8163 - let's release this fixed ipv6 for testing