Weekly GitHub Report for Terraso-mobile-client: April 08, 2025 - April 15, 2025 (11:16:55)
Weekly GitHub Report for Terraso-mobile-client
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 v238beta
1.2 Version Information:
The version released on March 11, 2025, includes several key updates such as fixes for husky scripts and non-deterministic tests, prevention of sending data from deleted depth intervals to the soil ID algorithm, and enhancements in app launch conditions. Additionally, there are multiple dependency updates, including logger, rexml, json, and httpclient, reflecting a trend towards maintaining up-to-date libraries and improving code quality through pre-commit linting with husky.
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. Bot comments are omitted.
As of our latest update, there are no active issues with ongoing comments this week.
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.
- Update images for Slope Shape - language and imagery, file formats: This issue involves updating the images used in the Slope Shape information sheet by replacing existing PNG files with SVGs, which are smaller in size and offer better performance. It was created as a separate task from a previous issue (#853) following a discussion on Slack, and includes references to related tasks that need to be completed.
- Generate SVGs for the slope steepness images: This issue involves creating SVG versions of the existing PNG images that depict slope steepness, as part of a broader task to improve the project's graphical assets. The task has been open for nearly a year, indicating it may be a lower priority or require specific expertise to complete.
- Soil match part 2 — rate match: This issue involves developing a user interface feature that allows users to rate the accuracy of a soil match within a mobile application, including implementing a button to initiate the rating process, a radio menu for assessment, and updates to the Soil Info page. The goal is to enable users, such as managers or contributors, to determine and record whether a soil is the correct match for a site, thereby facilitating the identification of an official SoilID and Ecological Site ID or eliminating incorrect options.
- tech-debt: replace remaining NativeBaseAdapter.tsx components: This issue involves addressing technical debt by replacing the remaining components in the project that are currently using the NativeBaseAdapter.tsx. The goal is to update these components to improve the codebase, likely by adopting a more modern or efficient solution.
- Soil ID - Top Soil Matches - Collapsed "See more soil matches": This issue addresses the functionality of the "Top Soil Matches" module on the Soil ID page, where users should be able to view the top four soil matches and have the option to expand the list to see more matches if available. The enhancement involves implementing a feature that allows users to toggle between viewing more or fewer soil matches by interacting with a "See more soil matches" option, ensuring a seamless user experience when navigating through potential soil matches.
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 provides a summary of pull requests that were opened in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.
Pull Requests Opened This Week: 0
As of our latest update, there are no open pull requests for the project this week.
3.2 Closed Pull Requests
This section provides a summary of pull requests that were closed in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.
Pull Requests Closed This Week: 0
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.
As of our latest update, there are no active contributors for the project this week.