But I also I think there is a need for this suuuuper simple generic plan type as well.
Instead of pursuing this module I’ve started, perhaps we could add an initial Project plan (naming?) to farmOS core? The code is really quite simple and shouldn’t be much work to maintain in farmOS core, I think it’s more the principal of having a basic plan type in farmOS core that we need to think about.
In the long run I do think there should be separate types of plans for specific purposes (Maintenance, cropping, grazing, etc) but I don’t think there is much harm in having a basic plan type as well. People might use a basic plan to represent something now that would be better suited as a specialized plan type in the future but at least an option would be available now. It seems there will always be a use-case that doesn’t have a perfect fit anywhere too… so having a (simple) default place to put that information is useful.
Most exciting is that having a basic plan type might help spur ideas for additional specialized plan types. And I’m particularly curious how we can make some of these additional features generalized for multiple plan types (UI to add/remove logs, recurring logs, etc); having a basic plan type might help validate if a feature is generally applicable?