Mike Boyle

I've gotten a pretty reasonable start on this sort of library [here](https://github.com/moble/sxs/tree/master/sxs/zenodo/api). I've had good results making new depositions, searching, etc. You can see an example of a pretty complicated...

@abubelinha That's right. The problem is that those examples quickly get tiring, with lots of repetition. Pretty much every time you access the API, you have to do something like...

I only pointed to that as an example of a pretty extensive API; it's not particularly designed for use by anyone but me. But if you want to try it,...

My guess is that you're probably right that it shouldn't create a dict — though to be honest, I really don't remember anything about that code. Also, slint probably has...

It would be particularly nice if this could be tied to github organizations, which are accessible via the github oauth API. So, for example, if I want my whole community...

@peterdesmet These are not mutually exclusive options; both could work. But for my use cases, it is impractical to grant permissions on a per-user per-deposit basis.

Obviously, I would also prefer multiple curators. But even if only one user is allowed to curate, is there at least a way to *transfer* curatorship from one user to...

[These commit messages](https://github.com/SciML/Surrogates.jl/search?q=paper&type=commits) refer to "paper", and [this docstring](https://surrogates.sciml.ai/dev/optimizations/#Surrogates.surrogate_optimize-Tuple{Function,%20SRBF,%20Any,%20Any,%20AbstractSurrogate,%20SamplingAlgorithm}) refers to "the original papers".

As mentioned in the [PyCall issue](https://github.com/JuliaPy/PyCall.jl/issues/903#issuecomment-1048884945), this seems to be caused by build options from certain python sources, and probably can't be fixed by anything in this repo — though...

> > Is it because I specified that in my project's compat section? > > Always this. It seems like it's not *always* this. I had a confounding problem when...