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

Structuring a "Breakout Teams" project board #244

Closed
1 of 7 tasks
SMotaal opened this issue Dec 23, 2018 · 2 comments
Closed
1 of 7 tasks

Structuring a "Breakout Teams" project board #244

SMotaal opened this issue Dec 23, 2018 · 2 comments

Comments

@SMotaal
Copy link

SMotaal commented Dec 23, 2018

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.

@SMotaal SMotaal added modules-agenda To be discussed in a meeting discussion labels Dec 23, 2018
@SMotaal
Copy link
Author

SMotaal commented Dec 23, 2018

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

@SMotaal SMotaal pinned this issue Dec 23, 2018
@SMotaal SMotaal unpinned this issue Dec 23, 2018
@MylesBorins MylesBorins removed the modules-agenda To be discussed in a meeting label Jan 29, 2019
@MylesBorins
Copy link
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 subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants