...
Question | Answer | Date Answered |
---|---|---|
Should we call money coming into the farm “Revenues” or “Income”? | Revenues |
|
Are there other revenue types we’re not tackling now? Why? | Yes! Per user meeting on . Then there were several that they mentioned, but I think we'll handle them once we add the relevant functionality:
Processed goods: As discussed in the past, we might want to wait on this as there is additional complexity to this. Probably need to add a "processing" task |
|
Should the attributes of revenues be defined at the “template” level or the “instance” level? If defined at the “template”, can users overwrite at the instance? Are there some of each? Current expected implementation is at the template level we ask if the revenue should be associated with crops or not. If the answer was yes then at the instance level we ask, “which crops?” | Kevin’s proposal (to be debated) Defined by revenue type:
Defined at creation:
Refactors under consideration:
Other related work:
Duncan Brain + Joyce Sato-Reinhold + Sayaka Ono + David Trapp | |
What attributes should be shown for each revenue type? (e.g. Crop sales, Event hosting, Tourism, Consultations, Crafts) | Crop sales: Shown:
Assumed, and therefor not shown:
All others (including custom): Shown:
Assumed, and therefor not shown:
|
...