Original forked

.github/ISSUE_TEMPLATE/bug_report.md

@@ -2,7 +2,7 @@
 name: Bug report
 about: Create a report to help us improve
 title: ''
-labels: 'Status: Review Needed, Type: Bug'
+labels: 'Status: Review Needed'
 assignees: ''
 ---
 

.github/ISSUE_TEMPLATE/feature_request.md

@@ -2,7 +2,7 @@
 name: Feature request
 about: Suggest an idea for this project
 title: ''
-labels: 'Status: Review Needed, Type: Enhancement'
+labels: 'Status: Review Needed'
 assignees: ''
 ---
 

.github/card-labeler.yml

@@ -0,0 +1,11 @@
+Roadmap:
+  Available:
+    - 'Status: Available'
+  Claimed:
+    - 'Status: Claimed'
+  In progress:
+    - 'Status: In Progress'
+  Done:
+    - 'Status: Completed'
+  On Hold:
+    - 'Status: On Hold'

.github/pull_request_template.md

@@ -1,9 +1,6 @@
 **Description of PR**
 
-**Type of PR**
-
-- [ ] Bugfix
-- [ ] New feature
+A brief description of what changes your PR introduces. The better this description, the quicker we can review, exchange feedback, and merge!
 
 **Relevant Issues**  
 Fixes #...
@@ -16,3 +13,5 @@ Fixes #...
 - [ ] Tested on phone
 
 **Screenshots**
+
+Add relevant screenshots here

.github/workflows/claim.yml

@@ -0,0 +1,40 @@
+on:
+  issue_comment:
+    types: [created]
+name: Claim Issue
+jobs:
+  assign:
+    name: Update labels and Assign
+    if: github.event.issue.pull_request == ''
+      && contains(github.event.comment.body, '/claim')
+      && contains(toJson(github.event.issue.labels), 'Available')
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/github-script@0.9.0
+        with:
+          github-token: ${{secrets.GITHUB_TOKEN}}
+          script: |
+            await github.issues.addLabels({
+              issue_number: context.issue.number,
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              labels: ['Status: Claimed']
+              })
+            await github.issues.removeLabel({
+              issue_number: context.issue.number,
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              name: 'Status: Available'
+              })
+            await github.issues.addAssignees({
+              issue_number: context.issue.number,
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              assignees: [context.payload.sender.login]
+              })
+            await github.issues.createComment({
+              issue_number: context.issue.number,
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              body: 'Thank you @'+context.payload.sender.login+' for claiming this issue! 🎉 \n\nPlease reference this issue when you submit your Pull Request and make sure you follow the [contributing guidelines](https://github.com/covid19india/covid19india-react/blob/master/CONTRIBUTING.md).'
+            })

.github/workflows/mod.yml

@@ -0,0 +1,49 @@
+on:
+  issue_comment:
+    types: [created]
+name: Mod
+
+jobs:
+  moderate:
+    runs-on: ubuntu-latest
+    name: Make issue Available
+    if: github.event.issue.pull_request == ''
+      && contains(github.event.comment.body, '/available')
+      && contains(toJson(github.event.issue.labels), 'Review Needed')
+    steps:
+      - uses: actions/github-script@0.9.0
+        with:
+          github-token: ${{secrets.jun_token}}
+          script: |
+            const { data } = await github.teams.getMembershipInOrg({
+              org: "covid19india",
+              team_slug: "mods",
+              username: context.payload.sender.login,
+            });
+            console.log(data);
+            console.log("User team state: "+data.state);
+            if(data.state != "active"){
+              return;
+            }
+      - uses: actions/github-script@0.9.0
+        with:
+          github-token: ${{secrets.GITHUB_TOKEN}}
+          script: |
+            await github.issues.removeLabel({
+              issue_number: context.issue.number,
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              name: 'Status: Review Needed'
+              })
+            await github.issues.addLabels({
+              issue_number: context.issue.number,
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              labels: ['Status: Available']
+              })
+            await github.issues.createComment({
+              issue_number: context.issue.number,
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              body: 'This issue is available for contribution.\n\nPlease reply "/claim" (without quotes) if you wish to work on this issue.'
+            })

.github/workflows/project-card-moved.yml

@@ -0,0 +1,10 @@
+on:
+  project_card:
+    types: [moved]
+name: Project Card Event
+jobs:
+  triage:
+    name: Auto card labeler
+    runs-on: ubuntu-latest
+    steps:
+      - uses: technote-space/auto-card-labeler@v1

.gitignore

@@ -26,3 +26,7 @@ node_modules/
 npm-debug.log*
 yarn-debug.log*
 yarn-error.log*
+
+# vim swap files
+*.swp
+*.swo

CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# 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, sex characteristics, 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 hello@covid19india.org. 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][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

CONTRIBUTING.md

@@ -1,20 +1,49 @@
-# Contributing to covid19india.org website
+# Contributing Guidelines
 
-First off, thanks for taking the time to contribute! :+1:
+First off, thanks for taking the time to contribute! 😄
 
-These are mostly guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request.
+Contributions are handled in the form of Pull Requests. You fork this repository, create a new branch, make relevant changes, and submit a Pull Request – once that's done we'll be able to review your PRs and merge them to the master branch.
 
-Regarding Pull Requests to this project, always submit a PR against an "Accepted Issue" assigned to you. If an issue doesn't exist, please raise one first and wait for it to get accepted, and assigned. PRs without having accepted issues mentioned will be closed. The only exception to this rule are for PRs that address critical bug fixes that cannot wait for a maintainer's approval.
+Always submit a PR against a "Claimed Issue" that's been assigned to you. If an issue doesn't exist, please raise one first and wait for it to be labelled as "Available", and then have it assigned to you. PRs without having accepted issues mentioned will be closed.
 
-Two kinds of issues can be raised in this project:
+## Process Flow
 
-1. Bug report
-2. Feature Request
+- When a new issue is created, "Status: Review Needed" and "Type: Bug or Type: Enhancement" label is automatically added to it.
+- Mods periodically check "Status: Review Needed" and add appropriate Priority and Status labels. If the issue is clear, set the status label as "Status: Available".
 
-## Process Flow
+<p align="center">
+  <img src="https://storage.googleapis.com/jrmyphlmn/images/github/label%20change.png" width="50%">
+</p>
+
+- People looking to contribute, filter issues by ["Status:Available"](https://github.com/covid19india/covid19india-react/issues?q=is%3Aissue+is%3Aopen+label%3A%22Status%3A+Available%22) and comment "/claim" on the issue they would like to be assigned to work on.
+
+<p align="center">
+<img src="https://storage.googleapis.com/jrmyphlmn/images/github/filter.png" width="50%">
+</p>
+<h6 align="center">Filter by label "Available"</h6>
+<p align="center">
+<img src="https://storage.googleapis.com/jrmyphlmn/images/github/claim.png" width="50%">
+</p>
+<h6 align="center">use /claim to have the issue assigned to you</h6>
+
+- Finally submit the pull request.
+
+## Formatting
+
+Format your PR titles likewise:
+
+> [Tag]: Describe change in present tense
+
+Tag can be:
+
+- Feat (new feature)
+- Fix (bug fix)
+- Refactor (refactoring code)
+- Style (formatting, no code change)
+- Doc (changes to documentation)
+- Test (adding or refactoring tests; no production code change)
+
+Remember to:
 
-- When a new issue is created, "Status: Review Needed" and "Type:Bug or Type:Enhancement" label is automatically added to it.
-- Mods periodically check "Status:Review Needed" and add appropriate Priority and Status labels. If the issue is clear, set the status label as "Label: Available"
-- People looking to contribute, filter issues by ["Status:Available"](https://github.com/covid19india/covid19india-react/issues?q=is%3Aissue+is%3Aopen+label%3A%22Status%3A+Available%22) and comment on the issue that they would like to be assigned to work on it.
-- Mods change the status label to "Status: Claimed" and assign the issue to the contributor.
-- Contributor change the label to "Status: In Progress" and finally submit the pull request.
+- Capitalize the subject line
+- Use the imperative mood in the subject line

README.md

@@ -1,11 +1,9 @@
-# covid19india.org
-
 <p align="center">
-<img src="https://lh3.googleusercontent.com/qsMx1mwj0beTKis5j6tAE5U27l1iAhZUarv6_rJMoeIc6bhQilShYnQfZZtfuAb39MXP-P3ZG_EZMV_TKNl3AdM8dMBGh0KP=s2560" width="100%">
+<img src="https://lh3.googleusercontent.com/-grjTcOMyemYN_JiN3QlkZzgh61D88LNFLj2-8QaqcjLWn_MouQe9zux8ZfMH4R7SLfR-cfHYD1b84KUlPqYucP5gZWTuo2J=s2560" width="100%">
 </p>
 
 <p align="center">
-  View our <a href="https://bit.ly/patientdb">live patient database</a>.
+  View our live <a href="http://patientdb.covid19india.org/">database</a>.
  </p>
 
 ## Setup
@@ -17,7 +15,12 @@ npm i && npm start
 ## Maintainers
 
 - [jeremyphilemon](https://github.com/jeremyphilemon)
+- [shuklaayush](https://github.com/shuklaayush)
+- [JunaidBabu](https://github.com/JunaidBabu)
+- [sudevschiz](https://github.com/sudevschiz)
 
 ## Contribution
 
 If you're new to contributing to Open Source on Github, [this guide](https://guides.github.com/activities/contributing-to-open-source/) can help you get started. Please check out the [contribution guide](CONTRIBUTING.md) for more details on how issues and pull requests work.
+
+###### This repository is just a small subset of work put together by a much larger pool of voluntary efforts contributed by generous people all around the world. Reach out to us through hello@covid19india.org