Merge from master branch

.eslintrc.json

@@ -0,0 +1,26 @@
+{
+    "env": {
+        "node": true,
+        "es6": true,
+        "jest": true
+    },
+    "parser": "@typescript-eslint/parser",
+    "parserOptions": {
+        "ecmaVersion": 2018,
+        "sourceType": "module"
+    },
+    "extends": [
+        "eslint:recommended",
+        "plugin:prettier/recommended",
+        "plugin:@typescript-eslint/recommended",
+        "plugin:jest/recommended"
+    ],
+    "globals": {
+        "Atomics": "readonly",
+        "SharedArrayBuffer": "readonly"
+    },
+    "plugins": [
+    ],
+    "rules": {
+    }
+}

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,38 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+ - OS: [e.g. iOS]
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 22]
+
+**Smartphone (please complete the following information):**
+ - Device: [e.g. iPhone6]
+ - OS: [e.g. iOS8.1]
+ - Browser [e.g. stock browser, safari]
+ - Version [e.g. 22]
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/settings.yml

@@ -11,41 +11,77 @@ repository:
   allow_squash_merge: true
   allow_merge_commit: true
 labels:
-  - name: 'Status: Blocked'
-    color: e2002a
-    description: An issued blocked
-
-  - name: 'Status: On Hold'
-    color: c0d2da
-    description: the tasks that we will not do until further notice
-
-  - name: 'Type: Bug'
+  - name: 'bug'
     color: CC0000
     description: An issue with the system bug
 
-  - name: 'Type: Enhancement'
+  - name: 'enhancement'
     color: 83b8e8
     description: An issue to enhancement the system ⚙️.
 
-  - name: 'Type: Maintenance'
-    color: fcc73a
-    description: An issue to maintenance the system.
-
-  - name: 'Type: Analysis'
+  - name: 'question'
     color: cd237b
     description: An issue to maintenance the system.
 
-  - name: 'Type: Feature'
+  - name: 'feature'
     color: 336699
     description: New functionality.
 
-  - name: 'Type: Discussion'
+  - name: 'discussion'
     color: ddd8cc
-    decription: we haven't reached a consensus there, maybe you can contribute?
+    description: we haven't reached a consensus there, maybe you can contribute?
+
+  - name: 'feedback'
+    color: fcc73a
+    description: General feedback more than bug reports or feature requests.
+
+  - name: 'help-wanted'
+    color: 46E251
+    description: The FullStacktf core team would appreciate help from the community in resolving these issues.
+
+  - name: 'more-information-needed'
+    color: 8A46E2
+    description: More information needs to be collected about these problems or feature requests (e.g. steps to reproduce).
+
+  - name: 'needs-reproduction'
+    color: C346E2
+    description: Likely bugs, but haven't been reliably reproduced
 
-  - name: 'Type: Epic'
+  - name: 'duplicate'
     color: 74b566
-    description: is an issue that can lead to several PRs and should be broken down into atomic issues before it gets implemented.
+    description: Issues which are duplicates of other issues, i.e. they have been reported before.
+
+  - name: 'blocked'
+    color: FA0415
+    description: Issues blocked on other issues.
+
+  - name: 'wontfix'
+    color: 04B0FA
+    description: The FullStacktf core team has decided not to fix these issues for now, either because they're working as intended or for some other reason.
+
+  - name: 'invalid'
+    color: FAD104
+    description: Issues which aren't valid (e.g. user errors).
+
+  - name: 'work-in-progress'
+    color: 6F04FA
+    description: Pull requests which are still being worked on, more changes will follow.
+
+  - name: 'needs-review'
+    color: FA0425
+    description: Pull requests which need code review, and approval from maintainers or FullStacktf core team.
+
+  - name: 'under-review'
+    color: 04FAFA
+    description: Pull requests being reviewed by maintainers or FullStacktf core team.
+
+  - name: 'requires-changes'
+    color: FA7F04
+    description: Pull requests which need to be updated based on review comments and then reviewed again.
+
+  - name: 'needs-testing'
+    color: 3EFA04
+    description: Pull requests which need manual testing.
 
   - name: 'Priority: Critical'
     color: e2002a
@@ -63,38 +99,6 @@ labels:
     color: 009922
     description: low priority tasks that can be done when there's no medium priority tasks
 
-  - name: 'Estimate: 1h'
-    color: bfe5c1
-    description: Estimate 1hour
-
-  - name: 'Estimate: 2h'
-    color: bfe5c1
-    description: Estimate 2 hours
-
-  - name: 'Estimate: 3h'
-    color: bfe5c1
-    description: Estimate 3 hours
-
-  - name: 'Estimate: 5h'
-    color: bfe5c1
-    description: Estimate 5 hours
-
-  - name: 'Estimate: 8h'
-    color: bfe5c1
-    description: Estimate 8 hours
-
-  - name: 'Estimate: 13h'
-    color: bfe5c1
-    description: Estimate 13 hours
-
-  - name: 'Estimate: 20h'
-    color: bfe5c1
-    description: Estimate 20 hours
-
-  - name: 'Estimate: 40h'
-    color: bfe5c1
-    description: Estimate 40 hours
-
 branches:
   - name: master
     protection:

.travis.yml

@@ -0,0 +1,53 @@
+branches:
+  only:
+    - master
+    - docs
+
+services:
+  - docker
+
+matrix:
+  include:
+    - language: node_js
+      name: "Testing Docker Server"
+      nodejs:
+          - "10"
+      before_script: 
+        - docker pull $DOCKER_USERNAME/express-mongo
+        - docker run -p 27017:27017 -d $DOCKER_USERNAME/express-mongo
+        - docker ps 
+        - set -e PORT=3000
+      script:
+        - npm run test:coverage
+        - npm run coverage:coveralls
+        - npm run coverage:codacy
+
+    - language: node_js
+      name : "Documentation Deployment"
+      nodejs:
+        - "10"
+      script: 
+        - npm run build
+        - npm run build:docs
+      deploy:
+        local_dir: docs/api
+        github_token: $GH_TOKEN
+        provider: pages
+        skip_cleanup: true
+        keep_history: true
+        on:
+          branch: docs
+
+    - language: bash  
+      name: "Docker Build"    
+      before_script: docker build -t $DOCKER_USERNAME/express-mongo .
+      script: docker run -d -p 27017:27017 $DOCKER_USERNAME/express-mongo
+      after_success: 
+        - docker ps  
+        - echo "$DOCKER_PASSWORD" | docker login -u "$DOCKER_USERNAME" --password-stdin
+        - docker push $DOCKER_USERNAME/express-mongo:latest
+
+
+
+
+

CODE_OF_CONDUCT.md

@@ -0,0 +1,94 @@
+# Citizen Code of Conduct
+
+## 1. Purpose
+
+A primary goal of Myment is to be inclusive to the largest number of contributors, with the most varied and diverse backgrounds possible. As such, we are committed to providing a friendly, safe and welcoming environment for all, regardless of gender, sexual orientation, ability, ethnicity, socioeconomic status, and religion (or lack thereof).
+
+This code of conduct outlines our expectations for all those who participate in our community, as well as the consequences for unacceptable behavior.
+
+We invite all those who participate in Myment to help us create safe and positive experiences for everyone.
+
+## 2. Open [Source/Culture/Tech] Citizenship
+
+A supplemental goal of this Code of Conduct is to increase open [source/culture/tech] citizenship by encouraging participants to recognize and strengthen the relationships between our actions and their effects on our community.
+
+Communities mirror the societies in which they exist and positive action is essential to counteract the many forms of inequality and abuses of power that exist in society.
+
+If you see someone who is making an extra effort to ensure our community is welcoming, friendly, and encourages all participants to contribute to the fullest extent, we want to know.
+
+## 3. Expected Behavior
+
+The following behaviors are expected and requested of all community members:
+
+ * Participate in an authentic and active way. In doing so, you contribute to the health and longevity of this community.
+ * Exercise consideration and respect in your speech and actions.
+ * Attempt collaboration before conflict.
+ * Refrain from demeaning, discriminatory, or harassing behavior and speech.
+ * Be mindful of your surroundings and of your fellow participants. Alert community leaders if you notice a dangerous situation, someone in distress, or violations of this Code of Conduct, even if they seem inconsequential.
+ * Remember that community event venues may be shared with members of the public; please be respectful to all patrons of these locations.
+
+## 4. Unacceptable Behavior
+
+The following behaviors are considered harassment and are unacceptable within our community:
+
+ * Violence, threats of violence or violent language directed against another person.
+ * Sexist, racist, homophobic, transphobic, ableist or otherwise discriminatory jokes and language.
+ * Posting or displaying sexually explicit or violent material.
+ * Posting or threatening to post other people's personally identifying information ("doxing").
+ * Personal insults, particularly those related to gender, sexual orientation, race, religion, or disability.
+ * Inappropriate photography or recording.
+ * Inappropriate physical contact. You should have someone's consent before touching them.
+ * Unwelcome sexual attention. This includes, sexualized comments or jokes; inappropriate touching, groping, and unwelcomed sexual advances.
+ * Deliberate intimidation, stalking or following (online or in person).
+ * Advocating for, or encouraging, any of the above behavior.
+ * Sustained disruption of community events, including talks and presentations.
+
+## 5. Weapons Policy
+
+No weapons will be allowed at Myment events, community spaces, or in other spaces covered by the scope of this Code of Conduct. Weapons include but are not limited to guns, explosives (including fireworks), and large knives such as those used for hunting or display, as well as any other item used for the purpose of causing injury or harm to others. Anyone seen in possession of one of these items will be asked to leave immediately, and will only be allowed to return without the weapon. Community members are further expected to comply with all state and local laws on this matter.
+
+## 6. Consequences of Unacceptable Behavior
+
+Unacceptable behavior from any community member, including sponsors and those with decision-making authority, will not be tolerated.
+
+Anyone asked to stop unacceptable behavior is expected to comply immediately.
+
+If a community member engages in unacceptable behavior, the community organizers may take any action they deem appropriate, up to and including a temporary ban or permanent expulsion from the community without warning (and without refund in the case of a paid event).
+
+## 7. Reporting Guidelines
+
+If you are subject to or witness unacceptable behavior, or have any other concerns, please notify a community organizer as soon as possible. .
+
+
+
+Additionally, community organizers are available to help community members engage with local law enforcement or to otherwise help those experiencing unacceptable behavior feel safe. In the context of in-person events, organizers will also provide escorts as desired by the person experiencing distress.
+
+## 8. Addressing Grievances
+
+If you feel you have been falsely or unfairly accused of violating this Code of Conduct, you should notify fullstacktf with a concise description of your grievance. Your grievance will be handled in accordance with our existing governing policies. 
+
+
+
+## 9. Scope
+
+We expect all community participants (contributors, paid or otherwise; sponsors; and other guests) to abide by this Code of Conduct in all community venues--online and in-person--as well as in all one-on-one communications pertaining to community business.
+
+This code of conduct and its related procedures also applies to unacceptable behavior occurring outside the scope of community activities when such behavior has the potential to adversely affect the safety and well-being of community members.
+
+## 10. Contact info
+
+
+
+## 11. License and attribution
+
+The Citizen Code of Conduct is distributed by [Stumptown Syndicate](http://stumptownsyndicate.org) under a [Creative Commons Attribution-ShareAlike license](http://creativecommons.org/licenses/by-sa/3.0/). 
+
+Portions of text derived from the [Django Code of Conduct](https://www.djangoproject.com/conduct/) and the [Geek Feminism Anti-Harassment Policy](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy).
+
+_Revision 2.3. Posted 6 March 2017._
+
+_Revision 2.2. Posted 4 February 2016._
+
+_Revision 2.1. Posted 23 June 2014._
+
+_Revision 2.0, adopted by the [Stumptown Syndicate](http://stumptownsyndicate.org) board on 10 January 2013. Posted 17 March 2013._