Stdlib-candidate Reset

[NotTheDr01ds]

On today's call, we decided to reset stdlib-candidate and start fresh (and try to manage it more effectively going forward).

This PR is that reset, along with an updated README for the new module.

The main thing that needs reviewing here is the README.

[fdncred]

LGTM. Glad you just moved the existing ones to "old". I'm wondering if there should be some more thorough instructions of how to try out stdlibcan with nupm and without nupm to make it more intuitive for people who want to dogfood with us?

[132ikl]

I agree, we should probably add std-rfc to the "official" nupm registry

[NotTheDr01ds]

I'm wondering if there should be some more thorough instructions of how to try out stdlibcan with nupm and without nupm to make it more intuitive for people who want to dogfood with us?

Agreed - Just didn't have time to write it up in this pass.

[NotTheDr01ds]

I agree, we should probably add std-rfc to the "official" nupm registry

I'm still not quite sure I fully understand nupm registries, but doesn't it require that the top level nu_scripts be the registry entry? I got the feeling from another comment somewhere that it doesn't support checking out individual modules from a mono-repo.

[fdncred]

I haven't used nupm yet, but I don't think it requires a file be in the root of nu_scripts but one in the sub-folder like nu-hooks and themes. @kubouch or @amtoine should be able to provide more insight.

[NotTheDr01ds]

I think we can add the installation instructions in a subsequent PR, right? I mean, the current version doesn't have any ;-)

That would at least get the "reset" locked in so that people can start moving things over if they want.

[fdncred]

That would at least get the "reset" locked in so that people can start moving things over if they want.

I guess so. People can just use <blah> to test things out, assuming they understand these will all be modules.