16. 4th Oct. 2023 (Wednesday)

1. For the Hive, might need to propose that we are not planning any major changes to the Hive. And for the vision, we are planning to pitching the model for achieving the consistency between different products launched by ACCESS-NRI.

2. What we need is more of a model of contributing and what's the plan forward for the all of the services that we provide.

3. For the website and the forum, there needs to be small relationships between these products and have a bit of a plan for giving us a few months on the decision making.

4. V would be hosting weekly meetings for the backend and front-end technologies, and Aiden would be covering the interests of the forum. And she would be giving some presentations and providing feedback.

5. Focus on mainly the Hive and there could be a little bit of other products too. And we can definitely discuss the forum strategy for one or two options look like for this plan includes how collectively we support the operational side of Hive and Forum.

6. For the forum, and we need to pick from Aiden - for the workshop and training events and not answering support model and from the community and there's an event coming up, then we need a little more integration.

7. We could improve the integration between the access-hive and access-hive forum and have someone to think across.

8. For the structure, should we have a meeting monthly with V and have the integration for all the workshops. And if you don't have an event, and we don't have such workflow and structure and we need that.

9. We really need to know of which content should go on one and which content should go on other website.

10. Main website, Hive and the forum are the three things are the official of how we prototype on the web. The representatives from these are sent into the Hive meetings, and we sync the changes across.

11. Discuss the higher level changes and flag for review and approval and we just don't want that happening too frequently.

12. We need to have the forum connected, and if there are things that are gonna change, then they can talk to the Hive meeting.

13. And the vision for these 3 to keep them neat them together.

14. Let's consider the three main websites and the path forward for the three main websites, and if it were to be the one kind of thing. And whether these three should be using the same platform and V could help with that.

15. We should put in place a workflow and have a monthly meeting where all of the different areas will have their representatives (including V who would be a coordinator), so that we know we are up to date with the work we do. And if there is something to be done together and something that has to be changed, and then we discuss that.

16. If we set a workflow like that, then it should be really easy to follow.

17. Long term vision - How should we design the tech stack for these applications.

18. Short term vision - Talking of the continuous content that needs to be changed. No event there at all - like adding documentation and release of a new configuration, we discuss how do we wanna advertise that.

19. Representatives come in the monthly meeting and there would be things that need to be covered in a month. And we need to discuss the changes together.

20. Spontaneous changes need to be communicated properly, and do more events and event processing and need to be aware from there. And little bit of process in everything we communicate to other teams and follow the scope of the meeting and the change of having an operating.

21. The communication strategy - Natalia would be integrated and we need to share the checklist of what things are changing.

22. And people should be aware of the changes made on the Hive and V should be over sighting that.

23. Contributing resources in the team and how people should get involved. And if you have new content, then you can add it on the Hive. And people should feel like they have a way to contribute.

24. Have a simple flowchart or something for the workflow and we can pitch that in the release meetings.

25. Meeting with Aiden and make sure for the forum responsibilities and just event what's the right thing to bring to the meeting. And what kind of ideas to bring to these meetings and creating new categories that match a particular event or activity. And the permissions could be a nice way to capture it and what community can't normally do on their own.

26. Creating examples of few sequences, - new content on the Hive and the new event and that sits somewhere for people to look into. Meetings with the vision meeting and we put forward our proposals of our examples.

27. It's an action that's completed after the meeting, and you are pitching the best option, and you get feedback and action from that meeting is that we are going to that finalised decision.

28. We need to have the support of team leads and forming this plan and set this up for the best access and everyone is on the same page and where you are pitching the operational plan for the Hive.

29. The assumption here is that for the next 6 months, we are going with these three services and that's really set the expectations for us as well and have some clear guidance of how people make changes to the documentation.

30. Training, MED needs to come there and we want anyone to work with the Hive and have the workflows set up.

31. Here's the model that we think works and if you are clear of how to get some basic workflows set up of we wanna go forward and for broader teams.

32. You get a question about whether I am a part of the team and how the workflow of the meeting should go.

33. And the week of 24th and gives a little bit more time up to speed and chat about what things are the core bits to be prepared.