[07:13:27] [PEP] Steditor opened issue #166: pointer cancel event with mouse buttons http://git.io/xykL [08:12:14] Since we already have tags in the repo from the Polymer days, I'd like to propose that our first release is 0.3.0. [08:12:23] It's the next highest minor version after the existing tags. [08:12:50] +1 i think anything else would be weird [08:13:04] and its pretty common first "official" release is NOT 0.1 [11:43:08] scott_gonzalez: what environments you want? [11:43:43] IE9+, latest for others [11:43:57] ok. you guys have a browserstack key? [11:44:01] yeah [11:44:37] Give me a minute to generate one for this project. [11:50:41] ok thanks [11:53:00] scott_gonzalez: jshint .jshintrc or in package.json? [11:53:14] or use eslint? [11:53:58] I'm not sure what the first question was, but jshint over eslint. [11:54:14] The future seems more collaborative with jshint right now. [11:55:19] oh, you can either create a .jshintrc or also add a jshintConfig property to package.json [11:55:38] Oh, definitely .jshintrc [11:55:45] I didn't know that jshint would look at package.json. [11:55:49] That's kinda crazy. [13:16:09] [PEP] csnover opened pull request #167: Update tests to use Intern (master...intern-tests) http://git.io/xHZG [16:43:13] arschmitz: do you have a valid browserstack username/key? [16:49:17] [PEP] scottgonzalez closed pull request #164: Use intern for testing2 (master...use-intern-for-testing2) http://git.io/A34V [17:59:31] snover: i do [17:59:58] snover: should add a readme section for this im sure ill be far from the last to just try and run grunt test [18:00:27] sure. i made a couple of updates to the PR, so `grunt test` doesn’t try to use browserstack directly any more [18:00:41] cool [18:00:53] `grunt ci` will use browserstack [18:01:11] snover: also have you ever tried using grunt-selenium-server [18:01:49] nice because then you can npm install it and start it with a grunt task [18:02:00] no, that’s what digdug is supposed to handle but nobody submitted a local selenium tunnel for it yet [18:02:18] that one might be useful in this case to reduce the friction [18:02:27] that was my thought [18:03:10] i did it on another project because a lot of new contributors and didn't want to have to have lots of setup instructions and there the tests need to go through selenium [18:03:41] what i’d *really* like is for someone to submit a digdug tunnel :) [18:04:42] snover: i was also thinking maybe add an index.html that just redirects to node_modules/intern/client.html?config=tests/intern [18:05:21] since that seems like a somewhat non obvious place to look [18:05:24] also sounds legit. [18:05:36] though maybe call it runTests.html [18:05:39] or something [18:05:50] yeah whatever works not picky on names [18:06:12] incase we ever what an actual index page [18:06:16] long term, that method of running the tests will go away since one of the ideas was to leverage functional testing so we get events from outside the sandbox [18:06:32] true [18:07:08] a simple redirect pages seems worth it until then though and just delete it after [18:08:24] since it wont change before the first release and we will likely get a flood of people then trying and testing anything to just reduce issues asking about how to run the tests i think is worth it [18:08:33] makes sense. [18:11:01] snover: i can do pr's for one or both of of those though [18:11:18] i got it. but i have an important question [18:11:25] what should the title of the redirect be [18:11:37] it’s these sorts of decisions that keep me up at night [18:11:41] lol [18:11:46] Holy moley, just hang on a gosh darn second... [18:13:35] this is not the test page your looking for... [18:15:48] ran it through translation party and i got our winner [18:15:49] “Just hang, hell the next day” [18:16:22] lol