Add project management

CODE_OF_CONDUCT.md

@@ -1,82 +1,54 @@
-# 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.
-We strive to create a truly open experience for everyone
-
-## 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
-* Including new comers with respect and grace
-* Accepting differences in thought and opinion
-
-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
-* Racial discrimination
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
- address, without explicit permission
-* Using unacceptable language while communicating with others
-* Sarcastic replies on issues for people with legitimate concerns or doubts
-* Other conduct which could reasonably be considered inappropriate in a
- professional setting.
-* Plagiarized code or contributions will not be accepted.
-
-## 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. 
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at amitmandliya.davviet@gmail.com. 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
+## Code of Conduct
+
+### Promise
+
+We promise that our project and community is harassment-free for everyone, regardless of gender, age, disability, education, nationality and race.
+
+### Standards
+
+- Examples of acceptable behavior to create our environment include:
+  - respect to all different points.
+  - Using inclusive language.
+  - Being enthusiastic to other project or community members.
+  - Accept different and constructive criticism from others.
+
+- Examples of unacceptable behavior to create our environment includes:
+  - Insulting comments and personal or political attacks.
+  - leaking other's private information (e.g. physical address, mobile phone number or e-mail address)
+  - harassment or attack from online or offline.
+  - Personal hatred.
+
+### Responsibilities
+
+Project creators and maintainers are responsible for the standards and behaviors that are mentioned above.
+
+ Project creators and maintainers have responsibilites to guarantee any behaviors that are not acceptable.
+
+ Project creators and maintainers have right to guarantee all codes and commits in the community and delete or remove the harmful words.
+
+### Scope
+
+The Code of Conduct are available both in this project and public. 
+
+Project creators and maintainers have the right to explain and clarify the scope of  the Code of Conduct.
+
+### Enforcement
+
+If anyone finds any unacceptable commits, behaviors or codes, you can contact the project creator from piazza. Project creators and maintainers have right to guarantee all codes and commits in the community and delete or remove the harmful words.
+
+And anyone in the project does not follow the Code of Conduct can be remove or ban permanently, you can also contact other maintainers to reflect this situation.
+
+### Attribution
+
+This Code of Conduct is adapted from [Contributor Covenant](https://www.contributor-covenant.org)
+
+If you have any other question, please search in [FAQ](https://www.contributor-covenant.org/faq/)
+
+
+
+
+
+
+
+
+

CONTRIBUTING.md

@@ -1,49 +1,87 @@
-# Contributing to TeamFormationAssistant
-The following is a set of guidelines for contributing to TeamFormationAssistant on GitHub.
+## CONTRIBUTING to HW2b
 
-## Code of Conduct
-This project and everyone participating in it is governed by the [TeamFormationAssistant Code of Conduct](https://github.com/lokesh45/TeamFormationAssistant/blob/master/CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code.
+First off, thank you for taking the time to contribute!
 
-### Coding Guidelines
-* Avoid code smells and writing spaghetti code
-* Use Tabs instead of 4 spaces
-* Write clear and concise comments
-* Please use Camel-case pattern to name method and variables
-* Avoid using _ or - in methond and variable names.
-* For writing unit tests, please mock all the dependancies and just test functionality of that particular method / class.
+The following is the guidelines for contributing to hw2b on GitHub. These are mostly guidelines, not rules.
+
+### Before Getting Started
+
+- You need to know the packages you need.
+- You need to make sure the design decisions.
+  - when you make a significant decision, you need to know how you maintain the project and what you can or cannot support.
+  - submit the meaningful questions bravely.
+
+### Getting Started
+
+- Make sure you have GitHub account.
+
+- Make the repository on GitHub.
+
+
+
+### How to Contribute
+
+First, you need to report bugs, you can create bug reports and please include as many details as possible. The information it asks can help to resolve the problem faster.
+
+Then, suggest enhancements. You can submit an enhancement suggestion for our project, including completely new features and minor improvements to existing functionality. You also need to suggest as many details as possible which can help to understand the suggestion and find the related suggestions.
+
+### Documentation Guide
+
+- Use markdown for .md documents.
 
 ### Pull Requests
-* After you submit your pull request, verify that all status checks are passing.
-* Add team member(s) as reviewers upon opening the Pull Request.
-* Give description and comments to help the reviewers understand the changes.
-* Ensure that the description and comments are self-explanatory.
-* Make sure to update the relevant file changes on README.md.
-* Package-lock.json is required for travis CI to run, so do not add it to .gitignore.
-* Add appropriate labels to the pull requests for better resolution.
-* The code will not be accepted if there is low readability and code smells.
-* Code not passing style checkers and code formatters will not be accepted.
-
-### Git Commit Messages
-* Use the present tense.
-* Limit the first line to 72 characters or less.
-* Please be consice in commit messages.
-* Avoid re-use of commit messages.
-
-## Branch Naming guideline
-1. Feature development branch should begin with  name as "feature" eg: feature/fronend_testing
-2. Each feature branch should have its own tests written
-3. Bugs fixing branch should begin with "bugfix"
-4. Patching branch should have "patch" in the name
-
-### Reporting Bugs
-Explain the problem and include additional details to help maintainers reproduce the problem:
-* Use a clear and descriptive title for the issue to identify the problem.
-* Describe the exact steps which reproduce the problem in as many details as possible.
-* Provide specific examples to demonstrate the steps. Include links to files or GitHub projects.
-
-### Suggesting Enhancements
-* Use a clear and descriptive title for the issue to identify the suggestion.
-* Provide a step-by-step description of the suggested enhancement in as many details as possible.
-
-## Attribution
-This is adapted from [Atom](https://github.com/atom/atom), available at [(https://github.com/atom/atom/blob/master/CONTRIBUTING.md)]
+
+The process described here has several goals:
+
+- Maintain project quality.
+- Fix problems that are important to users.
+- Engage the community in working.
+- Enable a sustainable system for project maintainers to review contributions.
+
+While the prerequisites above must be satisfied prior to having your pull request reviewed, the reviewer(s) may ask you to complete additional design work, tests, or other changes before your pull request can be ultimately accepted.
+
+### Committing Changes
+
+You first need to follow the pull request above.
+
+Then, please avoid working directly on master branch and you need to create a new branch from where you want to start your work.
+
+Last but not least, you need to write meaningful commit messages and test for your changes.
+
+### Submitting Changes
+
+- Push the changes to the repository.
+- Submit a pull request to the original repository and follow the pull requests above.
+- Wait for feedback on the request.
+
+### Table of Contents
+
+- .gitignore
+
+- .trivis.yml
+
+- CITATION.md
+
+- CODE-OF-CONDUCT.md
+
+- CONTRIBUTING.md
+
+- LICENSE.md
+
+- README.md
+
+- setup.py
+
+- requirements.txt
+
+- code/
+
+  _init _.py
+
+- test/
+
+  README.md
+
+- data/
+
+  README.md

Untitled Diagram.drawio

@@ -0,0 +1 @@
+<mxfile host="app.diagrams.net" modified="2021-09-23T15:43:22.198Z" agent="5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/93.0.4577.82 Safari/537.36" etag="kby8hDejOZ__c5kig9fU" version="15.2.9" type="github"><diagram id="kgpKYQtTHZ0yAKxKKP6v" name="Page-1">7ZjLcpswFIafhmU6RhgbL2Pn0kU6yTSdSbOU4QTUCMQIEeM+fSUQYC5OcGrctNOVpV8XxP/pnMPYsFZhds1xHHxhHlADTbzMsC4MhEyELPmjlK1WTAcVis+Jp7VauCc/QYsTrabEg6QxUTBGBYmbosuiCFzR0DDnbNOc9sRo86kx9qEj3LuYdtUH4omgUB17UuufgfhB+WRzokdCXE7WQhJgj212JOvSsFacMVG0wmwFVLlX+lKsu9ozWh2MQySGLLCidHmV8YW7vZnE0e3DN4Svz/QuL5im+oUN6/x2/UNZWZxabEsr5AvEqpmG9IY8ASWR7C1j4CQEAVyOUC3f1dpSghFYamrczPuU4jgh63zbiVQ4uClPyAt8haTgn6ssjTzwdK8yL+8Izp4rHGpT/RbABWR77TEr0+V1BSYPyLdySnVXNSd9Ux3d3dTUK7bBDnGrFLG+aX61dQ1DNjSPA9igLps2kpiRSOTPtZeGfdHCwbgImM8iTHeBHN/Y/Tdrr9tTu2H2vM/srtfmYiyvrY7XHkliLNyg47kyg8gEcU6JH0lpzYRgYe4e5uJc5RzlvdxKahB5pbKmzH0up+lE5wwlAF4nTQ3xXyZLzH14bR7q58SBYiFjsplQe2zXS+/UTaz5npn9gMsdEpZyF/SiFrvqFO/HOf2HQ8du5qkqb70RO85YoWP/LyFZqxR8mBIy+6vjwD6khPSa3VNCZmN5Pe94zUGkPBpeQHaKBYtBDi09nAS5z2YxvFM2ICPiuzZdtR9V+9PCfndFKVLy25dpWEUZFDe/WWTQvHkFkDVrblEcdbQq4xzho6HnA0G6xrcVWtV5PCTSDgeLBoKd/SmwnaAd+fNh0QEr0dE1lniOAtY8EdihETs9Gdhps0KiduUbGWxZEU6dpM2TJenph4vlNnJ7fqQkLbv1vyfF9PpPKOvyFw==</diagram></mxfile>

backend/server/.gitignore

@@ -0,0 +1,2 @@
+node_modules
+package-lock.json

backend/server/README.md

@@ -0,0 +1,66 @@
+# Node.js – JWT Authentication & Authorization example with JSONWebToken & Sequelize
+
+## User Registration, User Login and Authorization process.
+The diagram shows flow of how we implement User Registration, User Login and Authorization process.
+
+![jwt-token-authentication-node-js-example-flow](jwt-token-authentication-node-js-example-flow.png)
+
+For more detail, please visit:
+> [Node.js JWT Authentication & Authorization example](https://bezkoder.com/node-js-jwt-authentication-mysql/)
+
+You may need to implement Refresh Token:
+
+![jwt-refresh-token-node-js-example-flow](jwt-refresh-token-node-js-example-flow.png)
+
+> [Node.js JWT Refresh Token example](https://bezkoder.com/jwt-refresh-token-node-js/)
+
+Working with Front-end:
+> [Vue.js JWT Authentication with Vuex and Vue Router](https://bezkoder.com/jwt-vue-vuex-authentication/)
+
+> [Angular 8 JWT Authentication with HttpInterceptor and Router](https://bezkoder.com/angular-jwt-authentication/)
+
+> [Angular 10 JWT Authentication with HttpInterceptor and Router](https://bezkoder.com/angular-10-jwt-auth/)
+
+> [Angular 11 JWT Authentication with HttpInterceptor and Router](https://bezkoder.com/angular-11-jwt-auth/)
+
+> [Angular 12 JWT Authentication with HttpInterceptor and Router](https://bezkoder.com/angular-12-jwt-auth/)
+
+> [React JWT Authentication & Authorization (without Redux) example](https://bezkoder.com/react-jwt-auth/)
+
+> [React Redux JWT Authentication & Authorization example](https://bezkoder.com/react-redux-jwt-auth/)
+
+## More Practice:
+> [Build Node.js Rest APIs with Express, Sequelize & MySQL](https://bezkoder.com/node-js-express-sequelize-mysql/)
+
+> [Server side Pagination in Node.js with Sequelize and MySQL](https://bezkoder.com/node-js-sequelize-pagination-mysql/)
+
+> [Node.js Express File Upload Rest API example](https://bezkoder.com/node-js-express-file-upload/)
+
+> [Node.js Express File Upload with Google Cloud Storage example](https://bezkoder.com/google-cloud-storage-nodejs-upload-file/)
+
+> [Node.js JWT Authentication & Authorization example with MongoDB](https://bezkoder.com/node-js-mongodb-auth-jwt/)
+
+Associations:
+> [Sequelize Associations: One-to-Many Relationship example](https://bezkoder.com/sequelize-associate-one-to-many/)
+
+> [Sequelize Associations: Many-to-Many Relationship example](https://bezkoder.com/sequelize-associate-many-to-many/)
+
+Deployment:
+> [Deploying/Hosting Node.js app on Heroku with MySQL database](https://bezkoder.com/deploy-node-js-app-heroku-cleardb-mysql/)
+
+Integration on same Server/Port:
+> [Integrate Angular 8 with Node.js Express](https://bezkoder.com/integrate-angular-8-node-js/)
+
+> [Integrate Angular 10 with Node.js Express](https://bezkoder.com/integrate-angular-10-node-js/)
+
+> [Integrate React with Node.js Express](https://bezkoder.com/integrate-react-express-same-server-port/)
+
+## Project setup
+```
+npm install
+```
+
+### Run
+```
+node server.js
+```

backend/server/app/config/auth.config.js

@@ -0,0 +1,3 @@
+module.exports = {
+  secret: "bezkoder-secret-key"
+};

backend/server/app/config/db.config.js

@@ -0,0 +1,13 @@
+module.exports = {
+    HOST: "database",
+    USER: "dbuser",
+    PASSWORD: "dbuserpwd",
+    DB: "teamformationassistant",
+    dialect: "mysql",
+    pool: {
+        max: 5,
+        min: 0,
+        acquire: 30000,
+        idle: 10000
+    }
+};