Happy new year everyone! I've been bad at creating meeting notes for our meetings, but with this email I'm hoping to make a change in that area :D

Today we had our first status meeting of the year, and we used the 30 minutes to focus on where things are in the organization and what our focus should be for the catalog team. Here are some highlights:

The broader Monday meeting will be shifting focus to generating webinars for the upcoming events around the UN
In December, Dinesh and Anindita created a deck that described the next architecture of our catalog. This makes use of Github on the backend, and primarily a CLI for the user. Dinesh will send along this deck shortly.
We've been meeting regularly with other teams who are interested in ENS, primarily the "bee" and "satellite" folks. Our purpose is to see how our catalog (or generally similar tool) could be of use within their use case. The issue with this process seems to be that the catalog doesn't seamlessly fit. The investigation to find product-"project"-fit (rather than product-market-fit) is ongoing, but we realize this may be an inefficient use of time.
We discussed more broadly where the catalog could fit within the broader market. We agreed that there is too much competition in the training area, and that we likely need to remain simple and provide a service that doesn't yet exist if we want to be more successful at marketing the tool to a broader range of customers.
Defining standards around inference training and that service's communication with the catalog and the broader system could be a viable way to approach creating the catalog. Our catalog could be the initial implementation of a standard that we define. We discussed our previous work in other industries around this and agree there were similarities between that work and possibilities here.

Thanks to all who attended, and the next time we meet will likely be in the Monday call (let us know if you need an invite).

Josh Purcell

Senior Solution Architect, Redpanda