Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to locate the source code #345

Closed
ialbert opened this issue Apr 10, 2024 · 5 comments
Closed

Unable to locate the source code #345

ialbert opened this issue Apr 10, 2024 · 5 comments

Comments

@ialbert
Copy link

ialbert commented Apr 10, 2024

I may have misread the page, but I could not locate the tool's source code.

From the binary, it seems to be written in Go.

Is this tool a closed-source software?

@ialbert
Copy link
Author

ialbert commented Apr 10, 2024

moved it to a discussion.

@ialbert ialbert closed this as completed Apr 10, 2024
@ialbert
Copy link
Author

ialbert commented Apr 10, 2024

#346

@olearyna
Copy link
Contributor

Hi ialbert,

The tool isn't closed-source; we simply haven't made it publicly available yet. We do intend to release it, though we don't have a fixed timeline for this yet. And yes, it's developed in Go.
You can build your own client library in any language using the NCBI Datasets OpenAPI 3.0 specification. You can find more information here: NCBI Datasets API Documentation.

Nuala

Nuala A. O'Leary, PhD
Product Owner, NCBI Datasets
National Center for Biotechnology Information, NLM, NIH, DHHS

@ialbert
Copy link
Author

ialbert commented Apr 10, 2024

It is incorrect to claim that software is open source when it is unavailable. It makes no sense to say that it is open source, but we simply chose not to show you the code.

One of the essential ingredients of open source is that the source code is visible to the public.

Basically, what I think you are saying here is that you intend to release the code as open-source software at some point (in the future), but there is no timeline, and in the meantime, the software is closed source as of yet.

Your licensing is really odd, actually; it does not follow the standards that scientists use and, as such, sets the wrong example.

It lacks transparency, it does not allow others to build upon it, it does not promote learning etc.

I believe that you are not following the rules when publishing closed-source software. As a taxpayer-funded organization, you are (or should be) obligated to produce source code. I am surprised it is I who have to tell you that.

@corneliusroemer
Copy link

The client code has now been made public - thanks @olearyna, @BradHolmes, and everyone involved!

Having the source code was almost immediately useful, e.g. here: #448 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants