Sub-module or containment?

[brmarkus]

It looks like many libraries under "https://github.com/open-edge-platform/edge-ai-libraries/tree/main/libraries" are GIT sub-modules except "dl-streamer".

Is there a GIT feature to get notified about changes regarding specific sub-libraries only?
Currently I get notified about issues/pullrequests/discussions etc. regarding this whole repository where I would be interested in a few sub-libraries only (e.g. dl-streamer).

[biapalmeiro]

You can customize how you watch a repository. More instructions in the link below:

https://docs.github.com/en/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository

[brmarkus]

Yeah, sure.

"Watching" is based on repository base... But if a repository contains copies of components than changes to that "copy" cannot be watched specifically.

Subscriptions can be configured, again on a per repository base:

Sub-modules are considered and notified in case the commit-ID has been changed.

I'm specifically interested in modifications to e.g. "DL-Streamer". But it's a "copy" and not a Git-sub-module like the other components:

In the original DL-Streamer repo https://github.com/dlstreamer/dlstreamer we (users, maintainers, contributors) were told to use the "copy" under https://github.com/open-edge-platform/edge-ai-libraries/ instead and future issues/pull-requests/featre-requests shall be directed to here?

[biapalmeiro]

Then I don't have a good answer for you now. Let me investigate. @jangorecki1, from the governance perspective, do you have any comments regarding the following question:

In the original DL-Streamer repo https://github.com/dlstreamer/dlstreamer we (users, maintainers, contributors) were told to use the "copy" under https://github.com/open-edge-platform/edge-ai-libraries/ instead and future issues/pull-requests/featre-requests shall be directed to here?

[jangorecki1]

@xwu2intel , can you provide advice on it?

[brmarkus]

Have you had a chance to internally discuss this topic?
Why making a copy from the original repository - and not treating DL-Streamer as a GIT sub-module (like the other dependencies)? Why calling DL-Streamer "Edge Platform", "Edge AI Library"?

The original repo "https://github.com/dlstreamer/dlstreamer" hasn't been archived, yet. A note about deprecation or suspension of support&maintenance has not been added, yet.
The changes made to DL-Streamer in this repo have not been backported to the original repo.

[biapalmeiro]

I'm sorry for the delay on answering your question. It is still under discussion.

[pmalatyn]

DL-Streamer is now part of the Open Edge Platform, offered as one of our AI Libraries and that is why it is now called "Edge Platform”, "Edge AI Library”.
The original repo won’t be archived until August 2025 when next release of whole platform will happen. Appropriate notes were added to legacy DL Streamer repository.

[brmarkus]

Thank you for the clarification.

For a maintainer of DL-Streamer in the old repo is was easy to receive DL-Streamer specific notifications (PullRequests, Issues, asks for support).

In the new repo, however, there are lots of lots of other notifications regarding the other ingredients and libraries. With Github there can't be DL-Streamer specific notifications the way it is integrated.

DL-Streamer offers OpenVINO functionality to a media-processing framework like DL-Streamer. There is not so much edge-specifics with OpenVINO... quite the opposite....