Update readme or merge latest development with this repo?

[ffd8]

Great to see that this lib is still maintained here!
Kind of confusing that this main repo doesn't point there and that the new repo is a fork and thus doesn't have an issues section... perhaps a PR could merge that repo back here or somehow combine? Until now, this repo was the most up to date, but also suffered a lack of issues issue... it's too bad that somehow the latest one by @cansik is manually forked(?) so it doesn't show up in the network graph of progress while researching a solution for latest macos + apple silicon.

[cansik]

@ffd8 Issue section is enabled now, thanks for the hint: https://github.com/cansik/opencv-processing/issues

Here a brief history about what happened so far:

I started working on my fork back in 2020 when preparing a Processing and Computer Vision lecture. Due to my contributions at javacpp and my work with the Deep Vision for Processing library, I thought it would be great to update OpenCV for Processing to a more recent version. The work was quickly done by using the prebuilt opencv libraries from the JavaCV framework.

Because PR's are waiting for years to be merged (last in 2017)), I contacted Greg directly via email and he replied that he would be happy to merge a PR, but was less up to switch to JavaCV. I added more information why the switch would not change a lot in the codebase and could be very helpful in the future, but I never got an answer to that email**.

I opened the following discourse topic about my update to OpenCV4 and also opened this topic about
libraries that are not actively maintained and how to deal with it. There were some answers but nothing concrete was decided on how to deal with that problem.

Now in 2022 I noticed that the official OpenCV for Processing was still not updated and was not running on M1 chips (and other platforms). So I asked the maintainer of the contribution manager if it is possible to use my fork as the current version. He replied that others are working on updated forks as well (jaegonlee and n1ckfg) and that we should join forces. After some mails we decided to use my base to combine all the fixes from jaegonlee and n1ckfg (without Yolo).

Due to the fact that PR's do not seem to be merged and the complete build-system has changed, I detached my fork a few days ago. This can be reversed if needed.

** This should not be taken as an accusation (as already mentioned in discourse). All of us have projects that we close at some point.

[ffd8]

@cansik thanks for the thorough background and insights! Checked out all the links you placed throughout and:

Thanks again for taking this lib where it is now, together with additional contributors as mentioned. Thanks as well for activating the new repo's issues so discussion/bugs/etc can take place. it's probably still worthwhile to try and update the readme here to point towards it to help future folks, who once had it installed and now have issues due to upgraded hardware/os (thankfully no prob for those installing the first time within the manager).

From the discourse linked above about 'abandoned libs', I can also imagine situations where the libs had 'just worked' and then eventually the environmental updates (4.0 or latest hardware) stopped that being so. Even harder if the author isn't having those issues due to their own setup/workflow. And of course hard to get open-source-volunteers back maintaining them, not to mention how hard it can be to track a nickname from github to an email. While PRs might solve it, of course one wants to double check everything before hitting accept, not to mention everyone has their own way of doing things, so original author might not want to accept it. Anywho, I reeeally wish that github would have issues per fork, so a community can discuss given forks on their own and things stay connected within that network of code insights (oh so fun to browse and see who added/tweaked what).

Anyways - thanks again for the insights and looking forward to playing with OpenCV within Processing again on these latest m1 machines!