API Meeting Minutes

[nashif]

Minutes from the API meeting...

[nashif]

March 23rd 2021 Meeting:

• NOSYS vs ENOTSUP RFC: clarification and standardization of ENOTSUP/ENOSYS error returns #23727 (comment)
• I2S API: Add I2S driver for LPC devices  #32054 (comment)

[carlescufi]

2021.03.30:

• KConfig experimental feature: kconfig: add support for warnings when using experimental features #33566 (comment)
• FlexSPI: Introduce i.MX RT FlexSPI HyperRAM driver #33602 (comment)
• PinCTRL Started discussion about pinctrl again: Introduce pinctrl API to support pinctrl dts nodes #22748 (comment)

[carlescufi]

2021.06.04:

• Dictionary-based logging: Add support and sample backend for dictionary-based logging #30539 (comment)
• Doxygen warnings and #ifdef __DOXYGEN__: doc: fix multiple Doxygen and breathe problems #33972 (comment)

[mbolivar-nordic]

Why are we doing this here? This is inconsistent with other meetings that track minutes in a Google doc and may confuse external observers.

[carlescufi]

For consistency with the rest of the meetings, closing this in favor of:
https://docs.google.com/document/d/1lv-8B5QE2m4FjBcvfqAXFIgQfW5oz6306zJ7GIZIWCk/edit#

[nashif]

Why are we doing this here? This is inconsistent with other meetings that track minutes in a Google doc and may confuse external observers.

yeah, that was the original ask, have minutes in general, but then the idea of google docs for the API meeting was not appealing for some... :)

[mbolivar-nordic]

yeah, that was the original ask, have minutes in general, but then the idea of google docs for the API meeting was not appealing for some... :)

I can totally sympathize with that; I write minutes in my editor and then copy them into Gdocs later. I just think we should be consistent until we can all agree on an alternative.