Weekly GitHub Report for Monica: 04 October, 2024 to 11 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 for GitHub Project**: 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 how the issue also occurs when using MariaDB, the success of using Chandler with Redis locally, and a suggestion to open an issue on Laravel if there is a problem.
   • Number of comments: 4

2. AI Chatbot support for Q&A and Actions, aka ChatGPT for Monica: This issue is a feature request for adding AI Chatbot support, specifically ChatGPT, to Monica in order to enable Q&A and actions within the platform. The user is suggesting the implementation of a chat interface that can answer questions about contacts and perform tasks via text, such as adding notes or summarizing relationships.

   • The comments on this issue discuss the feasibility and potential challenges of integrating AI Chatbot support, such as the amount of data that would need to be sent to the language model, the cost implications, and the possibility of mitigating these issues by giving the model pseudo-functions to run and allowing for reasoning loops.
   • 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 mentioning that they registered through /register before but encountered the same password rejection issue, and speculating 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 suggest that the user should ask this question in Discussions as it is not an issue. Additionally, it is mentioned that while there is no way to increase storage limit via the web UI, users can directly update the storage limit for existing accounts by running SQL queries on the database if self-hosting.
   • Number of comments: 3

5. Support "unlimited" storage in Chandler: This issue is about supporting "unlimited" storage in Chandler by allowing a user to have unlimited storage by setting the limit to -1, as setting it to "0" is not interpreted as infinite in Monica 5.x. An alternative solution suggested is setting an incredibly high number for the limit, but a more explicit option would be preferred.

   • The comments on this issue mainly revolve around clarifying that setting the storage limit to 0 in Monica actually means unlimited storage, as indicated in the .env.example file and the codebase. There is also a discussion about updating the UI to display "Unlimited" instead of 0 for better clarity.
   • 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. 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.

   • Open for 346 days, 17 hours, 53 minutes

2. AI Chatbot support for Q&A and Actions, aka ChatGPT for Monica: This issue is a feature request for AI Chatbot support in Monica, specifically for Q&A and Actions, such as asking questions about contacts and performing tasks via text. The requester is seeking to enhance the user experience by integrating ChatGPT capabilities into the platform to streamline interactions and automate certain processes.

   • Open for 329 days, 08 hours, 26 minutes

3. 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 created and linked through the API on app.monicahq.com.

The bug description outlines that the expected behavior is for the occupation to be displayed in the overview page of a person under work information, but this is not currently happening in Monica version 4.0.0. - Open for 326 days, 17 hours, 30 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 326 days, 09 hours, and 42 minutes, and it describes a situation where the title input defaults to 'undefined' in post creation, causing posts to be added unexpectedly without any content provided in the title field. - Open for 326 days, 09 hours, 42 minutes

1. Inconsistent password requirements: This issue pertains to inconsistent password requirements within the Monica v5 platform, where the same password is accepted for an admin account but rejected for a user account, causing confusion and inconvenience for users. The bug description outlines a scenario where a specific password is accepted for an admin account but not for a user account, highlighting the discrepancy in password validation rules between different user roles within the system.
   • Open for 320 days, 20 hours, 37 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 to Components Conversion: This pull request is about converting some svg icons code to components in order to enhance the functionality of the project.
  • github.com/...

• SQL Query Issue Fix: This pull request fixes an issue where a single quote in the first_name field was breaking the SQL query in MariaDB.
  • github.com/...

• Login Process Validation: This pull request adds validation for navigation through the login process in the Monica project.
  • github.com/...

• Mobile View Overflow Menu Button: This pull request adds an overflow menu button for mobile view in the Monica project.
  • 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 of 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 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 issues with deleting contact information types without page refresh, resolving problems with deleting AddressType, and upgrading dependencies to address known issues.
• Performance Improvements: Commits focus on optimizing performance, including removing redundant bounds checks, improving dispatch optimization, and enhancing the efficiency of certain functions based on profiling observations.
• Code Refactoring: Multiple commits involve refactoring code to improve readability, maintainability, and overall code quality, such as restructuring functions, renaming variables for clarity, and simplifying complex logic.
• Feature Enhancements: Development efforts are directed towards adding new features or enhancing existing functionality, such as implementing new contact information types, improving error handling for specific scenarios, and enhancing user experience with updated interfaces.
• Security Updates: Commits address security concerns by updating dependencies, fixing vulnerabilities, and implementing secure coding practices to protect against potential threats and ensure data integrity.
• Documentation Improvements: Several commits focus on enhancing project documentation, including updating README files, adding code comments for clarity, and providing detailed explanations of functions and processes for better understanding.
• Testing and Quality Assurance: Development efforts include writing new tests, improving test coverage, and conducting quality assurance checks to ensure the reliability and stability of the project across different environments.
• Dependency Management: Commits involve managing project dependencies, such as upgrading libraries, resolving conflicts, and ensuring compatibility with the latest versions to maintain a robust and up-to-date codebase.
• Error Handling: Development efforts focus on improving error handling mechanisms, such as implementing proper error messages, handling exceptions gracefully, and ensuring robust error recovery strategies for critical functions.
• User Interface Updates: Commits involve updating the user interface, including enhancing the design, improving accessibility features, and optimizing the layout for better user interaction and overall user experience.
• Code Optimization: Development efforts focus on optimizing code performance, such as reducing memory usage, improving algorithm efficiency, and streamlining processes to enhance overall system performance and responsiveness.
• Database Management: Commits involve managing database operations, such as optimizing queries, updating data models, and ensuring data consistency and integrity for seamless interaction with the application.
• Localization Support: Development efforts include adding support for localization, such as implementing multi-language support, translating content, and adapting the interface for different regions and languages.
• Version Control: Commits involve version control operations, such as merging branches, resolving conflicts, and managing code changes to ensure a smooth and coordinated development process among team members.
• Continuous Integration: Development efforts focus on implementing continuous integration practices, such as setting up automated build processes, running tests automatically, and ensuring code quality checks for every commit.
• Code Review and Collaboration: Commits involve code reviews, collaboration among team members, and feedback integration to ensure code quality, consistency, and adherence to coding standards across the project.
• Performance Monitoring: Development efforts focus on monitoring performance metrics, analyzing bottlenecks, and identifying areas for improvement to enhance overall system performance and optimize resource utilization.
• Accessibility Improvements: Commits involve improving accessibility features, such as adding alt text to images, enhancing keyboard navigation, and ensuring compatibility with screen readers for users with disabilities.
• Data Validation: Development efforts focus on validating user input, sanitizing data, and implementing secure data handling practices to prevent security vulnerabilities, data corruption, and unauthorized access.
• Configuration Management: Commits involve managing project configurations, such as setting up environment variables, updating configuration files, and ensuring consistency across different deployment environments.
• Code Reviews: Development efforts include conducting code reviews, providing feedback, and addressing issues raised during the review process to ensure code quality, maintainability, and adherence to coding standards.
• Feature Deprecation: Commits involve deprecating certain features, removing obsolete code, and cleaning up the codebase to streamline development efforts and improve overall project maintainability.

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.