While working with Processing now for several years, I noticed that some of the most used libraries do never get an update or are maintained actively. Here just a few examples:
- oscp5 (last updated on github 5 years ago - contribution manager version is even older)
- opencv-processing (last update 3 years ago - still uses opencv 2.0)
- OBJexport (last updated 7 years ago)
- and so on…
I am not listing them to blame the developer, I really appreciate the work they did and totally understand that they maybe move on and are not actively contributing to the community anymore. To be honest, I myself also have libraries that are not actively developed and at a point, a library can be feature finished. But in my opinion this leads to a serious problem for the Processing community:
The libraries may still work, but a lot of people would have improvements, that never find the way back into Processing, because the maintainer is not acting on PR & issues anymore. Even worse, because the library owner holds the “key” to the Contribution Manager, forking a library and releasing it is not even possible.
I myself always tried to contact the library manager himself, some of them answered, some not, some where happy that I added something new, but then did not release it (because it’s too much effort). To be honest, that is a bit frustrating.
That’s why I rather consider rewriting a complete library myself and publish it under a new name, instead of contributing to an already existing but inactive one.
And here I would like to open the discussion:
- Have you experienced the same?
- Do you think it is a problem that libraries are not maintained?
- How should we as a community deal with libraries that are not actively maintained?
- Are we going to open the contribution manager for forks?
- How do we transfer the maintainer? (Should we?)
Btw.: I opened this thread in the Processing forum and not the Library forum, because it is a more general question on how to deal with maintenance of Processing code.