vimrc style guide
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 107
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
itchyny
せっかくvimrc読書会とかいう世界でも類を見ないものをやっているのに、それで鍛えられたvimrcを見る目を外国にフィードバックしないのはもったいない。
特に外国の人のvimrcを読んだりすると、本人のいないところで悪口言いあってる感じがする。それよりも何がよくて何が悪いかというのをちゃんと発表するほうがいい。
あと、vim-jpというコミュニティーとして発表することも大事なんじゃないかなぁと思った。
http://lingr.com/room/vim/archives/2014/11/16#message-20620208
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked Lingr discussion and the issue comments to understand the proposed vimrc style guide and the community context. The work is complete when vim-jp has an agreed, published guide that explains what makes a vimrc good or bad.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vim
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100