Rohit Lodha

@tomokos2 Yes, you can. You don't need to be an assignee to work on the issue.

@tomokos2 The 1st option looks fine to me. Having a common template that contains common functions and elements will be the way to go.

@goneall Is there a better RDF file we can use for tests? The current one - https://github.com/spdx/spdx-online-tools/blob/main/src/examples/SPDXRdfExample-v2.0.rdf - raise issues like `'org.spdx.library.model.SpdxIdInUseException: Can not create Apache-2.0. It is already in...

@goneall Thanks for the help! The new files worked perfectly! Now all the tests in api are passing, except one which is getting skipped. Will try to run that too...

You can host the website on Heroku (or any other free hosting service) for a production-like server. We don't expect these types of issues to be fixed by non-admin people...

@goneall @Ugtan Great idea! Having a tool that can raise an issue when the license submit feature/ license namespace submit feature fails in production is much needed. It will help...

@swinslow That makes sense. We are discussing a possibility to have a tool that will automatically raise the issue on author's behalf on our repo (not to the mailing list)...

@Ugtan Overall looks good to me, Can you also paste the screenshot/issue created after clicking submit? Left some comment to address, I'll merge it after that.

@Ugtan Can you please address the comments and post the screenshot here?

@Ugtan ping