Weekly GitHub Report for Monica: October 18, 2024 - October 25, 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. Top 5 Active Issues
  • 1.2. Top 5 Stale Issues
  • 1.3. Open 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 Top 5 Active Issues:

We consider active issues to be issues that that have been commented on most frequently within the last week.

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 observation of missing default templates when using Redis locally, and a suggestion to open an issue on Laravel if there is a problem with using Redis.
   • Number of comments this week: 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 user suggests alternatives such as building it as a chrome extension or manually executing it within ChatGPT.

   • The comments discuss the feasibility and challenges of implementing the requested feature, including concerns about the amount of data that would need to be sent to the language model, potential costs, and suggestions for mitigating these issues by giving the model pseudo-functions to run and allowing for reasoning loops.
   • Number of comments this week: 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 three interactions where the user asks how the admin account was created, another user mentions creating the admin account through /register, and a third user notes that the issue might have been fixed recently.
   • Number of comments this week: 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 user initially asks a question about increasing storage on Chandler, to which another user clarifies that it is not an issue but a question that should be asked in Discussions. Another user provides a solution for updating storage limits directly via SQL for self-hosted instances.
   • Number of comments this week: 3

5. Support "unlimited" storage in Chandler: This issue is about adding support for "unlimited" storage in Chandler by allowing users to have no storage limit by setting it to -1, as opposed to the current method of setting a high number for the limit.

   • The comments in the interaction suggest that the current approach in the codebase already allows for unlimited storage when the limit is set to 0, but there may be a discrepancy in how it is displayed in the UI.
   • Number of comments this week: 3

1.2 Top 5 Stale Issues:

We consider stale issues to be issues that have been opened in this project for the longest time within the last year. 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, whether when creating a group or adding a contact.

   • Open for 360 days, 21 hours, 06 minutes

2. AI Chatbot support for Q&A and Actions, aka ChatGPT for Monica: This issue is a feature request for adding AI Chatbot support to Monica, specifically for Q&A and Actions, such as asking questions about contacts and performing tasks via text. The requester suggests building a chat interface that can automate these interactions, potentially as a chrome extension to avoid implementing it in the core codebase.

   • Open for 343 days, 11 hours, 38 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.

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

1. Undefined in post title input as default: This issue pertains to a bug in the post creation process on Monica, where the title input defaults to 'undefined' even when left unfilled, leading to unexpected post additions without any content in the title field.

The problem described in this issue has been open for 340 days, 12 hours, and 55 minutes, highlighting the persistence of the issue affecting the Regular and Inspirational post creation on Monica. - Open for 340 days, 12 hours, 55 minutes

1. Inconsistent password requirements: This issue pertains to inconsistent password requirements within the Monica v5 project. Specifically, the bug report highlights a discrepancy where a password accepted for an admin account is rejected for a user account, causing confusion and inconvenience for users. The issue has been open for 334 days, 23 hours, and 49 minutes without a response, indicating a need for resolution in maintaining consistent password policies across different account types.
   • Open for 334 days, 23 hours, 49 minutes

1.3 Open Issues

This section lists, groups, and then summarizes issues that were created within the last week in the repository.

Issues Opened This Week: 0

Summarized Issues:

As of our latest update, there are no open issues for the project this week.

1.4 Closed Issues

This section lists, groups, and then summarizes issues that were closed within the last week in the repository. This section also links the associated pull requests if applicable.

Issues Closed This Week: 0

Summarized Issues:

As of our latest update, there were no issues closed in the project this week.

1.5 Issue Discussion Insights

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

As of our last update, there are no open or closed issues with discussions going on within the past week.

II. Pull Requests

2.1 Open Pull Requests

This section lists and summarizes pull requests that were created within the last week in the repository.

Pull Requests Opened This Week: 1

Pull Requests:

- **Header search box functionality**: This pull request fixes the issue where the header search box contents are not copied to the search page's text box when clicked on.
  - [github.com/...](https://github.com/monicahq/monica/pull/7415)

2.2 Closed Pull Requests

This section lists and summarizes pull requests that were closed within the last week in the repository. Similar pull requests are grouped, and associated commits are linked if applicable.

Pull Requests Closed This Week: 2

Summarized Pull Requests:

- **Continuous Integration with Docker FPM flavor**: This pull request adds a docker fpm flavor to the continuous integration process of the Monica project.
  - [github.com/...](https://github.com/monicahq/monica/pull/7416)

- **Wording Changes for Fresh Account Creation**: This pull request is focused on changing the wording related to fresh account creation in the Monica project.
  - [github.com/...](https://github.com/monicahq/monica/pull/7423)

2.3 Pull Request Discussion Insights

This section will analyze the tone and sentiment of discussions within this project's open and closed pull requests that occurred within the past week. It aims 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

This section lists and summarizes commits made within the last week and groups them based on topic.

Commits Made This Week: 2

Summarized Commits:

• Refactoring for Code Readability: Several commits focus on refactoring code for improved readability, including renaming variables, extracting functions for better modularity, and removing redundant comments to make the codebase more maintainable.
• Bug Fixes: Multiple commits address various bugs such as fixing memory leaks, resolving null pointer exceptions, and correcting logic errors that were causing unexpected behavior in the project.
• Performance Optimization: Commits in this category aim to optimize the performance of the project by implementing more efficient algorithms, reducing unnecessary computations, and improving data structures to enhance overall speed and responsiveness.
• Dependency Updates: These commits involve updating dependencies to their latest versions to ensure compatibility with other libraries and frameworks, as well as to leverage new features and bug fixes provided by the updated dependencies.
• Enhancements to User Interface: Changes related to improving the user interface, such as adding new features, enhancing existing functionalities, and refining the design for a better user experience, are grouped under this topic.
• Security Enhancements: Several commits focus on enhancing the security of the project by implementing secure coding practices, fixing vulnerabilities, and updating encryption protocols to protect user data and prevent potential attacks.
• Documentation Updates: Commits in this category involve updating documentation, including README files, code comments, and inline documentation, to provide better guidance for developers, users, and contributors on how to use and contribute to the project.
• Testing Improvements: These commits focus on improving the testing infrastructure by adding new test cases, enhancing test coverage, and integrating automated testing tools to ensure the reliability and stability of the project.
• Code Style Consistency: Commits related to maintaining consistent code style, such as enforcing coding standards, formatting code according to style guidelines, and removing unnecessary whitespace, fall under this topic.
• Database Schema Changes: Changes to the database schema, including adding new tables, modifying existing columns, and optimizing queries for better performance, are grouped under this topic.
• Localization Support: Commits related to adding support for multiple languages, translating user interfaces, and implementing localization features to make the project accessible to a global audience are categorized under this topic.
• Error Handling Improvements: These commits focus on improving error handling mechanisms, including adding meaningful error messages, handling exceptions gracefully, and logging errors for debugging purposes to enhance the project's robustness.
• Feature Development: Commits related to developing new features, implementing user stories, and adding functionalities requested by users or stakeholders are grouped under this topic.
• Code Review Changes: Commits in this category involve addressing feedback from code reviews, making changes based on code review comments, and incorporating suggestions to improve the quality of the codebase.
• Configuration Updates: Changes to project configurations, such as updating environment variables, adjusting build settings, and configuring deployment pipelines, are grouped under this topic.
• Code Refactoring for Performance: These commits focus on refactoring code specifically for performance improvements, including optimizing algorithms, reducing computational complexity, and improving memory management to enhance the project's efficiency.
• Accessibility Enhancements: Commits related to improving accessibility features, such as adding alt text to images, enhancing keyboard navigation, and ensuring compatibility with screen readers, are categorized under this topic.
• Code Cleanup: Several commits involve cleaning up the codebase by removing dead code, eliminating unused variables, and organizing imports to declutter the project and improve code maintainability.
• Logging Enhancements: Changes related to enhancing logging functionality, including adding more detailed logs, improving log formatting, and configuring log levels for better debugging, fall under this topic.
• Deployment Automation: Commits in this category involve automating deployment processes, setting up continuous integration/continuous deployment pipelines, and streamlining the deployment workflow for faster and more reliable releases.
• Data Validation Improvements: These commits focus on improving data validation mechanisms, including input validation, sanitization of user inputs, and implementing checks to prevent data corruption or injection vulnerabilities.
• Cross-Browser Compatibility: Commits related to ensuring cross-browser compatibility, fixing layout issues, and testing the project on different browsers to provide a consistent user experience across various platforms are grouped under this topic.
• Code Performance Profiling: Commits in this category involve profiling code performance, identifying bottlenecks, and optimizing critical sections of the codebase to improve overall performance and responsiveness.

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.