At CERN: Federico, Zoltan, Marko
On Vidyo: Daniela, Andrei, Ueda

Apologies: 

Follow-up from previous meeting

• Next DIRAC Users Workshop: confirmed in London, hosted by Imperial College. 13 - 17 May 2019 (Tuesday to Friday)
  • https://indico.cern.ch/event/DUW9
  • Announced on the forum, registration to open
•  

DIRAC communities roundtable

• CLIC:
  • NTR
• LHCb: 
  • Still looking into using parametric jobs in production
  • MP queues: hopefully deploying a few
• GridPP:
  • Updated to last release
• Belle2:
  • Testing update to v6r19 and v6r20
  • Production will jump from v6r17 to v6r20

Current situation

DIRAC

• v6r20p15 out

WebApp:

• PR for ExtJS6 should be merged for v7r0

Pilot3:

• NTR

DIRACOS:

• NTR

BOINC:

• NTR

Documentation

• all warnings removed
• website diracgrid.org
  • discussion if to keep it or not. Federico suggested fixed website, Andrei prefers the current wordpress based implementation
  • Marko and Zoltan suggests to put it on github
  • We'll keep the wordpress
    • Andrei will update its content
    • and give few of us login to update it

DB12:

• NTR

tornado and other externals

• NTR

Release planning, tests and certification

Release planning:

• v6r20 series
  • NTR
• v7r0 series
  • the list of feature request is already closed
  • Last PRs in the pipeline (dirac-install++ and ProductionSystem) can probably be merged
  • The PR for HTTPs needs to wait one for M2Crypto

Certification process: 

• v7r0 certification:
  • certification instance to update

Weekly development(s) focus

Discussion on DIRAC platforms and matching. Federico will look into possibly rethink how it's done. OSCompatibility section can maybe be removed in favor of using tags, which is a more generic mechanism.

DIRAC: current PRs and tasks being worked on, or topics from Google forum

• No interest in creating something generic for DB extension: https://github.com/DIRACGrid/DIRAC/issues/3848

AOB

• Next BiLD-Dev meeting will be held in 2 weeks

LHCbDIRAC

• v9r3 plan in the wiki
• v9r3 can probably be deployed using the lcgBundle (NOT LHCbGrid anymore)