Library tensorflow_lite_mirror repo no longer exists about library-registry HOT 3 CLOSED

Sorry! I somehow missed the original response to this issue.

Thanks for all the info, knowing the publishing workflow for this specific library makes sense to have it as a private repo.

As you mentioned, if the repo was made public it could have the issues disabled, but I don't think at this point that PRs can be disabled as well.

Would you mind telling me what was the reason you encountered this 404? This might give us a better understanding of the need to make the repository public.

I was basically looking for the tflite source code in the Arduino library format to easily it hack into a self contained project (all libraries used in the same repo). This was mostly to save me the time to learn how to create it (or a different output format) from the tf repository. In the end I just installed the library via Arduino IDE and transferred the code from there.

from library-registry.

Hi @carlosperate. The repository does exist, but it is private.

The reason for this repository is that, in order to be added to Library Manager, a library repository must have a specific structure (valid Arduino library with metadata located in the root of the repository). The upstream TensorFlow Lite source code does not have this structure, so it's not possible to distribute it directly via Library Manager:
https://github.com/tensorflow/tensorflow/tree/master/tensorflow/lite

So the upstream source code is repackaged as a valid Arduino library and then hosted in the bcmi-labs/tensorflow_lite_mirror repo solely for the sake of indexing. Since this repository is purely a mirror, it will be problematic if people submit issue reports or pull requests. So it's set to private purely to prevent that, not because anything in the repo is secret (it's available to the whole world via Library manager after all). It is quite common for popular public mirror repos to end up acting as a "honey pot" to waste the time of prospective contributors, despite earnest efforts by the maintainers to communicate that this is not supported.

I think GitHub does have some features that would allow that issue be mostly prevented if the repository was set up correctly. However, I'm not sure whether it's worth the effort to do that for this particular repo. Would you mind telling me what was the reason you encountered this 404? This might give us a better understanding of the need to make the repository public.

from library-registry.

Closing due to lack of activity. If you ever want to resume discussion on this subject I'll be happy to reopen.

from library-registry.