2025.09.30

[atambay37]

• ETL Pipeline Development and Collaboration: Peter updated Anshul on the progress of the ETL pipeline work, mentioning a recent pull request for Don and Nikki to review, and discussed involving students in the ETL process, with Anshul confirming that Peter has maintainer access and can add collaborators to the repository.
  • ETL Pipeline Progress: Peter reported that they had built components of the ETL pipeline in a separate repository and submitted a pull request for Don and Nikki to review, aiming to align the work with the team's expectations.
  • Student Involvement: Peter shared plans to have students work on the ETL part, specifically focusing on cleaning up internal data, and sought clarification on how to involve them in the main repository.
  • Repository Access and Collaboration: Anshul confirmed that Peter has maintainer access to the repository and can add students or other collaborators as needed, encouraging centralized work in the main repository for better coordination.
  • Repository Consolidation: Peter agreed to consolidate work into the main repository after the pull request is merged, moving away from using a separate repository to keep all project work centralized.
• Project Scope Clarification and Task Ownership: Peter raised questions about the division of responsibilities for the ETL process within the project, and Anshul clarified that Peter was not overstepping, referencing Don's review of the pull request and confirming that the current approach aligns with the agreed milestones.
  • Scope and Task Division: Peter expressed uncertainty about the scope of work for the ETL process, specifically regarding the University of Washington's (UW) role and whether their efforts might overlap with others' responsibilities.
  • Clarification from Anshul: Anshul reviewed the milestones and product requirements, assuring Peter that there was no overlap or risk of stepping on others' tasks, and noted that Don had already reviewed the pull request and would have raised concerns if necessary.
  • Product Requirements Document Access: Peter mentioned occasional difficulties accessing the product requirements document, and Anshul acknowledged the challenge, explaining why certain documents are not included in the public GitHub repository.
• Repository Management and Technical Details: Peter and Anshul discussed technical aspects of repository management, including handling .DS_Store files in gitignore and the evolving nature of the repository's configuration, with Peter agreeing to address the issue as suggested by Don.
  • Handling .DS_Store Files: Anshul explained the presence of .DS_Store files on Mac systems and the need to update the gitignore file to exclude them, noting that the gitignore configuration would evolve as the project progresses.
  • Action on Gitignore: Peter acknowledged the issue and agreed to update the gitignore file to address the .DS_Store files, as previously suggested by Don.
• Team Availability and Next Steps: Anshul provided updates on team members' availability, noting Nikki's and Don's return dates, and both Anshul and Peter agreed to continue progress asynchronously, with Peter mentioning possible unavailability for the next meeting due to travel.
  • Team Member Status: Anshul informed Peter that Nikki would return on Monday and Don would be back the next day after recovering from illness, ensuring continuity in project activities.
  • Asynchronous Communication: Both participants agreed that most discussions and reviews could continue asynchronously via pull requests and Slack, accommodating travel and varying schedules.
• Infrastructure as Code Tool Setup: Anshul mentioned that Nikki had been working on setting up an infrastructure as code tool before traveling, and Peter acknowledged Nikki's expertise in this area, noting recent discussions with her about the setup process.
  • Tool Setup Progress: Anshul stated that Nikki was focused on configuring an infrastructure as code tool prior to the recent convening, which was a key part of her current tasks.
  • Acknowledgment of Expertise: Peter confirmed that they had met with Nikki before her trip to discuss the setup, recognizing her proficiency in infrastructure as code.

Follow-up tasks:

• ETL Pipeline Collaboration: Invite students working on the ETL part to the shared git repository to facilitate collaboration and centralize work. (Peter)
• Project Scope Clarification: Review the product requirements document to clarify the division of responsibilities for the ETL process between UW and other team members. (Anshul)
• Gitignore File Update: Update the gitignore file to include the .DS_Store metadata file for Mac systems to prevent unnecessary files from being committed. (Peter)