PR merge rule and PR template suggestion about ko.reactjs.org

[taggon]

I think the third item should be "맞춤법 검사" rather than "띄어쓰기 검사", as the online tool checks more than spacing.

[gnujoow]

<!--

Thank you for the PR! Contributors like you keep React awesome!

Please see the Contribution Guide for guidelines:

https://github.com/reactjs/reactjs.org/blob/master/CONTRIBUTING.md

If your PR references an existing issue, please add the issue number below

-->

**progress**  

[ ] 번역 초안 작성
[ ] glossary 용어 확인 (wiki or issue links)
[ ] 띄어쓰기 검사 (http://speller.cs.pusan.ac.kr/)
[ ] 리뷰 반영
[ ] 최종 PR

if this checklist included in template, I think this will be able to help contributors to check their tranlation progress.

[gnujoow]

for PR mege I suggest PR is merged if it has (at least) two approve from reviewer or maintainer to check the quality of the translation.

[taehwanno]

for PR mege I suggest PR is merged if it has (at least) two approve from reviewer or maintainer to check the quality of the translation.

I agree :)

if this checklist included in template, I think this will be able to help contributors to check their tranlation progress.

Good idea. We need to add UNIVERSAL-STYLE-GUIDE.md in #17.

[hg-pyun]

Yeah, It is a very coool idea.

[cadenzah]

The idea of progress items is pretty nice. It will be easier to check important stuffs.

[taehwanno]

I applied "Require pull request reviews before merging" with options in the screenshot.

[simsim0709]

I agree 👍

[gnujoow]

I will close this issue and make PR for PR templete this sunday. if there is any feed back on the checklist, comment on this thread by this week.

[taggon]

The current PR template, which introduced by #25, contains broken links. If we don't have appropriate references for the items yet, it would be better to remove the links.

[gnujoow]

@taggon I've just made pr to resolve the issue you mention.
#45