Marcus Ottosson

Yeah, I like mkdocs. I would suggest keeping user and automatic docs separate - mkdocs has been good for user docs so far, haven't found any comfortable automatic kind just...

About the draft; I still think it's wordy, without providing much information. I'm missing a center-piece, the one-liner that sums up what it does. It's like a function, if you...

Reading the bcore README, one more thing comes to mind. http://en.wikipedia.org/wiki/Show,_don't_tell For example, as an alternative to this: ``` The requirements are kept minimal, which is why you need nothing...

Hey, I'm going through your docs at http://byron.github.io/bcore/bcmd/ Good job! Just one thing that keeps popping up that I think could be made better, which is that the word "_easy_"...

I would also tone down a bit on the word _arbitrary_. This is something you could let the reader witness as well, instead of being told. Possibly via an example,...

Reference of things that could be expressed via examples or exposition, in case you change it: > With bcmd it is already **easy** to create complex, plugin-based.. > > ..commands...

Here is my understanding so far, correct me if I'm wrong. A Bootstrapper adds and/or modifies environment with Python package paths, in this case those specific to _bcore_ bprocess resolves...

Cool, still quite wordy however. If possible, a 1-minute elevator pitch would help set the stage for newcomers like me.

Thanks for reporting this @celeste-ramirez, any idea of where the problem might be?

Implemented. Note that `allzparkconfig.py:applications_from_package` can now return specific versions. ```py def applications_from_package(package): return [ "nuke", # All versions "~maya==2018|==2019", # Only these exact versions ] ``` Allzpark will unpack a...