[RFC] Split vitalizer and modules into individual repositories

Open
  • Is something wrong?
#568 7 comments 0 reactions 1 assignee View on GitHub

@thinca is already working on this.

Since Jan 15, 2018.

Assessment

This issue has not been assessed yet.

Description

via https://vim-jp.slackarchive.io/general/page-40/ts-1514306851000160

Repositories

See https://github.com/vim-jp/vital.vim/issues/568#issuecomment-354590388

  • vim-jp/vital.vim - Vitalizer only
  • vim-jp/vital-core.vim - Core modules
  • vim-jp/vital-supplement.vim - Supplement modules

Vitalizer clones external repositories

  • Vitalize --repo=vim-jp/vital-core.vim {dir}
  • vim-jp/vital-core.vim is the default repository (does not have to specify it explicitly)
  • The specified repositories list are stored in autoload/vital/{name}.repo file so the next time users don't have to specify repositories twice
    • Can the list be written in autoload/vital/{name}.vital file with keeping the compatibility of the current format?
Dominant language
Vim Script
Stars
586
Forks
64
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from vim-jp/vital.vim

All issues in vim-jp/vital.vim

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.