> Ok, I'm able to start looking into that. > > Well, "language binding", it would basically be just the C API for starters. > I think that would be enough for DJL though. > @lanking520 @frankfliu Would there be anything specific from your team? > > For Jenkins, I assume I'd need to get access to the server and everything to > do something with that myself... > What about GitHub Actions? I see there is some work going on with those. Are > there plans to switch to that? > > For the docs, that would be something like the Jenkinsfile_website_java_docs > in the v1.x branch? > I also see a couple of short Markdown files there for getting started and > tutorials, so something like that... using the C API?
I would recommed to provide a basic Java interface that allow all Java developers can build frontend to it. As Sheng mentioned, you can start with the Jenkins template to add a Java publish job to it. -- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-mxnet/issues/17783#issuecomment-740030548
