Skip to end of metadata
Go to start of metadata

Location

BrowserRoom SystemPhone Dial-in
https://bluejeans.com/761546516/
  1. Dial: 199.48.152.152 or bjn.vc
  2. Enter Meeting ID: 761546516 -or- use the pairing code

Dial-in numbers:

  • +1 408 740 7256
  • +1 888 240 2560 (US Toll-Free)
  • +1 408 317 9253 (Alternate Number)

Meeting ID: 761546516

(Back to the DMCCB page)

Time

From 9.00 to 09.30 PT, Wednesday, March the 4th.


Attendees

Regrets

  • TBD

DMCCB Meeting Goals

      • See DMCCB responsibilities listed in LDM-294 section 7.4

DMCCB Additional Resources

Discussion Items

ItemDescriptionCCB Notes

Flagged RFCs

(To be approved by the DMCCB)

  • RFC-620 - Getting issue details... STATUS Planned end: Jan/15/2020
  • RFC-671 - Getting issue details... STATUS Planned end: Mar/02/2020
  • RFC-674 - Getting issue details... STATUS Planned end: Mar/03/2020
  • RFC-620 no news
  • RFC-671 waiting for JK to comment
  • RFC-674 Leanne to have a look at it.
Board Recommended RFCs

Adopted but not implemented LDM RFCs (only document RFCs)

Proposed RFCs

(to review, do not require DMCCB approval)

  • RFC-677 - Getting issue details... STATUS Planned end: Mar/20/2020
  • RFC-675 - Getting issue details... STATUS Planned end: Mar/06/2020
  • RFC-673 - Getting issue details... STATUS Planned end: Mar/10/2020
  • RFC-662 - Getting issue details... STATUS Planned end: Feb/26/2020
  • RFC-652 - Getting issue details... STATUS Planned end: Jan/22/2020
  • RFC-651 - Getting issue details... STATUS Planned end: Jan/22/2020
  • RFC-638 - Getting issue details... STATUS Planned end: Mar/31/2020
  • RFC-677: should be good to go
  • RFC-675: KT, using conda is problematic, using pip is fine, they have their own channel
    • question: where the scipipe-conda-env should contain everything or just what is requested by lsst_distrib. We agreed on the last.
    • John Swinbank we should write that down
    • In scipipe_conda_env there are libs that are not needed, but this is historic.
    • Tim Jenness  should we change in the developer guide:
    • Kian-Tat Lim a new environment is needed
  • RFC-673: Wil O'Mullane should comment on it
  • RFC-662: action on Colin
  • All other RFC should be just normal work

Adopted RFCs without Triggering issues

(to create implementing DM issues)

  • RFC-648 - Getting issue details... STATUS

Adopted RFCs with all triggered work COMPLETED

(to set status as 'IMPLEMENTED')



RFCs adopted since last CCB

(to review, no action required)

  • RFC-666 - Getting issue details... STATUS

RFCs implemented (or withdraw) since last CCB

(to review, no action required)

  • RFC-666 - Getting issue details... STATUS
  • RFC-658 - Getting issue details... STATUS


Releases

  • Planned
  • Changes to the release schedule
  • Next planned major release 20.0.0
    • Planned for Spring 2020
      DM-20564 - Getting issue details... STATUS

    • Blocking issues open:
  • We may be switching to the conda compiler.
  • Kian-Tat Lim we may need to support comcam with the next release, but there are no Jira issues related to that, blocking the release.

Monitor Jira issues status:

  • the most forgotten 10 DM issues
    • (resolution = Unresolved ORDER by updated asc)

Support to J. Swinbank monitoring activity - 

  1. DM-7909 - Getting issue details... STATUS  
  2. DM-7002 - Getting issue details... STATUS
  3. DM-7390 - Getting issue details... STATUS
  4. DM-7954 - Getting issue details... STATUS
  5. DM-7953 - Getting issue details... STATUS
  6. DM-5311 - Getting issue details... STATUS
  7. DM-4735 - Getting issue details... STATUS
  8. DM-289 - Getting issue details... STATUS
  9. DM-2445 - Getting issue details... STATUS
  10. DM-2678 - Getting issue details... STATUS

3867 unresolved issues (3858 on March the 4th)

  • DM-7909: Presumed obsolete given transition to Gen3. Changed team to Architecture; K-T or Tim can close this out (assuming they agree with me).
  • DM-7002: K-T has commented “this still seems to be a problem, but of low priority”.
  • DM-7390: Not obvious to John Swinbank if this is really a big deal. Tempted to close as “Won't Fix”; awaiting feedback.
  • DM-289: Fritz has commented "still relevant; low priority".
  • DM-2445: Fritz has commented.
  • DM-2678: Fritz has commented "still relevant; low priority".

Others were closed by the time I got here!

Open Actions

AOB


Next DM-CCB March the 18thCanceled March the 18 and March the 25th. Next DMCCB on April the 1st. Urgent RFCs to be discussed via slack.


Pending Flagged RFCs

Key Summary
Loading...
Refresh

Pending Proposed RFCs

Key Summary
Loading...
Refresh

Oldest issues

Key Summary
Loading...
Refresh

Meeting outcome


Pending DMCCB Actions

DescriptionDue dateAssigneeTask appears on
Gabriele ComorettoDMCCB#60 (2020 - 08 - 05)
Kian-Tat LimDMCCB#60 (2020 - 08 - 05)
  • John Swinbankwrite a text to clarify when an RFC need to flag (DM-25191)
John SwinbankDMCCB#51 (2020 - 05 - 27)
  • Tim Jenness  to write a policy on how external code written by DM shall be handled.
Tim JennessDMCCB#51 (2020 - 05 - 27)