Weekly GitHub Report for Monica: 03 October, 2024 to 10 October, 2024

Weekly GitHub Report for Monica

Thank you for subscribing to our weekly newsletter! Each week, we deliver a comprehensive summary of your GitHub project's latest activity right to your inbox, including an overview of your project's issues, pull requests, contributors, and commit activity.

Table of Contents

I. Issues 1.1. Open Issues 1.2. Top 5 Active Issues 1.3. Top 5 Quiet Issues 1.4. Closed Issues

II. Pull Requests 2.1. Open Pull Requests 2.2 Closed Pull Requests 2.3 Pull Request Discussion Insights

III. Commits 3.1. Commits

IV. Contributors 4.1. Contributors

I. Issues

1.1 Open Issues

Open Issues This Week: 2

Summarized Issues:

- **Account Deletion**: This issue addresses the inability to delete an account that was registered through Github on the Monica platform.
  - [github.com/monicahq/monica/issues/7398](https://github.com/monicahq/monica/issues/7398)

- **App Version Availability**: This issue discusses the availability of an app version for the GitHub project and the consideration of building additional features if one does not exist.
  - [github.com/monicahq/monica/issues/7399](https://github.com/monicahq/monica/issues/7399)

1.2 Top 5 Active Issues:

We consider active issues to be issues that have generated much discussion in the issue's comments.

1. [Chandler] Setting QUEUE_CONNECTION to redis causes Chandler not working: This issue is about a bug where setting QUEUE_CONNECTION to redis causes Chandler to not work properly, as the dispatched jobs to the queues are not executed. The user has to change QUEUE_CONNECTION to sync to get Chandler working, including sending email notifications.

   • The comments discuss the issue further, with one user confirming that the problem also occurs when using MariaDB, while another user mentions that using Redis locally with docker-compose causes certain defaults to not be added. Another user mentions using Redis locally without any issues and suggests that if there is an issue, it might be related to Laravel.
   • Number of comments: 4

2. AI Chatbot support for Q&A and Actions, aka ChatGPT for Monica: This issue is a feature request for AI Chatbot support for Q&A and Actions, specifically requesting the integration of ChatGPT into Monica to enable a chat interface for tasks such as asking questions about contacts and performing actions via text.

   • The comments on this issue discuss the feasibility and potential challenges of implementing AI Chatbot support, including considerations around privacy, token usage, and the need for pseudo-functions to enable reasoning loops for complex requests.
   • Number of comments: 3

3. Inconsistent password requirements: This issue is about inconsistent password requirements in Monica v5, where the same password is accepted for an admin account but rejected for a user account. The user encountered an error message stating that the password may only contain letters, numbers, and dashes.

   • The comments section consists of a user asking how the admin account was created, another user explaining that they registered through /register, and a third user mentioning that the issue might have been fixed recently.
   • Number of comments: 3

4. How do I increase storage on Chandler beyond 50MB? [Selfhosted]: This issue is about a user self-hosting Chandler on their own hardware using Docker and wanting to increase the maximum storage from 50MB to unlimited storage.

   • The comments on this issue revolve around clarifying that this is a question that should be asked in Discussions rather than being treated as an issue. Additionally, a suggestion is provided on how to update the storage limit for an existing account directly via SQL for self-hosted instances.
   • Number of comments: 3

5. Support "unlimited" storage in Chandler: This issue is about requesting support for "unlimited" storage in Chandler, specifically discussing the interpretation of setting the storage limit to "0" in Monica 5.x.

   • The comments in the interaction discuss verifying the interpretation of setting the limit to "0" in the .env.example file, the difference in behavior between versions 4 and 5, and the approach taken in the code to interpret 0 as no limits and the need to update the UI to reflect this.
   • Number of comments: 3

1.3 Top 5 Quiet Issues:

We consider quiet issues to be issues that have been opened in this project for the longest time. The team should work together to get these issues resolved and closed as soon as possible.

1. [Chandler] No option to create a role in groups (yet): This issue pertains to the lack of an option to create a role in groups within the Chandler project on GitHub. Users are unable to create roles for contacts within a group, leading to a limitation in functionality for managing group roles effectively.

The bug description highlights the presence of a field for roles of a contact in a group, but the inability to actually create such a role either when creating a group or adding a contact. This issue has been open for 345 days, 22 hours, and 49 minutes on the self-hosted instance of the project. - Open for 345 days, 22 hours, 49 minutes

1. AI Chatbot support for Q&A and Actions, aka ChatGPT for Monica: This issue is a feature request for adding AI Chatbot support for Q&A and Actions, specifically ChatGPT integration for Monica. The user is requesting a chat interface that can perform tasks such as asking questions about contacts and adding notes to contacts via text.

The user has considered alternatives such as building the feature as a Chrome extension or manually executing it within ChatGPT, but highlights the downsides of these approaches. They are seeking feedback and interest from other users by asking them to use the 👍 reaction and to refrain from commenting if they have no relevant information to add. - Open for 328 days, 13 hours, 22 minutes

1. Monica API: occupation and company are not visible: This issue pertains to a bug in the Monica API where the occupation and company information is not visible in the user interface, despite being linked through the API endpoints.

The bug has been open for 325 days, 22 hours, and 26 minutes, and the user expected to see the occupation in the overview page of a person under work information in the Monica v4 application. - Open for 325 days, 22 hours, 26 minutes

1. Undefined in post title input as default: This issue pertains to a bug in the GitHub project where the title input defaults to 'undefined' in both Regular and Inspirational post creation, leading to unexpected post additions even when no content is provided in the title field.

This issue has been open for 325 days, 14 hours, and 38 minutes, and it specifically addresses the issue of the title input defaulting to 'undefined' in post creation, causing posts to be added unexpectedly without proper title input. - Open for 325 days, 14 hours, 38 minutes

1. Inconsistent password requirements: This issue pertains to inconsistent password requirements within the Monica v5 project, where the same password is accepted for an admin account but rejected for a user account, causing confusion and inconvenience for users. The issue has been open for 320 days, 01 hours, and 33 minutes, highlighting the importance of aligning password requirements for both admin and user accounts to ensure a seamless user experience.
   • Open for 320 days, 01 hours, 33 minutes

1.4 Closed Issues

Closed Issues This Week: 1

Summarized Issues:

- **Deletion of AddressType**: When attempting to delete an AddressType, an error occurs due to the incorrect service class being imported, preventing the deletion process from being completed.
  - [github.com/monicahq/monica/issues/7365](https://github.com/monicahq/monica/issues/7365)

1.5 Issue Discussion Insights

This section will analyze the tone and sentiment of discussions within this project's open issues within the past week to identify potentially heated exchanges and to maintain a constructive project environment.

Based on our analysis, there are no instances of toxic discussions in the project's open issues from the past week.

II. Pull Requests

2.1 Open Pull Requests

Open Pull Requests This Week: 4

Pull Requests:

• SVG icons converted to components: This pull request involves converting some svg icons code to components in the Monica project. This change aims to improve code organization and reusability by turning the svg icons into reusable components.
  • github.com/...

• SQL query issue fix for first_name field: This pull request addresses an issue where a single quote in the first_name field was causing the SQL query to break in MariaDB. The fix ensures that special characters are properly handled in the database queries.
  • github.com/...

• Login process validation: This pull request introduces validation for navigation through the login process in the Monica project. By adding validation, the user experience is enhanced with clear feedback and error handling during the login process.
  • github.com/...

• Overflow menu button for mobile view: This pull request implements an overflow menu button for the mobile view in the Monica project. The addition of this button allows for better navigation and access to additional options on smaller screens.
  • github.com/...

2.2 Closed Pull Requests

Closed Pull Requests This Week: 4

Summarized Pull Requests:

• Fixing deletion of AddressType: This pull request fixes the issue with deleting address types in the Monica project.
  • github.com/...

• Fixing 'can_be_deleted' property in ContactInformationType object: This pull request fixes the issue of 'can_be_deleted' property in ContactInformationType object always being null after record creation by allowing deletion of contact information types without refreshing the page.
  • github.com/...

• Upgrading dependencies: This pull request is about upgrading dependencies in the Monica GitHub project.
  • github.com/...

2.3 Pull Request Discussion Insights

This section will analyze the tone and sentiment of discussions within this project's open pull requests within the past week to identify potentially heated exchanges and to maintain a constructive project environment.

Based on our analysis, there are no instances of toxic discussions in the project's open pull requests from the past week.

III. Commits

3.1 Commits

Commits This Week: 3

Summarized Commits:

• Bug Fixes: Several commits address various bugs in the project, such as fixing the deletion of contact information types without page refresh, addressing issues with deleting AddressType, and resolving other reported bugs.
• Dependency Upgrades: Commits focus on upgrading project dependencies to ensure compatibility with the latest versions and improve overall project stability.
• Performance Optimization: Changes are made to optimize the performance of the project, including removing redundant bounds checks, improving dispatch efficiency, and enhancing the speed of certain functions.
• Code Refactoring: Commits involve refactoring code to improve readability, maintainability, and overall code quality, such as restructuring functions, renaming variables, and simplifying complex logic.
• Feature Implementation: New features are implemented in the project, adding functionality like user authentication, data visualization tools, and enhanced search capabilities.
• Documentation Updates: Commits involve updating project documentation, including README files, code comments, and developer guides to provide clearer instructions and information for users and contributors.
• Testing Enhancements: Changes focus on enhancing testing procedures, including adding new test cases, improving test coverage, and ensuring the reliability of automated tests.
• Security Fixes: Commits address security vulnerabilities in the project, such as fixing authentication issues, preventing SQL injection attacks, and implementing secure coding practices.
• User Interface Improvements: Changes are made to enhance the user interface of the project, including updating styles, improving accessibility, and optimizing layout for better user experience.
• Database Schema Changes: Commits involve modifying the database schema, such as adding new tables, altering existing columns, and optimizing queries for improved performance.
• Error Handling: Changes are made to improve error handling in the project, including adding error messages, handling edge cases, and providing graceful fallback mechanisms.
• Localization Support: Commits focus on adding support for multiple languages and regions in the project, including implementing translation features and adapting content based on user preferences.
• Code Cleanup: Commits involve cleaning up the codebase, including removing dead code, eliminating unused variables, and organizing imports for better code hygiene.
• Logging Enhancements: Changes focus on improving logging mechanisms in the project, including adding more detailed logs, capturing error traces, and monitoring system behavior.
• Accessibility Updates: Commits involve updating the project to meet accessibility standards, such as improving keyboard navigation, adding alt text to images, and ensuring compatibility with screen readers.
• Configuration Changes: Commits involve modifying project configurations, such as adjusting environment variables, updating settings files, and managing dependencies for different deployment environments.
• Code Reviews and Collaboration: Commits reflect collaboration efforts, including code reviews, feedback incorporation, and teamwork to enhance project quality and foster a collaborative development environment.
• Performance Monitoring: Changes involve implementing performance monitoring tools, profiling code execution, and analyzing resource usage to identify bottlenecks and optimize performance.
• Version Control Management: Commits focus on version control management, including branching strategies, merging changes, resolving conflicts, and ensuring code consistency across the project.
• Continuous Integration/Continuous Deployment (CI/CD): Commits involve setting up CI/CD pipelines, automating build processes, running tests automatically, and deploying changes to production environments seamlessly.
• Feature Deprecation: Commits involve deprecating certain features in the project, such as removing outdated functionalities, replacing legacy code with modern alternatives, and streamlining project scope.
• Third-Party Integration: Changes involve integrating third-party services or APIs into the project, such as adding authentication providers, payment gateways, or data analytics tools for enhanced functionality.

IV. Contributors

4.1 Contributors

Active Contributors:

We consider an active contributor in this project to be any contributor who has made at least 1 commit, opened at least 1 issue, created at least 1 pull request, or made more than 2 comments in the last month.