Always happy to answer questions!
(1) Yes, there are these long term plans. There are two primary tasks (1) adding files (2) adding the package to the registry. The former is pretty simple, and I plan to write a short tutorial explaining what must be done so that read/write access is not necessary … for this one we just wanted to keep your life simple . The latter will always need to be done by the owner of the registry, but adding the files and then requesting to be added is something we can have users do without our involvement in the future.
(2) In this case you would be managing your own personal registry, which wouldn’t be connected to the Mimi registry. That seems doable, if you wanted, but would require going through the steps to establish a registry which @davidanthoff could advise you on.
The described situation certainly makes sense for you to want to avoid, and would make our use of the registry less effective! I think we can establish a workflow where you would follow instructions on what files to add to your package, and then formally request to be added to the registry … and after that request we guarantee adding it within X days.
(3) You are welcome to export whatever functions you want, and we suggest putting instructions in the README or docs. At minimum it would be good to have a
construct_nice() type function, but if you want to export more that’s totally up to you, you would just put that in the
MimiNICE.jl file i.e.
export construct_nice(), optimize_nice() ...
The rule we’ve tried to follow is only putting functions In the
export list that we don’t plan to break … but again it’s your package so it’s up to you!