chore: add md files

Author: DongWoo Kim

CODE_OF_CONDUCT.md

@@ -0,0 +1,38 @@
+Contributor Covenant Code of Conduct
+Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+    Using welcoming and inclusive language
+    Being respectful of differing viewpoints and experiences
+    Gracefully accepting constructive criticism
+    Focusing on what is best for the community
+    Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+    The use of sexualized language or imagery and unwelcome sexual attention or advances
+    Trolling, insulting/derogatory comments, and personal or political attacks
+    Public or private harassment
+    Publishing others' private information, such as a physical or electronic address, without explicit permission
+    Other conduct which could reasonably be considered inappropriate in a professional setting
+
+Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected]. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+Attribution
+
+This Code of Conduct is adapted from the Contributor Covenant, version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html

CONTRIBUTING.md

@@ -0,0 +1,88 @@
+Contributing to TOAST UI
+
+First off, thanks for taking the time to contribute! 🎉 😘 ✨
+
+The following is a set of guidelines for contributing to TOAST UI. These are mostly guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request.
+Reporting Bugs
+
+Bugs are tracked as GitHub issues. Search the list and try reproduce on demo before you create an issue. When you create an issue, please provide the following information by filling in the template.
+
+Explain the problem and include additional details to help maintainers reproduce the problem:
+
+    Use a clear and descriptive title for the issue to identify the problem.
+    Describe the exact steps which reproduce the problem in as many details as possible. Don't just say what you did, but explain how you did it. For example, if you moved the cursor to the end of a line, explain if you used a mouse or a keyboard.
+    Provide specific examples to demonstrate the steps. Include links to files or GitHub projects, or copy/pasteable snippets, which you use in those examples. If you're providing snippets on the issue, use Markdown code blocks.
+    Describe the behavior you observed after following the steps and point out what exactly is the problem with that behavior.
+    Explain which behavior you expected to see instead and why.
+    Include screenshots and animated GIFs which show you following the described steps and clearly demonstrate the problem.
+
+Suggesting Enhancements
+
+In case you want to suggest for TOAST UI Editor, please follow this guideline to help maintainers and the community understand your suggestion. Before creating suggestions, please check issue list if there's already a request.
+
+Create an issue and provide the following information:
+
+    Use a clear and descriptive title for the issue to identify the suggestion.
+    Provide a step-by-step description of the suggested enhancement in as many details as possible.
+    Provide specific examples to demonstrate the steps. Include copy/pasteable snippets which you use in those examples, as Markdown code blocks.
+    Include screenshots and animated GIFs which helps demonstrate the steps or point out the part of TOAST UI Editor which the suggestion is related to.
+    Explain why this enhancement would be useful to most TOAST UI users.
+    List some other text editors or applications where this enhancement exists.
+
+First Code Contribution
+
+Unsure where to begin contributing to TOAST UI? You can start by looking through these document, good first issue and help wanted issues:
+
+    document issues: issues which should be reviewed or improved.
+    good first issues: issues which should only require a few lines of code, and a test or two.
+    help wanted issues: issues which should be a bit more involved than beginner issues.
+
+Pull Requests
+Development WorkFlow
+
+    Set up your development environment
+    Make change from a right branch
+    Be sure the code passes npm run lint
+    Make a pull request
+
+Development environment
+
+    Prepare your machine node and it's packages installed.
+    Checkout our repository
+    Install dependencies by npm install
+
+Make changes
+Checkout a branch
+
+    master: PR Base branch.
+    production: lastest release branch with distribution files. never make a PR on this
+    gh-pages: API docs, examples and demo
+
+Check Code Style
+
+Run npm run lint and make sure all the tests pass.
+Commit
+
+Follow our commit message conventions.
+Yes! Pull request
+
+Make your pull request, then describe your changes.
+Title
+
+Follow other PR title format on below.
+
+    <Type>: Short Description (fix #111)
+    <Type>: Short Description (fix #123, #111, #122)
+    <Type>: Short Description (ref #111)
+
+    capitalize first letter of Type
+    use present tense: 'change' not 'changed' or 'changes'
+
+Description
+
+If it has related to issues, add links to the issues(like #123) in the description. Fill in the Pull Request Template by check your case.
+Code of Conduct
+
+This project and everyone participating in it is governed by the Code of Conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to [email protected].
+
+    This Guide is base on atom contributing guide, CocoaPods and ESLint

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2019 NHN Entertainment Corp.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.