Meeting Notes: 2023-06-14 #351

Sephsekla · 2023-06-21T14:41:03Z

Sephsekla
Jun 21, 2023
Maintainer

Note
Meeting agenda: #349
Slack discussion: https://wordpress.slack.com/archives/C2K1C71FE/p1686754838505239

A really positive event for the project, we have a lot of new contributors and additional awareness of its aims!
Several new issues added to the repo during the event.
Both the survey and redesign work (below) came out of the Contributor Day.

There was some discussion during the meeting around visibility; several new contributors were not aware of the project before the Contributor Day. How can we address this as the project?
@Sephsekla to work to post more on the Make Core blog, with both meeting notes and other updates
How else can we promote the project? Potentially work with other media, e.g. news sites and podcasts.
Everyone is encouraged to spread awareness, this doesn't need to be @Sephsekla's area only.
Hopefully the upcoming survey will spread awareness as well.

At WCEU Contributor Day, @EdithAllison worked on a survey on the current notices/notifications experience within WordPress.
This can inform our direction/user stories.
It will also provide potential marketing stats, and raise awareness of the project.
Some concerns around data and GDPR, do we want to collect emails to follow up?
The consensus is that this should be removed, it's largely unnecessary and adds unnecessary risk.

At WCEU Contributor Day, Nick put together an updated design based on the idea of Design System #253.
Designs at https://www.figma.com/file/sC0QzxbY1Azm6wtc2X6bXV/WP-Notify-design-blueprints-i6-(by-Nick-Heurter)?type=design&node-id=158%3A105&t=kODRNurZMamE3Fbz-1
This better integrates and builds upon existing WP Core components.
It should make maintenance easier, as well as better fitting with the ongoing development of the Dashboard.
This lead to some discussion about how we will handle notifications which are important but ephemeral - do we want to introduce some kind of toast component to the system?

In Split this project between the API and Hub #339 @dartiss proposed splitting the project, with the data model and API in one feature plugin and the hub in another.
This would allow easier adoption of the new API without finalising the UI for the dashboard
However there are some concerns about how to handle display if we don't include the new UI by default
The hub could be the default solution, but pluggable and easily disabled, so any custom solution can take over with the same API calls (e.g. Calypso).

We have a number of A11y tickets open at present.
It would be good to have a full audit of the UI before we continue much further, to ensure we are fully accessible from launch.
This would be a good opportuniy to work with the Accessibility Team.

@johnhooks had previously recommended reducing the scope of the endpoints for our next release.
However with the addition of new contributors, this may no longer be necessary.
@EdithAllison is now also working on the REST endpoints, so we will process on all of them and reevaluate as necessary.