Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

openjs summit session tracking issue #74

Closed
boneskull opened this issue Jun 15, 2020 · 10 comments
Closed

openjs summit session tracking issue #74

boneskull opened this issue Jun 15, 2020 · 10 comments

Comments

@boneskull
Copy link
Collaborator

boneskull commented Jun 15, 2020

SCHEDULE: https://openjscs2020.sched.com/event/clHF/nodejs-tooling-group-collaboration

See openjs-foundation/summit#299

@boneskull
Copy link
Collaborator Author

@nodejs/tooling

we need an agenda. We can just pull stuff off of the list like usual, but we're also likely to have more participants that aren't normally involved.

the way this usually goes is that we give an introduction to what the group is and what it does and what it's done. that's fine

personally, I like to get more ideas from the community about what's important to them and what pain points they are having.

@darcyclarke
Copy link
Member

I'd like to propose an agenda item:

  • Discuss adding a standing mob programming session alongside our weekly call:
    • would be a 1hr timeslot (don't need to use the entire session if there's no work to be done)
    • would happen after our weekly call (so that we can discuss work before diving in)
    • we'd have a rotating "driver" &/or can rotate during the session if it makes sense
    • this should help push work forward (as it forces some dedicated time to be allotted to resolving our backlog) & garner better consensus/understanding

@bcoe
Copy link

bcoe commented Jun 25, 2020

I thought it worked well at the last event where we floated a few topics we were thinking of covering, and allowed the attendees to pick a few for discussion. Given our hour slot, perhaps we could cover 2 or 3 ideas.

@iansu
Copy link
Contributor

iansu commented Jun 25, 2020

What time is this meeting? The schedule doesn't include a timezone. Is it June 25th at 12pm Pacific?

@bengl
Copy link
Member

bengl commented Jun 25, 2020

@iansu The time zone for the schedule is UTC-5 (i.e. CDT), so the meeting is scheduled for 2pm EDT, 11am PDT. (I hope I did that math right?)

@bcoe
Copy link

bcoe commented Jun 25, 2020

I was given a calendar invite, as I'm co-hosting the session, it's 11AM PDT (Ben time).

@bengl
Copy link
Member

bengl commented Jun 25, 2020

I thought it worked well at the last event where we floated a few topics we were thinking of covering, and allowed the attendees to pick a few for discussion. Given our hour slot, perhaps we could cover 2 or 3 ideas.

I'm all for this. I'd recommend avoiding fs hooks as a topic though, since that's being covered in the sightly-overlapping Unified Hooks meeting.

@boneskull
Copy link
Collaborator Author

agree w/ @bengl

@boneskull
Copy link
Collaborator Author

can somebody volunteer to take notes

@boneskull
Copy link
Collaborator Author

I guess that somebody was me.

Minutes landed in f9bb0d9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants