Session Proposal: Package Maintenance Working Group For Maintainers

[wesleytodd]

Proposal

Topic of the session

The Package Maintenance Working Groups will present what we are working on for project maintainers.

Type of the session

• Collaborate
• Workshop
• Talk

Session facilitator(s), Github handle(s) and timezone(s)

• @wesleytodd (Pacific US Time)
• @ghinks, you are interested right? (Eastern US Time)
• Other members of @nodejs/package-maintenence TBD (discussion: Submit sessions to Collab Summit nodejs/package-maintenance#335)

Estimated duration of the session

1 hour

Follow-up / Set-up sessions (if any)

Level

• Beginner
• Intermediate
• Advanced

Pre-requisite knowledge

None, but we hope to reach project maintainers.

Describe the session

The Package Maintenance will present some of our work to open a conversation with project maintainers (OpenJSF member projects or external). We hope to find partners to work with on our programs, as well as get feedback from important projects in the ecosystem.

Additional context (optional)

See here for our team discussion: nodejs/package-maintenance#335

---

This section is for contributors handling Collaborator Summit logistics

Track

• New Contributor Orientation Track (see New Contributor Orientation Track #251)
• Regular Track
• Cross-Project Track

Triage

• Track chosen
• Scheduled

[ghinks]

I'm signing on with you @wesleytodd

[ghinks]

@wesleytodd I'm going to start a draft document. It will at least be a starting point.

[ghinks]

@jorydotcom Jory how long are these talks? Previously we have talked, when I say we I mean @wesleytodd , for about 10 minutes then opened the floor up to questions. As the format is remote and what we have done previously in person may be difficult I find myself wondering how format the presentation.

[jorydotcom]

@ghinks they can be as long as you want or need, but I'm encouraging shorter 'talks' so that there's more time for discussion. It would be better to think about it less as a 'Talk' and more like a short presentation that frames a discussion. You will have as much (or as little) time as you need!

[ghinks]

🙏🏻

[wesleytodd]

Hey, just taking a look to make sure everything is prepared for this, and I don't see the time schedule in here. I know you all are busy getting everything sorted, so no rush, just thought I would ask.

[wesleytodd]

I see this doc got merged, so disregard my previous comment!

[ghinks]

@wesleytodd I sent you access to the slides and the talk notes.

I have incorporated the talk notes into the slides and I have emailed you access to them on slides.com

[wesleytodd]

Yep, that email was buried, but I just logged in and it looks like a good structure. I will add some comments into the slides.com comments tonight!

[ghinks]

Excellent, we will almost certainly have to get on a call together to align before we present

[ghinks]

@jorydotcom, apologies just read the instructions can you add me to the QIQO access list for the event. Sorry @wesleytodd just reading these instructions for Friday.

[wesleytodd]

@ghinks You just need to register for the event. There were some issues with it on Monday, but I assume those are worked out and just registering on both platforms with the same email (like the instructions detail) should work.

[wesleytodd]

Closing, as session is complete and went well. Thanks all!

[jorydotcom]

Notes from the session

@wesleytodd do you recall if this session was recorded?