From e5235186cd0ab063a23b2daa0233954fe6b9c0e9 Mon Sep 17 00:00:00 2001 From: Subin Siby Date: Mon, 15 Nov 2021 13:39:43 +0530 Subject: [PATCH] Move README to root --- .github/CODE_OF_CONDUCT.md | 46 ----------------------- .github/CONTRIBUTING.md | 19 ---------- .github/ISSUE_TEMPLATE/bug_report.md | 35 ----------------- .github/ISSUE_TEMPLATE/crash_report.md | 33 ---------------- .github/ISSUE_TEMPLATE/feature_request.md | 17 --------- .github/PULL_REQUEST_TEMPLATE.md | 17 --------- .github/README.md => README.md | 0 7 files changed, 167 deletions(-) delete mode 100644 .github/CODE_OF_CONDUCT.md delete mode 100644 .github/CONTRIBUTING.md delete mode 100644 .github/ISSUE_TEMPLATE/bug_report.md delete mode 100644 .github/ISSUE_TEMPLATE/crash_report.md delete mode 100644 .github/ISSUE_TEMPLATE/feature_request.md delete mode 100644 .github/PULL_REQUEST_TEMPLATE.md rename .github/README.md => README.md (100%) diff --git a/.github/CODE_OF_CONDUCT.md b/.github/CODE_OF_CONDUCT.md deleted file mode 100644 index db24fc9..0000000 --- a/.github/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,46 +0,0 @@ -# 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, 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 daivajnanam@gmail.com. The project team will review and investigate all complaints, and will respond in a way that it deems 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][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version] - -[homepage]: http://contributor-covenant.org -[version]: http://contributor-covenant.org/version/1/4/ diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md deleted file mode 100644 index 5009628..0000000 --- a/.github/CONTRIBUTING.md +++ /dev/null @@ -1,19 +0,0 @@ -These instructions are for contributing to the Lipika family of open source projects including but not limited to [lipika-engine](https://github.com/ratreya/lipika-engine), [lipika-ime](https://github.com/ratreya/lipika-ime) and [lipika-board](https://github.com/ratreya/lipika-board). - -1. Download and setup the latest xcode from the appstore -1. Clone the appropriate Github Lipika project -1. Choose an issue or open a new issue for the planned work - * Mark the issue as a *bug* or *feature* - * Use the appropriate template and fill it in - * Assign the issue to yourself - * You may also want to comment and ask for help if you’re new or if you get stuck. We’re happy to help! -1. Make changes with *test driven development* and make sure there is a regression that fails without your changes and passes with them -1. Make sure all other tests pass -1. Make one commit for one issue - a single unit of roll-back -1. Open a merge request - * Use and fill in the merge request template - * You can mark it as a Work in Progress to signal that you’re not done yet -1. Wait for a reviewer. You’ll likely need to change some things once the reviewer has completed a code review for your merge request. You may also need multiple reviews depending on the size of the change. -1. Get your changes merged! - -If you have questions or concerns, please feel free to open an issue or post in the [user group](http://facebook.com/groups/lipika.ime). diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md deleted file mode 100644 index 4c4d40d..0000000 --- a/.github/ISSUE_TEMPLATE/bug_report.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -name: Bug report -about: Create a report to help us improve -labels: bug ---- - -**Describe the bug** -A clear and concise description of the bug. - -**To Reproduce** -Steps to reproduce the behavior: -1. Go to '...' -2. Click on '....' -3. Scroll down to '....' -4. See error - -**Expected behavior** -A clear and concise description of what you expected to happen. - -**Screenshots** -If applicable, add screenshots to help explain your problem. - -**Desktop (please complete the following information):** - - OS: [e.g. macOS 10.14.3] - - Application: [e.g. textedit, safari] - - Version: [e.g. 2.2] - -**Smartphone (please complete the following information):** - - Device: [e.g. iPhone6] - - OS: [e.g. iOS8.1] - - Application: [e.g. whatsapp, imessage] - - Version: [e.g. 2.1] - -**Additional context** -Add any other context about the problem here. diff --git a/.github/ISSUE_TEMPLATE/crash_report.md b/.github/ISSUE_TEMPLATE/crash_report.md deleted file mode 100644 index aeadf55..0000000 --- a/.github/ISSUE_TEMPLATE/crash_report.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -name: Crash report -about: Report crashes so we can fix our reliability -labels: crash ---- - -**Attach the crash report** -* [macOS] Open Console app, under `User Reports`, find the appropriate LipikaIME crash report and attach it here. -* [iOS] Connect your iOS device to your macOS computer, open Console app, choose the iOS device, select appropriate log lines, copy and paste them here. - -**To Reproduce** -Steps to reproduce the behavior: -1. Go to '...' -2. Click on '....' -3. Scroll down to '....' -4. See error - -**Screenshots** -If applicable, add screenshots to help explain your problem. - -**Desktop (please complete the following information):** - - OS: [e.g. macOS 10.14.3] - - Application: [e.g. textedit, safari] - - Version: [e.g. 2.2] - -**Smartphone (please complete the following information):** - - Device: [e.g. iPhone6] - - OS: [e.g. iOS8.1] - - Application: [e.g. whatsapp, imessage] - - Version: [e.g. 2.1] - -**Additional context** -Add any other context about the problem here. diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md deleted file mode 100644 index 2356405..0000000 --- a/.github/ISSUE_TEMPLATE/feature_request.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -name: Feature request -about: Suggest an idea for this project -labels: enhancement ---- - -**Is your feature request related to a problem? Please describe.** -A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] - -**Describe the solution you'd like** -A clear and concise description of what you want to happen. - -**Describe alternatives you've considered** -A clear and concise description of any alternative solutions or features you've considered. - -**Additional context** -Add any other context or screenshots about the feature request here. diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index 7ce421b..0000000 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,17 +0,0 @@ -## Summary ## - -* Please provide enough information so that others can review your pull request. -* Explain the **details** for making this change. What existing problem does the pull request solve? - -## Version Bump ## - -* What version bump [MAJOR | MINOR | PATCH] do your changes require and why? -* Please refer to [Semantic Versioning](https://semver.org/) for more details. - -## Test plan (required) ## - -Demonstrate the code is solid. If there are regression tests, call them out. Also state any manual testing that may have been done, for example, the exact commands you ran and their output, screenshots if the pull request changes UI. - -## Closing issues ## - -*IMPORTANT*: Please do not create a Pull Request without creating an issue first. diff --git a/.github/README.md b/README.md similarity index 100% rename from .github/README.md rename to README.md