Ready 👍

* Add cursors and README

* Create CODE_OF_CONDUCT.md

* Create CONTRIBUTING.md

* Create PULL_REQUEST_TEMPLATE.md

* Create bug-report.yml

* Create feature_request.yml

* Create triager.yml

* Create approved.yml

* Create config.yml

* Create release-drafter.yml

* Create comment.md

* Update comment.md

* Create index.md

* Add Minima theme

* Change some things in Minima

Co-authored-by: code-lokesh2008 <[email protected]>

.github/ISSUE_RESPONSES/comment.md

@@ -0,0 +1,5 @@
+## Thank you!
+
+We appreciate your contribution to this project! Please be sure to read the [_**contributing guide**_](https://github.com/im-coder-lg/comboser/blob/main/CONTRIBUTING.md) to learn how you can help make this project better!
+
+If you've created this issue with the `bug` label, rest assured that we've added it to backlog for triage.

.github/ISSUE_TEMPLATES/bug-report.yml

@@ -0,0 +1,39 @@
+name: Bug report for the blog
+description: Make a bug report and help to improve the blog
+title: "[Bug]: "
+labels: [bug]
+assignees:
+- im-coder-lg
+
+body:
+- type: markdown
+  attributes:
+    value: |
+      Thanks for taking the time to fill out this feature request!
+
+- type: textarea
+  id: what-happened
+  attributes:
+    label: What happened?
+    description: "A detailed and clear concise description of the bug:"
+    placeholder: "Bug description:"
+    value: "What happened in the bug:"
+  validations:
+    required: true
+- type: textarea
+  id: expectations
+  attributes:
+    label: What did you expect to happen?
+    description: "A detailed and concise description of what you expected to happen:"
+    placeholder: "What you expected to happen:"
+    value: "Eg: Expected to see this..."
+
+- type: textarea
+  id: version-of-os
+  attributes:
+    label: Version of OS
+    description: "What version of the OS are you running?"
+    placeholder: "OS Version"
+    value: "Eg: Windows 21H1 Build 19043.2 or macOS Big Sur 11.2 or Ubuntu 20.04.2 Focal Fossa"
+  validations:
+    required: true

.github/ISSUE_TEMPLATES/feature_request.yml

@@ -0,0 +1,28 @@
+name: Feature Request
+description: File a feature request and help to improve the blog
+title: "[Feature]: "
+labels: [enhancement]
+assignees:
+- im-coder-lg
+
+body:
+- type: markdown
+  attributes:
+    value: |
+      Thanks for taking the time to fill out this feature request!
+- type: textarea
+  id: feature
+  attributes:
+    label: What kind of feature and what is it?
+    description: "A detailed and concise description of whatfeature you are suggesting:"
+    placeholder: "What kind of feature:"
+    value: "Eg: I want this feature..."
+
+
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Extra info(how it can be possible, etc.)
+    description: |
+      Post extra info here.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,28 @@
+# Pull Request for Comboser
+Thanks for opening a PR here. Be sure to read the contributing guidelines to see how to contribute here!
+## Description
+
+Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
+
+Fixes # (issue)
+
+## Type of change
+
+Please delete options that are not relevant.
+
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] This change requires a documentation update
+
+## Checklist:
+
+- [ ] My code follows the style guidelines of this project
+- [ ] I have performed a self-review of my own code
+- [ ] I have commented my code, particularly in hard-to-understand areas
+- [ ] I have made corresponding changes to the documentation
+- [ ] My changes generate no new warnings
+- [ ] I have added tests that prove my fix is effective or that my feature works
+- [ ] New and existing unit tests pass locally with my changes
+- [ ] Any dependent changes have been merged and published in downstream modules
+- [ ] I have checked my code and corrected any misspellings

.github/config.yml

@@ -0,0 +1,27 @@
+
+# Configuration for request-info
+# https://github.com/behaviorbot/request-info
+
+# *OPTIONAL* Comment to reply with
+requestInfoReplyComment: >
+  We would appreciate it if you could provide us with more info about this issue/pr!
+# *OPTIONAL* default titles to check against for lack of descriptiveness (MUST BE ALL LOWERCASE)
+requestInfoDefaultTitles:
+  - update readme.md
+  - updates
+
+# *OPTIONAL* Label to be added to Issues and Pull Requests with insufficient information given
+requestInfoLabelToAdd: need-more-info
+
+# *OPTIONAL* Require Pull Requests to contain more information than what is provided in the PR template (Will fail if the pull request's body is equal to the provided template)
+checkPullRequestTemplate: true
+
+# *OPTIONAL* Only warn about insufficient information on these events type (Keys must be lowercase. Valid values are 'issue' and 'pullRequest')
+requestInfoOn:
+  pullRequest: true
+  issue: true
+
+# *OPTIONAL* Add a list of people whose Issues/PRs will not be commented on (keys must be GitHub usernames)
+requestInfoUserstoExclude:
+  - im-coder-lg
+  - # the other users you wanna add here

.github/release-drafter.yml

@@ -0,0 +1,19 @@
+name-template: 'v$NEXT_PATCH_VERSION'
+tag-template: 'v$NEXT_PATCH_VERSION'
+categories:
+  - title: '🚀 Features'
+    labels:
+      - 'feature'
+      - 'custom'
+      - 'enhancement'
+  - title: '🐛 Bug Fixes'
+    labels:
+      - 'fix'
+      - 'bug'
+  - title: '🧰 Maintenance'
+    labels:
+      - 'devops'
+      - 'custom'
+template: |
+  ## What’s new:
+  $CHANGES

.github/workflows/approved.yml

@@ -0,0 +1,14 @@
+on: pull_request_review
+name: Label approved pull requests
+jobs:
+  labelWhenApproved:
+    name: Label when approved
+    runs-on: ubuntu-latest
+    steps:
+    - name: Label when approved
+      uses: pullreminders/label-when-approved-action@master
+      env:
+        APPROVALS: "2"
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        ADD_LABEL: "approved"
+        REMOVE_LABEL: "awaiting%20review"

.github/workflows/triager.yml

@@ -0,0 +1,37 @@
+name: Issue comments and project triage adding
+
+on:
+  issues:
+    types: [opened]
+
+jobs:
+  comment-and-project-adding:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout repo
+        uses: actions/checkout@v2
+
+      - name: Comment on new issue
+        uses: actions/[email protected]
+        with:
+          github-token: ${{secrets.GITHUB_TOKEN}}
+          script: |
+             const fs = require('fs')
+             const issueBody = fs.readFileSync(".github/ISSUE_RESPONSES/comment.md", "utf8")
+             github.issues.createComment({
+             issue_number: context.issue.number,
+             owner: context.repo.owner,
+             repo: context.repo.repo,
+             body: issueBody
+             })
+      - name: Add issue to project board
+        if: contains(github.event.issue.labels.*.name, 'bug')
+        uses: actions/[email protected]
+        with:
+          github-token: ${{secrets.GITHUB_TOKEN}}
+          script: |
+            github.projects.createCard({
+            column_id: 15856224,
+            content_id: context.payload.issue.id,
+            content_type: "Issue"
+            });

Android-Material-Cursors-Blue/Install.inf

@@ -0,0 +1,51 @@
+[Version]
+signature="$Chicago$"
+
+[DefaultInstall]
+CopyFiles = Scheme.Cur, Scheme.Txt
+AddReg    = Scheme.Reg
+
+[DestinationDirs]
+Scheme.Cur = 10,"%CUR_DIR%"
+Scheme.Txt = 10,"%CUR_DIR%"
+
+[Scheme.Reg]
+HKCU,"Control Panel\Cursors\Schemes","%SCHEME_NAME%",,"%10%\%CUR_DIR%\%pointer%,%10%\%CUR_DIR%\%help%,%10%\%CUR_DIR%\%work%,%10%\%CUR_DIR%\%busy%,%10%\%CUR_DIR%\%cross%,%10%\%CUR_DIR%\%Text%,%10%\%CUR_DIR%\%Hand%,%10%\%CUR_DIR%\%unavailiable%,%10%\%CUR_DIR%\%Vert%,%10%\%CUR_DIR%\%Horz%,%10%\%CUR_DIR%\%Dgn1%,%10%\%CUR_DIR%\%Dgn2%,%10%\%CUR_DIR%\%move%,%10%\%CUR_DIR%\%alternate%,%10%\%CUR_DIR%\%link%"
+
+[Scheme.Cur]
+normal-select-blue.cur
+help.cur
+working-in-background.ani
+cursor-spinner.ani
+txt-selection-blue.cur
+unavailable-blue.cur
+vertical-resize-blue.cur
+horizontal-resize-blue.cur
+diagonal-resize-frontslash-blue.cur
+diagonal-resize-backslash-blue.cur
+move-blue.cur
+link-select.cur
+precision-select.cur
+handwriting.cur
+alternate-select-blue.cur
+
+[Scheme.Txt]
+
+[Strings]
+CUR_DIR       = "Android-Material-Cursors"
+SCHEME_NAME   = "Android Material Cursors"
+pointer       = "normal-select-blue.cur"
+help          = "help.cur"
+work          = "working-in-background.ani"
+busy          = "cursor-spinner.ani"
+text          = "txt-selection-blue.cur"
+unavailiable  = "unavailable-blue.cur"
+vert          = "vertical-resize-blue.cur"
+horz          = "horizontal-resize-blue.cur"
+dgn1          = "diagonal-resize-backslash-blue.cur"
+dgn2          = "diagonal-resize-frontslash-blue.cur"
+move          = "move-blue.cur"
+link          = "link-select.cur"
+cross         = "precision-select.cur"
+hand          = "handwriting.cur"
+alternate     = "alternate-select-blue.cur"

CODE_OF_CONDUCT.md

@@ -0,0 +1,94 @@
+# Citizen Code of Conduct
+
+## 1. Purpose
+
+A primary goal of Cursor Combination is to be inclusive to the largest number of contributors, with the most varied and diverse backgrounds possible. As such, we are committed to providing a friendly, safe and welcoming environment for all, regardless of gender, sexual orientation, ability, ethnicity, socioeconomic status, and religion (or lack thereof).
+
+This code of conduct outlines our expectations for all those who participate in our community, as well as the consequences for unacceptable behavior.
+
+We invite all those who participate in Cursor Combination to help us create safe and positive experiences for everyone.
+
+## 2. Open [Source/Culture/Tech] Citizenship
+
+A supplemental goal of this Code of Conduct is to increase open [source/culture/tech] citizenship by encouraging participants to recognize and strengthen the relationships between our actions and their effects on our community.
+
+Communities mirror the societies in which they exist and positive action is essential to counteract the many forms of inequality and abuses of power that exist in society.
+
+If you see someone who is making an extra effort to ensure our community is welcoming, friendly, and encourages all participants to contribute to the fullest extent, we want to know.
+
+## 3. Expected Behavior
+
+The following behaviors are expected and requested of all community members:
+
+ * Participate in an authentic and active way. In doing so, you contribute to the health and longevity of this community.
+ * Exercise consideration and respect in your speech and actions.
+ * Attempt collaboration before conflict.
+ * Refrain from demeaning, discriminatory, or harassing behavior and speech.
+ * Be mindful of your surroundings and of your fellow participants. Alert community leaders if you notice a dangerous situation, someone in distress, or violations of this Code of Conduct, even if they seem inconsequential.
+ * Remember that community event venues may be shared with members of the public; please be respectful to all patrons of these locations.
+
+## 4. Unacceptable Behavior
+
+The following behaviors are considered harassment and are unacceptable within our community:
+
+ * Violence, threats of violence or violent language directed against another person.
+ * Sexist, racist, homophobic, transphobic, ableist or otherwise discriminatory jokes and language.
+ * Posting or displaying sexually explicit or violent material.
+ * Posting or threatening to post other people's personally identifying information ("doxing").
+ * Personal insults, particularly those related to gender, sexual orientation, race, religion, or disability.
+ * Inappropriate photography or recording.
+ * Inappropriate physical contact. You should have someone's consent before touching them.
+ * Unwelcome sexual attention. This includes, sexualized comments or jokes; inappropriate touching, groping, and unwelcomed sexual advances.
+ * Deliberate intimidation, stalking or following (online or in person).
+ * Advocating for, or encouraging, any of the above behavior.
+ * Sustained disruption of community events, including talks and presentations.
+
+## 5. Weapons Policy
+
+No weapons will be allowed at Cursor Combination events, community spaces, or in other spaces covered by the scope of this Code of Conduct. Weapons include but are not limited to guns, explosives (including fireworks), and large knives such as those used for hunting or display, as well as any other item used for the purpose of causing injury or harm to others. Anyone seen in possession of one of these items will be asked to leave immediately, and will only be allowed to return without the weapon. Community members are further expected to comply with all state and local laws on this matter.
+
+## 6. Consequences of Unacceptable Behavior
+
+Unacceptable behavior from any community member, including sponsors and those with decision-making authority, will not be tolerated.
+
+Anyone asked to stop unacceptable behavior is expected to comply immediately.
+
+If a community member engages in unacceptable behavior, the community organizers may take any action they deem appropriate, up to and including a temporary ban or permanent expulsion from the community without warning (and without refund in the case of a paid event).
+
+## 7. Reporting Guidelines
+
+If you are subject to or witness unacceptable behavior, or have any other concerns, please notify a community organizer as soon as possible. .
+
+
+
+Additionally, community organizers are available to help community members engage with local law enforcement or to otherwise help those experiencing unacceptable behavior feel safe. In the context of in-person events, organizers will also provide escorts as desired by the person experiencing distress.
+
+## 8. Addressing Grievances
+
+If you feel you have been falsely or unfairly accused of violating this Code of Conduct, you should notify im-coder-lg with a concise description of your grievance. Your grievance will be handled in accordance with our existing governing policies. 
+
+
+
+## 9. Scope
+
+We expect all community participants (contributors, paid or otherwise; sponsors; and other guests) to abide by this Code of Conduct in all community venues--online and in-person--as well as in all one-on-one communications pertaining to community business.
+
+This code of conduct and its related procedures also applies to unacceptable behavior occurring outside the scope of community activities when such behavior has the potential to adversely affect the safety and well-being of community members.
+
+## 10. Contact info
+
+
+
+## 11. License and attribution
+
+The Citizen Code of Conduct is distributed by [Stumptown Syndicate](http://stumptownsyndicate.org) under a [Creative Commons Attribution-ShareAlike license](http://creativecommons.org/licenses/by-sa/3.0/). 
+
+Portions of text derived from the [Django Code of Conduct](https://www.djangoproject.com/conduct/) and the [Geek Feminism Anti-Harassment Policy](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy).
+
+_Revision 2.3. Posted 6 March 2017._
+
+_Revision 2.2. Posted 4 February 2016._
+
+_Revision 2.1. Posted 23 June 2014._
+
+_Revision 2.0, adopted by the [Stumptown Syndicate](http://stumptownsyndicate.org) board on 10 January 2013. Posted 17 March 2013._