Weekly GitHub Report for Monica: December 11, 2024 - December 18, 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 Version Information:
Version 4.1.2, released on May 4, 2024, addresses a bug fix related to the contact listing feature, ensuring that the updated_at date is no longer incorrectly modified for all contacts.
1.3 README Analysis:
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 available in 27 languages, with support for multiple currencies and customizations.
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 bug encountered during the migration process after updating the Monica application from version 4.0.0 to 4.1.0. The user reports that the migration fails with a SQL error indicating that the 'accounts' table already exists, which prevents the migration from completing successfully.
- The first comment suggests that the issue might be related to an architecture or installation problem rather than a bug in Monica, as the commenter cannot reproduce the issue. The second comment mentions that a fresh installation using the latest helm chart also encounters deployment issues during migration on both PostgreSQL and MySQL, indicating that the problem might be more widespread.
- 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 reminders for events like birthdays to be sent to multiple email addresses, specifically to both their own and their spouse's email. The user suggests either sending reminders to both emails directly or using a mailing list that both users are subscribed to, as currently, reminders are only sent to the person who created the contact.
- A comment suggests checking the new version, v5, available on the beta site, which allows defining multiple notification channels. It mentions that 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 discuss the nature of the inquiry, with one user expressing a similar need for increased storage due to large profile pictures. Another comment suggests that this is more of a question suited for the Discussions section rather than an issue. A solution is proposed by a commenter, who explains that while there is no web UI option, users can directly modify the storage limit in the database using an SQL query, depending on their 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 within the forgot password functionality, which is susceptible to Host header injection. This vulnerability allows an attacker to manipulate the Host header in HTTP requests during the password reset process, potentially leading to an account takeover.
- The comments section includes a user expressing interest in working on the issue, followed by a response granting permission to proceed with addressing the problem.
- 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 wants to set a storage limit to indicate infinity, similar to how it was done in a previous version of the software. The user suggests using -1 to represent unlimited storage, as setting the limit to 0 in the current version does not work as expected, unlike in the previous version.
- The comments discuss the current implementation where setting the storage limit to 0 should mean unlimited, as indicated in the documentation and code references. However, the user reports that this does not work in version 5 as it did in version 4. Another commenter suggests that the UI should be updated to display "Unlimited" when the limit is set to 0, indicating a possible discrepancy between the backend logic and the user interface.
- 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: 0
Summarized Issues:
As of our latest update, there are no open issues for the project this week.
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.
As of our last update, there are no open or closed issues with discussions going on within 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 | 4 | 0 | 0 | 0 |
| lenaxia | 0 | 0 | 1 | 1 |
| asbiin | 0 | 1 | 0 | 0 |
| beemej | 0 | 0 | 1 | 0 |