Ubuntu TechHive

Event Proposals

Review member-submitted ideas and support the topics you would attend.

Propose Event
proposals.index

8 proposals

  1. Proposed

    Cross-Team Handoff Lab: Write the Ticket Another Team Can Actually Ship

    Convert vague requests into context, constraints, examples, risks, and acceptance checks.

    Difficulty: Mixed Duration: 1 hour 30 minutes Target date: August 31, 2026 #collaboration#handoff#product
  2. Proposed

    Feature Deprecation Lab: Retire Old Workflows Without Surprising Loyal Users

    Plan notices, migration paths, compatibility windows, metrics, and support scripts for removals.

    Difficulty: Mixed Duration: 2 hours Target date: July 20, 2026 #deprecation#product#support
  3. Proposed

    Privacy-Respecting Analytics: Events, Consent, Retention, and Data Quality

    A practical two-hour session on Privacy-Respecting Analytics, focused on Events, Consent, Retention, and Data Quality. Attendees work through concrete engineering tradeoffs, review examples, and leave with a checklist they can apply in real team projects.

    Difficulty: Intermediate Duration: 2 hours Target date: January 19, 2027 #analytics#privacy#product
  4. Proposed

    Release Notes Lab: Explain What Changed So Users Actually Care

    Turn technical changes into clear, honest release notes for members, operators, and stakeholders.

    Difficulty: Mixed Duration: 1 hour 30 minutes Target date: October 27, 2026 #communication#product#release-notes
  5. Proposed

    SLO Poker: Decide What Reliability Is Worth Before It Fails

    A hands-on prioritization game for turning reliability tradeoffs into explicit product decisions.

    Difficulty: Mixed Duration: 2 hours Target date: June 15, 2026 #product#reliability#slo
  6. Proposed

    Search Relevance Lab: Fix Bad Results Without Guessing

    Diagnose why users cannot find content, then tune ranking with evidence instead of vibes.

    Difficulty: Mixed Duration: 2 hours Target date: June 20, 2026 #data#product#search
  7. Proposed

    Spec to Test Matrix: Catch Ambiguity Before It Becomes a Bug

    Turn a fuzzy feature request into edge cases, acceptance tests, and reviewable behavior.

    Difficulty: Mixed Duration: 1 hour 30 minutes Target date: August 14, 2026 #product#requirements#testing
  8. Proposed

    Support Debugging Desk: Turn Angry Tickets Into Reproducible Bugs

    Practice extracting facts, reproducing issues, and escalating with evidence instead of noise.

    Difficulty: Mixed Duration: 2 hours Target date: June 29, 2026 #debugging#product#support