Merge pull request elizaOS#3484 from YoungPhlo/docs/contributor-meetings

docs: Add weekly contributor meeting notes (2025-02-04 + 2025-02-11)

docs/community/Contributors/weekly-contributor-meeting/2025-02-04.md

@@ -0,0 +1,44 @@
+---
+title: "Weekly Contributor Meeting Notes"
+date: 2025-02-04
+description: "Discussion on API key management, plugin architecture changes, code review tools (Windsurf, Graphite, CodeRabbit), and database adapter standardization. Key decisions on version numbering and plugin repository separation."
+---
+
+# Weekly Contributor Meeting Notes
+
+(February 4, 2025 4:00 PM PST)
+
+**Navigating API Keys, Plugin Re-Arch, and Database Adapter Standardization**
+
+
+## Summary
+
+**Action Items:**
+
+*   Troubleshoot the "Merge Queue" issue for forked repositories.
+*   Continue efforts to standardize on Biome and clean up ESLint configurations in older plugins.
+*   Thoroughly test database adapters in conjunction with knowledge base changes.
+*   Investigate and potentially implement consolidation of adapter code (using an ORM like Drizzle).
+*   Spin up a new copy of the Eliza website and configure the domain.
+*   Await updates on the plugin re-architecture effort (moving plugins to separate repos).
+*   Provide OpenAI key to Yags, and figure out a plan for providing keys for testing and development.
+*   Fix the minify script to omit specific files that cause GitHub warnings (related to smart contract code).
+*   One contributor to check in with a colleague who was focusing on an AWS Docker setup.
+*   One contributor to ping Jin for an open router key.
+
+**Main Discussion Points:**
+
+*   **Runtime Error Detection and API Keys:** The meeting began with a discussion about the importance of running code in runtime to catch errors that static analysis might miss. A key issue raised was that many plugins rely on API keys, and if a user lacks credits or a valid key, actions won't execute, making it difficult to test and debug properly. The idea was brought to know and fix coding errors even before actions take place.
+*   **Code Review Tools:** Several code review tools were discussed:
+    *   **Windsurf:** A PR reviewer tool from the Codeium team, still in beta (and therefore free). It was suggested as a potential tool for reviewers, and even the possibility of creating a VSCode extension to integrate it was raised.
+    *   **Graphite:** Another tool mentioned, with a CLI for creating PRs locally and integration with VS Code. It was noted that Graphite, along with CodeRabbit, had been helpful in catching typos in PRs.
+    *   **CodeRabbit:** Another tool that was mentioned as a helper for making PRs.
+*   **Merge Queue:** A contributor had trouble getting their PRs merged and was advised to use the "Merge Queue" label to add PRs to the merge queue. Troubleshooting was needed as the contributor encountered an error related to forked repositories.
+*   **Biome vs. ESLint:** There was a discussion about the transition from ESLint to Biome for code linting and formatting. The contributor confirmed that new contributors should be using Biome, but acknowledged that some older plugins might still have ESLint configurations due to copying from existing plugins. The importance of cleaning up and standardizing on Biome was emphasized.
+*   **New Features and Adapters Testing:** The team discussed how new features can affect adapters and that there is a necessity to test all adapters with the new knowledge before deploying the tool. It was mentioned that PG family and Vector family adapters should have their own classes.
+*   **Database Adapter Standardization:** Concerns were raised about the knowledge base changes and their potential impact on database adapters (SuperBase, PG, Light, Quadrant, etc.). The need for thorough testing and alignment of adapters, especially those related to Postgres (PG), was stressed. A proposal was made to consolidate and standardize adapter code, potentially using an ORM (like Drizzle, which was mentioned as a good option).
+*   **Version Numbering Change:** The team decided to change the version numbering scheme to reflect the year and week of release (e.g., 0.25.6 for year 2025, week 6).
+*   **Graphite Integration:** A contributor requested access to the Graphite app within the Eliza OS organization, and it was confirmed that the integration was likely already in place.
+*   **Plugin Re-architecture:** A high-priority task was reiterated: moving plugins to separate repositories (outside the main Eliza OS repo). This is a major architectural change, and the team is awaiting an update from the group working on this. The intention is for each plugin to reside in its own repo and be discoverable via GitHub tags. Concerns were raised about how this shift might affect community contributions, and how tags must be properly handled.
+*   **Eliza Website (eliza.gg, elizas.com):** The website was down, and a contributor volunteered to spin up a new copy. There was a discussion about domain names, and a contributor offered to provide access to `eliza.xyz` via Cloudflare.
+*   **OpenAI Key:** One of the contributors asked for an OpenAI Key.

docs/community/Contributors/weekly-contributor-meeting/2025-02-11.md

@@ -0,0 +1,48 @@
+---
+title: "Weekly Contributor Meeting Notes"
+date: 2025-02-11
+description: "Discussion on Discord server consolidation, v2 development progress including local AI plugin improvements, upcoming Hong Kong promotional events, and new plugin registry system implementation. Updates on v2 release timeline targeting April."
+---
+
+# Weekly Contributor Meeting Notes
+
+(February 11, 2025 4:00 PM PST)
+
+**Local AI Progress, Discord Changes, and Hong Kong Events**
+
+
+## Summary
+
+**Action Items:**
+
+*   Fix contributor roles and permissions on the Eliza OS Discord server.
+*   Inform contributors about the server migration and provide instructions.
+*   Work on the local AI plugin in the v2 development branch, improving its functionality and performance.
+*   Coordinate with the team member attending the Hong Kong events to provide promotional materials and messaging.
+*   One team member will start looking into the v2 develop branch.
+*   Continue development and testing of v2, aiming for the April release target.
+*   Review the v2 develop branch and become familiar with the codebase.
+*   Create a better marketing campaign to promote calls.
+
+**Main Discussion Points:**
+
+*   **Discord Server Consolidation:** The team discussed the need to consolidate their development communication to the official Eliza OS Discord server. Currently, there are two servers in use, causing confusion. The goal is to migrate everyone to the Eliza OS server, which requires setting up appropriate roles and permissions (like a "contributor" role) and informing contributors.
+*   **V2 Development and Local AI Plugin:** A major focus was on the development of version 2 (v2) of Eliza OS.
+    *   AIFlow agreed to join the V2 team.
+    *   The team discussed needed improvements, one of which was the "local AI plugin". The plan is to move the existing local AI functionality from the "plugin node" into the main system of v2, improve its performance, and ensure feature parity with the current Eliza version.
+    *   There are some small, well-performing models that do not require outside dependencies.
+    *   The v2 development branch already includes some working plugins (OpenAI, Anthropic), but the local AI plugin needs significant work.
+*   **Hong Kong Trip and Promotion:**
+    *   One team member will be attending events in Hong Kong and plans to promote Eliza OS.
+    *   The individual spoke with someone from Google's Web 3.0 development division that may be able to provide Eliza support and exposure.
+    *   There are plans to create and distribute Eliza OS t-shirts at an event.
+    *   The team member requested clear messaging and information about v2 to share with people, as there's high interest in the new version.
+*   **Plugin System and Registry:**
+    *   The team discussed the new plugin system and registry.
+    *   A new repository called "Eliza OS Plugins" has been created to house official plugins.
+    *   A separate "Registry" repository contains an `index.json` file that acts as a directory of all available plugins and their GitHub locations.
+    *   This new system allows plugin developers to maintain their own plugins without relying on the core Eliza OS team for merging and code reviews.
+    *   A command-line utility has been created to simplify plugin installation for v1.
+*   **V2 Release Timeline:**
+    *   The team is still aiming for an April release of v2.
+    *   There's a desire to have v2 ready for a major convention in Dubai (April 25th - May 1st), but no promises were made.