In our pursuit of increasing sustainable flow and yield, One Community proudly champions a paradigm created by our all-volunteer team, and guided by “The Highest Good of All“. Our holistic approach encompasses sustainable practices in food, energy, housing, education, for-profit and non-profit economic design, social architecture, fulfilled living, global stewardship practices, and more. Beyond building a community, we’re creating a replicable model set to establish teacher/demonstration hubs globally. At the core of our strategy is open sourcing and free sharing, ensuring the evolution of sustainability and the enhancement of flow and yield for the betterment of our planet.
Click on each icon to be taken to the corresponding Highest Good hub page.
One Community’s physical location will forward this sustainable flow and yield movement as the first of many self-replicating teacher/demonstration communities, villages, and cities to be built around the world. This is the December 11th, 2023 edition (#560) of our weekly progress update detailing our team’s development and accomplishments:
DONATE | COLLABORATE | HELP WITH LARGE-SCALE FUNDING
CLICK HERE IF YOU’D LIKE TO RECEIVE AN EMAIL EACH WEEK WHEN WE RELEASE A NEW UPDATE
One Community is increasing sustainable flow and yield through Highest Good housing that is artistic and beautiful, more affordable, more space efficient, lasts longer, DIY buildable, and constructed with healthy and sustainable materials:
This week, Abhishek Kadian (Architect) focused on integrating the 4 Dome structure with the existing 3D files for the Earthbag Village (Pod 1), nearing completion. Furthermore, he began developing a Revit file based on it to generate a roof plan and additional sectional views. Progress has been made in constructing a wall and roof, with work ongoing. Earthbag construction is part of our sustainable flow and yield plan for housing. The collage below shows his work on the 4 Dome structure.
Yiwei He (Mechanical Engineer) dedicated her time to catching up on previous processes involving Vermiculture Toilets and reviewing all updated materials and comments. Additionally, she met with Chris to discuss the future schedule and coordinate the next steps, providing clarity on the team’s objectives. Vermiculture is a solution for sustainable flow and yield in human waste processing. Check out the collage below to see her work for the week.
Charles Gooley (Web Designer) concentrated on addressing comments for the Most Sustainable Windows and Window Companies page. The majority of the comments pertained to typographical errors in the mouseover text, with additional feedback related to anchor links. Two images on the Sustainable Doors page were substituted with full-size images. In the Best and Most Sustainable Companies section of both pages, company logos were incorporated and linked to their respective websites. These pages share our research into the companies and products best demonstrating sustainable flow and yield for windows and doors. The images below show his work on sustainable door comparison.
Khushboo Vyas (Architect) focused on organizing construction phases according to the guidelines, ensuring a step-by-step, chronological process for the Earthbag Village DIY tutorial. Khushboo focused on making sure that information flows smoothly and references within the steps connect well (sustainable flow and yield!). She added some temporary logos and organized the details in a clear step-by-step order. See the collage below of Khushboo’s work on DIY tutorials.
One Community is increasing sustainable flow and yield through a Duplicable and Sustainable City Center that is LEED Platinum certified/Sustainable, can feed 200 people at a time, provide laundry for over 300 people, is beautiful, spacious, and saves resources, money, and space:
This week, Amiti Singh (Architectural Designer) reviewed the 3D renders she generated for Room 10 in the Duplicable City Center, initially centered around a Boho-industrial aesthetic. The renders integrated eclectic industrial furniture and boho decor to temper the color palette. To achieve a more formal appearance, Amiti eliminated redundant objects and introduced materials to enrich the room’s texture. Alongside this, she finished file finalization for earlier room design projects within the City Center. We’re addressing sustainable flow and yield in our room designs by looking a the sustainability of all components in each room, and the benefits for those who stay in them. Amiti’s beautiful architectural renderings are shown in the collage below.
Justin Varghese (Mechanical Engineer) focused on frame analysis and simulation to assess the City Center Hub Connector’s response to seismic (earthquake) loading, specifically employing response spectrum analysis (RSA). These analyses were created following guidance from the Senior Engineer, with a focus on enhancing the accuracy of the analysis by incorporating more than 90% mass participation through the inclusion of additional modes. This is about sustainable flow of load forces to yield safe structural design. The images below show some of Justin’s work on frame analysis.
One Community is increasing sustainable flow and yield through Highest Good food that is more diverse, more nutritious, locally grown and sustainable, and part of our open source botanical garden model to support and share bio-diversity:
This week, the core team continued working with Hayley on the Highest Good food component. Collaborative efforts were undertaken both collectively and individually to advance the Food Infrastructure document and its corresponding Edits document. Attention was given to sections 50, 100, and 400, addressing personnel arrival procedures at the One Community property and the sustainable flow and yields of our food infrastructure rollout process. Furthermore, we completed the audio recording of Eckhart Tolle’s book “A NEW EARTH,”. You can see the images in the collage below.
Hayley Rosario (Sustainability Research Assistant) continued her review of the open-source Highest Good Food rollout plan. She reviewed and addressed comments and suggestions provided by the core team, making edits to the EDIT’s document to his specifications. She also resolved issues related to capitalization, images, and information. Additionally, Hayley incorporated the 100, 400, and over 400 drafts, adding webpages, refining formatting, and reviewing personal information in the over 400-people categories as part of the sustainable flow and yields of our food infrastructure rollout process. See below for the picture.
Shivangi Patel (Graphic Designer) continued her work the Transition Food Self-sufficiency Plan UI/UX Web and Graphics development. This week she created both volunteer announcements and profile images for volunteer work using Photoshop. Simultaneously, she authored pertinent web content for the announcement. Later in the week, Shivangi focused on designs for the transition menu recipe webpages. She incorporated small banners and iterated on the designs, prioritizing a user experience. Additionally, Shivangi compiled a deck to organize and present the designs for submission to the web designer. See below for the visual images.
Smit Bhoir (Data and Business Analyst) continued data analysis for the menus for the Transition Food Self-sufficiency Plan. Smit completed the review for Shaurya’s weekly blog post and made progress on data tasks related to the Kitchen menu. His focus remained on data analysis for the Transition Kitchen menu, emphasizing the creation of interpretation tables and tutorials for the “master Recipe FWA” documentation. Smit concluded the week by working on the data interpretation task for the FWA recipe ingredient cost analysis from the Transition Kitchen Menu. These designs are about the sustainable flow and yield of food procurement and preparation during our transition to food self-sufficiency. A visual representation of Smit’s work can be observed in the accompanying picture collage below.
One Community is increasing sustainable flow and yield through Highest Good education that is for all ages, applicable in any environment, adaptable to individual needs, far exceeds traditional education standards, and more fun for both the teachers and the students. This component of One Community is about 95% complete with only the Open Source School Licensing and Ultimate Classroom construction and assembly details remaining to be finished. We’ll report on the final two elements to be finished as we develop them.
With over 8 years of work invested in the process, the sections below are all complete until we move onto the property and continue the development and open sourcing process with teachers and students – a development process that is built directly into the sustainable flow and yield structure of the education program and everything else we’re creating too:
One Community is increasing sustainable flow and yield through a Highest Good society approach to living that is founded on fulfilled living, the study of meeting human needs, Community, and making a difference in the world:
This week, the core team completed 53 hours managing One Community volunteer-work review not included above, emails, social media accounts, web development, new bug identification and bug-fix integration for the Highest Good Network software, and interviewing and getting set up new volunteer team members. We also shot and incorporated the video above that talks about sustainable flow and yield and how sustainable flow and yield integrate into the bigger picture of everything One Community is doing. The pictures below show some of this work.
The core team tested Highest Good Network PRs for One Community this week. They worked on HGN pull request (PR) testing, recorded a video detailing the issues identified in the testing of one PR, and shared the link with the volunteer on Slack. The team also updated locations for inactive accounts ensuring the accuracy of information. They faced a challenge when attempting to update the location for one account, as clicking on the ‘Get Time Zone’ button consistently resulted in a white screen. The Highest Good Network software is how we’ll be measuring much of the sustainable flow and yield of our construction, production, and maintenance processes. See the collage pictures below.
Aaron Wang (Fundraising Assistant) continued to help One Community with working on fundraising. We won’t be able to have sustainable flow and yield without funding. This week, Aaron researched eight potential funders: Michael R. Bloomberg, Marcel Arsenault and Cynda Collins Arsenault, Mark Zuckerberg, Ted Turner, Jeff Skoll, Tom Secunda, Tom Steyer and Kat Taylor, and Laura and John Arnold. His research focused on their sustainability activities, funding histories, and the specific organizations they have supported. The outcome is intended to facilitate future networking and connection strategies. Alongside this new research, Aaron also completed the ranking of previously researched funders, categorizing them based on the priority for future connection. You can view this work in the image below.
Vishvesh Sheora (Artificial Intelligence Specialist) focused on enhancing the SEO performance on the live main site, achieving an improvement from 35 to a much better 80. The more web traffic we have, the more we can promote sustainable flow and yield. He also focused on refining SEO criteria as outlined by RankMath, and worked on addressing specific elements to optimize the overall SEO score. Emphasizing content quality, Vishvesh balanced length and pruned content where necessary. See some of his work in the image below.
This week, the Administration Team’s summary, covering their work administrating and managing most of One Community, was managed by Catherine Liu (Administrative and Analytics Assistant, Team Manager) and includes Alyx Parr (Senior Support Specialist), Olawunmi “Ola” Ijisesan (Administrative and Management Support), Ruiqi Liu (Administrative Assistant), Shaurya Sareen (Administrative Assistant), Xiaolai Li (Administrative Assistant). Alyx reviewed and recognized Ola’s work and also began working on a new project, helping integrate keywords like “sustainable flow and yield”. Catherine completed a thorough evaluation of the Admin, Blue Steel, and Alpha teams, along with individual team members. Concurrently, she organized images and summaries, establishing an accessible repository for relevant information. In parallel, Catherine took Google Analytics courses and began the review of the water conservation webpage. Ola took on a new assignment involving the review of a designed webpage, complemented by a video tutorial elucidating task instructions. She also evaluated both the admin and PR Review Teamwork, providing constructive feedback. Ola organized and decluttered the workspace to prepare for the team’s weekly tasks. Ruiqi focused on the four-step review process for the Code Crafters Git-R-Done, Graphic Design, and Expresser Team, providing feedback and creating collage images stored in Dropbox and the WordPress media library. She utilized weekly summaries for SEO keywords on WordPress and compared the management team’s modified webpage. In the business plan project, Ruiqi refined the cost analysis, adding more details, and completed her announcement and bio. Shaurya did a review of pull requests (PRs), addressing issues with team members and updating tracking sheets and weekly tables for the Highest Good Network team. He wrote up the team summary and compiled a team collage featuring all PRs. Finally, Xiaolai focused on organizing summaries and documents, setting up the weekly report page, reviewing documents, scrutinizing the final PDF version, and resetting the webpage for the ongoing week. Additionally, he engaged in reviewing and editing summaries, organizing documents, and offering valuable feedback on development work for week 560. The work and development of this team represents our sustainable flow and yield management and acknowledgement process. You can see the work for the team in the image below.
This week, the Alpha Team’s summary, covering their work on the Highest Good Network software, was managed by Carl Bebli (Software Engineer, Team Manager) and includes Yongjian Pan (Software Engineer). The Highest Good Network software is how we’ll be measuring much of the sustainable flow and yield of our construction, production, and maintenance processes. Carl addressed and resolved the malfunction of the replyTo feature related to automated infringements, implementing fixes. He also enhanced user communication by incorporating a volunteer’s duration into community emails, progressing towards resolution. Carl played a key role in co-hosting the inaugural meeting with Team Alpha, facilitating discussions on Phase two challenges. Additionally, he assessed pull requests, offering constructive feedback and resolving issues flagged under numbers #1623, #1631, and #1636. Yongjian worked to resolve npm test errors, occurring during Github actions despite passing locally. Despite attempts to comment out failed tests, the issues existed on GitHub. Yongjian investigated the root cause, aiming to identify and rectify discrepancies between local and Github environments, ensuring successful npm test execution across all platforms. View some of this work in the collage below.
This week, the Blue Steel Team’s summary, covering their work on the Highest Good Network software, was managed by Nathan Hoffman (Software Engineer, Team Manager) and includes Haohui Lin (Software Engineer), Shubhankar Valimbe (Lead Full Stack Software Developer), Xiao Wang (Software Engineer) and Yubo Sun (Full Stack Software Developer). The Highest Good Network software is how we’ll be measuring much of the sustainable flow and yield of our construction, production, and maintenance processes. Haohui made efforts to familiarizing himself with the app’s features and completed reviews of multiple pull requests (PR#1604, 1611, 1623, 1634, 1632, 1637) submitted by team members. Nathan engaged with messages and comments on pull requests, subsequently initiating work on new PRs (#643, #1658, #1659, #1664) focusing on permissions related to bios, report segregation, and role permissions. Additionally, He followed up on existing PRs, addressed a fix, and resolved a broken test merged into development. Shubhankar put attention to bug resolution, specifically addressing the ‘i’ popup bug and ensuring visibility for all users in the Weekly Summaries Reports tab. He also reviewed weekly team summaries, addressing frontend PR 1359 and backend PR 556, enhancing team creation and member addition/deletion functionalities. Xiao completed four PRs, including a hot fix for failed png files (PR1592) caused by end-of-line setup differences. Two subsequent PRs (frontend PR1600 and backend 623) resolved an owner’s inability to create a new team bug. Another PR addressed an audio reminder request during timer force pauses, while ongoing work on the TimeEntryFrom refactoring is in progress. Yubo focused on addressing the blue square email issue for core teams, exploring the impact of excessive aggregation on application performance through research. He also attempted testing PR #1585, addressing a failure in the task tab due to a MongoError, and shared findings on the Slack channel. The collage below shows some of this work.
This week, the Code Crafters Team’s summary, covering their work on the Highest Good Network software, was managed by Ruiqi (Administrative Assistant) and includes Anirudh Ghildiyal (Software Engineer), Ramya Ramasamy (Software Engineer), and Shantanu Kumar (Software Engineer). The Highest Good Network software is how we’ll be measuring much of the sustainable flow and yield of our construction, production, and maintenance processes. Ramya worked on online tutorials and reviewed the team’s testing strategies and documentation. She also formulated test cases for the basicInformationTab. Additionally, she investigated the limitations of the ‘see all’ functionality, addressing potential causes for malfunctions and working towards their resolution. Shantanu focused on writing unit test cases for the Profile Dot Nav component and initiating work on the Set Up Final Day Pop-Up. He reviewed the bug document and addressed newly identified issues. Anirudh completed the final testing phase for the task involving the awarding of badges to managers leading teams with fewer members. He followed up with other teammates assigned to this task and got its resolution. He also reviewed the progress of his teammates’ tasks and led the team in conducting weekly standup meetings. The Highest Good Network is how we’ll be measuring and tracking sustainable flow and yield, related investments of time, and the components as we develop them. The collage below shows some of this work.
This week, the Expressers Team’s summary, covering their work on the Highest Good Network software, was managed by Tim Kent (Full Stack Software Engineer) and includes Olga Yudkin (Software Engineer), Sahil Patel (Frontend Developer), and Vishala Ramasamy (Software Developer). The Highest Good Network software is how we’ll be measuring much of the sustainable flow and yield of our construction, production, and maintenance processes. Vishala focused on optimizing the CircleCI load, doing a thorough web analysis, and identifying code-splitting as a potential solution to reduce build time by minimizing the bundle size. Additionally, she addressed issues with tasks and leaderboard APIs not functioning on the dashboard page. Olga advanced the AddForm component design, completing foundational work on the form’s responsive design, and initiating the development of a drag-and-drop component to facilitate easy image uploads of tools and equipment. In the realm of quality testing, Sahil reviewed PRs #1636, #1643, #1668, #1667, #1660, #1653, #1650, and #1654, emphasizing the importance of unit testing within the HighestGoodNetworkApp. He focused on developing and executing unit tests across various components, ensuring all test cases passed and validating their functionality. Sahil also initiated writing a quality test for the ToggleSwitch component. Tim defined the MongoDB schema for reusable and consumable inventory categories. Additionally, he focused on refactoring inventory category schemas with discriminator inheritance methods to streamline code and accommodate all inventory in the same database collection. He was also involved in ongoing discussions with team members, contributing comments to the Phase 2 documentation, and providing managerial guidance to ensure effective collaboration within the team. The collage below shows some of this work.
This week, the Git-R-Done Team’s summary, covering their work on the Highest Good Network software, was managed by Eduardo Horta (Software Engineer) and includes Olena Danykh (Software Engineer), Miguelcloid Reniva (Software Developer), Rhea Wu (Software Engineer), Shuhua Liu (Full-Stack Developer), and Ziming Song (Software Engineer). The Highest Good Network software is how we’ll be measuring much of the sustainable flow and yield of our construction, production, and maintenance processes. Olena implemented the like button functionality, considered a pause for the filter functionality pending schema clarification, and addressed feedback on the lesson cards’ horizontal scrollbar. Miguel tackled CSS alignment issues, fixed a dropdown menu bug, and improved code adaptability. Ziming resolved the Add New Project functionality bug and submitted a pull request. Shuhua resumed work on creating a different view for “!Summary,” finished a tests, and delved into Phase II specifications for Consumables. Rhea worked on New Lesson routing and controller. Eduardo focused on the BM New Issue project, concentrating on Routes and Controller tasks, setting up Mongo Compass, and exploring discriminators for schema inheritance. He executed POST and GET requests and planned to define a proper MongoDB SCHEMA for the New Issue Form. Additionally, he reviewed GIT-R-DONE team members’ work, hosted the weekly team meeting, and emphasized Phase 2 features and documentation improvement. The collage below shows some of this work.
This week, the Graphic Design Team’s summary was managed by Ruiqi (Administrative Assistant) and includes Ashlesha Navale (Graphic Designer), Emily Ferguson (Visual Designer), Jackie King (Graphic Designer), and Nancy Mónchez (Graphic Designer). Ashlesha created nine Social Media Images, researched nature-themed images, and updated web content for a volunteer announcement. Emily crafted diverse and attention-grabbing graphics, contributing to online visibility. Jackie focused on Photoshop work for BioImages and Volunteer Announcements. She also worked on Social Media Images, managing data on a shared spreadsheet. Nancy maintained design continuity, incorporating animal photos and informative footers in her redesign posts. These images convey our messages associated with creating sustainable flow and yield. The collage below shows some of this work.
This week, Moonfall Team’s summary, covering their work on the Highest Good Network software, was managed by Navneeth Krishna (Software Engineer) and includes Abdelmounaim “Abdel” Lallouache (Software Developer), Anny Wang (Software Engineer), Cheng-Yun Chuang (Software Engineer), Haoji Bian (Software Engineer), Jiadong Zhang (Software Engineer), Lu Wang (Software Engineer), Palak Gosalia (Software Engineer), Tzu Ning “Leo” Chueh (Software Engineer), Yi Lin (Software Engineer), YuFu Liao (Software Engineer) and Zijie “Cyril” Yu (Software Engineer). The Highest Good Network software is how we’ll be measuring much of the sustainable flow and yield of our construction, production, and maintenance processes. Abdelmounaim implemented a new function to prevent overlap in time-off entries, addressing conflicts on both the frontend and backend for PR 1471. Additionally, he enhanced the blue square scheduler modal by adding and styling an alert, and developed functionalities to generate and dispatch notifications to users and administrators following the scheduling or deletion of a blue square. Anny created the quick-setup modal for a new user. She set the permissions for the Owner and Admin to view the modal. Cheng-Yun reviewed unit test code for Project.jsx and Overview.test.jsx. He looked into PR#1610 and PR#1574, providing a thorough evaluation and modification of the unit test code within the pull request. Haoji developed and integrated a new feature into the application, enabling users to selectively subscribe and unsubscribe from email communications. Jiadong focused on updating the badge functionality on the dashboard. He modified the badge button style to toggle between hide and show states. Additionally, Jiadong implemented a popup window for the badge component. Lu implemented asynchronous testing using waitFor to ensure the expected Redux actions (createNewBadge and closeAlert) are appropriately triggered after form submission. Additionally, Lu addressed bugs related to the component being wrapped in a Provider with a mocked Redux store. Palak focused on creating a pull request (PR) for a unit test case of the assignTableRow component. She developed a total of eight unit test cases, covering both positive and negative scenarios. Navneeth collaborated with Nathan Hoffman to discuss a frontend fix related to the implementation of a non-overlapping permissions list, aligning with the latest updates specified in the Permissions Management Fixes document, where specific categories were transitioned into non-permissions. In addition, Navneeth undertook debugging of the weekly summaries user profile aggregator located in src/utilities/reporthelper.js. Tzu Ning resolved several critical issues in the software development process, addressing a display problem with the “Back to Top” button on the People Reports page and rectifying the badge assignment issue within the checkXHrsForXWeeks function. Yi accomplished several tasks related to unit testing in the project. In PR #1643, Yi added a unit test for the TaskCompletedModal.jsx component. Yi also added unit tests for the DiffedText.jsx component in PR #1642. Yufu cleared around 20 branches that hadn’t been edited for over four months and merged them into the main repository. And Zijie worked closely with Yiyun to fix a very unusual bug during the merge of the report component, completed three lint fixes, and submitted pull requests for each (numbers 1669, 1670, and 1671), examining the potential impact on the entire app if these components were absent and updating the rules in the lintignore file. Look below for a collage of their work.
This week, Reactonauts’ Team’s summary, covering their work on the Highest Good Network software, was managed by Masasa Thapelo (Software Engineer) and includes Changhao Li (Software Engineer), Jiangwei Shi (Full Stack Engineer), Jiyuan Xia (Software Engineer), Obeda Andrilalaina Velonjatovo (Front End Developer/Software Developer), Shengwei Peng (Software Engineer), Shihao Xiong (Software Engineer), Shiwani Rajagopalan (Software Engineer), Shrey Jain (Software Engineer), Vikram Badhan (Software Engineer), Wanting Xu (Software Engineer) and Yixiao Jiang (Software Engineer). The Highest Good Network software is how we’ll be measuring much of the sustainable flow and yield of our construction, production, and maintenance processes. Changhao performed unit testing for textSearchbox.jsx and userSearchPanel.jsx. Jiangwei created unit tests for the Selectors component and TasksTable component. Additionally, he allocated extra time to develop tests for another vital module, contributing to the overall strength and stability of the project. Jiyuan completed PR #1641 and #640 and implemented changes, ensuring a smooth integration process. Masasa completed the creation of visualizations and enabled the table to contain links redirecting to the profiles of specific individuals displayed within it. Obeda continued working on the Add Project task and worked on the Delete Project. Shengwei focused on PR reviewing tasks, completing over 20 reviews. He identified issues in several PRs where insufficient details for testing steps posed during case reproduction. Shihao reorganized file structures and completed unit tests for DueDateTime.jsx, UserLinkLayout.jsx, and BadgeImage.jsx components. Shiwani completed the unit testing of the TagsSearch component and created four test cases. She also worked on a critical task related to the creation of a leaderboard feature for tracking individuals’ time off during the week. Additionally, she enhanced the dashboardHelper, which provides leaderboard data to the frontend by adding fields for time off and the current date. Shrey wrote unit test cases for two components, EffortBar.jsx and UserTableHeader.jsx, he considered all possible cases to ensure complete coverage of the code. Vikram configured the local frontend and backend environments and engaged in the review of six pull requests. In addition, he addressed an issue related to the non-functionality of the “90-hour in one week” badge within the HGN application. Wanting completed the final unit test task for ProjectTableHeader and initiated a new unit test task for AddWBS.jsx. Yixiao resolved issues with the TaskEditSuggestions.test.js file and submitted a pull request for this file. Yixiao also wrote tests for the actions.test.js file and completed testing for four of its functions. Look below for pictures of this work.
This week, Skye’s summary, covering their work on the Highest Good Network software, was managed by Luis Arevalo (Front End Developer) and includes Bailey Mejia (Software Engineer), Hemsharavanan Bharathithasan (Full Stack Software Engineer), Jerry Ren (Full Stack Developer), Roberto Contreras (Software Developer) and Yao Wang (Software Engineer). The Highest Good Network software is how we’ll be measuring much of the sustainable flow and yield of our construction, production, and maintenance processes. Bailey addressed a CSS issue for his colleague Yao. He resolved a text alignment problem in a modal by adjusting the container’s width to 100% and setting it to a flex display. He improved loading speeds and encountered a ‘400 Bad Request’ error while managing tasks in the user interface, specifically when resolving or removing tasks from the teams/tasks component. Additionally, he reviewed two pull requests, PR #1662 and PR #1403. Jerry addressed the auto dropoff bug within the X-hours in X-weeks streak feature. His primary efforts involved creating a Jest testing library-compatible test file to assess the functionality of the checkXHrsForXWeeks() function. Additionally, he addressed the specific bug at hand and also laid the groundwork for the streamlined creation of tests for other potential scenarios. Yao removed the text “(function under development)” beneath a blue square in the project interface. Following this, he implemented an “i” button for the blue block, improving user interaction and information accessibility. Yao also developed a new FAQ button, triggering a modal with relevant information upon clicking. Roberto examined Luis’ current branch and contributed to the setup of the backend route, addressing schema requirements for the database. Additionally, he identified an undefined userId problem in the frontend. Luis integrated the frontend and backend with assistance from Roberto. Upon integration, a discrepancy was identified in the correct transmission of user IDs. He resolved the issue by implementing Redux useSelector to retrieve the user ID and subsequently submit it to the backend. Luis also achieved the functionality to submit warnings to the user’s warnings array. Hemsharavanan reviewed and provided feedback on several PRs, he made improvements in test descriptions and parameter passing for TextSearchBox’s test suite to enhance clarity and maintainability. See the collage below for some of their work.
The PR Review Team’s summary covering their work on the Highest Good Network software, was managed by Shaurya Sareen (Administrative Assistant). This week’s active members of this team were: Anish Pandita (Software Engineer), Demi Zayas (Software Engineer), Ilya Flaks (Software Engineer), Jacob Smith (Software Engineer), Jay Yong (Software Engineer), Jiarong Li (Software Engineer), John Mumbi (Software Engineer), Kurtis Ivey (Software Engineer), Sucheta Mukherjee (Software Engineer), Xuying He (Software Engineer), Zichan Yang (Software Engineer). They reviewed all the Highest Good Network PRs (Pull Requests) shared in this week’s update. The Highest Good Network is how we’ll be measuring and tracking creating positive change permanence, related investments of time, and the components as we develop them. The Highest Good Network software is how we’ll be measuring much of the sustainable flow and yield of our construction, production, and maintenance processes. The collage below shows a compilation of the work from this team.
AND WE PRODUCED THIS WEEKLY UPDATES BLOG – CLICK HERE TO SUBSCRIBE