People like Karthik (Climate Science people probably) are not used to Git/Github -> we should put together a quick description/documentation + ressources to get them started asap with our workflow on github
@ClementFeltin is part of an NGO creating CC educational resources and they'd like to be part of a potential beta-testing programme we may have some day
The website for the crowd source image collection project (we need a better name by the way) needs some actual UI design. I have create some basic prototypes just to have something from which to work from but in the grand scheme of things, if we want to use this project for more than floods, we will need to think about this. Here is a list of the main functionality I think the website should possess:
Usable through a web page or a mobile app. We will use React Native for this. I have the Android part covered, however, even though React Native create the necessary files to build a project for iPhone, we still need a Mac, a XCode license, an Apple Developer license and to tailor the app for the AppStore guidelines.
User can upload one or more picture(s) from their phone or take one using their camera.
User can read about who we are, the goals of the project and legal stuff for their images.
Once a user has uploaded their image(s), they can preview what they will send and delete those they do not want to send anymore.
The user can send their image(s) or cancel.
For me, this is the bare minimum. Now, if we want to scale this to other type of natural disasters, my concerns are as follows:
We can either leave the website as is. This will allow us to quickly promote it and hopefully reach an audience. However, we will need to skim through all the pictures ourselves to organize them by natural disaster.
We can add a description box. But then the user needs to enter text and the process is slower and more tedious which might make them less inclined to use it.
Edit:
Suggestions to be RGPD compliant:
Handling creation of an account.
Provide the user with a unique ID associated with the images. They can then contact us by email to get their images removed.
We need to work on this workflow so everyone should start adding issues, even if they are not critical, just to get a feel of how things work issues, labels, assignments, interaction org <-> project <-> repos, the role of kdb and so on