Skip to end of metadata
Go to start of metadata

Location

Zoom link available on Slack channel.

(Back to the DMCCB page)

Time

From 9.00 to 09.30 PT, Wednesdays.


Attendees: 


Regrets: 

DMCCB Meeting Goals

  • See DMCCB responsibilities listed in LDM-294 section 7.4

DMCCB Additional Resources

Discussion Items

ItemDescription

CCB Notes

Flagged RFCs

(To be approved by the DMCCB)

  • RFC-771 - Getting issue details... STATUS
  • RFC-863 - Getting issue details... STATUS
  • RFC-888 - Getting issue details... STATUS
  • RFC-889 - Getting issue details... STATUS
  • RFC-890 - Getting issue details... STATUS
  • First two need Gregory's attention
  • Is it more confusing that not if we say that all middleware expect bps?
  • K-T I think all science code should be gpl
  • TJ: We already lost that fight, AURA uses BSD. This was triggered by Paul who said "the plugin should be bsd" 
  • K-T I don't see any problem with asking plugin writers to use GPL, but your example on the RFC wasn't convincing in itself.
  • K-T: Its a viral think that now you have to use BSD because all the BSD people want to use you.
  • TJ: If GPL won the world we wouldn't be having this convo. I think we need Wil to make a decision. DMCCB can say that we don't want to do it. 
  • TJ: we at least have precedent in pex_config

JFB: I'll update 888 to reflect the discussion. 

RFC-890: Is the name appropriate for putting it up on pypi? JFB:  I think its precise (its about relational algebra expression trees), but dont know if its generally meaningful to people. 

TJ: I'm recommending. 


Board Recommended RFCs

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

Proposed RFCs

(to review, do not require DMCCB approval)

  • RFC-867 - Getting issue details... STATUS
  • RFC-880 - Getting issue details... STATUS
  • RFC-884 - Getting issue details... STATUS
  • RFC-881 - Getting issue details... STATUS







 Adopted RFCs without Triggering issues

(to create implementing DM issues)



Adopted RFCs with all triggered work COMPLETED

(to set status as 'IMPLEMENTED')



RFCs adopted since the last DMCCB

(to review, no action required)

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


RFCs implemented (or withdrawn) since the last DMCCB

(to review, no action required)

  • RFC-885 - Getting issue details... STATUS
  • RFC-869 - Getting issue details... STATUS
  • RFC-874 - Getting issue details... STATUS





Releases

  • Planned
  • Changes to the release schedule



Monitor Jira issues status:

  • the most forgotten 10 DM issues
    • (resolution = Unresolved ORDER by updated asc)
  1. DM-16348 - Getting issue details... STATUS
  2. DM-18360 - Getting issue details... STATUS
  3. DM-17050 - Getting issue details... STATUS
  4. DM-13974 - Getting issue details... STATUS
  5. DM-6391 - Getting issue details... STATUS
  6. DM-18427 - Getting issue details... STATUS
  7. DM-18432 - Getting issue details... STATUS
  8. DM-18429 - Getting issue details... STATUS
  9. DM-18040 - Getting issue details... STATUS
  10. DM-18487 - Getting issue details... STATUS


Unresolved issues: 4224



Open Actions



AOB 



Next DM-CCB 2022-11-16


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
  • Tim Jenness investigate astropy warnings filter for tests.
05 Oct 2022Tim JennessDMCCB#142 (2022 - 09 - 28)
  • Tim Jenness  to write a policy on how external code written by DM shall be handled.
Tim JennessDMCCB#51 (2020 - 05 - 27)