-
Notifications
You must be signed in to change notification settings - Fork 14
CWG 2023 03 24
👋 Hello! Today, David and Italo had the first meeting of the HerbsJS working group. They discussed several topics related to the project's short and long-term goals. Let's go over what was discussed:
David introduced the working group, explaining that it will be a monthly meeting to discuss the short term roadmap for the HerbsJS project and make small project decisions. He also mentioned that, as the project evolves, requirements are coming from new stakeholders, not just Vórtx. They agreed that more people should be invited to the working group, including MagIT devs. Since people aren't checking Discord frequently, they discussed creating a WhatsApp group with a link to the Discord channel or sending reminders about the meeting.
David shared that he has been working on HerbsJS to reinforce how it can help with the maintainability of a project, based on conversations he had with other CTOs. The focus is to bring more information about the infrastructure on the Shelf. He's currently working on Herbs2REST so it can generate metadata that can be used on Shelf to show how to call a use case from a REST endpoint. The next step will be to do the same for Herbs2GraphQL. Revisiting Herbs2REST has been interesting and might culminate in a big refactoring. Once it's done, David plans to "sell" HerbsJS to some CTOs and consultancies companies (like MagIT).
David suggested that they should start thinking about the long term and discuss how they see HerbsJS in the next 5 years. They agreed that all people in the working group should participate in this discussion, either asynchronously or in the next meeting.
Italo and David discussed SemVer and how they don't currently have control over the major part of the release (V2, V3). This can be problematic since a small PR can create a new major version automatically, losing the opportunity to market the new version with a press release. They also talked about accommodating multiple versions (like 'official', 'beta', 'alpha') and agreed that a roadmap for each release would be beneficial. Italo shared that he is close to the official node.js process and working group responsible for it and will bring alternatives for this problem.
The working group discussed the importance of having an official blog for HerbsJS. They agreed that it would help market the ideas behind the project, inform users about new releases, and communicate in a more human-friendly voice. They discussed whether to use an internal blog (like Ghost on blog.herbsjs.org) or an external platform like Medium, Substack, or DevTo. They acknowledged that Medium has the advantage of disseminating and suggesting posts to users of the platform, but it has a paywall. They decided to create content about Herbs on their personal accounts to see which platform brings more attention.
Italo mentioned that they could use more AI to help developers on other use cases. They agreed to keep bringing up this subject in the next meetings.
David brought up that they should update the node version for HerbsJS in general to version 18. They agreed to make the update by the end of Q1.2023.
If you couldn't participate in the meeting, feel free to comment here. The working group would be happy to discuss it with you. Also, they hope to see you in the next meeting!