Weekly GitHub Report for Monica: December 10, 2024 - December 17, 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. News
1.1 Recent Version Releases:
The current version of this repository is v4.1.2
1.2 Other Noteworthy Updates:
II. Issues
2.1 Top 5 Active Issues:
We consider active issues to be issues that that have been commented on most frequently within the last week.
-
Migration fails after updating to 4.1.0: This issue is about a migration failure encountered after updating a non-docker installation of the Monica application from version 4.0.0 to 4.1.0. The user reports that the migration process fails with a SQL error indicating that the 'accounts' table already exists, which prevents the migration from completing successfully.
- The comments discuss the nature of the issue, with one person suggesting it might be related to the installation or architecture rather than a bug in Monica itself, as they could not reproduce the problem. Another comment mentions encountering a similar deployment issue during migration on both PostgreSQL and MySQL with a fresh install using the latest helm chart.
- Number of comments this week: 1
-
Send reminders to different email address (or multiple): This issue is about a feature request for the Monica application, where the user wants the ability to send reminders to multiple email addresses or a mailing list, so both the user and their spouse can receive notifications for events like birthdays. The current system only sends reminders to the person who created the contact, which is not ideal for users who share contacts and want shared notifications.
- A comment suggests that the new version, v5, of the Monica application allows defining multiple notification channels, and if multiple users are in one vault, notifications will be sent to all users in that vault.
- Number of comments this week: 0
-
How do I increase storage on Chandler beyond 50MB? [Selfhosted]: This issue is about a user seeking guidance on how to increase the storage limit for Chandler, a self-hosted application, beyond the default 50MB using Docker. The user is looking for a way to set the storage to unlimited capacity.
- The comments suggest that others have the same question about increasing storage due to large profile pictures. One comment indicates that this is not an issue but rather a question for the Discussions section. Another comment provides a potential solution by suggesting that users can update the storage limit directly in the database using an SQL query, though the method to execute this query depends on the user's specific setup.
- Number of comments this week: 0
-
Account Takeover via Host Header injection: This issue reports a security vulnerability in the Monica application, specifically in its password reset functionality, which is susceptible to Host header injection. This flaw allows an attacker to manipulate the Host header in HTTP requests during the password reset process, potentially leading to unauthorized account access.
- The comments section includes a user expressing interest in working on the issue, followed by a response granting permission to proceed with addressing the vulnerability.
- Number of comments this week: 0
-
Support "unlimited" storage in Chandler: This issue is about a feature request to support "unlimited" storage in the Chandler project, where the user suggests using a specific value to denote no storage limit. The user notes that in a previous version, setting the storage limit to "0" was interpreted as infinite, but this does not seem to work in the current version, and proposes using "-1" for unlimited storage instead.
- The comments discuss the current implementation where setting the storage limit to "0" should mean unlimited, but the user reports that this does not work as expected in the latest version. Another commenter confirms that the code indicates "0" should be unlimited and suggests that the user interface needs updating to reflect this correctly.
- Number of comments this week: 0
2.2 Top 5 Stale Issues:
We consider stale issues to be issues that has had no activity within the last 30 days. The team should work together to get these issues resolved and closed as soon as possible.
As of our latest update, there are no stale issues for the project this week.
2.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: 1
Summarized Issues:
- Enhancing User Experience with Predictive Features: This issue suggests implementing a feature that predicts relationships between newly inputted contacts based on existing connections. The goal is to streamline the process of linking relationships, which can be time-consuming when done manually. By prompting the user for confirmation, the feature aims to reduce the time spent on manual data entry and improve overall user experience.
2.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.
2.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.
Based on our analysis, there are no instances of toxic discussions in the project's open issues from the past week.
III. Pull Requests
3.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: 0
Pull Requests:
As of our latest update, there are no open pull requests for the project this week.
3.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: 0
Pull Requests:
As of our latest update, there are no closed pull requests for the project this week.
3.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.
As of our last update, there are no open or closed pull requests with discussions going on within the past week.
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.
| Contributor | Commits | Pull Requests | Issues | Comments |
|---|---|---|---|---|
| Alexis Saettler | 8 | 0 | 0 | 0 |
| laurell seville | 7 | 0 | 0 | 0 |
| lenaxia | 0 | 0 | 1 | 1 |
| Laurell Seville | 1 | 0 | 0 | 0 |
| Laurell876 | 0 | 1 | 0 | 0 |
| asbiin | 0 | 1 | 0 | 0 |
| beemej | 0 | 0 | 1 | 0 |
ReadMe Summary: Monica is an open-source personal relationship management system designed to help users document and organize their interactions with family and friends. Key features include contact management, reminders, activity logging, and a diary, all while ensuring user data privacy and control. The project encourages community contributions and is supported by a dedicated team and a vibrant developer community.