Because some of nnstreamer elements are not yet implemented, or in
poor quality, it appears that I may need to try gst-plugins-bad first.
However, there are a few questions before acually preparing for upstreaming
the code to gst-plugins-bad.
Q1. May I ignore autotools script and add meson scripts only?
(we are using CMake for now and will change it to meson soon)
Q2. If I want to keep the developmental processes in
github.com/nnsuite/nnstreamer so that I can keep running the current CI
systems for nnstreamer, with the newly introducing GStreamer Gitlab,
I'll need to send pull-request (or merge-request) from ours
to GStreamer repos.
Then, may I send a set of whole commits as a single pull-request (e.g.,
50 commits in a single PR) from "nnstreamer.git" to "gst-plugins-*.git"?
Or, should I sens each pull-request with a specific topic (so that there
will be around 1 to 4 commits in a single PR)?
If the latter is the case, should we start with hundreds of PRs for the
first PR (pull-request) to gst-plugins-*.git? or can we send them in a single
PR or a single commit?
(https://github.com/nnsuite/nnstreamer/ has currently 452 commits)
Because we want our own CI system (we need to support Tizen with a lot of
Tizen test cases), we'd prefer to have our own github repo and upstream
a set of commits for each RC version or weekly to gst-plugin-*.git.