Bilingual

Reconsider
a day ago
- The author initially licensed Keygen under ELv2 and called it 'open source', but realized that caused miscommunication and was perceived as dishonest.
- After trying 'source-available' and other ambiguous terms, the author discovered Sentry's 'fair source' model with Delayed Open Source Publication (DOSP).
- DOSP adds a timer to a proprietary license, after which the code becomes truly open source, ensuring longevity even if the author abandons the project.
- The author was convinced by Sentry's founders to adopt DOSP, despite initial fear, because it benefits users and customers by backing up promises of longevity.
- The author wrote a new license blending FSL and ELv2, relicensed Keygen under DOSP, and adopted the 'fair source' label.
- The author calls on 37signals to reconsider their stance on open source terminology and codify their promise of longevity, as they already have that promise in spirit.
<antirez>
a day ago
- The author left Redis 4.44 years ago and avoided all related work, but returned after feeling a lack of purpose and concern over community fragmentation.
- They contacted Redis CEO Rowan Trollope for a part-time role as a 'bridge' between the company and community, focusing on demos, design, and documentation.
- The author argues the license switch from BSD to SSPL is understandable, as it prevents cloud providers from using Redis without revenue sharing.
- They see vector capabilities as a natural fit for Redis, introducing 'Vector Sets' (e.g., VSIM command) for K-NN searches using embeddings.
- The author emphasizes Redis as 'Lego for programmers,' leaving design flexibility to users rather than enforcing rigid patterns.
- AI tools like Claude have helped the author improve coding and writing efficiency, and they believe vector search is crucial for Redis's future.
Why Copyright Analysis Alone Is Not Enough for Open Source Licensing
16 days ago
- Japanese IP advice on open-source licensing often focuses narrowly on copyright law (Layer 1) while neglecting contractual issues (Layer 2) and practical business/community concerns (Layer 3), leading to impractical conclusions for companies.
- Modern licenses, including AI model terms and source-available licenses, are designed as contracts with use restrictions, requiring analysis of enforceability, jurisdiction, and breach consequences beyond copyright infringement.
- Global business operations, community norms, and reputational risks must be considered, as decisions based solely on Japanese law may ignore suspension risks, compliance costs, and ecosystem expectations.
- Effective licensing decisions require collaboration among legal teams, engineers, and Open Source Program Offices (OSPOs) to integrate legal, technical, and community perspectives.
- Companies should ask broader questions about license acceptance in global contexts, internal policy alignment, and community trust, rather than just legal enforceability under Japanese law.

Hasty Briefsbeta

open source licensing

Reconsider

<antirez>

Why Copyright Analysis Alone Is Not Enough for Open Source Licensing