I kinda agree with the comments there and your conclusion. The functions do not do anything very complex (they take about 5~10 lines of code) and could either be implemented as a convenience by the users that feel the need to use it, or obtained by means of a package. The Pkg is for the building blocks that are impossible to implement outside of it.
No, not at all. This generates a new package, but most new users do NOT want to write packages, just want to use a package or a set of packages, run some examples and then write there own code, which will never gets published. And if you teach bachelor students they will not even use git. So a user project is NOT a package. It took me 5 years of being a Julia user before I wrote my first package.
I think of a user project as a place for scripts that use a common set of existing packages without defining any modules.
Just FYI, I threw jeeves together very quickly and I’d be happy to put some more work into it to make it more usable for a broader audience. I use it for every new project I start and haven’t really wanted anything new (I did add some functionality to make it check for the latest available Julia version a while back, but that won’t work for non-Windows users) but I’d be happy to implement any good ideas that others want to see incorporated : )
From my point of view, item 2 “to find, copy, and execute examples” is the most critical one.
PkgTemplates could be a bit easier to use and get simple default settings, but at least the mechanism is there.
We have add to include packages and dev to work on packages, but there is no good way to get a package and play with the examples.
I am using a slightly cumbersome workflow similar to what I described here: How to use VSCode and REPL to write and test a package? - #33 by mefob
Something like this should absolutely become part of Pkg to establish a standard way to setup packages with examples.