-
Notifications
You must be signed in to change notification settings - Fork 1
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
Making the repo public? #253
Comments
Hi @mialondon, we're investigating this at the moment. I don't believe there are barriers, but before opening it there are still some last steps required, including updating the API to the latest changes, testing, reviewing the documentation, and figuring out where we put all the resources that are required to run T-Res (we've already decided to put some in the BL research repository, but the the wikipedia/wikidata resources are quite heavy, so we might just point to the repo where they have been created, instead. We still need to make a decision about this). |
How big is big? Elsewhere a 5gb file is going in (when the repository software people fix a bug). |
Graham is checking with the developers to see if there's an absolute fize size limit but he doesn't know of one, so size probably doesn't matter. |
Thank you @mialondon! |
@mcollardanuy one of Kalle's last To Do notes was about making this repo public. Are there any plans for this underway, and are there any barriers to making it public?
The text was updated successfully, but these errors were encountered: