Initial Commit

Author: avivkeller

CODE_OF_CONDUCT.md

@@ -84,11 +84,66 @@ The current list of all Web Team members across all subteams is maintained in [M
 
 ## Governance
 
-### TSC Oversight
+### Relationship with the TSC
 
-Any website change that expresses a position about a global event or group of people requires explicit [TSC](https://github.com/nodejs/TSC/blob/main/TSC-Charter.md#section-4-responsibilities-of-the-tsc) approval through one of these methods:
-- Pinging `@nodejs/tsc` and receiving no objections after seven days
-- Emailing `tsc@iojs.org` and receiving at least one approval with no objections after seven days
+The Website Team operates with significant autonomy for most website decisions, but must recognize the TSC's ultimate authority on matters affecting Node.js project representation, branding, and strategic partnerships.
+
+#### Decision Authority Hierarchy
+
+1. **Website Team Authority**
+
+   - Technical implementation details
+   - User interface and experience design
+   - Content organization and information architecture
+   - Day-to-day maintenance and updates
+
+2. **TSC Authority**
+   - Project-wide policies and governance
+   - Strategic partnerships and representation
+   - Major structural or navigational changes
+   - Content that affects Node.js project positioning
+
+#### Content Requiring TSC Approval
+
+- **Statements on Sociopolitical Issues**: Any content expressing positions on political, social, cultural, or humanitarian matters
+- **Commercial Relationships and Endorsements**: Any content establishing or promoting commercial partnerships, vendor preferences, or paid services related to Node.js
+
+Website changes falling under these categories require **formal TSC endorsement** as outlined in the [TSC Charter](https://github.com/nodejs/TSC/blob/main/TSC-Charter.md#section-4-responsibilities-of-the-tsc). Valid approval consists of at least one TSC member's explicit approval with no objections from any TSC members. This endorsement may be secured through either:
+
+- Pinging `@nodejs/tsc` OR
+- Sending an email to `tsc@iojs.org`
+
+#### Handling TSC Feedback and Concerns
+
+When TSC members express concerns about proposed changes:
+
+1. **Documentation Requirement**: Document all TSC feedback in the relevant issue or PR
+2. **Hold Period**: Pause implementation until concerns are addressed
+3. **Resolution Process**:
+   - Seek clarification on specific concerns
+   - Propose compromise solutions
+   - Document resolution attempts and outcomes
+
+#### Dispute Resolution Process
+
+If disagreements arise between the Website Team and TSC regarding website changes:
+
+1. **Escalation Path**:
+
+   - First attempt: Direct discussion on the PR/issue
+   - Second attempt: Scheduled discussion in TSC meeting
+   - Final resolution: Formal TSC vote if needed
+
+2. **Implementation Requirements**:
+
+   - Changes with unresolved TSC objections must not proceed without formal TSC approval
+   - When in doubt about approval status, seek explicit confirmation
+   - Document the resolution and approval in the PR before merging
+
+3. **Documentation Standard**:
+   - All significant disagreements and their resolutions must be documented
+   - TSC approvals should be explicit and documented in writing
+   - Approval pathways should be clear to all current and future contributors
 
 ### Team Meetings
 

GOVERNANCE.md

@@ -1,6 +1,11 @@
 name: 'Slack Notify Composite'
 description: 'Sends a Slack notification for direct pushes to a branch'
 
+inputs:
+  webhook:
+    description: 'The Slack webhook'
+    required: true
+
 runs:
   using: "composite"
   steps:
@@ -16,4 +21,4 @@ runs:
           Before: <https://github.com/${{ github.repository }}/commit/${{ github.event.before }}|${{ github.event.before }}>
           After: <https://github.com/${{ github.repository }}/commit/${{ github.event.after }}|${{ github.event.after }}>
         SLACK_USERNAME: nodejs-bot
-        SLACK_WEBHOOK: ${{ secrets.SLACK_WEBHOOK }}
+        SLACK_WEBHOOK: ${{ inputs.webhook }}

actions/notify-on-push/action.yml

@@ -5,10 +5,18 @@ inputs:
     description: 'Whether to use pnpm (true) or npm (false)'
     required: false
     default: 'false'
+  install-flags:
+    description: 'Additional installation flags'
+    required: false
+    default: ''
   ref:
     description: 'The ref to checkout'
     required: false
-    default: ''
+    default: ${{ github.event_name == 'pull_request_target' && github.event.pull_request.head.sha || github.ref }}
+  fetch-depth:
+    description: 'The fetch depth'
+    required: false
+    default: 1
   node-version:
     description: 'Node.js version to setup'
     required: false
@@ -21,6 +29,10 @@ inputs:
     description: 'Optional registry URL for Node.js setup'
     required: false
     default: ''
+  token:
+    description: 'The token to use for checkout'
+    required: false
+    default: ${{ secrets.GITHUB_TOKEN }}
 
 runs:
   using: 'composite'
@@ -34,6 +46,8 @@ runs:
       uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
       with:
         ref: ${{ inputs.ref }}
+        fetch-depth: ${{ inputs.fetch-depth }}
+        token: ${{ inputs.token }}
 
     - name: Setup Node.js (with version file)
       if: inputs.use-version-file == 'true'
@@ -58,9 +72,9 @@ runs:
     - name: Install dependencies with pnpm
       if: inputs.pnpm == 'true'
       shell: bash
-      run: pnpm install --frozen-lockfile
+      run: pnpm install --frozen-lockfile ${{ inputs.install-flags }}
 
     - name: Install dependencies with npm
       if: inputs.pnpm != 'true'
       shell: bash
-      run: npm ci
+      run: npm ci ${{ inputs.install-flags }}

actions/setup-environment/action.yml

@@ -0,0 +1,25 @@
+> [!NOTE]
+> These notes were taken from https://github.com/nodejs/nodejs.org/issues/7773#issuecomment-2981323158,
+> since this was an informal meeting.
+
+# Node.js Website Team Meeting 2025-06-17
+
+## Present
+
+- Matteo Collina @mcollina
+- Claudio Wunder @ovflowd
+- Robin Bender Ginn @rginn (Invited)
+- Jeo Eames @joeeames (Invited)
+
+## Agenda
+
+### nodejs/nodejs.org
+
+* https://github.com/nodejs/nodejs.org/issues/7773
+
+    * After some discussion, it was agreed that we do need to move forward with promoting this ESP as the situation with folks using EOL versions is a significant security problem for the ecosystem (for example, Node.js 12 is getting ~25 million downloads per month still), and with the agreement that's in place with the ESP, it will also help bring in some additional cash into Node.js.
+    * The plan seems to be:
+        * Move forward with the [redesigned homepage](https://nodejs-org-git-fork-canerakdas-feat-simplified-download-openjs.vercel.app/), but with `Getting Involved` replaced with a `Get EOL Security Updates` button (final text tbd, might want to mention Node.js 18 specifically)
+        * Adding a global banner for a short while to promote the EOL blog post
+        * Ensure that we hook the button + banner up to click tracking in Vercel to give us data
+    * Our aim, ideally, is to have this live on Monday so that we can start getting numbers on how this is doing (this should be coordinated w/ @kyliewd). This might not be the final state, consider this somewhat an experiment as we see what traffic and conversions this generates, and if it increases awareness for upgrading Node.js versions as well.