Skip to content

Druhin13/corona

Folders and files

NameName
Last commit message
Last commit date

Latest commit

ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 

Repository files navigation

Corona Info ๐Ÿ‡ฎ๐Ÿ‡ณ
Awesome

Codacy Badge


Snapshots

Contributing to Corona Info

Thanks for your interest in helping Corona Info

Getting Started

Corona Info's open issues are here In time, we'll tag issues that would make a good first pull request for new contributors. An easy way to get started helping the project is to create an issue. You can do that on the coronainfo's issues page by clicking on the green button at the right.

Issues can include bugs to fix, features to add, or documentation that looks outdated.

Contributions

Corona Info welcomes contributions from everyone.

Contributions to Corona Info should be made in the form of GitHub pull requests. Each pull request will be reviewed and either landed in the master tree or given feedback for changes that would be required.

Make sure you check the open issues.

Pull Request Checklist

  • Branch from the master branch and, if needed, rebase to the current master branch before submitting your pull request. If it doesn't merge cleanly with master you may be asked to rebase your changes.

  • Try to make small commits if possible, while ensuring that each commit is correct independently (i.e., each commit should compile and pass tests). It helps us to review that as well.

  • Don't put submodule updates in your pull request unless they are to landed commits.

Licence

All code in this repository is licensed under the MIT License.



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 [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

For answers to common questions about this code of conduct, see https://www.contributor-covenant.org/faq





What's New ๐Ÿ‘€

Release 3.0 ๐Ÿ”ฅ

  • A whole new UI ๐Ÿคฉ
  • Simpler Interactions ๐Ÿ˜…
  • Dark mode ๐ŸŒœ
  • Notifications ๐Ÿ””
  • Footer added ๐Ÿ“ฐ๐Ÿ“Œ & offcourse
  • Bug fixes ๐Ÿคญ

Support

Release 3.0 is accessible only in West Bengal
Support for other states will be added in the Release 3.1

IE 11+
Edge 79+
Firefox 72+
Safari 12+
Opera 66+
Chrome 79+
iOS 11+
Android 4+

Contact

Mail me - [email protected]
Github - https://github.com/Druhin13
Dribbble - https://dribbble.com/druhin

Made with ๐Ÿ’• & โ˜• by Druh.in