ml5js · joeyklee · Oct 17, 2019 · May 23, 2019 · Jun 3, 2019 · Jun 5, 2019
diff --git a/.all-contributorsrc b/.all-contributorsrc
@@ -548,6 +548,107 @@
         "design",
         "userTesting"
       ]
+    },
+    {
+      "login": "jepster-dk",
+      "name": "jepster-dk",
+      "avatar_url": "https://avatars3.githubusercontent.com/u/7010555?v=4",
+      "profile": "http://jepster.dk",
+      "contributions": [
+        "code",
+        "ideas"
+      ]
+    },
+    {
+      "login": "xanderjakeq",
+      "name": "Xander Jake de los Santos",
+      "avatar_url": "https://avatars1.githubusercontent.com/u/13279523?v=4",
+      "profile": "https://xanderjakeq.page/",
+      "contributions": [
+        "ideas"
+      ]
+    },
+    {
+      "login": "catarak",
+      "name": "Cassie Tarakajian",
+      "avatar_url": "https://avatars1.githubusercontent.com/u/6063380?v=4",
+      "profile": "https://github.com/catarak",
+      "contributions": [
+        "bug",
+        "infra",
+        "ideas"
+      ]
+    },
+    {
+      "login": "dcbriccetti",
+      "name": "Dave Briccetti",
+      "avatar_url": "https://avatars0.githubusercontent.com/u/55099?v=4",
+      "profile": "http://davebsoft.com",
+      "contributions": [
+        "bug"
+      ]
+    },
+    {
+      "login": "Sblob1",
+      "name": "Sblob1",
+      "avatar_url": "https://avatars0.githubusercontent.com/u/38335473?v=4",
+      "profile": "https://github.com/Sblob1",
+      "contributions": [
+        "bug"
+      ]
+    },
+    {
+      "login": "jwilber",
+      "name": "Jared Wilber",
+      "avatar_url": "https://avatars2.githubusercontent.com/u/8595819?v=4",
+      "profile": "https://www.jwilber.me/",
+      "contributions": [
+        "example",
+        "ideas",
+        "code"
+      ]
+    },
+    {
+      "login": "tezzutezzu",
+      "name": "danilo",
+      "avatar_url": "https://avatars2.githubusercontent.com/u/135866?v=4",
+      "profile": "https://github.com/tezzutezzu",
+      "contributions": [
+        "code",
+        "ideas"
+      ]
+    },
+    {
+      "login": "EmmaGoodliffe",
+      "name": "Emma Goodliffe",
+      "avatar_url": "https://avatars1.githubusercontent.com/u/32788926?v=4",
+      "profile": "https://github.com/EmmaGoodliffe",
+      "contributions": [
+        "ideas",
+        "question",
+        "maintenance"
+      ]
+    },
+    {
+      "login": "EonYang",
+      "name": "Yang",
+      "avatar_url": "https://avatars3.githubusercontent.com/u/9332910?v=4",
+      "profile": "http://yangyang.blog",
+      "contributions": [
+        "code",
+        "bug"
+      ]
+    },
+    {
+      "login": "lydiajessup",
+      "name": "Lydia Jessup",
+      "avatar_url": "https://avatars3.githubusercontent.com/u/26204298?v=4",
+      "profile": "https://github.com/lydiajessup",
+      "contributions": [
+        "code",
+        "ideas",
+        "example"
+      ]
     }
   ],
   "contributorsPerLine": 7,

diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md
@@ -1,23 +1,57 @@
-## → Description 📝
+<!--------------------------------------------
+🌈DEAR BELOVED ML5 COMMUNITY MEMBER. WELCOME. 🌈
+---------------------------------------------->
 
-A clear and concise description of what the issue is about. Let us know if you:
+Dear ml5 community, 
 
-- found a bug 🐛
-- want to suggest an update 💡
-- have an idea for a new feature 🆕 
+I'm submitting a new issue. Please see the details below.
 
 
 
-## → Screenshots 🖼
-(Any relevant screenshots, sketches, or helpful concept diagrams)
+### → Step 1: Describe the issue 📝
+> Did you find a bug? Want to suggest an idea for feature?
 
 
-## → Helpful Information 🦄
 
-A list of relevant information for this issue. This will help people navigate the project and offer some clues of where to start. Depending on the nature of this issue, important and helpful information might include:
 
-- **Web browser and version** (e.g. Firefox version 65, Chrome version 71.0)
-- **Operating System** (e.g. MacOS, Windows, Ubuntu)
-- Steps to reproduce the issue
-- ml5 version you're using 
-- Links to example code in the [p5 web editor](https://editor.p5js.org) or other online shareable code editor
+### → Step 2: Screenshots or Relevant Documentation 🖼
+> Here's some helpful screenshots and/or documentation of the new feature 
+
+
+
+### → Step 3: Share an example of the issue 🦄
+> Here's some example code or a demonstration of  in https://github.com/ml5js/ml5-examples OR in the https://editor.p5js.org or codepen/jsfiddle/etc...
+
+
+
+
+
+
+**Other relevant information, if applicable**
+
+### → Describe your setup 🦄
+> Here's some helpful information about my setup...
+
+- **Web browser & version**:
+- **Operating System**:
+- **ml5 version you're using**:
+- **Any additional notes**
+
+
+
+<!--------------------------------------------
+🌈🌈🌈🌈🌈🌈🌈🌈🌈🌈🌈🌈🌈🌈🌈🌈🌈🌈🌈
+DEAR BELOVED ML5 COMMUNITY MEMBER. WELCOME.
+
+BEFORE SUBMITTING AN ISSUE PLEASE MAKE
+SURE TO SUBMIT THE RELEVANT INFORMATION
+TO THE SECTIONS LISTED BELOW. 
+HELP US HELP YOU BY PROVIDING ALL THE HELPFUL
+INFORMATION THAT WILL ALLOW THE ML5 COMMUNITY
+TO UNDERSTAND WHAT YOUR ISSUE SUBMISSION IS ABOUT.
+WE WILL PRIORITIZE WELL DOCUMENTED ISSUES.
+
+THANK YOU! MERCI! ABRIGADO! GRACIAS! DANKE!
+🌈🌈🌈🌈🌈🌈🌈🌈🌈🌈🌈🌈🌈🌈🌈🌈🌈🌈🌈
+---------------------------------------------->
+
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
@@ -1,31 +1,55 @@
-<!-- MANY MANY THANKS FOR YOUR CONTRIBUTION. ML5 ❤️S YOU! -->
-## → Submit changes to the relevant branch 🌲
+<!--------------------------------------------
+🌈DEAR BELOVED ML5 COMMUNITY MEMBER. WELCOME. 🌈
+---------------------------------------------->
 
-We have 2 branches you can submit to, **development** or **release**. You'd make us so happy 😊 if you submitted your pull request to the branch that is most relevant for your submission.
+Dear ml5 community, 
 
-- for pull requests related to **new features** 🆕 make sure to use the **development** branch
-- for pull requests related to bug 🐛fixes of the existing stable release, make sure your pull request  goes to the **release** branch.
+I'm making a Pull Request(PR). Please see the details below.
 
 
-## → Description 📝
+**A good PR 🌟**
 
-A clear and concise description of what the pull request is about. Let us know if you are:
+### → Step 1:  Which branch are you submitting to? 🌲
+> Development (for new features or updates), Release (for bug fixes), or ___________?
 
-- fixing a bug 🐛
-- adding an update 🛠
-- submitting a new feature 🆕 
 
-## → Screenshots 🖼
-(Any relevant screenshots, sketches, or helpful concept diagrams - these are helpful for our release notes and for getting people excited about your super cool feature and/or fix!)
 
+### → Step 2: Describe your Pull Request 📝
+> Fixing a Bug? Adding an Update? Submitting a New Feature? Does it introduce a breaking change?
 
-## → Relevant Example or Paired Pull Request to [ml5-examples](https://github.com/ml5js/ml5-examples) 🦄
 
-In order to help the ml5 team understand your pull request, we ask that you please submit an example to [ml5-examples](https://github.com/ml5js/ml5-examples) showcasing how your integrated feature works. You're also welcome to show how this works by providing code that can be easily run by others. 
 
-## → Relevant documentation 🌴
 
-Write a few notes about your pull request. Document any functionality that might be helpful for others who want to run and test your changes. If we don't know how to make use of your contribution, we won't be able t integrate it! 🙏
+
+**A great PR 🌟🌟**
+
+### → Step 3: Share a Relevant Example 🦄
+> Here's some example code or a link to another PR in https://github.com/ml5js/ml5-examples OR in the https://editor.p5js.org or codepen/jsfiddle/etc...
+
+
+
+
+**The best PR 🌟🌟🌟**
+
+### → Step 4: Screenshots or Relevant Documentation 🖼
+> Here's some helpful screenshots and/or documentation of the new feature 
+
+
+
+
+<!-- 
+
+BEFORE SUBMITTING YOUR PULL REQUEST PLEASE MAKE
+SURE TO SUBMIT THE RELEVANT INFORMATION
+TO THE SECTIONS LISTED BELOW. 
+HELP US HELP YOU BY PROVIDING ALL THE HELPFUL
+INFORMATION THAT WILL ALLOW THE ML5 COMMUNITY
+TO UNDERSTAND WHAT YOUR PR IS ABOUT.
+WE WILL PRIORITIZE WELL A DOCUMENTED PR.
+
+THANK YOU! MERCI! ABRIGADO! GRACIAS! DANKE!
+-->
+
 
 
 
diff --git a/.nojekyll b/.nojekyll
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
@@ -1,10 +1,60 @@
-# Contributor Covenant Code of Conduct
+# ml5.js Community Statement and Code of Conduct
 
-## Our Pledge
+## ml5.js Community Statement
+
+Adapted from the [p5.js community statement](http://p5js.org/community/).
+
+ml5.js is a community interested in exploring the creation of art and design with technology. 
+
+We are a community of, and in solidarity with, people from every gender identity and expression, sexual orientation, race, ethnicity, language, neuro-type, size, ability, class, religion, culture, subculture, political opinion, age, skill level, occupation, and background. We acknowledge that not everyone has the time, financial means, or capacity to actively participate, but we recognize and encourage involvement of all kinds. We facilitate and foster access and empowerment. We are all learners.
+
+We like these hashtags: #noCodeSnobs (because we value community over efficiency), #newKidLove (because we all started somewhere), #unassumeCore (because we don't assume knowledge), and #BlackLivesMatter (because of course).
+
+
+**In practice:**
+
+
+-  We are not code snobs. We do not assume knowledge or imply there are things that somebody should know.
+-  We insist on actively engaging with requests for feedback regardless of their complexity.
+-  We welcome newcomers and prioritize the education of others. We strive to approach all tasks with the enthusiasm of a newcomer. Because we believe that newcomers are just as valuable in this effort as experts.
+-  We consistently make the effort to actively recognize and validate multiple types of contributions.
+-  We are always willing to offer help or guidance.
+
+
+**In times of conflict:**
+
+-  We listen.
+-  We clearly communicate while acknowledging other's feelings.
+-  We admit when we're wrong, apologize, and accept responsibility for our actions.
+-  We are continuously seeking to improve ourselves and our community.
+-  We keep our community respectful and open.
+-  We make everyone feel heard.
+-  We are mindful and kind in our interactions.
+
+
+**In the future:**
+
+-  The future is now.
+
+
+### Contribute
+
+Our community is always looking for enthusiasts to help in all different ways. 
+
+-  **Develop**. [GitHub](https://github.com/ml5js/ml5-library) is the main place where code is collected, issues are documented, and discussions about code are had. Check out the [contributing documentation to get started](https://github.com/ml5js/ml5-library/blob/development/CONTRIBUTING.md) with developing the library.
+-  **Document**. Everyone loves documentation. Help is needed porting examples, and adding documentation, and creating tutorials.
+-  **Teach**. Teach a workshop, a class, a friend, a collaborator! Tag [@ml5js on Twitter](https://twitter.com/ml5js?lang=en) and we will do our best to share what you're doing.
+-  **Create**. ml5.js is looking for designers, artists, coders, programmers to bring your creative and amazing work to show and inspire other people. Submit your work to info@ml5js.org.
+-  **Donate**. ml5.js is a free and open source and made by artists. While ml5.js is not currently accepting donations, you can help support the development of ml5.js through a donation to other adjacent open source projects and endeavors such as the [Processing Foundation](https://processingfoundation.org/support).
+
+
+## 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, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
 
-## Our Standards
+### Our Standards
 
 Examples of behavior that contributes to creating a positive environment include:
 
@@ -22,23 +72,29 @@ Examples of unacceptable behavior by participants include:
 * 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
+### 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
+### 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
+### Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team:
+
+* @shiffman, Dan Shiffman - info@ml5js.org. 
+*  @AshleyJaneLewis, AshleyJaneLewis - hello@ml5js.org
+
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at info@ml5js.org. The project team will review and investigate all complaints, and will respond in a way that it deems 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.
+The project team will review and investigate all complaints and will respond in a way that it deems 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
+### Attribution
 
 This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]