Subject: KampalaMeetingLog-2017-03-16.txt Date: March 16, 2017 at 3:50:36 PM PDT [15:00:04] Hi Peter [15:00:41] hi HideyoImazu-san! [15:01:07] welcome back! [15:01:19] how is weather in tokyo? [15:01:27] hanami time? [15:01:36] still cold [15:01:52] 5C now at 7am [15:02:44] cherry blossom will start blooming on Mar 23 in Tokyo, according to a forecast [15:02:46] ah, yes, one hour earlier for you now [15:02:47] sorry [15:02:56] and in full bloom around April 2 [15:03:07] soon [15:03:49] my evening conf calls with NY shift one hour [15:04:08] so the release meeting starting a 7am is fine [15:05:15] hold on... [15:05:48] ... back [15:06:18] hopefully that evening call is not on your fri evening [15:06:40] I have one Fri evening call [15:06:57] from izakaya? ;-) [15:07:11] mostly from home [15:07:32] izakaya would be too noisy [15:07:48] we got nice weather recently [15:08:00] last sat we went to the beach near santa cruz [15:08:17] nice! [15:09:17] https://www.flickr.com/photos/peterthoeny/33025960860/ [15:09:41] https://www.flickr.com/photos/peterthoeny/32589171714/in/dateposted/ [15:09:58] HDR! [15:10:20] harald seems not to be joining today [15:10:24] yup [15:11:00] the one with the climbers against sun would not be possible without hdr [15:11:49] shall we start? [15:11:51] that's what I thought [15:11:56] sure. let's start [15:12:06] http://twiki.org/cgi-bin/view/Codev/KampalaReleaseMeeting2017x03x16 [15:12:19] 1. Feature Requests for Kampala Release [15:12:19] 2. Extensions [15:12:19] 3. Review Urgent and Not So Urgent Bugs [15:12:19] 4. TWiki Release Discussion [15:12:19] 5. Miscellaneous [15:12:42] ---++ 1. Feature Requests for Kampala Release [15:12:50] http://twiki.org/cgi-bin/view/Codev/WebChanges [15:13:01] no changes since last time [15:13:04] anything? [15:13:16] nothing from me [15:13:24] ---++ 2. Extensions [15:13:30] http://twiki.org/cgi-bin/view/Plugins/WebChanges [15:13:42] also quiet here [15:13:46] nothing from me [15:13:49] anything? [15:13:57] no [15:14:06] ---++ 3. Review Urgent and Not So Urgent Bugs [15:14:13] http://develop.twiki.org/~twiki/cgi-bin/view/Bugs/WebChanges [15:14:49] http://develop.twiki.org/~twiki/cgi-bin/view/Bugs/Item7776 [15:14:56] Item7776: MAKETEXT mis-renders mailto links within strong tags [15:15:04] harald fixed a maketext bug [15:15:28] status is confirmed, but i have seen checkin actifity [15:15:36] "activity" [15:15:41] ok [15:15:49] no other changes since last time [15:15:53] anything? [15:16:02] no [15:16:09] ---++ 4. TWiki Release Discussion [15:16:26] i have not made progress on app packager [15:16:32] hopefully some this weekend [15:16:41] same here [15:17:14] anything item you'd like to discuss for release preparation? [15:17:22] i don't [15:17:44] any thoughts on my mockups? [15:19:36] posted where? [15:19:48] did i miss something? [15:19:53] sent to you by email [15:20:10] ah, i remember, in your email [15:20:11] two weeks ago [15:20:46] maybe still too early to comment [15:20:57] i like the fact of boostrap to automagically reformat the menu based on screen size [15:21:51] yes. heavy lifting is done by the framework. [15:22:32] i think it will be a bit challenging to define a menu structure that is functional and also works well on mobile [15:22:59] probably [15:23:09] the current topmenuskin has multiple dropdowns [15:23:18] but it doesn't have to be perfect from the beginning [15:23:27] does that translate to nested menu in bootstrap? [15:23:46] agree, try and refine is a good apprach [15:23:49] I see some extensions doing that [15:23:53] "approach" [15:24:21] once we have something working, we can discuss in concrete terms. [15:24:57] yes [15:25:18] i am looking forward to review and possibly help define a standard [15:25:31] ideally and eventually, everything including the edit page will be using the framework. [15:25:45] but initially, it will be only of view. [15:25:52] for example, the topmenuskin has a concept of adding your own dropdown per web [15:26:55] topmenu skin may need enhancement [15:26:57] it would be cool to have a data-driven approach to define and customize menus [15:27:32] yes, i would do the tomenuskin differently now [15:28:03] such as based on a json construct that can be extended [15:28:40] it would be cool to define a menu structure that can be used by bootstrap based skin and topmenuskin [15:30:41] possibly all in javascript (global menu object), a SetGetPlugin json object, or a SpreadSheetPlugin hash(es) [15:31:18] plus we may need to rethink overall navigation structure [15:31:36] we can review that, yes [15:32:16] personally i am happy with the logical functionality of topmenu dropdowns [15:32:45] always good to look at it with fresh eyes [15:33:37] shall we close meeting early today? [15:33:43] i've been using StructNavPlugin understanding TML sections and bullet points and translate them into tabs, subtabs, and dropdown menus [15:34:35] is that something you wrote? [15:34:43] that plugin tightly coupled with our custom skin, so far, I cannot make it public [15:35:06] yes, I wrote it 10 years ago [15:35:50] ah, just found http://twiki.org/p/pub/Codev/KampalaReleaseMeeting2015x09x17/KampalaMeetingLog2015x09x17.txt [15:36:00] where you describe it [15:36:52] maybe with the responsive skin, I finally can make the plugin public [15:38:44] i think breadcrumb is easier defined with physical parent-child relationship [15:39:15] yes. but what if you need to restructure a web having many topics? [15:40:04] it's way more intuitive restructuring sections and bullet points [15:40:09] then we need a tool that shows whole hierarchy, and drag and drop capability to reparent [15:40:27] should not be difficult to create [15:41:32] we made and used such a tool. but in most cases, editing a topic with sections and bullet point in raw text seems fine [15:41:39] i have created hierarchical twiki apps that show the breadcrumb in topic header [15:42:58] With AutoSectionsPlugin, now you can edit a part of site map (WebMap). [15:43:15] back to menu and nav structure, i think we have two levels: 1. web level, 2. topic level with parent-child relationship [15:43:16] anyway, for you, this may be too abstract. [15:44:29] i think it is possible to define a standard that works for very large number of webs (like you have) and smaller ones (like twiki.org) [15:44:36] I mean for me using the plugin daily, it's an everyday reality. but for you, it's an abstract discussion [15:45:30] with StructNavPlugin, a web navigation structure is defined by a topic. [15:45:34] personally i would prefer to stay with simple parent-child relationship for topics, and in return add an easy way to reparent (drag and drop) [15:45:43] when the plugin reads the topic, variables are expanded. [15:46:01] so you can make web navigation dynamic [15:46:11] ah, with treeplugin [15:46:23] and you can split navigation into pieces and combine them INCLUDE [15:46:47] you can show some tabs and dropdown menus only to a group of people [15:46:59] understood [15:47:19] yes, i see value in terms of flexibility it brings [15:47:42] I really hope we can discuss this in concrete terms soon. [15:48:23] ok [15:48:31] time check: +48 min [15:48:37] shall we close the meeting? [15:48:49] sure [15:48:58] ok [15:49:07] i'll post the logs and minutes as usual [15:49:17] thank you HideyoImazu-san! ttyl [15:49:30] thanks, Peter! [15:49:34] ttyl