Aaron Peikert

I agree with all what you state above but would like to add one crucial point (at least for me): **learning time is the metric to optimize for** For me,...

Cool. Yes to a clearly defined project scope! I could draft a lengthier version of this list, which includes details about the concrete implementation, but only if you could read/check...

Thank you, that would be great. The paper should definitely be the top priority. I just had the idea for the graphic today and thought it fitting to better explain...

I don't know where to write down that thought, but I think a good rule of thumb for what features to include in worcs is: * worcs should only contain...

Maybe to make this distinction more pronounced format the package as code, so it is WORCS (the approach) vs `worcs` (the package)?

What would that entail?

Ahh I see. Over at repro, I check these things on a per-component basis. Hence, if `use_worcs()` is implemented by bundling a bunch of use_* function, `use_worcs()` would convert any...

That is a great idea and we should put it on our to-do list. (Maybe that is even something we should contribute to papaja). Never wrote something in lua though....

Would be great if you could make this compatible to repro: https://github.com/aaronpeikert/repro/blob/66a8c07221b0802c19fd7f170c7235db51b0777b/R/zzz.R#L1-L22 How the directory is called is a branding thing, but as you see I left this as an...

`.onLoad()` is called when the package is loaded, and my `.onLoad()`-function just sets some options where certain files should be. To customize these file locations a user would use `options(repro.dockerfile.packages...