Easy one first: the current RFC process looks to be documented in the README.md of the RFCs repo:

Though we are still awaiting our official first submission and Vince is on vacation.

Could you be a more explicit about what you see that rises to the level of an RFC? Are these establishing new patterns and protocols for interoperability of modules? Would you think of them as FOLIO infrastructure?

I would expect the password management (bad password lists, etc.) will be part of mod-login and will have to not interfere with SSO, so that could be a consideration. And for sending email, mod-notify would seem to be what is needed (or the non-yet-extant mod-notification that Mike Taylor referred to last week) and would be common infrastructure for use by many modules.

The RFC process is very new, not yet tested. I don't yet have a feel for how we apply it, so want to be explicit.

-Tod

On Jul 23, 2018, at 10:50 AM, Jakub Skoczen <jakub@indexdata.com> wrote:

TC,

Khallah, who is the PO for the new EPAM team, is looking for reviewers to review technical designs that her team plans to follow. Currently, there are two areas to review:

1. Password management (Rules, Blacklist, Reuse) UIU-499, UIU-509, UIU-510

2. FOLIO E-mail sender module UIU-568

I have pointed at several folks from the core team that might help and others volunteered their input through Jira. Given, however, that the TC have established the RFC process I propose we use this more formalised approach for requesting reviews. Would that make sense? If so, do we have documentation of the RFC process that we could point the EPAM developers at? Finally, once RFC documents are prepared, how would we assign reviewers (I can't recall we discussed this though I had to skip the TC meeting last week)?

--
Regards,

Jakub Skoczen

To unsubscribe from this list please go to http://www.simplelists.com/confirm.php?u=GzifSquIJCjuDCxXBWbjN0P4Uc6E51Jd