GQ-014 · Durable Upstream Bets

Which upstream teams and projects are worth adopting when maintenance, compatibility and eventual removal are considered together?

SISO Open Source Foundation

experimental

scoped

Not declared

Define the minimum public-safe question program before scheduling research.

No selected release

Not released — the selected Release has no public answer artifact.

hybrid

Adopt, adapt, retain or replace a source dependency using its actual long-term benefit and ownership boundary.

Compare a needed capability against realistic maintained alternatives and the option of building it. · Preserve upstream attribution and account for adaptation, compatibility, support and exit costs.

The dependency's total adaptation and maintenance burden consumes its claimed benefit. · A recommendation depends on popularity while failing the required interface, rights or continuity conditions.

Popularity and a single successful integration do not establish maintainer resilience or lifetime value.

New owner-approved outcome or counterexample changes the decision evidence. · The relevant source, operating constraint or acceptance boundary materially changes.

Public source histories, licenses and maintenance signals · Authorized integration, upgrade and removal receipts

A dated adoption decision with source evidence, alternatives, risk and exit conditions, plus what would change the decision.

Review when relevant owner evidence or decision conditions change; registration starts no collector, benchmark, scheduler or new execution lane.

public metadata only