-
Notifications
You must be signed in to change notification settings - Fork 27
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
Assigning correct data to correct courses/trainings #96
Comments
Hi, we have 600mb training files for SD4CP training/course. It still sitting on HOT's Google Drive and my hard drive. I'm thinking the best way to upload it all files through InaSAFE Dropbox since our connection is really sloooow :( |
Looking at the InaSAFE dropbox it tells me that you already joined the On Wed, Dec 4, 2013 at 11:26 AM, emirhartato [email protected]:
|
Yes that is why I edited my previous comment ;) I will put it a new folder and will upload all the contents overnight. |
Be Aware that we already use 1.8GB of the 2.25GB free space available there On Wed, Dec 4, 2013 at 11:42 AM, emirhartato [email protected]:
|
Errrr.... is it possible to link it directly from Google Drive? |
hmm .. not that I currently know of .. |
623 megabytes |
So we should have enough space if someone is accepting an invitation and On Wed, Dec 4, 2013 at 12:00 PM, emirhartato [email protected]:
|
I can have a look at deleting some of the datasets inside the inasafe dropbox. WE have packages in there that we could put somewhere else. |
Okay, I have looked at the dropbox and shifted some things around and will now update rst files. |
Problem
The training material data is currently not really linked inside the documentation.
I already added the general link to
../training/index.rst
../training/intermediate/index.rst
../training/socialisation/functionality_datasets.rst
../training/socialisation/index.rst
but I think we need to be more specific
Suggested Solution
Expected Results
No confusion among visitors to find the correct data for each training/course.
CC
@emirhartato @wonderchook
As this is a hotfix it should be in "master" AND "develop" branch
The text was updated successfully, but these errors were encountered: