← Back to Transparency

Community Meeting

Date: February 19, 2026 Format: Google Meet call (~1 hour)
67 attendees at peak, including board members, leads, and community members Board members present: Daniel (host), Pablo, Ben, Ward, Peter

Full Records

Overview

Third community meeting of the Nobodies Collective Asociación (NCA). The meeting covered production progress on vendor management and financial planning, permit and compliance preparations, MetaLeads meeting updates, the Humans volunteer platform nearing launch, a legal update on asset procurement, the Governance Working Group’s go/no-go decision process and timeline, collaborator onboarding progress, and a community vote on alternative event names.

Presentations

Daniel — Vibe Update

  • The “8 to 80” phase is in full swing — strong energy and positive collaboration across areas
  • The community may already be in the “80 to 800” phase given the number of active participants
  • Meeting held on Google Meet instead of Zoom; noted that chat messages would not be saved

Daniela — Production Update

  • Those interested in lead roles should reach out directly while the Humans app is being finalized
  • Planning to gather departmental needs so job descriptions can be created for specific roles
  • Vendor management advancing — receiving more quotes, discussions ongoing with vendors responding positively
  • Getting a clearer picture of initial financial needs and payment schedules
  • Permit and compliance work started — reached out to the person responsible for the self-protection plan
  • Looking at different levels of insurance: core protection (D&O and event liability), plus potential group accident and volunteer insurance
  • Site inspection preparation progressing, closely linked to permit day milestone; Jorge leading the effort this year
  • Detailed checklist of 26 mini-checklists ready for permit day inspection

Ward — MetaLeads Meeting Update

  • MetaLeads meeting held on Tuesday was enthusiastic and went quickly
  • Some teams are fully staffed; others (e.g. Cantina) need to recruit new people
  • Discussion about changing the name from “Metalit” to something less corporate
  • Roles that need to be filled will be shared soon

Peter — Humans Platform Update

  • Good review with Ben on onboarding workflow to ensure Humans follows a similar pattern
  • Consolidated onboarding: association membership and volunteering combined into one form instead of two
  • Platform manages human resources, links users to Google Drives and mailing lists, automates access permissions
  • Handles compliance (GDPR) and auditing — knows who had access to what and when
  • If someone steps down, allocated resources are automatically revoked
  • Hoping to launch by Friday or Saturday
  • QA testers will be notified to move over to production

Pepe — Legal Update on Asset Procurement

  • Progress on securing the operational assets needed for the event
  • Hope to hear back within a day or two; documents could be in motion next week
  • Aim to resolve all legal fine print within a couple of weeks
  • Priority item: securing container access

Kate — Go/No-Go Decision Process

  • Governance Working Group formed around February 5 to design a non-partisan, objective process
  • Focused on safety and financial viability — evaluating across eight key areas
  • Conducting interviews and compiling an information pack for the community
  • Information pack expected by end of the weekend
  • Non-binding community poll opening on February 24th or 25th for association members
  • Poll open for a few days; results will inform the board’s final decision
  • Observations so far: some polarization but strong willingness to understand other viewpoints
  • Community members can DM Kate on Discord to share input

Ben — Collaborator Onboarding & Membership

  • Board approved approximately 40 new collaborators, bringing total to 71 fully registered
  • 35 people still need to respond to the final onboarding form — check spam/junk email
  • Overall: ~140 people in the pipeline (71 onboarded + 35 pending + 36 newly emailed + 8 board members)
  • Everyone is being onboarded as collaborators first for speed
  • Board established in-principle criteria for full voting membership (to be published soon)
  • Once voting members are established, a General Assembly can be called where members can propose policies and changes
  • Association membership is NOT required to attend the event

Pablo — Alternative Event Naming

  • Survey received about 300 name suggestions from ~100 respondents
  • Top suggestions include “Core Newer,” “Now Here,” “Somewhere,” “Elsewhere,” and “Everywhere”
  • Duplicates and obvious conflicts removed; some names discarded for legal reasons
  • Ranked-choice vote to be sent to voting members by Monday or Tuesday at the latest
  • Suggestions to be posted openly in Discord for transparency
  • Final choice may need to account for legal considerations and DNS availability

Key Community Questions & Discussion

Containers

Multiple questions about the timeline for securing container access. Pepe confirmed this is the number one priority being actively accelerated. A clearer timeline is expected in a couple of weeks. The community was reminded that containers hold critical build infrastructure, though some teams have demonstrated they can build without knowing container contents.

Community Outreach

A community member asked about reaching out to the broader community. Pepe explained that GDPR compliance requires careful handling of mailing lists. Personal outreach (telling friends about the association) is not a GDPR issue and is encouraged.

Ticket Sales Timeline

Anna asked about the timeline for ticket sales and the event website. Daniel confirmed tickets will not go on sale until the go/no-go process is complete, providing at least until February 28–29. Participant wellness content (code of conduct, inclusion policies) needs to be on the website before sales begin. A separate event website will be needed once the event name is confirmed.

FIST Volunteer System

Ben F asked about using the open-source FIST software for volunteer task management. Peter confirmed the system is ready to deploy and could be launched quickly once a domain is available. There are some known issues to fix, potentially with AI assistance.

Action Items

  • Daniela — Continue vendor meetings and check on optional first aid training for coordinators
  • Ward — Share roles that need to be filled soon
  • Pablo — Post name suggestions in Discord and set up ranked-choice vote by Monday/Tuesday
  • Peter — Notify QA testers to move to production; coordinate with Ben F on FIST
  • Ben D — Publish official membership criteria; check Raffaella’s email and resend onboarding if needed
  • Kate — Share go/no-go timeline on Discord updates channel
  • Board — Determine earliest possible date for ticket sales and communicate it