The maintainability of open source code 20 years from today
Formal Metadata
| Title | The maintainability of open source code 20 years from today |
|
| Title of Series | |
| Number of Parts | 69 |
| Author | |
| Contributors | |
| License | You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor. |
| Identifiers | |
| Publisher | |
| Release Date | |
| Language | |
Content Metadata
| Subject Area | |
| Genre | |
| Abstract | To commemorate 20 years since Doug Cutting open sourced Lucene and donated it to Apache, I want to talk about ways everyone can pitch in to ensure the long term viability of the open source project. Someone looking at replication code for the first time in 20 years, might really understand the behavior of something like master-slave. Even though we understand it today, the onus is on the contributors and maintainers to constantly add more clarity to a project. Landing such a complex PR can be tricky and usually involves multiple people. Here's how I did it, and here are a few other areas where I have been focused to improve the long-term viability of the code base. |
|