Loadpath should support subdirs about lyra

[kenazk]

Thanks @jdwelch for keeping us honest. The two key scenarios in my mind are:

• As a producer of Workflows, I want Lyra to load workflows from a simple directory structure so that I can organize my Workflows in a simple, understandable way.
• As a contributor to Lyra, I want Lyra to load workflows from a simple directory structure so that I know how and where to contribute code and other examples.

[thallgren]

I would like to add:

• As a producer of workflows, I want to workflows organized so that I can reference one workflow from another using qualified names.
• As a producer of workflows, I want dynamic loading so that my workflow to be able to consume workflows provided by another producer.
• As a user of Lyra, I only want to load the workflow I indent do apply so that the load is quick and cpu cycles, processes, and memory aren't wasted

[thallgren]

I think we should consider letting subdirectories imply namespaces and file names imply name of the workflow they contain. I.e. a workflow named my::​cool::stuff should reside in a file named "stuff.pp" under directory "workflows/my/cool". This would allow us to use a file based loader rooted under the "workflows" directory and load workflows on demand rather than pre-load everything at start-up like we do today.

[jdwelch]

Where's the "so that"; why is this feature important for an end-user? Why is this the right solution to whatever that problem is?

[jdwelch]

I'm +1 to the "workflows/my/cool" corresponds to "workflows::my::cool" pattern and am fine with going ahead and ticketing/implementing that solution.