UI Revamp and live analytics

.coveralls.yml

@@ -0,0 +1,2 @@
+service_name: travis-pro
+repo_token: 0vbZ3LqjoO2fwYBVFcdpeNZJjLT5iPumw

.gitignore

@@ -0,0 +1,32 @@
+lib-cov
+*.seed
+*.log
+*.csv
+*.dat
+*.out
+*.pid
+*.gz
+*.swp
+
+pids
+logs
+results
+tmp
+
+# Coverage reports
+coverage
+
+# Dependency directory
+node_modules
+bower_components
+
+# Editors
+.idea
+*.iml
+
+# OS metadata
+.DS_Store
+Thumbs.db
+
+# Ignore built ts files
+dist/**/*

CONTRIBUTING.md

@@ -1,74 +1,81 @@
-The following contributing guide has been inspired by [flask](https://github.com/pallets/flask/blob/main/CONTRIBUTING.rst)
-
-# Contributing guide
-
-First of all, Thank you for your interest in contributing to our repository. 🤩🥳🎉
-
-We welcome contributions in the form of bug reports, documentation  pull requests. Following are
-certain guidelines and instructions to follow while making your contribution.
-
-## Table of Contents
-
-[Code of Conduct](#code-of-conduct)
-
-[Found a Bug](#found-a-bug)
-
-[Updating or Adding documentation](#updating-or-adding-documentation)
-
-[Code contributions](#code-contributions)
-
-
-## Code of Conduct
-
-This project and everyone participating in it is governed by the [Code of Conduct](https://github.com/hetthakkar/polly/blob/main/CODE_OF_CONDUCT.md). By participating and working with this repository, you are expected to sustain this code. If you witness any unacceptable behavior, please report it to lorenz.scheller@gmail.com.
-
-## Found a Bug?
-
-Help us by submitting an issue to our [GitHub Repository](https://github.com/hetthakkar/polly). Use github issues for reporting bugs and make sure your post follows details:
-- Present a [minimal, reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of your issue and remove any unnecessary details
-- Make sure to use the latest release of the library to avoid reporting bugs that were fixed in later releases
-- Optionally, add your device configuration information
-
-## Updating or Adding documentation
-
-For suggesting minor changes to documentation(typos, etc.) use the Edit button✏️ in Github to make the change and click "Propose Changes" to submit it for review.
-
-For adding new pages, fork the repository, create a branch and submit it as a PR
-
-## Code contributions
-
-### Getting Started
-
-Make sure you have 
-
-Follow these steps to get polly setup on your local machine
-- Fork the polly repository to your own Github account 
-- Clone the repository
-
-        $ git clone https://github.com/Neelkanth7/TUSK
-        $ cd TUSK
-- Add your fork as remote to push your work to
-- Create a virtual environment and install the required dependencies
-- Install the polly package by running
-  ```
-      pip install .
-  ```
-- Run tests using the following command
-  ```
-      pytest
-  ```
-- When ready to submit, raise a pull request and describe the feature/bug fix thoroughly in the description. Also add a link to the issue if relevant
-
-### Commit guide
-
-All commit messages must follow the [conventional commit specification](https://www.conventionalcommits.org/en/v1.0.0/). This helps others to easily understand commit logs and allows for automated changelog generation. Here's an example of a commit message that follows the conventional commit spec
-
-    feat: allow provided config object to extend other configs
-
-In general, the messages must follow the following syntax
-
-    <type>[optional scope]: <description>
-
-    [optional body]
-
-    [optional footer(s)]
+The following contributing guide has been inspired by [flask](https://github.com/pallets/flask/blob/main/CONTRIBUTING.rst)
+
+# Contributing guide
+
+First of all, Thank you for your interest in contributing to our repository. 🤩🥳🎉
+
+We welcome contributions in the form of bug reports, documentation  pull requests. Following are
+certain guidelines and instructions to follow while making your contribution.
+
+## Table of Contents
+
+[Code of Conduct](#code-of-conduct)
+
+[Found a Bug](#found-a-bug)
+
+[Updating or Adding documentation](#updating-or-adding-documentation)
+
+[Code contributions](#code-contributions)
+
+
+## Code of Conduct
+
+This project and everyone participating in it is governed by the [Code of Conduct](https://github.com/shahrk/polly/blob/main/CODE_OF_CONDUCT.md). By participating and working with this repository, you are expected to sustain this code. If you witness any unacceptable behavior, please report it to lorenz.scheller@gmail.com.
+
+## Found a Bug?
+
+Help us by submitting an issue to our [GitHub Repository](https://github.com/shahrk/polly). Use github issues for reporting bugs and make sure your post follows details:
+- Present a [minimal, reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of your issue and remove any unnecessary details
+- Make sure to use the latest release of the library to avoid reporting bugs that were fixed in later releases
+- Optionally, add your device configuration information
+
+## Updating or Adding documentation
+
+For suggesting minor changes to documentation(typos, etc.) use the Edit button✏️ in Github to make the change and click "Propose Changes" to submit it for review.
+
+For adding new pages, fork the repository, create a branch and submit it as a PR
+
+## Code contributions
+
+### Getting Started
+
+Make sure you have 
+
+i) Docker installed.
+ii) Visual studio code for development.
+
+That's it. Having docker is the only requirement. All that is needed to get started and running the application code is docker-compose up.
+
+- When ready to submit, raise a pull request and describe the feature/bug fix thoroughly in the description. Also add a link to the issue if relevant
+
+
+
+
+### Commit guide
+
+All commit messages must follow the [conventional commit specification](https://www.conventionalcommits.org/en/v1.0.0/). This helps others to easily understand commit logs and allows for automated changelog generation. Here's an example of a commit message that follows the conventional commit spec
+
+    feat: allow provided config object to extend other configs
+
+In general, the messages must follow the following syntax
+
+    <type>[optional scope]: <description>
+
+    [optional body]
+
+    [optional footer(s)]
+
+
+### PR Raising guide
+
+All PR raised must follow the following pattern:
+
+i) Ensure that there is atleast an issue created for the code you are pushing.
+ii) Raise a new Issue on the Github if the issue doesn't exist.
+ii) Start working on the code for the same.
+iii) List the issues fixes in the PR description. Following is an example :- https://github.com/shahrk/polly/pull/28
+
+
+### Frontend coding standards
+
+We extensively follow the following for frontend code :- http://www.w3big.com/bootstrap/bootstrap-css-codeguide-html.html