Skip to main content

Week 1 Meetings and Activities

Project Sync Meeting 2

(June 3, 2025)

Attendees

Discussion

  • Discussed the current understanding of the FOSSology tech stack and clarified any remaining doubts around React fundamentals and FOSSology’s architecture.
  • Discussed the potential shift from using plain React to adopting the Next.js framework for the UI project, enabling better structure and performance.
  • Explored the benefits of adopting Next.js, such as routing, server-side rendering, better performance, and enhanced developer experience.
  • Mentors recommended prioritizing the migration tasks in the FOSSologyUI repo, with bug fixes and enhancements to follow in subsequent phases.

Sync Meet with Mentor

(June 4, 2025)

Attendees

Discussion

  • Discussed the next steps for the migration work, specifically setting up the Next.js + pnpm environment.
  • Raised and clarified questions related to the overall project idea and migration strategy.
  • Aligned on the learning curve involved and outlined an approach for migrating the existing React codebase to Next.js.
  • Gained a clearer vision of the upcoming development tasks and roadmap.

FOSSology GSoC Weekly Meet

(June 5, 2025)

Attendees

Missed

Discussion

Mentors

  • Shaheem Azmal M MD: General updates regarding project, Request to update the gsoc wiki before joining the call.
  • Gaurav Mishra: Requests all the mentors/contributors to send the meeting invites to him or kaushl, so that the timings and invites can be added to WIKI.

Contributors

  • Tiyasa Kundu

    • Shared that I have been looking into FOSSologyUI code base.
    • Mentioned that currently focussing on the migration process of the React code base to Next.js.
    • Also mentioned spending some time learning the new framework and tooling to ensure a smoother migration process.
  • Other Contributors

    • Each contributor briefly shared their weekly progress and updates.

Activities Done in Week 1

  • Completed brushing up on key React concepts, FOSSology’s workflow, and the overall tech stack prior to the meeting.
  • Actively participated in discussions around choosing Next.js as the base framework instead of plain React.
  • Discussed and finalized the migration approach that satisfies the shift from CRA to Vite and React 17 to 19, by adopting Next.js.
  • Clarified initial doubts about the project scope and direction during sync meetings.
  • Began outlining a structured plan for migrating the existing UI codebase into the new framework setup.

Next Steps

  • Learn the basic core concepts of Next.js required to start off with the migration.
  • Set up a basic development environment using Next.js with pnpm, ensuring compatibility with the existing project structure.
  • Begin migrating the existing React UI components to the new Next.js framework.