Meeting Minutes - Doc team meeting of 5/21/2020

Thursday May 21st 2020, 18:00 UTC

Presents: Steve, Drew, Dan, Carlisle, Olivier
IRC chanel:
https://irc.documentfoundation.org/?settings=#libreoffice-doc

Telegram Group
https://t.me/joinchat/ALeRuUFCxyZY0wzoddldWQ

Live TDF Jitsi Room
https://jitsi.documentfoundation.org/tdfdocteam

Pending items:
* Submit proposal for new Guide template (olivier)

Topics and Discussion:
    + Call for Documentation Mentor
       + Need 2 more mentors for Google seasons of Doc
    + Solver for Calc
       + Help pages almost ready, waiting for wiki contents (Olivier)
           + What is
               + Espilon level in Linear Solver (1 phrase)
               + Branch and bound (1 phrase)
           + Use OpenOffice NLP wiki contents as a start in LO wiki
               e.g: [NLPSolver]
       + Thanks to Drew Jensen for his recent work in this area (SF)

    + Questions and Answers on Guides and Help

    * Calc Guide (SF)
      - Current status of update
          + Moving on to deliver
      - Reviewing Keyboard Shortcuts chapter
          + Needs revision
          + heavy rewriting,
          + depends on OS (Linux, Windows, Mac)
AI: Verify Linux (Drew)

      - Does 6.x template currently used in the master document need
update for 6.4?
          + Stick with the Calc current 6.2 template
      - Lessons learned about unexpected user interface changes in LO
          + Lots of changes,
             + Not everithing changes in release notes
             + e.g. MSO lock files
             + For notebook bars, let description of NB be in GS guides
(Steve)
             +
    * Discuss recent updates to the Calc Functions area of the wiki (SF)
          + Revert if necessary
          + wiki pages often suffer vandalism
    + Order of creating a ePUB version for the user guides? (Dan)
        + Base guide
AI: Update Contributor Guide for e-PUB (Tabs issue) (olivier)

    + On template for 7.0 (olivier)
      + What to change?
       + Name of styles (currently messy, but low impact)
          + Cleanup of excessive styles
          + Prefer to use the Standard/Default style names (Steve, Dan)
          + Design a new style only if absolutely necessary
          + Notes, Warning and Tips should change?
                 ==> Unconclusive
          + "On using mailing list (...)", change to warning (Dan, SF, Drew)
          + Removal of unused styles
          + Adjust for ePUB (eliminate automatic tabs, no OLE objects)
          + Create a macro to manage styles
              + check direct formatting, check style not "oficial"
              + Use the extension to change char templates

         + Use acessibility (a11y) features in 7.0 to verify a11y
              + Let's document this new feature (Drew)
          + What about fonts? Serif or Sans serif? No change
          + Heading font color? Keep current green, choose other?
          + Margins, page size?
          + No headers thus reduce uper margin (Steve).
AI: present a proposal for new template 7.0 and discuss (olivier)

Next meeting : *THURSDAY* June 4th 2020 at 18:00 UTC.

Thursday May 21st 2020, 18:00 UTC

    + Call for Documentation Mentor
       + Need 2 more mentors for Google seasons of Doc
    + Solver for Calc
       + Help pages almost ready, waiting for wiki contents (Olivier)
           + What is
               + Espilon level in Linear Solver (1 phrase)
               + Branch and bound (1 phrase)

I found some lines in the internet, enough for a start.

Help pages published

https://help.libreoffice.org/7.0/en-US/text/scalc/01/solver.html?DbPAR=CALC

https://help.libreoffice.org/7.0/en-US/text/scalc/01/solver_options.html?DbPAR=CALC

https://help.libreoffice.org/7.0/en-US/text/scalc/01/solver_options_algo.html?DbPAR=CALC

           + Use OpenOffice NLP wiki contents as a start in LO wiki
               e.g: [NLPSolver]

Done. I opened an empty page for later community work.
https://wiki.documentfoundation.org/NLPSolver

Regards

Hi Olivier & all.,

just jumping in the bandwagon for a quick self-ad :wink:

> [...]

           + Cleanup of excessive styles
           + Removal of unused styles
           + Create a macro to manage styles
               + check direct formatting, check style not "oficial"
               + Use the extension to change char templates

I don't know if that might be of interest for that purpose, but I'd want to make you know that I've been working on such a tool for some time now. This "WriterStylesReporter" is meant to become a Writer extension [1].

Its functionalities are:

-- documenting the paragraph and character styles by creating report under Calc (another report with Writer is scheduled)
Note: not all styles details are reported, only the ones I consider being of importance.

-- suppression of unused styles

FWIW, I've placed a demo report and a screenshot in a zip file, here:
https://catdrop.drycat.fr/r/U3yZebJD#Grb3MqcFjUFvZGUuqQoIouEnwlYXQs/+mG/hY66HZ6w=

[1] This is inspired by an extension (acStyleInspect) by Alain de la Chaume, that seems to be unavailable for some time now.

HTH,