Leanne Guy can you clarify what this RFC is requesting please? I see a ticket branch but no content and so there is nothing to review. Are you asking permission to start working on the changes you note in the description?

I thought an RFC wass needed for all changes to LDM documents

Yes. An RFC is required for all LDM documents before we send them to LCR. That does require the DMCCB be able to read the proposed text. A RFC asking permission to start making changes is fine but usually that would be for something that involves a lot of changes that might be contentious. RFC-771 is an example of that where we had the discussion and decided that Gregory Dubois-Felsmann could move forward with updating the document. We debated whether the RFC should be accepted and a new one created when the actual text changes appeared and decided we would keep it open. We don't want people to spend weeks working on a proposed change to an LDM only to have CCB reject it immediately.

In this case the proposal is to update the document to reflect current reality (similarly RFC-856) and is not going to be contentious. A 6 day proposed debate period suggested to me that you had some text in mind and I didn't find any on the branch. I'm fine with proceeding with this as a pre-approval and then having a new RFC to look at the text if that is what you want.

We do not need to send LDM documents to LCR

Relevant pull requests:
https://github.com/lsst/LDM-503/pull/94
https://github.com/lsst/LDM-503/pull/93
https://github.com/lsst/LDM-503/pull/92

Thanks. I'm not sure what I was thinking about LCRs. I was confused by the ticket branch showing no changes so thanks for pointing out that all the changes were done in previous tickets.

Those changes look okay to me (organigram and organogram seem to both be allowed according to my dictionary).

As discussed by DMCCB I am board recommending.