Release Meeting: 05 Feb 2018


General status.

1. Task review

  • 14494 (Confirmed): PlainFileStoreContrib shows ProjectContributor as UnknownUser Checkins on branches: - Crawford proposed a change.
  • 14516 (Confirmed): table not processed when there is a %FOOBAR{} before Checkins on branches: - Crawford mostly implies this is a "won't fix" situation
  • 14616 (Closed): The generic tools/extension_installer no longer functions on perl 5.26+. Checkins on branches: Release02x01 master Item14288 - 3 areas to fix.
    • Configure::Load should do a better job of trapping errors
    • Example =Config.spec files should include a comment and end with 1; to avoid issues.
    • BuildContrib should do a better job of checking Config.spec, and don't bundle ones without any settings.

2. Development Discussion

Decided to slip 2.2 one more time. Target for May 2018. This will be the last delay.

3. Next release

Patch release 2.1.6

  • Release from: Release02x01
  • Beta start: (none planned)
  • Release target: (none planned)

Feature release 2.2.0

  • Feature Freeze: 01 May 2018
  • Release from: master
  • Beta start: 01 June 2018
  • Release target: 01 July 2018

4. Community Events

  • Joint "Wiki-Based Projects" booth at FOSDEM 2018 together with TikiWiki, XWiki and DocuWiki
    • MichaelDaum was the only Foswiki team member to attend FOSDEM, and represent us at the shared booth.

Next meeting - - Monday 19 Feb 2018 1300Z — ReleaseMeeting02x02_20180219

Please review and be prepared to discuss FeatureProposals and ReleasePlan


(08:02:06 AM) MichaelDaum: Hi there
(08:02:28 AM) gac410: Hi everyone.   
(08:02:55 AM) gac410: Are we ready to start?    How is Fosdem going/
(08:03:21 AM) MichaelDaum: It is over by now.
(08:03:28 AM) MichaelDaum: took place Sat+Sun
(08:03:42 AM) gac410: Ah.   Did you make it there?
(08:04:25 AM) MichaelDaum: erm
(08:05:00 AM) MichaelDaum: Didn't you noticed that we had a joint booth with Tiki and Xwiki?
(08:05:43 AM) MichaelDaum:
(08:05:49 AM) gac410: Yes  I heard.  Wasn't sure who was at the booth.   Though if not you ...  ;)
(08:06:24 AM) MichaelDaum: I was on the booth. The only one from Foswiki.
(08:06:48 AM) gac410: Anyway, how was the it.  
(08:07:05 AM) MichaelDaum: I repeatedly blogged and twittered and asked here on IRC for people to join the initiative. Alas no feedback whatsoever.
(08:07:16 AM) gac410: That's too bad nobody else from the community could make it. 
(08:07:28 AM) MichaelDaum: It shows how dysfunctional we are
(08:07:33 AM) MichaelDaum: as a community
(08:07:54 AM) MichaelDaum: anyway
(08:08:18 AM) gac410: Much traffic / interest at the booth?
(08:08:19 AM) MichaelDaum: it was fun nevertheless, though a bit intense with all those geeks visiting the fosdem
(08:08:38 AM) MichaelDaum: I've never seen so many IT geeks in one place.
(08:09:19 AM) MichaelDaum: absolutely overcrowded ... you constantly bumped into somebody 
(08:09:21 AM) vrurg: Hi all
(08:09:28 AM) gac410: Cool.  Well it was great that you could make it and staff the booth.   
(08:09:29 AM) MichaelDaum: interesting talks. 
(08:09:33 AM) gac410: Hi vrurg
(08:09:47 AM) MichaelDaum: the best of it was meeting the other communities
(08:10:30 AM) MichaelDaum: while I was looking forward to meet the Tiki guys again, I was most exciting meeting the Xwiki people: very nice, very friendly, lots of interesting conversations with em.
(08:10:44 AM) gac410: nice
(08:11:27 AM) MichaelDaum: Ludovic, the CEO, is awesome. As well as Vincent Massol, the CTO. 
(08:11:49 AM) MichaelDaum: I've demoed Foswiki to them
(08:11:54 AM) gac410: CEO/CTO of ... Xwiki?   or Fosdem
(08:12:06 AM) MichaelDaum: CEO and CTO of Xwiki
(08:12:24 AM) MichaelDaum: and
(08:13:14 AM) gac410: Good size organization then.  They've made Xwiki into paying software.
(08:13:25 AM) MichaelDaum: I had a very exciting conversation with Anca Luca ( about OpenFoodFacts (built with perl)
(08:14:26 AM) MichaelDaum: well Xwiki is open source, but not the way we do it.
(08:15:20 AM) MichaelDaum: was interesting to talk to them about their business model, i.e. how features are evolving.
(08:17:07 AM) MichaelDaum: next to us were CiviCRM, a crm system for non profit orgs. interesting as well.
(08:17:16 AM) MichaelDaum:
(08:18:04 AM) gac410: So XWiki seems to be somewhat syntax agnostic?   Feed it TML or feed it Confluence or ... ....  
(08:18:20 AM) vrurg: MichaelDaum: would you somehow summarize your Xwiki talks? It is definitely not the IRC format.
(08:18:33 AM) MichaelDaum: only sour point is that I didn't have any giveaways for people visiting the booth. I simply wasn't prepared well enough.
(08:19:24 AM) gac410: Well our marketing team doesn't give you much support.  :(   
(08:21:31 AM) MichaelDaum: Froscon would be another fair to organize a booth for...but I am not going to make it all alone, nor without any substantial material to garnish the booth.
(08:22:08 AM) MichaelDaum: if we want to grow the community, then we have to do events like these.
(08:22:13 AM) MichaelDaum: but right
(08:24:06 AM) gac410: y,   or pull in some new developers from the existing installed base community.  But so far we don't find too many willing to give back to the community.  Really vrurg has been the only new blood in a long time.
(08:24:41 AM) gac410: once in a while we get a github related nibble,  but nothing seems to have developed :(
(08:25:51 AM) gac410: Well anyway ... onto tasks.    I discovered a  bug in extension installer.   Perl has removed "." from the default path for "do" ...  so  "do tools/configure"   in does not work.    Needs to be either do "./tools/configure"   or resolve to the explicit filename 
(08:26:06 AM) MichaelDaum: Foswiki isnt visible enough. 
(08:27:06 AM) MichaelDaum: one thing that I noticed while having seen and heard about Tiki and Xwiki is: we are actually quite good in what we do 
(08:27:10 AM) gac410: Also discovered, trying to build a new site.  That if Config.spec is empty,  the extensions installer fails to save the config,  if ASSERTs is enabled in LocalLib.cfg
(08:28:05 AM) gac410: That is a lot of your extensions Michael,    Empty  Config.spec stops the install   when the "do Config.spec" fails.
(08:31:56 AM) gac410: It might be best to NOT include any empty  Config.spec file in the manifest.    Or just not check them in.   
(08:32:28 AM) MichaelDaum: sorry. let's get back to our release meeting.
(08:32:36 AM) MichaelDaum: empty Config.spex
(08:33:52 AM) gac410: The failure is in Configure/Load.cfg    It does a "do Config.spec"  to pull in the spec.  And do fails for empty files.   But most times the failure is trapped and ignored.   With debug enabled   configure aborts the install.
(08:34:40 AM) gac410: I was scripting a CLI install for all the extensions for NatSkin,    And couldn't figure out why none of them were doing their "save config"  to pull in the defaults.
(08:36:37 AM) MichaelDaum: does it only happen in debug mode?
(08:36:52 AM) gac410: Yes.   Otherwise the do fails, and we ignore the failure.
(08:37:08 AM) gac410: The test site I was playing with happened to have asserts enabled. 
(08:37:09 AM) MichaelDaum: do ''; is just fine
(08:37:25 AM) MichaelDaum: do '' && continue(); won't call continue()
(08:37:35 AM) gac410: right
(08:38:36 AM) gac410: In 2.1.5   it's lib/Configure/ line 129   
(08:38:48 AM) MichaelDaum: the default Config.spec has got a 1; at the end ... which we better should not rely on to always be there
(08:40:08 AM) gac410: Fails here:
(08:40:24 AM) gac410: Well,  the block following it.
(08:40:47 AM) MichaelDaum: and a bit further down: "Pointless (says CDot), Config.spec does not need 1; at the end"
(08:41:46 AM) gac410: Right,  but a bit prior,  the WARN gets turned into a failure if ASSERT is enabled.
(08:42:47 AM) MichaelDaum: why do we have to warn and fail?
(08:43:20 AM) gac410: well,   if the Config.spec has real perl syntax errors,  we still want to know the resulting configuration is bogus.
(08:43:34 AM) gac410: That establishes all the defaults for the extension.
(08:44:19 AM) MichaelDaum: a real perl error, like an exception, should better be catched using
(08:44:37 AM) MichaelDaum: try { do ./file; } catch with {...};
(08:44:53 AM) gac410: Y,  so maybe it needs rewriting.   :p
(08:45:24 AM) gac410: For now and for all the older foswikis out there, may be best to not ship empty Config.spec   
(08:46:45 AM) gac410: We could also have BuildContrib fail during packaging, and/or ignore zero length Config.spec files.
(08:47:11 AM) gac410: Better to catch typos during build than during install.
(08:47:31 AM) vrurg: Zero-length check wouldn't help. Config.spec could be empty with a comment inside.
(08:47:48 AM) MichaelDaum: xactly
(08:48:50 AM) gac410: Well 3 changes.   1)   have our "skeleton" extension include a comment and 1; in the prototype spec file.    2)  Have buildcontrib "do" and report issues before upload and 3) have configure be smarter about error handling.
(08:49:43 AM) vrurg: +,+,+
(08:50:16 AM) gac410: I'll open a task later
(08:51:30 AM) vrurg: BTW, BuildContrib has another minor architectural deficiency I stumbled upon recently. But that's, perhaps, a matter beyond release meeting subjects.
(08:51:53 AM) gac410: Other than that .. and the "do " no longer includes "." current path,  which breaks tools/configure,    I have not heard any feedback +/- regarding 2.1.5
(08:52:15 AM) gac410: Only one other minor one vrurg?   
(08:53:15 AM) vrurg: gac410: I should open a task on 2.1.5 configure issue too. Related to running it on macOS. A checker for storage encoding tries matching agains unitialized config entry.
(08:53:32 AM) gac410: Y,   please do.  
(08:53:54 AM) vrurg: gac410: Sorry, on your question – my English falls short here. :( 
(08:54:11 AM) vrurg: Could you, pls, re-phrase it?
(08:55:17 AM) gac410: It was a joke... you only found one other minor issue,  which I figure is an understatement.
(08:55:17 AM) ***gac410 takes the blame on that one I'm sure.   I did not have a mac to test against for the utf encoding test
(08:56:22 AM) gac410: CDot did comment on our other two blockers.  
(08:56:29 AM) vrurg: It's not about encoding itself but rather about settings it to something meaningful in bootstrap.
(08:57:53 AM) vrurg: Regarding CDot – it reminds me that my fix for EditRowPlugin being shaky/flikering is done. Works fine for me.
(08:58:16 AM) MichaelDaum: vrurg, go ahead checking it in then.
(08:58:39 AM) gac410:  Item14494 - (ProjectContributor vs UnknownUser) in PFS store,   I don't really like his solution but ...
(08:58:45 AM) vrurg: I'd like somebody to test it too beforehand. If possible.
(08:59:13 AM) vrurg: If nobody can do it then will merge it.
(08:59:42 AM) gac410: And Item14516 - the incomplete %MACRO{}     breaking tables,   he mostly said that's life... if I read between the lines   ;)
(08:59:57 AM) gac410: I can try it after the meeting vrurg
(09:00:28 AM) gac410: So that's our blockers,  I'm not sure where to go with them 
(09:00:49 AM) MichaelDaum: _saveDamage is a pita
(09:01:24 AM) MichaelDaum: though the workaround CDot proposed in Item14494 is okay, in some sense.
(09:01:44 AM) MichaelDaum: Item14516 is next to WontFix
(09:01:51 AM) vrurg: gac410: Thanks, it in the branch. BTW, I based it on Release, eventually. :)
(09:02:14 AM) gac410: Y  I was somewhat seeing your adventure there ;)
(09:03:52 AM) gac410: Y,  In some ways, our macro parser really needs a redesign,  but it's so fundamental to foswiki,  it's mostly untouchable.    The ability to create new macros out of concatenated macros,  not just nested macros,  is a mess.
(09:04:50 AM) gac410: At one point I traced the macro expansion, and in some cases it iteratively expands useless macros many may thousands of times looking for a possible closure.
(09:06:26 AM) gac410: Item14437: Macro expansion runs away, reprocessing some macros many times
(09:08:59 AM) gac410: Anyway that's it for tasks unless anyone has any to escalate.
(09:09:07 AM) gac410: Going once ... going twice ...
(09:09:27 AM) gac410: For features,  there is one with the 2-week clock expiring.
(09:09:29 AM) gac410:
(09:10:37 AM) gac410: The last time this was tried, ages ago,  Sven also changed the WikiWord definitioin to  wikiWord   and that broke everything.    My proposal does not change wikiWord,  
(09:12:15 AM) gac410: MichaelDaum:    On another note ... I like your new proposal pages.   Very nice
(09:12:29 AM) MichaelDaum: gac410, thanks
(09:13:02 AM) MichaelDaum: we have a bit of a mixed terminology here: FeatureProposal = FeatureRequest = ChangeRequest
(09:13:33 AM) MichaelDaum: so I merged the first two into one
(09:14:00 AM) MichaelDaum: a FeatureProposal still has got a ChangeRequest form attached to it ... which kind of is confusing
(09:14:02 AM) gac410: Yes.    Also singular vs. plural.    FeaturePropsal was where you create new ones.   FeatureProposals (plural) was the mega search that I used constantly 
(09:14:37 AM) MichaelDaum: did you notice that I've added direct links to the Development.WebHome?
(09:14:49 AM) MichaelDaum: direct links to FPs in a certain stage
(09:14:53 AM) gac410: Yes
(09:15:42 AM) MichaelDaum: I also introduced the notion of "active" vs "passive" FPs . Most of the time, as a RM, you might be more interested in active FPs, part of the ReleasePlan
(09:15:43 AM) ***gac410 just liked a catagorized single page with everything that I could scan / and use in-browser search to try to sniff out stuff.
(09:16:09 AM) gac410: y,   the new pages are easy to work with.
(09:16:15 AM) MichaelDaum: okay. good.
(09:17:00 AM) gac410: I used to do a lot of "ctrl-F" trying to pick out words from the search.    We have so many old similar requests.  They are impossible to find.
(09:17:58 AM) gac410: Anyway...   Lower case topic names.   Seems to be a very easy thing to enable,  at least as experimental.   I've not found any negative side effects,  other than possible collisions with directory names.
(09:19:13 AM) vrurg: Could collisions be avoided at creation time by simply checking webname against directories? A kind of 'reserved words' check.
(09:21:30 AM) gac410: I have not experimented with that yet.   If the cgi script has priority over the existence of a directory,  then it just works.  The issue would be if apache or nginx attempts to access the directory 
(09:22:27 AM) gac410: The *only* directory that we web server should ever access would be bin and pub.   I really don't like our approach of selectively blocking directories in the web server.  If you add a new directory and forget ... oops.
(09:23:10 AM) vrurg: Right.
(09:23:54 AM) gac410: Anyway,  more onto our "process"...    I am very uncomfortable with our feature proposal process, where things seem to just get approved by default without any obvious review.
(09:27:01 AM) gac410: Any thoughs on 2.2    Michael,  you still have a pretty big list of stuff you wanted in the next release.  Should we set another freeze date? 
(09:27:40 AM) gac410: I'm just puttering along.  Any features that don't make the current train,  I have no problem deferring.  
(09:27:42 AM) MichaelDaum: I was afraid of asking :]
(09:27:51 AM) vrurg: gac410: I'm afraid, not much could be done about the process anyway. At least for now, when it's really only three of us mostly.
(09:28:45 AM) gac410: Well we just released 2.1.5     so holding off another 3 months is not a huge hit.    Maybe May 1st freeze?   Release in June/July?
(09:29:34 AM) gac410: 2.1.0 was released Feb 2016,  so we are 2-years out from our last minor release
(09:32:00 AM) gac410: Okay ... how about 2.2.0  feature freeze  May 1st,  Beta June 1st.   this time no more slips.   Any features not merged by May 1st 2018 will be lost to the sands of time ... or Foswiki 3.0   whichever comes first  :D
(09:33:20 AM) gac410: The lower case topic names points out how BAD our sorting is.  We really need to implement Julian's  changes to dump Locales and move to a better unicode based sort, etc.
(09:34:01 AM) vrurg: You have my voice for the strict plan. It makes you all availabe to work oin 3.0 sooner. ;)
(09:34:36 AM) gac410: That our sort is  ABCDE.........abcde     is not really obvious until aTopic sorts to the end of the topic list.  I debugged that sort issue thinking that store was not reading lower case names.   
(09:35:52 AM) gac410: wrapping our sort in   lc()  cmp lc()    fixes that somewhat, although you get mixed results  of aA  and Aa   so a real sort implementation would be better.
(09:37:31 AM) vrurg: Weird fix for mixed result: lc($a) . $a cmp lc($b) . $b
(09:38:00 AM) vrurg: Dirty, but could serve as a quick fix until better algo is implemented.
(09:38:28 AM) gac410: hm   what would performance be like.   I was uncomfortable even using lc()   
(09:38:56 AM) vrurg: No slower than a complex utf staff, I would guess.
(09:41:26 AM) gac410: Anyway,  that's it for me.      Anything else for the meeting?
(09:42:23 AM) vrurg: Not on my side.
(09:43:28 AM) gac410: MichaelDaum:   ping    May 1st feature freeze   Last chance for features before moving onto 3.0    Are you good with that?
(09:44:29 AM) MichaelDaum: gac410, yes. thanks for the extended reprieve.
(09:44:57 AM) gac410: YW....  though I'm a bit selfish.   I have a few features I want to finish up too :D
(09:45:23 AM) MichaelDaum: hehe
(09:45:30 AM) MichaelDaum: all good then
(09:46:47 AM) gac410: Okay.   I'm flipping the LowerCase names to approved unless there are any last minute objections.  
(09:47:36 AM) gac410: We should press JulianLevens a bit more.   I'd love to see him get the Locales mess fixed.   backlinks would be nice, but really the Locales is more important IMO
(09:48:10 AM) gac410: but these for 3.0 ...  at the earliest  :(
(09:48:49 AM) gac410: thanks everyone.    Back to the main channel    
(09:48:50 AM) vrurg: Totally agree. utf support is what made me to move from t* to foswiki a few years ago. Locales are no less important to have this complete.
(09:49:16 AM) vrurg: thanks!
(09:49:27 AM) gac410: They (t*) are making no movement in that direction at all that I can see.   
(09:50:19 AM) gac410: Focus is more on trying to keep t* running on new distros.  They are getting hit by all the perl changes.   CPAN they are dealin with by bundling old code   yeech.

Topic revision: r1 - 05 Feb 2018, GeorgeClark - This page was cached on 14 Nov 2018 - 05:33.

The copyright of the content on this website is held by the contributing authors, except where stated elsewhere. See Copyright Statement. Creative Commons License    Legal Imprint    Privacy Policy