Checklist for initial release

[mjlbach]

• write some guidance for required/optional features of implementers
• Settle on name packagespec, plugspec and updated the package_specification field and the documentation
• Provide a section on plugin expectations? (Semver, vimdoc, etc.)
• Address concern about dependencies format (including neovim as a dependency) Dependencies format #19
• Add build steps for plugins Post-install hook #23
• Upload final version of json schema to schema store

[ii14]

If there is a new name, maybe plugin.{lua,json} should be changed to plugspec.{lua,json} too?

[mjlbach]

I'm still not sold onplug, this spec can apply to libraries as well, and also still has vim-plug connotations. On the other hand, it would be weird to call it package.json.

[lewis6991]

Go with packspec then?

[wbthomason]

See #17 for the first checkbox.

[lewis6991]

Consider moving neovim out of external dependencies to it's own versioned key

I lean against doing this. We could maybe add a general requirements field but that would pretty much only contain Neovim.

[mjlbach]

Yeah, just wanted to put it as it came up on the neovim general chat by shougo :)

[lewis6991]

I've changed my mind on this and think we should pull it out.

[mjlbach]

Are you thinking more like #19 initially proposed (as an independent field in dependencies or more top level?

[lewis6991]

Yeah pretty much. I also think we need to change dependencies as per that ticket.