Matti HiltunenI request a repo that will be managed by the RICAPP project (for now):
com/asn-to-json-converter
Summary: A streaming application that receives ASN.1 messages via Kafka and publishes them as JSON via Kafka
Description: The ASN1 to JSON converter is a Kafka Streamer application that received from the E2Terminator messages with ASN1 Binary payload (PER) that is encoded in Base64 and convert it to textual JSON that can be consumed by other applications. The converter receives the packed messages on an input Kafka Topic and publishes the input on dedicated output topics. Aligned with O1 tracing. Can be used for traces from any component that uses ASN.1 message format.
Request the addition of two more committers ORDWAY, ADAM G <ao8347@att.com>, LFID ao8347 and MEILINGER, JUSTIN <jx088j@att.com>, LFID jx088j to the it/otf Gerrit repository to help completing the Amber release target.
Source code repo is a recipe. The source code is not imported into the repo. It is the recipe that puts it there.
During build time the upstream.
Is the resulting build unique to our project so O-RAN SC will use that work.
Yes, it is optimized kernel and the packages.
Be careful in impacting all of our other resources and projects.
How often do you need to rebuild this?
No, we want to build once per release or patch releases. Maybe one or two times per release should be good.
Concerns about managing the resource consuming job. Work with Lusheng to schedule time early in the process so we can be efficient in the resources across projects and not block others.
Lusheng - tonight will provide the full report at the f2f.
We thought seed code is possible through open source. Binary is not an option on the table. We are reluctant to open our code to binary code. We learned binary code is being submitted by another vendor.
Jack - This is a rich topic for discussion. In open source the code is open and people can look and contribute. We've had discussions with companies about including the binary code as an option. Binary code is not a contribution to the open source community. However binary code can be used for integration and test. For example Intel wanted to keep their layer 1 software. They didn't have to contribute that software. Instead they are contributing a loader module that will pull in their binary from their location. The process to get their code is consistent. The open source community doesn't treat it as open source but instead uses it for test and integration. In this case the O-DU could choose to license from Intel and build it into their process. Intel would contribute the loader. The binary itself is not open source. The company would have to deal with Intel directly for their binary. They are not open source but are build, test, and integration options. The build APIs are open source.
Jinri - Do we need to discuss this with the O-RAN legal team?
The broader issue for us is that it is hosted by the Linux Foundation. These contributions aren't in source code. Theoretically, if you could contribute binary it would have to under one of our two licenses meaning people could use it. That is not their intent. It is best for them to keep their code under their management. If we use it for integration and test then O-RAN would have to set up how to make it available for us to use.
Jun Hyuk Song TOC membership. There are open vacancies for the TOC membership.
Jack - We want to promote open source developers. Interest in a viable candidate to contribute open source code.
Jun Hyuk Song What about xApps? Are there requirements for that?
Jack- We didn't put a hard requirement on contributing magnitude of code. Demonstrate your interest in the activity and the community.
F2F Summary
Samsung - contributions in the form of binary code.
Planning for Next Meeting
Open Discussion
Any Other Business (AOB)
Meeting Summary (resolutions, new action items, etc.)
Votes
The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
Request the addition of two more committers ORDWAY, ADAM G <ao8347@att.com>, LFID ao8347 and MEILINGER, JUSTIN <jx088j@att.com>, LFID jx088j to the it/otf Gerrit repository to help completing the Amber release target.