The Changelog: Software Development, Open Source Naming conventions that need to die (News)
Oct 21, 2024
This discussion dives into the frustration over unclear naming conventions in software, stifling clarity and innovation. It touches on the implications of Bitwarden's shift to proprietary software. There are practical tips for code collaboration and security updates, along with the importance of networking at conferences. Finally, it highlights the value of informal interactions at events and recent advancements in WordPress, particularly its integration with SQLite.
AI Snips
Chapters
Transcript
Episode notes
Effective Naming Conventions
- Use names that facilitate understanding and avoid eponymous or numbered names.
- Don't use overloaded terms; create fresh names or add specific suffixes.
Bitwarden's Licensing Change
- Bitwarden introduced a proprietary dependency, raising concerns about its open-source status.
- Founder Kyle Spearin claims the change maintains GPL compatibility, but users remain skeptical.
Forking Best Practices
- Maintain forks effectively with atomic commits, clear identification of fixes, and avoiding unnecessary merges.
- Rebase frequently, contribute upstream, and keep a good relationship with the original project.