Great feedback @pat and @walt!! I think this illustrates just how many different directions a “simple” Project plan could go in. 
I see two ways forward, which could take place in parallel:
- Incremental (baby step) additions to a “barebones” plan type, like the one Paul started, with beta testers trying it out and suggesting next steps.
- A holistic process to elucidate what “planning” means to different people, and for different use-cases, and where there are differences and overlap.
Feels like #2 could be a really good focus of an OpenTEAM HCD (human centered design) process to spec out requirements. It would require a lot more than a single one hour session, though, and bringing in more stakeholders would be critical.
I’m particularly interested in thinking about “planning features” that might be reusable across different plan types. For example, “recurring tasks”, “timeline visualization/gantt chart”, “quick form plan integrations”, etc are all things that seem to come up as ideas in different planning contexts. I think farmOS core’s focus should be on providing common building blocks like these, and leave it to downstream plan-type-providing modules to use these pieces (and build their own) to create use-case-specific UI/UX workflows.
I will say that the “recurring tasks” request has come up a lot - and could be a good candidate for a core plan type IMO: https://www.drupal.org/project/farm/issues/2962368
I want to acknowledge that all of these things are much more than what @tlcarpenter69 was originally asking about, though… which I think literally boils down to a “wishlist” (not in the farmOS feature request sense, but in the literal “wishlist of things to do on the farm” sense). So we may have blown up the scope on this thread a bit.