Subject: KampalaMeetingLog-2017-11-02.txt Date: November 2, 2017 at 4:24:23 PM PDT [15:36:08] hi HideyoImazu-san, sorry for delay! [15:36:19] HaraldJoerg (~haj@ip5f5bea14.dynamic.kabel-deutschland.de) joined the channel [15:36:41] still trying to get online on slack [15:36:43] Hi Peter [15:37:04] Back again. I managed to power off my equipment :) [15:37:06] hi HaraldJoerg, sorry for delay!! [15:37:42] it's less late than usual for you HaraldJoerg [15:37:45] just this week [15:38:14] Yes, and it's the first time I don't miss the meeting because of that [15:38:17] i can't understand why europe and usa does not coordinate the summer savings time change-over [15:38:30] just this week [15:38:46] usa will change this coming weekend [15:39:28] question: what is better to use? slack, or irc? [15:39:49] Wow, Firefox managed to re-open all my windows and tabs, and Emacs had my file changes ready for recovery... so the power fault apparently had no consequences at all... [15:39:51] I prefer slack [15:40:01] I don't care, slack is fine, too [15:40:07] cool HaraldJoerg [15:40:25] i find slack a bit heavy [15:40:33] it takes forever to start [15:40:43] meaning CPU consuming? [15:40:47] or slow? [15:41:21] it takes maybe two minutes to start up when i am on hotspot [15:41:32] ah [15:41:36] it seems to download tons of stuff before i see the channels [15:41:56] but bigger disadvantage is the copy/paste format for logs [15:42:05] it needs to synchronize all the channels [15:42:26] i need to edit the file before i can save as attachment, the format is useless [15:42:52] so from that i would prefer irc [15:42:55] that's true but isn't it a matter of having one regex replace? [15:42:59] but i can live with slack [15:43:25] yea, i could use regex [15:44:14] I wonder if you can send commit notification to slack [15:44:15] irc format is better (with the textual client i use), each line has timestamp, person, and text [15:44:49] btw, recently i started to use telegram [15:45:09] great chat platform, lean clients for mac and mobile [15:45:17] telegram is popular in Germany, I hear [15:45:22] or German speaking people? [15:45:43] Never heard of it, though [15:45:43] startups in usa start to use it because of encryption [15:46:16] WhatsApp encrypts end-to-end, right? [15:46:28] yes [15:47:02] shall we start with meeting? make it short? [15:47:21] sure [15:47:32] http://twiki.org/cgi-bin/view/Codev/KampalaReleaseMeeting2017x11x02 [15:47:34] short or long, I'm fine [15:47:45] 1. Feature Requests for Kampala Release [15:47:45] 2. Extensions [15:47:45] 3. Review Urgent and Not So Urgent Bugs [15:47:45] 4. TWiki Release Discussion [15:47:45] 5. Miscellaneous [15:48:02] ---++ 1. Feature Requests for Kampala Release [15:48:11] http://twiki.org/cgi-bin/view/Codev/WebChanges [15:48:41] just one update [15:48:43] http://twiki.org/cgi-bin/view/Codev/TestingTWikiThePerlWay [15:48:52] any comments HaraldJoerg? [15:49:12] The question is: Should this stuff go to SVN? [15:49:39] i was just going to ask, when will be have this in svn? [15:50:16] so question, should. we continue twiki way of testing, or align with perl way [15:50:23] At any time, as far as I am concerned. Needs a bit more documentation, e.g. a "home topic" in Codev. [15:50:40] i am for perl way [15:51:06] question how to go forward [15:51:20] I don't mind the TWiki way because I've integrated the TWikiSuite into the perl way - other TWiki tests could be added in the same fashion [15:51:55] over time does it make sense to discontinue TWikiSuite.pm and create perl .t files, or continue this layered approach? [15:52:03] Some tests, e.g. the compilation and warnings stuff, turned out to be too cumbersome to get wrapped into Test::Unit [15:52:49] I think that there's little value in converting existing tests [15:53:01] ok [15:53:25] And experience shows that with large projects, the "perl way" testing needs to be structured and planned [15:53:27] am i right that nothing in .t needs to be done if a new test is added to the twiki test suite? [15:53:35] Correct [15:53:52] so then it makes sense to continue with the layered approach [15:53:57] The TWikiSuite.t is just a thin wrapper and then calls the original stuff, whatever that is [15:54:41] so, maybe we do not need a new test topic in codev, just updated the existing one? [15:55:30] Update - also in the sense of moving obsolete stuff into an archive section [15:55:49] yes, makes sense [15:56:32] http://twiki.org/cgi-bin/view/Codev/TestCasesTutorial [15:56:45] that topic is big [15:56:58] ...and messy [15:57:19] :-) [15:57:33] anything else on this topic, or features? [15:58:05] The most important feature of the new test approach is that some of the manual tests can be automated [15:58:08] ---+ 2. Extensions [15:58:26] yes, that is great [15:58:30] http://twiki.org/cgi-bin/view/Plugins/WebChanges [15:59:06] only one update [15:59:36] two weeks ago during the release meeting i updated the spreadsheetplugin so that tests run on 64bit arch [15:59:48] that is all on extensions [15:59:51] anything? [16:00:09] In SVN, I've added two more changes to the spreadsheet plugin tests [16:00:33] Not yet published because I'm not finished with the tests [16:00:40] ah [16:00:42] thanks [16:00:50] ---+ 3. Review Urgent and Not So Urgent Bugs [16:00:56] http://develop.twiki.org/do/view/Bugs/WebChanges [16:01:28] ah, i see your test case [16:01:43] TWikibug:Item7826: The HASHREVERSE test case in SpreadSheetPluginTestCases fails.... randomly [16:01:50] http://develop.twiki.org/do/view/Bugs/Item7826 [16:01:54] Items 7826 and 7827 [16:02:22] TWikibug:Item7827: With non-threaded Perl, the $SPLIT function of SpreadSheetPlugin fails after splitting on '$empty' [16:02:28] http://develop.twiki.org/do/view/Bugs/Item7827 [16:02:42] Both are trivial fixes [16:03:21] In 7827, it's actually a workaround for a Perl bug which will be fixed in Perl 5.28 [16:03:57] and look good [16:04:03] thank you harald [16:04:42] TWikibug:Item7796: TWiki with current Perl: Make CGI::Carp work from TWiki's distribution [16:04:48] http://develop.twiki.org/do/view/Bugs/Item7796 [16:04:53] any comment on this? [16:05:43] I did a second attempt to fix this issue: Run TWiki on an installation with Perl 5.24 and no CGI.pm installed on the system [16:06:11] just read you latest comment, makes sense [16:06:35] thank you for working on this HaraldJoerg! [16:07:22] A lot of these fixes came from the automated test runs with various Perl versions [16:07:27] ah [16:07:35] I'd say we are safe up to 5.26 now [16:07:45] anything else on bugs? [16:07:59] ---++ 4. TWiki Release Discussion [16:08:05] Just a few where I'd ask for your approval to close the bugs [16:08:52] ah, if you don't hear from person reporting, make a decision [16:09:06] I was the person reporting :) [16:09:28] you are the boss :-) [16:09:43] One of them is the notorious insecure dependency - which vanishes with Perl 5.24 [16:09:52] let me look through recent items as well (offline) [16:09:53] Or at least, I could not reproduce it [16:10:16] ok [16:10:28] back to twiki release [16:10:36] same goal to release before end of the year [16:11:10] in 2017-09-21 meeting we decided to raise required perl from 5.8 to 5.10.1 [16:11:24] i have nothing else on release [16:11:29] anything? [16:11:54] Nope [16:12:25] nothing from me [16:12:25] ---+ 5. Miscellaneous [16:12:34] anything? [16:13:36] Nope [16:13:43] i don't have twiki related misc [16:14:15] any progress with notification after commit? [16:14:27] unrelated, tomorrow i'll have my first exhibit of hdr photos in a gallery, tomorrow is opening reception [16:14:50] not yet, let me ping isp again [16:15:21] as I mentioned earlier, any interest to send notification to slack? [16:15:33] it can be handy [16:15:53] for me it would not add value, e-mail is good for notification [16:16:11] but if it can be done easily, why not? [16:16:36] on slack, things are archived and anybody having access to slack can see it [16:16:43] especially if it is convenient for you HideyoImazu-san [16:16:55] I hear you [16:16:59] let me look into it [16:17:53] ha! [16:17:54] http://search.cpan.org/~mihyaeru/WebService-Slack-WebApi-0.01/lib/WebService/Slack/WebApi.pm [16:18:51] my $posted_message = $slack->chat->post_message( [16:18:51] channel => 'channel id', # required [16:18:51] text => 'hoge', # required [16:18:51] username => 'fuga', # optional [16:18:51] # othre optional parameters... [16:18:51] ); [16:19:39] ok, shall we close the meeting? [16:19:42] looks like it's written by a Japanese speaker [16:20:27] At least his blog https://blog.mihyaeru.com/ looks pretty unreadable for me [16:20:33] https://twitter.com/mihyaeru21 [16:21:06] definitely japanese [16:21:13] right [16:22:03] TTYL, guys! [16:22:04] ok, let's close the meeting at +82 min [16:22:16] Ok, TTYL! [16:22:18] i'll post the logs and minutes as usual [16:22:29] thank you and ttyl!