Transfer requirements from notes doc to GH Issues

[pterygaphykion]

Convert requirements from the Project Requirements doc to github issues so we can track milestones.

[jgaehring]

I moved those requirements to a new public repository, since it covers 2 separate interventions for the pilot project with RGO, this Early Warning System being only one. I figure that way it can live there for future reference and provide a broader overview of our aims at the outset of this. And as we explore other projects, it can be sort of public forum for further discussion of topics outside the scope of this repo specifically. I also added a qualification to the requirements:

Below is an outline of proposed features for the interventions above. Although they may not be "requirements" in the strictest sense, they can serve as "gestures" towards a few potential outcomes, as we iterate on a practicable solution.

I'll try to map the better defined features from that list onto issues here, taking into account some of the more technical limitations, so it won't be a strict 1-to-1 mapping, but should provide us with a few starting points.

[jgaehring]

Okay, I added the following issues which I think are needed for the first MVP:

• Manually input qualitative assessments per farm location #5
• Depreciate farm status over time #6
• Submit qualitative assessments per crop #7
• Submit quantitative and qualitative assessments for specific health indicators #8

This does not include any semi-automated submissions from the farmers themselves (eg, via SurveyStack), let alone fully automated sensor readings. Nor does it address more complex evaluation of things like distance from the central office to each farm, pending orders, etc. Those can come later, but the above features, once implemented, should be sufficient for a first MVP that we can put in users' hands. Even #7 and #8 are probably not absolutely necessary.

Should we group them into a milestone then?