Non-free materials in repo: WSDL files and documentation #956

stevendh commented 2023年03月08日 22:12:09 +01:00

A piece of software I want to develop on Codeberg talks to a private SOAP web service. I have the associated WSDL files and the documentation here, and if possible I'd like to add them to project repository. Particularly the WSDL descriptions would be handy to include, the stubs generated from them would be part of the working software program.

At this moment I don't have explicit permission to release these files publicly. If I am allowed to do that, I don't know under what licence that would be. In case that's not a free software/culture licence, would it still be acceptable for inclusion on Codeberg? The ToS mention limited exceptions to the requirement to free licensing, but I feel that what I'm asking is a good bit larger than that.

A piece of software I want to develop on Codeberg talks to a private SOAP web service. I have the associated WSDL files and the documentation here, and if possible I'd like to add them to project repository. Particularly the WSDL descriptions would be handy to include, the stubs generated from them would be part of the working software program. At this moment I don't have explicit permission to release these files publicly. If I am allowed to do that, I don't know under what licence that would be. In case that's not a free software/culture licence, would it still be acceptable for inclusion on Codeberg? The ToS mention limited exceptions to the requirement to free licensing, but I feel that what I'm asking is a good bit larger than that.

fnetX commented 2023年03月08日 22:59:47 +01:00

Tough question. Depending on the size of the file, it might be okay. In any case, please make it really unambiguous that this file is not covered by a FLOSS license.

But if it's really just one or a few file(s), it might be easiest to upload them somewhere else (maybe even as an issue attachment?).

Tough question. Depending on the size of the file, it might be okay. In any case, please make it really unambiguous that this file is not covered by a FLOSS license. But if it's really just one or a few file(s), it might be easiest to upload them somewhere else (maybe even as an issue attachment?).

stevendh commented 2023年03月08日 23:26:23 +01:00

The WSDL are a lot of files: at the moment there are 206 files in 89 maps, totalling 20716 lines, just under a megabyte in size. I expect that to grow organically. This is distributed to the developers of the SOAP API clients as about fifteen zip files. It's all a bit tedious to work with and get in the right form at the exact right spot. That's why I'd like to distribute them along with my code, if possible. But I realize it's not a small exception I'm asking.

The documentation consists of about twenty PDFs and a few text documents, circa 15 MiB.

The WSDL are a lot of files: at the moment there are 206 files in 89 maps, totalling 20716 lines, just under a megabyte in size. I expect that to grow organically. This is distributed to the developers of the SOAP API clients as about fifteen zip files. It's all a bit tedious to work with and get in the right form at the exact right spot. That's why I'd like to distribute them along with my code, if possible. But I realize it's not a small exception I'm asking. The documentation consists of about twenty PDFs and a few text documents, circa 15 MiB.

fnetX commented 2023年03月08日 23:41:42 +01:00

You could create a private repository for this, then, if this suits your workflow. We currently generally don't act on private repositories if the total size does not exceed 50MB.

You could create a private repository for this, then, if this suits your workflow. We currently generally don't act on private repositories if the total size does not exceed 50MB.

stevendh commented 2023年03月09日 15:31:40 +01:00

Hm, yes, perhaps as a git subtree or something? Or just a directory next to the repo (../wsdl/) where the zip files go, and let the build script figure out unzipping et cetera. I'll think and try to find something that works.

Thanks for your consideration!

Hm, yes, perhaps as a git subtree or something? Or just a directory next to the repo (`../wsdl/`) where the zip files go, and let the build script figure out unzipping et cetera. I'll think and try to find something that works. Thanks for your consideration!