Skip to content
This repository was archived by the owner on Sep 2, 2023. It is now read-only.
This repository was archived by the owner on Sep 2, 2023. It is now read-only.

Structuring a "Breakout Teams" project board #244

Description

@SMotaal

Let's discuss how we want to structure the Breakout Teams project board here which was created per last meeting discussions related to Discussion: Organizing work #230.

Proposed Structure

  • Board

    • Purpose: to coordinate breakout teams efforts across phases

    • Template: None
      We're simply using this to structure efforts

  • Columns

    • General: Structure (top), announcements, overlapping issue cards... etc.

    • Teams: Spotlight (top), events, milestone checklists, specific issue cards... etc.

    • Meta: References, community matters... etc.


Updated regularly to reflect decisions reach below.

Activity

  1. SMotaal commented on Dec 23, 2018

    @SMotaal
    Author

    Please join #244 for discussing how we want to structure the newly created teams board (/nodejs/modules/projects/6). I'd like to invite members from the various teams to coordinate and to begin creating and populating respective columns to help us figure what works best more organically.

    cc @nodejs/modules

  2. pinned this issue on Dec 23, 2018
  3. unpinned this issue on Dec 23, 2018
  4. MylesBorins commented on Apr 10, 2019

    @MylesBorins
    Contributor

    Closing this as there has been no movement in a while, please feel free to re-open or ask me to do so if you are unable to.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions