added template repository structure

Author: xkeshav

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,152 @@
+# Contributor Covenant Code of Conduct
+
+**Table of Contents:**
+
+- [Contributor Covenant Code of Conduct](#contributor-covenant-code-of-conduct)
+  - [Summary](#summary)
+  - [Our Pledge](#our-pledge)
+  - [Our Standards](#our-standards)
+  - [Enforcement Responsibilities](#enforcement-responsibilities)
+  - [Scope](#scope)
+  - [Enforcement](#enforcement)
+  - [Enforcement Guidelines](#enforcement-guidelines)
+    - [1. Correction](#1-correction)
+    - [2. Warning](#2-warning)
+    - [3. Temporary Ban](#3-temporary-ban)
+    - [4. Permanent Ban](#4-permanent-ban)
+  - [Attribution](#attribution)
+
+**Version**: 1.0.0
+
+## Summary
+
+As contributors and maintainers of this projects, we will respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities.
+
+Communication regarding the projects through any channel must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. Courtesy and respect shall be extended to everyone involved in this project. Our experiences as individuals differs widely, and as such contributors are expected to be respectful of differing viewpoints and ideas.
+
+We expect all contributors to uphold our standards of conduct. If any member of the community violates this code of conduct, the Embedded Artistry team and project maintainers will take action. We reserve the right to remove issues, comments, and PRs that do not comply with our conduct standards. Repeated or significant offenses will result in blocked accounts and disassociation with our projects and the Embedded Artistry community.
+
+If you are subject to or witness unacceptable behavior, or have any other concerns, please email us at [`xkeshav@gmail.com`][contact].
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible 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.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders 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, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[*this email*](mailto:xkeshav@gmail.com).
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+<https://www.contributor-covenant.org/version/2/0/code_of_conduct.html>.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+<https://www.contributor-covenant.org/faq>. Translations are available at
+<https://www.contributor-covenant.org/translations>.
+
+[contact]: mailto:xkeshav@gmail.com

.github/CONTRIBUTING.md

@@ -0,0 +1,196 @@
+# Contribute
+
+This article explains how to contribute to project. Please read through the following guidelines.
+
+Write something nice and instructive as an intro. Talk about what kind of contributions you are interested in.
+
+> Welcome! We love receiving contributions from our community, so thanks for stopping by! There are many ways to contribute, including submitting bug reports, improving documentation, submitting feature requests, reviewing new submissions, or contributing code that can be incorporated into the project.
+
+## Summary
+
+This document describes our development process. Following these guidelines shows that you respect the time and effort of the developers managing this project. In return, you will be shown respect in addressing your issue, reviewing your changes, and incorporating your contributions.
+
+> 👉 **Note**: before participating in our community, please read our
+> [code of conduct][coc].
+> By interacting with this repository, organization, or community you agree to
+> abide by its terms.
+
+## Contributions
+
+There’s several ways to contribute, not just by writing code. If you have questions, see [support][support].
+
+### Financial support
+
+It’s possible to support us financially by becoming a backer or sponsor through [Open Collective][collective].
+
+### Improve docs
+
+As a user you’re perfect for helping us improve our docs.Typo corrections, error fixes, better explanations, new examples, etcetera.
+
+### Improve issues
+
+Some issues lack information, aren’t reproducible, or are just incorrect. You can help by trying to make them easier to resolve.
+Existing issues might benefit from your unique experience or opinions.
+
+### Write code
+
+Code contributions are very welcome.
+It’s probably a good idea to first post a question or open an issue to report a bug or suggest a new feature before creating a pull request.
+
+## Submitting an issue
+
+* The issue tracker is for issues. Use discussions for support
+* Search the issue tracker (including closed issues) before opening a new issue
+* Ensure you’re using the latest version of our packages
+* Use a clear and descriptive title
+* Include as much information as possible: steps to reproduce the issue, error message, version, operating system, etcetera
+* The more time you put into an issue, the better we will be able to help you
+* The best issue report is a  proper reproduction step to prove it
+
+## Development Process
+
+What is your development process?
+
+> This project follows the basic git glow
+
+Talk about branches people should work on. Specifically, where is the starting point? `main`, `feature`, `hotfix` `task` etc.
+
+### Testing
+
+If you add code you need to add tests! We’ve learned the hard way that code without tests is undependable. If your pull request reduces our test coverage because it lacks tests then it will be rejected.
+
+Provide instructions for adding new tests. Provide instructions for running tests.
+
+```sh
+npm run test
+```
+
+### Style Guidelines
+
+run below command
+
+```sh
+npm run lint
+```
+
+### Code Formatting
+
+use code formatter in your IDE, add prettier and some other useful extension in your IDE.
+
+### Git Commit Guidelines
+
+below are the guidelines for your commit messages.
+
+* add clear message and with 50 lines
+* prefix feature / issue number from issue page
+
+### Submitting a pull request
+
+* Run `npm test` locally to build, format, and test your changes
+* Non-trivial changes are often best discussed in an issue first, to prevent you from doing unnecessary work
+* For ambitious tasks, you should try to get your work in front of the community for feedback as soon as possible
+* New features should be accompanied by tests and documentation
+* Don’t include unrelated changes
+* Test before submitting code by running `npm test`
+* Write a convincing description of why we should land your pull request: it’s your job to convince us  
+  
+## Pull Request Process
+
+Add notes for pushing your branch:
+
+When you are ready to generate a pull request, either for preliminary review, or for consideration of merging into the project you must first push your local topic branch back up to GitHub:
+
+```sh
+git push origin feature/branch-name
+```
+
+Include a note about submitting the PR:
+
+Once you've committed and pushed all of your changes to GitHub, go to the page for your fork on GitHub, select your development branch, and click the pull request button. If you need to make any adjustments to your pull request, just push the updates to your branch. Your pull request will automatically track the changes on your development branch and update.
+
+1. Ensure any install or build dependencies are removed before the end of the layer when doing a build.
+2. Update the README.md with details of changes to the interface, this includes new environment variables, exposed ports, useful file locations and container parameters.
+3. Increase the version numbers in any examples files and the README.md to the new version that this Pull Request would represent. The versioning scheme we use is [SemVer](http://semver.org/).
+4. You may merge the Pull Request in once you have the sign-off of two other developers, or if you do not have permission to do that, you may request the second reviewer to merge it for you.
+
+### Review Process
+
+Who reviews it? Who needs to sign off before it’s accepted? When should a contributor expect to hear from you? How can contributors get commit access, if at all?
+
+> The core team looks at Pull Requests on a regular basis in a weekly triage meeting that we hold in a public Google Hangout. The hangout is announced in the weekly status updates that are sent to the puppet-dev list. Notes are posted to the Puppet Community community-triage repo and include a link to a YouTube recording of the hangout. After feedback has been given we expect responses within two weeks. After two weeks we may close the pull request if it isn't showing any activity.
+
+> Except for critical, urgent or very small fixes, we try to leave pull requests open for most of the day or overnight if something comes in late in the day, so that multiple people have the chance to review/comment.  Anyone who reviews a pull request should leave a note to let others know that someone has looked at it.  For larger commits, we like to have a +1 from someone else on the core team and/or from other contributor(s).  Please note if you reviewed the code or tested locally -- a +1 by itself will typically be interpreted as your thinking its a good idea, but not having reviewed in detail.
+
+Perhaps also provide the steps your team will use for checking a PR. Or discuss the steps run on your CI server if you have one. This will help developers understand how to investigate any failures or test the process on their own.
+
+### Addressing Feedback
+
+Once a PR has been submitted, your changes will be reviewed and constructive feedback may be provided. Feedback isn't meant as an attack, but to help make sure the highest-quality code makes it into our project. Changes will be approved once required feedback has been addressed.
+
+If a maintainer asks you to "rebase" your PR, they're saying that a lot of code has changed, and that you need to update your fork so it's easier to merge.
+
+To update your forked repository, follow these steps:
+
+### Fetch upstream master and merge with your repo's main branch
+
+```sh
+
+git fetch upstream
+git checkout main
+git merge upstream/main
+```
+
+#### If there were any new commits, rebase your development branch
+
+```sh
+git checkout feature/branch-name
+git rebase main
+```
+
+If too much code has changed for git to automatically apply your branches changes to the new master, you will need to manually resolve the merge conflicts yourself.
+
+Once your new branch has no conflicts and works correctly, you can override your old branch using this command:
+
+```sh
+
+git push origin feature/branch-name
+
+```
+
+Note that this will overwrite the old branch on the server, so make sure you are happy with your changes first!
+
+## Community
+
+Do you have a mailing list, Google group, slack channel, IRC channel? Link to them here.
+
+Include Other Notes on how people can contribute
+
+* You can help us answer questions our users have here:
+* You can help build and design our website here:
+* You can help write blog posts about the project by:
+* You can help with newsletters and internal communications by:
+
+* Create an example of the project in real world by building something or showing what others have built.
+* Write about other people’s projects based on this project. Show how it’s used in daily life. Take screenshots and make videos!
+
+## Resources
+
+* [How to contribute to open source](https://opensource.guide/how-to-contribute/)
+* [Making your first contribution](https://medium.com/@vadimdemedes/making-your-first-contribution-de6576ddb190)
+* [Using pull requests](https://help.github.com/articles/about-pull-requests/)
+* [GitHub help](https://help.github.com)
+* [git commit message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)
+
+## License
+
+© [Keshav Mohta][author]
+
+<!-- Definitions -->
+
+[author]: https://xkeshav.com  
+
+[collective]: https://opencollective.com/recursivezero
+
+[support]: https://github.com/xkeshav/template/blob/main/.github/SUPPORT.md
+
+[coc]: https://github.com/xkeshav/template/blob/main/.github/CODE_OF_CONDUCT.md

.github/COOWNERS

@@ -0,0 +1,19 @@
+# Lines starting with '#' are comments
+
+# Each line is a file pattern followed by one or more owners
+
+# These owners will be the default owners for everything in the repo
+
+*       @xkeshav
+
+# Order is important. The last matching pattern has the most precedence
+
+# So if a pull request only touches javascript files, only these owners
+
+# will be requested to review
+
+*.js    @xkeshav
+
+# You can also use email addresses if you prefer
+
+docs/*  <xkeshav@gmail.com>