LVGL Definitions - Changing kconfig options to match LVGL. Whether or not kconfigs are considered APIs or not (have not historically treated as APIs)
[Anas] Different levels of kconfig - those that are visible to users and those below the surface (e.g. dependencies). Concerns about kconfigs changing that would change the logic. The tooling that we have would provide some safety net - if something has been renamed, we would have an error.
[Carles] Problem is where do you draw the line? Has to be case-by-case
[Anas] Recommend having general guidelines
[Kumar] Haven’t looked, but there could be GitHub Action logic that exists?
Next step: create general guidelines in an upcoming meeting
UX Study [Maureen]
Next step: Recommend addition to a roll-up GitHub Issue. If we feel something is already addressed, we can mark it as done