From e7722243ddbd43db1bdc158dddb4913a5fdc24a9 Mon Sep 17 00:00:00 2001
From: Kevin Schaaf <kschaaf@google.com>
Date: Tue, 9 Jan 2018 11:05:45 -0800
Subject: [PATCH] Prefer jsBin since glitch.me requires signin to not be gc'ed.

---
 .github/ISSUE_TEMPLATE.md | 5 ++++-
 CONTRIBUTING.md           | 2 +-
 2 files changed, 5 insertions(+), 2 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md
index 86df276a3c..3aece94598 100644
--- a/.github/ISSUE_TEMPLATE.md
+++ b/.github/ISSUE_TEMPLATE.md
@@ -9,8 +9,11 @@ If you are asking a question rather than filing a bug, try one of these instead:
 <!-- Example: Error thrown when calling `appendChild` on Polymer element -->
 
 #### Live Demo
-<!-- Fork this glitch, or provide your own URL -->
+<!-- jsBin starting point (fork and edit) -->
+http://jsbin.com/luhaxab/1/edit
+<!-- glitch.me starting point (remix and edit -- must be logged in to persist!) -->
 https://glitch.com/edit/#!/polymer-repro?path=my-element.html:2:0
+<!-- ...or provide your own repro URL -->
 
 #### Steps to Reproduce
 <!--
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 2a2e8ca884..b6d381e2c9 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -42,7 +42,7 @@ If you find an issue, please do file it on the repository. The [Polymer/polymer
 
 For issues with elements the team maintains, please file directly on the element's repository. If you're not sure if a bug stems from the element or the library, air toward filing it on the element and we'll move the issue if necessary.
 
-Please file issues using the issue template provided, filling out as many fields as possible. We love examples for addressing issues - issues with a glitch.me, Plunkr, jsFiddle, or jsBin repro will be much easier for us to work on quickly. You can start with [this glitch](https://glitch.com/edit/#!/polymer-repro?path=my-element.html:2:0) which sets up the basics to demonstrate a Polymer element and serves the source via polyserve for automatic transpilation (note the glitch.me editing environment is not compatible with IE11, however the live view link of the running code should work).
+Please file issues using the issue template provided, filling out as many fields as possible. We love examples for addressing issues - issues with a jsBin, Plunkr, jsFiddle, or glitch.me repro will be much easier for us to work on quickly. You can start with [this jsbin](http://jsbin.com/luhaxab/edit) which sets up the basics to demonstrate a Polymer element.  If you need your repro to run in IE11, you can start from [this glitch](https://glitch.com/edit/#!/polymer-repro?path=my-element.html:2:0), which serves the source via polyserve for automatic transpilation, although you must sign up for a glitch.me account to ensure your code persists for more than 5 days (note the glitch.me _editing environment_ is not compatible with IE11, however the "live" view link of the running code should work).
 
 Occasionally we'll close issues if they appear stale or are too vague - please don't take this personally! Please feel free to re-open issues we've closed if there's something we've missed and they still need to be addressed.