Summit Session 3 - Sustainable package maintenance models
summary
A community session recounts a concrete rescue: an inactive wake_lock package gets forked and released as wake_lock -> wake_lock_plus, with apps using pub dependency_overrides and the Flutter community GitHub org adopting shared publishing as Flutter community.dev publisher. Participants propose automation for stale-package handoffs (freshness triggers and name-release by pub), optional namespacing like npm, git-tag versioning for repo deps, and funding routes: GitHub Sponsors, thanks.dev, bounties/Flutter Bounty Hunters, corporate sponsorships or a nonprofit steward.
AI-written summary · about
chapters (7)
- 0:00Sustainable package maintenance
- 1:47Forking abandoned packages
- 10:52Funding models for maintainers
- 20:04Investing in Flutter
- 30:36Namespacing and ownership
- 38:50Package funding transparency
- 44:04Next steps and action
related talks
50mSustainable package maintenance models
30mHappy Developers, Healthy Modules - Together We Can Do This
39mManaging an Open Source Project
47mProject Talk: Maintenance Update
37mLessons learned from crafting an in-house framework
10mStreamlining npm modules and lock files Management
16mManaging multiple packages in a monorepo
16mMaintaining an OSS Project (Babel)