Release 1.0.0, 24.04.

Author: p-ogrady

.dockerignore

@@ -0,0 +1,15 @@
+.git
+# Python cache
+.pytest_cache
+__pycache__
+# cache
+.cache
+# build folders
+build*
+*.egg-info
+# tao peoplenet files
+*.fp16
+*.onnx
+# NSight profiler files
+*.ncu-rep
+*.nsys-rep

.flake8

@@ -0,0 +1,2 @@
+[flake8]
+max-line-length=88

.gitattributes

@@ -0,0 +1,5 @@
+**/*.pcap filter=lfs diff=lfs merge=lfs -text
+**/*.pdf filter=lfs diff=lfs merge=lfs -text
+**/*.png filter=lfs diff=lfs merge=lfs -text
+.gitlab-ci.yml export-ignore
+RELEASE.sh export-ignore

.gitignore

@@ -0,0 +1,17 @@
+__pycache__
+.cache
+*.swp
+ci/coverage.xml
+dist
+tags
+cscope.*
+# cache
+.cache
+# build folders
+*.egg-info
+# tao peoplenet files
+*.fp16
+*.onnx
+# NSight profiler files
+*.ncu-rep
+*.nsys-rep

CMakeLists.txt

@@ -0,0 +1,30 @@
+# SPDX-FileCopyrightText: Copyright (c) 2024 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
+# SPDX-License-Identifier: Apache-2.0
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+cmake_minimum_required(VERSION 3.20)
+
+project(hololink)
+
+find_package(holoscan 0.6 REQUIRED CONFIG PATHS "/opt/nvidia/holoscan")
+
+# add CMAKE_MODULE_PATH for pybind11_add_hololink_module
+list(APPEND CMAKE_MODULE_PATH ${CMAKE_SOURCE_DIR}/cmake)
+
+if(NOT CMAKE_INSTALL_LIBDIR)
+  set(CMAKE_INSTALL_LIBDIR lib)
+endif()
+
+add_subdirectory(src)
+add_subdirectory(python)

CONTRIBUTING.md

@@ -0,0 +1,153 @@
+# Contributing to Holoscan Sensor Bridge
+
+## Table of Contents
+
+- [Introduction](#introduction)
+- [Types of Contributions](#types-of-contributions)
+- [Developer Workflow](#developer-workflow)
+- [Preparing your submission](#preparing-your-submission)
+- [Reporting issues](#reporting-issues)
+
+## Introduction
+
+Welcome to Holoscan Sensor Bridge! Please read our [README](./README.md) document for an
+overview of the project.
+
+Please read this guide if you are interested in contributing open source code to
+Holoscan Sensor Bridge.
+
+## Types of Contributions
+
+Before getting started, assess how your idea or project may best benefit the Holoscan
+community.
+
+If your code is:
+
+- _feature-complete and tested_: Submit a
+  [pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)
+  to contribute your work to Holoscan Sensor Bridge.
+- _a work in progress:_ We recommend to
+  [fork](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo)
+  Holoscan Sensor Bridge and track your local development there, then submit to Holoscan
+  Sensor Bridge when ready. Alternatively, open pull request and indicate that it is a
+  "work-in-progress" with the prefix "WIP".
+- _a patch for an existing application or operator_: Submit a
+  [pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)
+  and request a review from the original author of the contribution you are patching.
+
+We recommend referring to contributing guidelines for testing and styling goals
+throughout your development process.
+
+## Developer Workflow
+
+### Requirements
+
+We recommend that new developers review GitHub's
+[starting documentation](https://docs.github.com/en/get-started/start-your-journey)
+before making their first contribution.
+
+### Workflow
+
+1. Developers must first [fork](https://help.github.com/en/articles/fork-a-repo) the
+   \[upstream\](https://github.com/nvidia-holoscan/holoscan-sensor-bridge) Holoscan
+   Sensor Bridge repository.
+
+1. Git clone the forked repository and push changes to the personal fork.
+
+   ```bash
+   git clone https://github.com/YOUR_USERNAME/YOUR_FORK.git
+   # Checkout the targeted branch and commit changes
+   # Push the commits to a branch on the fork (remote).
+   git push -u origin <local-branch>:<remote-branch>
+   ```
+
+1. All code submissions must be formatted according to the rules in `ci/lint.sh`. You
+   can run `ci/lint.sh --format` to automatically format all C++, Python, and Markdown
+   files-- usually that's enough to get `ci/lint.sh` to pass.
+
+1. Once the code changes are staged on the fork and ready for review, please
+   [submit](https://help.github.com/en/articles/creating-a-pull-request) a
+   [Pull Request](https://help.github.com/en/articles/about-pull-requests) (PR) to merge
+   the changes from a branch of the fork into a selected branch of upstream.
+
+   - Exercise caution when selecting the source and target branches for the PR.
+   - Creation of a PR creation kicks off the [code review](#preparing-your-submission)
+     process.
+
+1. Holoscan Sensor Bridge maintainers will review the PR and accept the proposal if
+   changes meet Holoscan Sensor Bridge standards.
+
+Thanks in advance for your patience as we review your contributions. We do appreciate
+them!
+
+### License Guidelines
+
+- Make sure that you can contribute your work to open source. Verify that no license
+  and/or patent conflict is introduced by your code. NVIDIA is not responsible for
+  conflicts resulting from community contributions.
+
+- We encourage community submissions under the Apache 2.0 permissive open source
+  license, which is the [Holoscan Sensor Bridge License](./LICENSE).
+
+- We require that members [sign](#signing-your-contribution) their contributions to
+  certify their work.
+
+### Coding Guidelines
+
+- All source code contributions must strictly adhere to the Holoscan Sensor Bridge
+  coding style.
+
+### Signing Your Contribution
+
+- We require that all contributors "sign-off" on their commits. This certifies that the
+  contribution is your original work, or you have rights to submit it under the same
+  license, or a compatible license.
+
+- Any contribution which contains commits that are not Signed-Off will not be accepted.
+
+- To sign off on a commit you simply use the `--signoff` (or `-s`) option when
+  committing your changes:
+
+  ```bash
+  $ git commit -s -m "Add cool feature."
+  ```
+
+  This will append the following to your commit message:
+
+  ```
+  Signed-off-by: Your Name <[email protected]>
+  ```
+
+- Full text of the DCO:
+
+  ```
+    Developer Certificate of Origin
+    Version 1.1
+    
+    Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
+    1 Letterman Drive
+    Suite D4700
+    San Francisco, CA, 94129
+    
+    Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
+  ```
+
+  ```
+    Developer's Certificate of Origin 1.1
+    
+    By making a contribution to this project, I certify that:
+    
+    (a) The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or
+    
+    (b) The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or
+    
+    (c) The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it.
+    
+    (d) I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.
+  ```
+
+## Reporting issues
+
+Please open a
+[Holoscan Sensor Bridge Issue Request](https://github.com/nvidia-holoscan/holoscan-sensor-bridge/issues)
+to request an enhancement, bug fix, or other change in Holoscan Sensor Bridge.