DMCCB#6 (2019 - 02 - 20)

RFC-573 - Getting issue details... STATUS

• Requires experts for discussion, Jim Bosch or Robert Lupton
• Note that Jim & Robert have now okayed the approach being taken on the RFC — I suggest that's probably all the input we need from them.

RFC-575 - Getting issue details... STATUS

RFC-574 - Getting issue details... STATUS

• RFC-573
  • input provided by Jim and Robert in the RFC, they are fine with the proposal
  • RFC set to "Board Recommend"
• RFC-575
  • John flagged this RFC in order to bring this attention to Leanne
  • All external stakeholders using weekly, need to be addressed to which weekly to use.
  • Leanne Guy to add a comment and assess the RFC-575 with Simon Krughoff
• RFC-574
  • RFC adopted since it is a document
  • Unknown User (gcomoretto) to release LDM-682 in docushare

RFC-576 - Getting issue details... STATUS

• RFC-576
  • Tim Jenness commented that the first part of the RFC is agreed, but the second part need some developments
  • John Swinbank LSE-400 still need to be released in docushare,

None

None

RFC-571 - Getting issue details... STATUS

RFC-562 - Getting issue details... STATUS

RFC-549 - Getting issue details... STATUS

None

• 17.0 planned for the end of 2018
  • DM-17880 - Getting issue details... STATUS
    
    • DM-17881 - Getting issue details... STATUS
  • Expected availability by end of February
• LDM-564 need to be updated

• Unknown User (gcomoretto) explained the status of the release:
  • at the moment there is an issue on codekit connecting to GitHub API
• John Swinbank asked for the status of thew release procedure
  
  • DMTN-106 drafted

Support to J. Swinbank monitoring activity

1. DM-945 - Getting issue details... STATUS
2. DM-615 - Getting issue details... STATUS
3. DM-591 - Getting issue details... STATUS
4. DM-327 - Getting issue details... STATUS
5. DM-2196 - Getting issue details... STATUS
6. DM-2251 - Getting issue details... STATUS
7. DM-2252 - Getting issue details... STATUS
8. DM-2204 - Getting issue details... STATUS
9. DM-2260 - Getting issue details... STATUS
10. DM-485 - Getting issue details... STATUS

3674 unresolved issues (3671 on Feb. the 13th)

• DM-945 : no activities since 2014, comment added
• DM-615: reassigned
• DM-591:
  • Colin Slater to comment on DM-591
• DM-327:
  • Tim Jenness to assess the status of DM-327
• The other issues have been closed before the DMCCB telecon starts
• DM-2276 updated by Leanne Guy during the DMCCB

• Currently when the CCB marks a flagged RFC as "board recommended" it is required that the next step be "manager approves". Since the manager is on the CCB this step is superfluous and the CCB would like the workflow modified such that "Adopt RFC" is the next step after "board recommended" . This allows the proposer to adopt the RFC themselves and add the "is triggering" Jira tickets.
  • Unknown User (gcomoretto) to update the dev guide with the RFC workflow update: Originator adopt a "Board Recommend" RFC after opening the triggering issue(s)
    
• Colin Slater End dates of RFCs are not taken in account.
  • DMCCB can board recommend even if others are not OK.. or due date is not met still
  • only proposed RFC with problems or due date in the past need to be discussed by the DMCCB
  • Unknown User (gcomoretto) to include RFC due date in agenda page
• Next week, on February the 27th, there is no DMCCB, since everybody will be in the DMLT Face 2 Face