TSC Meeting 19-May-2025

[ovflowd]

Date/Time

Timezone	Date/Time
America/Los_Angeles	Mon 19-May-2025 10:00 (10:00 AM)
America/Denver	Mon 19-May-2025 11:00 (11:00 AM)
America/Chicago	Mon 19-May-2025 12:00 (12:00 PM)
America/New_York	Mon 19-May-2025 13:00 (01:00 PM)
Europe/London	Mon 19-May-2025 18:00 (06:00 PM)
Europe/Amsterdam	Mon 19-May-2025 19:00 (07:00 PM)
Europe/Moscow	Mon 19-May-2025 20:00 (08:00 PM)
Asia/Kolkata	Mon 19-May-2025 22:30 (10:30 PM)
Asia/Shanghai	Tue 20-May-2025 01:00 (01:00 AM)
Asia/Tokyo	Tue 20-May-2025 02:00 (02:00 AM)
Australia/Sydney	Tue 20-May-2025 03:00 (03:00 AM)

Or in your local time:

• https://www.timeanddate.com/worldclock/?iso=2025-05-19T17:00:00

Agenda

Extracted from tsc-agenda labelled issues and pull requests from webpack/tsc prior to the meeting.

• GSOC work governance#4
• TC39 attendance governance#3
• Create initial Working Groups and host first tsc meetings governance#2

Invited

• Webpack TSC (@webpack/tsc)

Observers/Guests

This meeting is open for anyone who wants to attend. Reminder to follow our Code of Conduct.

Joining the meeting

• Join Webpack's Discord server then the #tsc channel

---

Please use the following emoji reactions in this post to indicate your
availability.

• 👍 - Attending
• 👎 - Not attending
• 😕 - Not sure yet

[ovflowd]

FYI the Bot generated Transcript will contain the private content; Going to manually delete the private content.

[ovflowd]

Meeting Summary: Webpack Core Team - Focus: Issue Tracking, Org Structure, and Automation

Attendees: evenstensberg, snitin315, alexander.akait, wunderacle

Key Topics & Decisions:

1. Issue Tracking & Project Management (Initial Discussion):

• The team discussed improving project management and issue tracking. Details were not fully fleshed out but the conversation started with a general desire for improvement.

2. Single GitHub Organization (webpack vs. webpack-contrib):

• Problem: Currently, Webpack projects are split across two GitHub organizations (webpack & webpack-contrib), creating administrative overhead (permissions, automation) and complicating processes like dependabot PRs and payouts.
• Proposed Solution: Consolidate all Webpack projects into a single organization (webpack).
• Concerns: Potential breakage of existing links (documentation, package.json, automated site generation), and disruption to existing workflows.
• Decision:
  • Open a discussion on webpack/webpack (link: Merge webpack-contrib to the webpack organization on github webpack#19548).
  • Document the rationale for the move.
  • Prioritize testing changesets on webpack itself before migrating other repos.
  • Address link updates in documentation, package.json files, and automated site generation (webpack.js.org).
• Next Steps: Discussion & Documentation.

3. Automation & Changesets:

• The team wants to implement changesets for automated release management and changelog generation.
• Changesets are seen as a key enabler for a single organization structure.
• The plan is to initially test changesets on the webpack project itself.

4. Next Meeting & Wrap-Up:

• Next meeting scheduled in 2 weeks.
• The team wrapped up the public portion of the meeting.
• Private topics (tc39 & core devs) remain to be discussed.

Action Items:

• evenstensberg: Open a discussion on webpack/webpack regarding the single organization proposal.
• evenstensberg: Create a document outlining the reasons for moving to a single organization.
• Team: Test changesets on the webpack project.
• Team: Address link updates in documentation and automated site generation if the single organization move is approved.
• Team: Schedule follow-up discussion on the single org proposal.

Key Themes:

• Centralization: The team is moving towards centralizing Webpack projects and administration.
• Automation: Automating release management, changelog generation, and dependency updates is a high priority.
• Long-Term Planning: The team is focused on making changes that will improve the long-term maintainability and scalability of the Webpack ecosystem.