[3:59 PM] <jacine> Hello everyone :D
[3:59 PM] <Druplicon> jacine: 1 day 2 hours ago <Bojhan> tell jacine Hey, could you take a look at http://drupal.org/node/1467914, we are trying to do major improvements to the module page. But we are running into the issue that it needs to be a table. However this breaks our design, because you cant have the same visual elements (e.g border around each row). Do you have any ideas?
[4:00 PM] <Druplicon> jacine: 4 hours 35 min ago <JohnAlbin> tell jacine What do you think of this? http://drupal.org/node/1360994#comment-5694314
[4:00 PM] <jacine> Transition: sure, no problem :)
[4:00 PM] Transition is now known as Transition|AFK
[4:00 PM] <cosmicdreams> heya jacine
[4:01 PM] <jacine> hey cosmicdreams!  Thanks so much for all the work you've been doing to help move patches along.
[4:01 PM] <jhood> hey jacine
[4:01 PM] <cosmicdreams> jacine: np
[4:01 PM] <jacine> jhood: hello!!! :)
[4:01 PM] <jacine> We've had a really, really good sprint.
[4:01 PM] <cosmicdreams> jacine: my pleasure.  We have 7 fixed issues in the sprint queue
[4:01 PM] <NiklasFiekas> cosmicdreams++
[4:01 PM] <jacine> Yes, and wasn't all in the last 2 weeks, but it's great to see.
[4:02 PM] <jacine> NiklasFiekas++
[4:02 PM] <jacine> NiklasFiekas: Didn't realize you were here, but definitely wanted to say thank you to you as well.  You've been rocking the Form API issues, which we sorely needed.
[4:02 PM] <jacine> and aspilicious of course :)
[4:03 PM] <NiklasFiekas> :)
[4:03 PM] <jacine> We were sorta held up for a long time because of issue queue thresholds.
[4:03 PM] <NiklasFiekas> jacine: how many criticals are aloud?
[4:03 PM] <jacine> Which really sucks to say the least, given that I don't believe any of the work we are doing falls under the "feature" category.
[4:03 PM] <jacine> thresholds?
[4:03 PM] <Druplicon> Max. 15 critical bugs + 15 critical tasks, as well as 100 majors (each). Above that threshold, new features and API changes will not be accepted. Read http://drupal.org/node/1201874 for more information.
[4:03 PM] <NiklasFiekas> *allowed
[4:04 PM] <jacine> NiklasFiekas: ^^ That's basically it.
[4:04 PM] <NiklasFiekas> we're two critical tasks over it :/
[4:04 PM] <jacine> Apparently we were under thresholds for a few days last week, but we're over again.
[4:04 PM] <jacine> Yeah.
[4:05 PM] <NiklasFiekas> aspilicious: so much for our plans to get url committed now ;)
[4:05 PM] <jacine> So… jhodgdon has been tasked with committing some of our patches, under the premise that they are "coding standards" and "cleanup" patches.
[4:05 PM] <jacine> I don
[4:05 PM] <NiklasFiekas> that one is a feature addition
[4:05 PM] <jacine> I don't know if I necessarily agree with that, but whatever helps getting things in, I'll take it.
[4:06 PM] <webchick> jacine: yeaj, I'm casting the net a bit wide so you can get some help. :)
[4:06 PM] <jacine> webchick: thank you :)
[4:06 PM] cosmicdreams runs tests locally for the comment module css cleanup
[4:06 PM] <webchick> jacine: the more serious ones like Form API, etc. still need to go through catch/Dries tho
[4:06 PM] <jacine> Obviously there has been a huge increase in activity as a result.
[4:07 PM] <webchick> trutfully, I think jennifer is the only one of the 4 of us who actually understands markup. :D
[4:07 PM] <jacine> LOL
[4:07 PM] <cosmicdreams> jacine: what would you like us to focus on for the next sprint?
[4:07 PM] <jacine> So… here's where we are currently at, ordered by status: http://drupal.org/project/issues/search/drupal?order=sid&sort=desc&status%5B0%5D=Open&version%5B0%5D=8.x&issue_tags_op=and&issue_tags=html5%2C+sprint&text=&assigned=&submitted=&participant=
[4:08 PM] <jacine> There's still some stuff in there, but we need to add some more.
[4:08 PM] <webchick> yay greeeeen
[4:09 PM] jacine wishes she could search for tagged HTML5 and NOT sprint.
[4:09 PM] webchick had a patch for that at one point
[4:09 PM] <jacine> of course you did ;) haha!
[4:10 PM] <aspilicious> Ok I'm here :)
[4:10 PM] <jacine> Here's one: http://drupal.org/node/1174628
[4:10 PM] <Druplicon> http://drupal.org/node/1174628 => Add new HTML5 FAPI element: search => Drupal core, forms system, normal, needs work, 22 comments, 1 IRC mention
[4:10 PM] <jacine> hey aspilicious :)
[4:11 PM] <aspilicious> jacine, can you remove the green issues from the lsprint?
[4:11 PM] <jacine> Apparently that one is waiting for CSS updates, so anyone can help
[4:11 PM] <aspilicious> the dark green ones ;)
[4:11 PM] <cosmicdreams> jacine can you please put the following issues on the next sprint: http://drupal.org/node/1217054 http://drupal.org/node/1216976 http://drupal.org/node/1217038
[4:11 PM] <jacine> anyone can do that :)
[4:11 PM] <Druplicon> http://drupal.org/node/1217054 => Clean up the CSS for User module => Drupal core, user.module, normal, needs work, 25 comments, 1 IRC mention
[4:11 PM] <Druplicon> http://drupal.org/node/1216976 => Clean up the CSS for Comment module => Drupal core, CSS, normal, reviewed & tested by the community, 97 comments, 17 IRC mentions
[4:11 PM] <Druplicon> http://drupal.org/node/1217038 => Clean up the CSS for the Shortcut module => Drupal core, shortcut.module, normal, needs work, 18 comments, 2 IRC mentions
[4:11 PM] <aspilicious> jacine, search and css is a nightmare
[4:11 PM] <webchick> Oooh.
[4:11 PM] <webchick> http://drupal.org/node/582402
[4:11 PM] <Druplicon> http://drupal.org/node/582402 => Allow to filter by issues NOT having a certain issue tag => Drupal.org webmasters, Site organization, normal, closed (fixed), 3 comments, 4 IRC mentions
[4:11 PM] <webchick> says it was fixed.
[4:11 PM] <jacine> webchick++
[4:11 PM] webchick tries
[4:11 PM] <jacine> wait what???
[4:12 PM] <jacine> well, yeah NOT, but not NOT = sprint + IS =html5, right?
[4:12 PM] <webchick> Oh, ignore me. :( that was for 'not' to begin with
[4:12 PM] <jacine> oh ok :)
[4:12 PM] webchick stfus until she has smething useful to say :D
[4:12 PM] <NiklasFiekas> oh yes ... i have no idea while the html5 search element must be so different from other input elements and doesn't accept the most basic css
[4:12 PM] NiklasFiekas cries
[4:13 PM] <jacine> NiklasFiekas: I haven't fully read through it lately, but if you cry I cry. :)  Maybe you should update the issue with your concerns?
[4:13 PM] <Schnitzel> NiklasFiekas: a new input file field?
[4:14 PM] <NiklasFiekas> Schnitzel: yeah ... but here i can't find a reason (like security) why styling should be disallowed
[4:14 PM] <NiklasFiekas> jacine: i linked http://css-tricks.com/webkit-html5-search-inputs/ in the issue. it shows that we can't do a great deal of the styling we usually do in our core themes
[4:14 PM] <cosmicdreams> jacine: should we focus more on the remaining html 5 field issues rather than the CSS cleanups
[4:15 PM] <jacine> NiklasFiekas: What is the problem in the issue.  I'd rather no CSS be provided by core for these TBH.
[4:15 PM] <jacine> cosmicdreams: you just pasted in 3 CSS issues...?
[4:15 PM] <NiklasFiekas> jacine: well ... the screenshot looks stupid: http://drupal.org/node/1174628#comment-5623954
[4:15 PM] <Druplicon> http://drupal.org/node/1174628 => Add new HTML5 FAPI element: search => Drupal core, forms system, normal, needs work, 22 comments, 2 IRC mentions
[4:15 PM] <cosmicdreams> yes
[4:16 PM] <jacine> NiklasFiekas: Oh, so it's just bartik that needs to be fixed…?
[4:16 PM] <jacine> NiklasFiekas: That's easy.
[4:16 PM] <aspilicious> jacine, every browser has his own set of markup
[4:16 PM] <aspilicious> jacine, for the search element
[4:16 PM] <aspilicious> and webkit adds a cross and other crap
[4:16 PM] <NiklasFiekas> jacine: yes, it's bartik and seven and the other one. if that's really easy that's awesome
[4:16 PM] <jacine> aspilicious: so?
[4:17 PM] <aspilicious> jacine, it's rly rly hard to get rid of it
[4:17 PM] <jacine> aspilicious: we don't have to make it look the same in all browsers.
[4:17 PM] <jacine> I don't think we should for form elements… TBH.
[4:17 PM] <aspilicious> jacine, hmm true... so... just adjust the height?
[4:17 PM] <jacine> That input clearly has no styling because of the CSS Bartik used in the first place
[4:18 PM] <jacine> probably targets .form-text or whatever.
[4:18 PM] <NiklasFiekas> jacine: yep. but you can't even use padding, line-height, font-family and stuff that we usually do
[4:18 PM] Crell proposes we just not support web browsers.  That would make it very easy.
[4:18 PM] <jacine> Are you sure?
[4:18 PM] <jacine> I don't think that is the case.
[4:18 PM] <NiklasFiekas> jacine: pretty sure
[4:18 PM] <jacine> NiklasFiekas: Alright, I will assign it to myself and see what I can do this sprint.
[4:19 PM] davereid finally gets active in the meeting
[4:19 PM] <NiklasFiekas> jacine: see "styling limitations" on http://css-tricks.com/webkit-html5-search-inputs/
[4:19 PM] <NiklasFiekas> jacine++
[4:19 PM] <jacine> hey davereid :)
[4:19 PM] <jacine> Alright, done.
[4:20 PM] <jacine> Alright, I tagged this one: http://drupal.org/node/1216976#comment-5697388
[4:20 PM] <Druplicon> http://drupal.org/node/1216976 => Clean up the CSS for Comment module => Drupal core, CSS, normal, reviewed & tested by the community, 97 comments, 18 IRC mentions
[4:21 PM] <cosmicdreams> jacine: testing that one as we speak
[4:21 PM] <jacine> cosmicdreams: nothing to test, it's just waiting for the bot.
[4:21 PM] <cosmicdreams> All green with 50% tests one
[4:21 PM] <cosmicdreams> jacine: no i'm actually doing the until tests locally, we'll see who wins this race.
[4:21 PM] <jacine> cosmicdreams: haha. ok :)
[4:22 PM] <NiklasFiekas> cosmicdreams: you're running the whole testsuite locally?
[4:22 PM] <cosmicdreams> NiklasFiekas: NO no no
[4:22 PM] davereid double-confirms the url input element is ready to go
[4:22 PM] <cosmicdreams> NiklasFiekas: just the tests for comments
[4:22 PM] <jacine> davereid++
[4:22 PM] <NiklasFiekas> cosmicdreams: oh ... :) you shocked me there
[4:22 PM] <davereid> NiklasFiekas++
[4:22 PM] <davereid> ericduran++
[4:22 PM] <aspilicious> davereid, the number patch is also rdy
[4:22 PM] <jacine> Tagged this one as well: http://drupal.org/node/1217038#comment-5697398
[4:22 PM] <Druplicon> http://drupal.org/node/1217038 => Clean up the CSS for the Shortcut module => Drupal core, shortcut.module, normal, needs work, 18 comments, 3 IRC mentions
[4:22 PM] <aspilicious> whoops not
[4:22 PM] <ericduran> ls Oh is the meeting
[4:23 PM] <webchick> Question. Do we have a meta issue somewhere to start using these newfangeldy fields in core?
[4:23 PM] <ericduran> lol we shoudl get reminders
[4:23 PM] <NiklasFiekas> aspilicious: ugg ... number tests just came back red
[4:23 PM] NiklasFiekas looks
[4:23 PM] <aspilicious> NiklasFiekas, wtf happened with your patches
[4:23 PM] <ericduran> webchick: yea, the original issue
[4:23 PM] <aspilicious> it's a bot issue
[4:23 PM] <aspilicious> or patch issue
[4:23 PM] <NiklasFiekas> aspilicious: oh ... yeah
[4:23 PM] <ericduran> webchick: the original issue was changes to meta-hmtl5-forms-blah
[4:23 PM] <jacine> webchick, ericduran: A table for those should also be added here: http://drupal.org/node/1183606
[4:23 PM] <Druplicon> http://drupal.org/node/1183606 => Implement Form API support for new HTML5 elements => 0 comments, 14 IRC mentions
[4:23 PM] <NiklasFiekas> aspilicious: no ... logs say it didn't manage to clone drupal core
[4:23 PM] <jacine> Anyone want to take that on?
[4:24 PM] <webchick> jacine: yeah, THAT would be super helpful.
[4:24 PM] <cosmicdreams> jacine: so are the localStorage issues moot now.  Now that there's no really performant way to implement localStorage?
[4:24 PM] <davereid> jacine: you mean like field formatters?
[4:24 PM] <aspilicious> jacine, well I can make a table I guess
[4:24 PM] <davereid> err widgets?
[4:24 PM] <jacine> aspilicious++
[4:24 PM] <webchick> aspilicious++
[4:24 PM] <aspilicious> HTML5 fields?
[4:25 PM] <davereid> webchick: I'm not sure what you mean. We've been converting core to use them in each issue?
[4:25 PM] <ericduran> NiklasFiekas: that's a bot issue
[4:25 PM] <jacine> cosmicdreams: I think that issue needs a summary.
[4:25 PM] <webchick> davereid: OH! I should actually read patches and not titles. AWESOME then!
[4:25 PM] <ericduran> davereid: I assumed webchick means Field API
[4:26 PM] <NiklasFiekas> ericduran: yep. the bot also tried three times. poor bot :( ... requested retesting
[4:26 PM] <davereid> Yeah, we should probably add new text field formatters for e-mail, URL, etc.
[4:26 PM] <davereid> WIDGETS
[4:26 PM] <webchick> yeah, field API, other things like the authored by date, "number of pots to show on front page" etc.
[4:26 PM] <davereid> not formatters
[4:26 PM] <ericduran> webchick: davereid jacine : We do need field api widgets
[4:26 PM] <ericduran> yea
[4:26 PM] <jacine> ericduran: I have no idea.
[4:26 PM] <davereid> Grrr, we really needed a 'plain text' field type in core...
[4:27 PM] <webchick> Anyway, definitely not critical. It's not like putting something into core and not using it didn't hapen in D7 *cough* jQuery UI ;)
[4:27 PM] <jacine> davereid: hell yes.
[4:27 PM] <webchick> But might be a good source of some novice tasks
[4:27 PM] <jacine> webchick: ugh, tell me about it. I hate that.
[4:27 PM] <jacine> yet it loads everywhere.
[4:27 PM] <NiklasFiekas> davereid: like http://drupal.org/project/link and http://drupal.org/project/email into core but with our new html5 form element types?
[4:27 PM] <webchick> hm. really? that's odd. it definitely shoudln't be iunless something asks for it.
[4:28 PM] <ericduran> NiklasFiekas: not as complex ;-)
[4:28 PM] <davereid> NiklasFiekas: I'm thinking more like new widgets for the 'text' field type
[4:28 PM] <ericduran> NiklasFiekas: just the widgets for simple textfield, not of the other crazy things they do
[4:28 PM] <jacine> webchick: I'm pretty sure it does. I ended up removing it in a base theme. I should double check that I guess.
[4:28 PM] <NiklasFiekas> ericduran: makes sense
[4:28 PM] <cosmicdreams> jacine: can you put this onto the next sprint? http://drupal.org/node/1372374
[4:28 PM] <Druplicon> http://drupal.org/node/1372374 => Adapt states.js to new required html5 attribute => Drupal core, javascript, normal, needs work, 3 comments, 1 IRC mention
[4:29 PM] <jacine> cosmicdreams: I've actually asked for help on that one from effulgentsia. So, yes, that is a good one.
[4:29 PM] <ericduran> jacine: cosmicdreams I think we should skip that one
[4:30 PM] <jacine> ericduran: I don't know if that is the proper fix, but we need to get #required back in, so we need to figure it out.  Why do you think we should skip it?
[4:30 PM] <ericduran> jacine: 1st we should get the required attribute fix, so we know how we're using it
[4:30 PM] <ericduran> jacine: yea, once we have that fixed than we can tackle this issue
[4:30 PM] <jacine> ericduran: But isn't that the only "solution" that has been proposed?
[4:31 PM] <jacine> I'm thinking we should either rule it out or accept it.
[4:31 PM] <ericduran> jacine: we need to fix http://drupal.org/node/1174938 before doing http://drupal.org/node/1372374
[4:31 PM] <Druplicon> http://drupal.org/node/1174938 => Natively support the HTML5 #required FAPI property => Drupal core, forms system, normal, needs review, 77 comments, 10 IRC mentions
[4:31 PM] <Druplicon> http://drupal.org/node/1372374 => Adapt states.js to new required html5 attribute => Drupal core, javascript, normal, needs work, 3 comments, 2 IRC mentions
[4:31 PM] <ericduran> jacine: jacine so the #required should be tag for the sprint
[4:31 PM] <ericduran> sorry, I'm doing like 20 things at once
[4:31 PM] <jacine> ericduran: So you are saying that the states issue is not a solution for that?
[4:32 PM] jacine thought it was.
[4:33 PM] <jacine> I tagged it: http://drupal.org/node/1174938#comment-5697442
[4:33 PM] <Druplicon> http://drupal.org/node/1174938 => Natively support the HTML5 #required FAPI property => Drupal core, forms system, normal, needs review, 77 comments, 11 IRC mentions
[4:33 PM] <jacine> I still don't get it though.
[4:33 PM] <ericduran> jacine: I dodn't remember but I don't think so, I'm pretty sure David_Rothstein had the right approach to fixing it
[4:33 PM] <ericduran> in #65
[4:34 PM] Transition|AFK is now known as Transition
[4:34 PM] <Transition> I'm back! What'd I miss?
[4:34 PM] <jacine> ericduran: Ok, well I've asked effulgentsia to look into it anyway, and tagged it so hopefully we'll see some progress.
[4:34 PM] <aspilicious> jacine, what kinda stuff do you want in your table
[4:34 PM] <aspilicious> url, email, number, range, ??
[4:34 PM] <Transition> Also, I need to figure out what's going on with my Calendar syncing on my iPhone! It's been acting funny!
[4:34 PM] <aspilicious> tel
[4:34 PM] <ericduran> jacine: Yea, I'm also not sure why there's two issues
[4:35 PM] Transition goes to read the chat log thus far...
[4:35 PM] <jacine> we'll figure it out.
[4:35 PM] <effulgentsia> jacine: which one?
[4:36 PM] <jacine> effulgentsia: oh hey! This one: http://drupal.org/node/1174938
[4:36 PM] <Druplicon> http://drupal.org/node/1174938 => Natively support the HTML5 #required FAPI property => Drupal core, forms system, normal, needs review, 77 comments, 12 IRC mentions
[4:36 PM] davereid is reading that issue too
[4:36 PM] <jacine> trying to remember that php tag.
[4:37 PM] <effulgentsia> jacine: i need to be away for the next couple hours, but i'll check-in when i'm back to see where ericduran or davereid have gotten with it.
[4:37 PM] <cosmicdreams> jacine: not to change the subject but this one sounds like another good one to add to the sprint: http://drupal.org/node/1174892
[4:37 PM] <Druplicon> http://drupal.org/node/1174892 => Rich media display with <video> and <audio> HTML5 elements. => Drupal core, file.module, normal, needs review, 23 comments, 6 IRC mentions
[4:37 PM] <jacine> effulgentsia++
[4:37 PM] <jacine> thank you :)
[4:37 PM] <aspilicious> jacine, http://drupal.org/node/1183606
[4:37 PM] <Druplicon> http://drupal.org/node/1183606 => Implement Form API support for new HTML5 elements => 0 comments, 15 IRC mentions
[4:37 PM] <jacine> cosmicdreams: oh yes, that is a good one. Thanks :)
[4:38 PM] <aspilicious> jacine, oh and we can( do local storage at the moment
[4:38 PM] <jacine> aspilicious: Thanks, there are existing issues already somewhere.
[4:38 PM] <jacine> only a couple I think.
[4:38 PM] <aspilicious> we should remove it from the sprint and mark it postponed
[4:38 PM] <cosmicdreams> agree
[4:38 PM] <effulgentsia> davereid: http://drupal.org/node/1174892 looks like a good one for you to pay attention to as well :)
[4:38 PM] <Druplicon> http://drupal.org/node/1174892 => Rich media display with <video> and <audio> HTML5 elements. => Drupal core, file.module, normal, needs review, 23 comments, 7 IRC mentions
[4:38 PM] <jacine> aspilicious: Why can't we do local storage?  We can mark it postponed but we need to state why.
[4:38 PM] <aspilicious> there is lots of controverse about the spec (its bad for the performance at current state)
[4:38 PM] <davereid> effulgentsia: yeah I've been meaning to review and submit and alternative :)
[4:39 PM] <jacine> Ok, so add that with some references and postpone it :o)
[4:39 PM] <jacine> (to a comment)
[4:40 PM] <aspilicious> html5 sprint?
[4:40 PM] <Druplicon> html5 sprint is http://bit.ly/html5-sprint
[4:40 PM] <cosmicdreams> jacine: is Dashboard really going away?  And is there an issue for it's removal?
[4:40 PM] <jacine> aspilicious: I'm going to remove the sprint tags from the fixed ones right now
[4:40 PM] <Crell> aspilicious: I think some of those are overblown.
[4:40 PM] <jacine> cosmicdreams: I sure hope so.
[4:40 PM] <Crell> If you're using localStorage for big files, there may be performance issues.
[4:40 PM] <Crell> If you're storing a 4 byte string, um, don't worry.
[4:40 PM] <jacine> cosmicdreams: yes, there is an issue. don't have the # handy right now
[4:41 PM] <Crell> Also, there's still sessionStorage which is all in-memory, so there's no issue.
[4:41 PM] <aspilicious> Crell, performance hogs? I don't want drupal to eat my local storage on every startup of chrome
[4:41 PM] <jacine> Crell: thanks :)
[4:41 PM] <aspilicious> Crell, ok I'll leave it open
[4:41 PM] <Crell> aspilicious: Are you following the comments on that article from yesterday? :-)
[4:41 PM] Crell commented a few times and has been getting the updates.
[4:41 PM] <aspilicious> Crell, did yesterday
[4:42 PM] <cosmicdreams> jacine: It would be nice to have this one knocked out during the sprint: http://drupal.org/node/405360
[4:42 PM] <Druplicon> http://drupal.org/node/405360 => Use aria-describedby to link form elements with form element descriptions => Drupal core, markup, normal, needs work, 61 comments, 1 IRC mention
[4:42 PM] <Crell> AFAIK there are no benchmarks that says LS IS slow, just architectural commentary that it is designed slower than it should be.
[4:42 PM] <Crell> Vis, it's not a panacea.
[4:42 PM] <Crell> But that doesn't mean we shouldn't touch it.
[4:42 PM] <jacine> cosmicdreams: I hate that issue.
[4:42 PM] <cosmicdreams> jacine: Oh?
[4:42 PM] <jacine> cosmicdreams: Let's see where we are at once I clean out the fixed issues, give me like 3 minutes.
[4:42 PM] <cosmicdreams> jacine: np
[4:43 PM] <jacine> I think this one needs a change notice: http://drupal.org/node/1174620#comment-5697500
[4:44 PM] <Druplicon> http://drupal.org/node/1174620 => Change notice: Add new HTML5 FAPI element: email => Drupal core, forms system, normal, active, 77 comments, 10 IRC mentions
[4:44 PM] <aspilicious> davereid, you got an issue with all these elements
[4:44 PM] <davereid> jacine: "Note I added 'email' to the change notification at http://drupal.org/node/1315186"
[4:44 PM] <Druplicon> http://drupal.org/node/1315186 => HTML5 support for form elements => 0 comments, 4 IRC mentions
[4:45 PM] <jacine> davereid: OH
[4:45 PM] <jacine> davereid: you're on top of shit, eh? :D
[4:45 PM] <jacine> davereid++
[4:46 PM] davereid can at least be on top of organizing the input elements and their change notifications
[4:47 PM] <aspilicious> those centralized changenotifications are so good
[4:47 PM] <jacine> yeah :) they are.
[4:47 PM] Crell needs to write a few still...
[4:48 PM] aspilicious forces Crell to write one each night before he goes to bed :p
[4:48 PM] <jacine> html5 sprint?
[4:48 PM] <Druplicon> html5 sprint is http://bit.ly/html5-sprint
[4:48 PM] <Crell> bah!
[4:48 PM] <jacine> Alright, done.
[4:48 PM] <jacine> Personally, I think that's enough for this sprint.
[4:49 PM] <cosmicdreams> cool
[4:49 PM] <aspilicious> jacine, more than enough
[4:49 PM] <jacine> yeah
[4:49 PM] <jacine> alright…. so unless anyone has anything else??
[4:49 PM] <cosmicdreams> so can we talk about http://drupal.org/node/1090592 ?
[4:49 PM] <Druplicon> http://drupal.org/node/1090592 => [meta] Use HTML5 data-* attributes instead of #ID selectors in Drupal.settings => Drupal core, javascript, normal, active, 13 comments, 5 IRC mentions
[4:49 PM] <jacine> cosmicdreams: sure
[4:49 PM] <aspilicious> I would like to get autocomplete in but thats to advanced for me
[4:49 PM] <Crell> Ooo...
[4:50 PM] <Crell> aspilicious: What about autocomplete?
[4:50 PM] <cosmicdreams> jacine: I wrote a few user stories and would like some feedback on the sanity of those
[4:50 PM] <aspilicious> Crell, http://drupal.org/node/1309394
[4:50 PM] <Druplicon> http://drupal.org/node/1309394 => Process #autocomplete_path for all form elements; remove custom/duplicated code from theme_textfield() => Drupal core, forms system, major, needs review, 15 comments, 5 IRC mentions
[4:50 PM] jacine reads #1090592-12
[4:50 PM] <Transition> My cat walked across the keyboard and says, "loo" to everyone. :-/
[4:51 PM] <Crell> Hi cat!
[4:51 PM] <cosmicdreams> lol loo-Cat
[4:51 PM] jhood is now known as jhood|away
[4:52 PM] <Transition> Ok, I'm FINALLY caught up on the chat log...
[4:52 PM] <Transition> |-)
[4:52 PM] <cosmicdreams> Transition: can you read http://drupal.org/node/1090592#comment-5663962 and give feedback?
[4:52 PM] <jacine> cosmicdreams: So those user stories are great, but don't those all need proper widgets first before we can talk about implementing them with data attributes?  Or am I wrong?
[4:52 PM] <Druplicon> http://drupal.org/node/1090592 => [meta] Use HTML5 data-* attributes instead of #ID selectors in Drupal.settings => Drupal core, javascript, normal, active, 13 comments, 6 IRC mentions
[4:53 PM] <Transition> cosmicdreams: I'm on it!
[4:53 PM] <cosmicdreams> well, I'm not sure, in my mind we just need to implement a state-storage machanism first, then we can widget-ize them.
[4:54 PM] <jacine> cosmicdreams: alright, well I am not the best person to give feedback on this then. :)
[4:54 PM] <cosmicdreams> jacine: or rather, those are seperate tasks
[4:54 PM] <cosmicdreams> seen linclarke
[4:54 PM] <Druplicon> Sorry, I haven't seen linclarke.
[4:54 PM] <jacine> cosmicdreams: I think that those separate tasks should exist as issues.
[4:54 PM] <cosmicdreams> seen linclark
[4:54 PM] <Druplicon> linclark was last seen in #drupal-contribute 1 hour 19 min ago saying 'RobinMonks: I think m_sonnabaum meant with the infrastructure team'.
[4:54 PM] <ericduran> cosmicdreams: Idk those might be too much
[4:55 PM] <aspilicious> I'll do the sortcut css in an hour
[4:55 PM] <cosmicdreams> ericduran: Am I on the right path?
[4:55 PM] aspilicious watching video tag video now
[4:55 PM] <ericduran> I'm a little undecided with the whole data-* attribute, I like them. But I'm not sure if or why drupal should try to wrap that in anything
[4:55 PM] <ericduran> they work pretty good alone
[4:55 PM] <cosmicdreams> ericduran: jacine: Crell: is this even a proper use of data- attributes?
[4:56 PM] <jacine> ericduran: yeah… I thought that issue was supposed to be more about where to use them.
[4:56 PM] <cosmicdreams> ericduran: data- attributes might come in handy when implementing superblock layouts
[4:56 PM] <Crell> cosmicdreams: Interesting.  How so?
[4:56 PM] <ericduran> cosmicdreams: yea, but they're each pertaining to a specific implementation, not really a generic use
[4:56 PM] <Crell> I agree that data- cannot completely replace drupal.settings, but it can probably replace it in many places.
[4:57 PM] <ericduran> I would like to see the whole data-* attribute kinda become a best practice sort of speak
[4:57 PM] <ericduran> but not really any wrappers around it
[4:57 PM] <Crell> ericduran: Right.
[4:57 PM] <jacine> yeah
[4:57 PM] <cosmicdreams> well you can have an "active-store" that holds the ids of widgets you drag and drop into a region.  Then when you save, you can use the data- attributes to push the active state into the database.
[4:57 PM] <cosmicdreams> Crell: ^
[4:57 PM] <Crell> So rather than finding all elements of class fancyeffect, then looking up Drupal.settings.fancyeffect[id-of-the-element].blah, we can just find anything of class fancyeffect and check that elements data-blah.
[4:57 PM] <jacine> So, that issue should really be a meta issue that links to a bunch of places where it makes sense to implement data attributes, no?
[4:58 PM] <Crell> jacine: Yes.
[4:58 PM] <ericduran> jacine: yep
[4:58 PM] <jacine> good :)
[4:58 PM] <Crell> Including what cosmicdreams just suggested.  I don't know if that's a good use or not, but it's worth a shot. :-)
[4:58 PM] <mortendk> oi oi … only 3 weeks late ;)
[4:58 PM] <jacine> hey mortendk :)
[4:58 PM] <jacine> cosmicdreams: you alright with that?
[4:58 PM] <cosmicdreams> mortendk: 'sup dude
[4:58 PM] <mortendk> jacine: hey i just had a frontendunited to plan + drupalcon stuff :)
[4:59 PM] <jacine> mortendk++
[4:59 PM] cosmicdreams reads the backscroll to find out what Jacine is asking
[4:59 PM] <jacine> mortendk: the contextual patch went in :)
[4:59 PM] <jacine> cosmicdreams: "So, that issue should really be a meta issue that links to a bunch of places where it makes sense to implement data attributes, no?"
[4:59 PM] <cosmicdreams> jacine: totally
[4:59 PM] <jacine> cosmicdreams: great :)
[5:00 PM] <jacine> Anyone have anything else to discuss?
[5:00 PM] <cosmicdreams> jacine: Did I just volunteer to modify it's description?
[5:00 PM] <jacine> cosmicdreams: Haha, I don't know, did you?
[5:00 PM] <Crell> You did.
[5:00 PM] <webchick> cosmicdreams: the answer is always YES :D
[5:00 PM] <cosmicdreams> jacine: yes, yes I did.....LOL
[5:00 PM] <jacine> :D
[5:00 PM] <jacine> cosmicdreams++
[5:00 PM] <Transition> cosmicdreams: I agree with jacine and Crell on the "data-* should be a linked meta-issue" issue.
[5:00 PM] <mortendk> jacine: wooohooo
[5:01 PM] <jacine> ok, great… so let's create specific issues where it makes sense to do it.
[5:01 PM] mortendk is planning a frontend united meetup on the first day at drupalcon before the opening party 
[5:01 PM] <ericduran> so whens the next sprint?
[5:01 PM] <ericduran> oh is the next sprint live?
[5:01 PM] <ericduran> lol
[5:01 PM] <jacine> Drupalcon!
[5:01 PM] Transition won't be at druplicon. :-(
[5:01 PM] <webchick> Transition: :(
[5:01 PM] <Crell> Sadness.
[5:01 PM] <jacine> aw :(
[5:01 PM] <Transition> Indeed!
[5:01 PM] <fubhy> mortendk can i come even if i wasnt at frontendunited? :P
[5:02 PM] <mortendk> well mark you calendars first day after last session frontend united meetup
[5:02 PM] <Transition> But I'll by trying to 'watch' and follow on IRC and Twitter! :-)
[5:02 PM] <jacine> We'll make sure to create an event node for the next sprint that says it's going on at Drupalcon on Friday.
[5:02 PM] <cosmicdreams> Wow, I just realized that data- would really fix the markup madness in dashboard and overlay
[5:02 PM] <mortendk> fubhy:  oofcourse its just a way to get the frontend ppl together :)
[5:02 PM] <Transition> jacine: I've got a question!
[5:02 PM] <jacine> Transition: what's up?
[5:02 PM] <cosmicdreams> All of that javascript is hooked into the ids.  That's what makes it so difficult to get rid of all of those divs
[5:03 PM] <jacine> cosmicdreams: yeah, for sure.
[5:03 PM] <NiklasFiekas1> (ugg ... disconnect)
[5:03 PM] <jacine> ;)
[5:03 PM] <Transition> jacine: I'm helping with the Mobile Initiaitve's Mobile Guide. Specifically, Feature/Browser/Device detection.
[5:03 PM] <Crell> cosmicdreams: The sooner we start...
[5:03 PM] <cosmicdreams> Crell: I've already started working on both Dashbaord and Overlay
[5:04 PM] <Transition> jacine: So, it seems there's JavaScript to detect and also HTML5.
[5:04 PM] <cosmicdreams> I'll get going on those later this week.
[5:04 PM] <cosmicdreams> jacine: can we put the cleanups for overlay and dashboard on the sprint (pretty please)
[5:04 PM] <Transition> jacine: Is there anything we can/should do to make HTML5 feature detection easier or better in Drupal? I may not be phrasing that correctly, as I'm kind of new to the subject.
[5:05 PM] <jacine> cosmicdreams: They don't need to be in a sprint. You can still work on them. :)
[5:05 PM] <Transition> jacine: I'm trying to "Document My Way to Understanding" like webchick suggested, LONG ago. :-)
[5:05 PM] <webchick> Yay! :D
[5:05 PM] <cosmicdreams> jacine: true
[5:05 PM] <webchick> Transition++
[5:05 PM] <jacine> Transition: There's a whole long issue on this here: http://drupal.org/node/1252178 Have you read it?
[5:05 PM] <Druplicon> http://drupal.org/node/1252178 => Add a polyfill loading solution => Drupal core, javascript, normal, needs work, 28 comments, 10 IRC mentions
[5:05 PM] <Transition> webchick: the problem is, I've got VERY little understanding to document! :-P That's why I'm working on it. :-)
[5:05 PM] <jacine> It could totally use an issue summary.
[5:05 PM] jhood|away is now known as jhood
[5:06 PM] <Transition> jacine: I'm looking at it now.
[5:06 PM] <Crell> Aren't there off-site resources we can link to for why feature detection > device detection?
[5:06 PM] <Crell> It's not like it's a Drupal-specific best practice...
[5:06 PM] NiklasFiekas1 is now known as NiklasFiekas
[5:06 PM] <Transition> jacine: I could probably DO an Issue Summary! :-)
[5:06 PM] <jacine> Yeah, I'm sure there are…. I can't remember but there is a really good site.
[5:06 PM] <jacine> Transition++
[5:07 PM] <webchick> Transition: hey when I started with Drupal there were no docs on how to use CVS beyond super-advanced workflow crap. :) so that's where I started was trying things, breaking them, asking questions, and documenting every step. :)
[5:07 PM] mortendk is just off a bit to plan drinking binches at drupalcon 
[5:07 PM] <jacine> This is a good one: http://html5please.com/
[5:07 PM] <mortendk> jacine: why u not coming to frontendunited  were gonna sprint n stuff
[5:07 PM] <webchick> jacine: nice!
[5:07 PM] <jacine> mortendk: because no one is paying for me to go, and I am not rich :)
[5:08 PM] <mortendk> jacine: damn yeah good answer
[5:08 PM] <jacine> haha :D
[5:08 PM] Transition is ALSO not rich
[5:08 PM] <mortendk> we need more sponsors next time (and thats allready in the planning)
[5:08 PM] Crell is not rich, just works for a company that believes in investing in Drupal. :-)
[5:08 PM] <jacine> mortendk: I'm also going to Aruba the week before.
[5:09 PM] <cosmicdreams> my company looked to sponsor this year but values paying to send our nerds to the conference more.
[5:09 PM] <Transition> Hmm…I don't think the current 2 sentence issue summary for http://drupal.org/node/1252178 is cutting it… :-)
[5:09 PM] <Druplicon> http://drupal.org/node/1252178 => Add a polyfill loading solution => Drupal core, javascript, normal, needs work, 28 comments, 11 IRC mentions
[5:09 PM] <jacine> Transition: haha :)
[5:10 PM] <Transition> Ok, I'll add a comment that I'm going to update the Issue Summary for
[5:10 PM] <Transition> 1252178
[5:10 PM] <Druplicon> http://drupal.org/node/1252178 => Add a polyfill loading solution => Drupal core, javascript, normal, needs work, 28 comments, 12 IRC mentions
[5:10 PM] <cosmicdreams> jacine: how much would it cost to send you to frontendunited?
[5:10 PM] Transition can't type!
[5:10 PM] <jacine> Last time I went to Amsterdam is was ~$4-5k
[5:10 PM] <cosmicdreams> jacine: and can we start to pool donations so that you can make it?
[5:11 PM] <jacine> I have to also pay for Drupalcon, minus the conference ticket, and whatever else I end up doing this year, and I am only working 20-25 billable hours a week so that I can do this initiative so I am also not getting paid as much as I used it.
[5:11 PM] <Transition> webchick: earlier you mentioned something that would be a good source of novice issues. What was that?
[5:12 PM] <jacine> It's not just the expenses to get there, food, drink and everything else. It adds up.
[5:12 PM] <cosmicdreams> jacine: don't know if you will see what I see on this: http://www.hipmunk.com/?campaign=Brand&keyword=hipmunk&gclid=CNrRoJSl064CFSgCQAoddnFlcw#!NYC.AMS,Apr20.Apr23
[5:13 PM] <jacine> Yep, I see it. :)
[5:13 PM] <cosmicdreams> not crazy expensive.  but up there
[5:13 PM] <webchick> Transition: Oh, it was to start making use of these HTML5 form api elements in core.
[5:13 PM] <jacine> But, like I said, I'm also traveling the week before.
[5:14 PM] <NiklasFiekas> lol at the tipp: "keep multiple searches open using tabs"
[5:14 PM] <jacine> cosmicdreams: You need to add hotel expenses, food, drink, etc :)
[5:14 PM] <webchick> Transition: like for example, there is now a "number" field. We should probably start using it on fields like "Number of things to show in block"
[5:14 PM] <webchick> if we aren't alrady
[5:14 PM] <NiklasFiekas> webchick: we aren't already
[5:15 PM] <webchick> Guys, Jacine is going on vacation to Aruba, let her enjoy herself and let the vacation high last a week or two. ;)
[5:15 PM] <jacine> hehe :)
[5:15 PM] <jacine> yes, thank you webchick :)
[5:15 PM] <mortendk> webchick:  yups
[5:15 PM] <mortendk> im still gonna work for a big ass gathering in 2012 +2013 ;)
[5:16 PM] <jacine> Transition: this is also a good resource: https://github.com/Modernizr/Modernizr/wiki/HTML5-Cross-browser-Polyfills
[5:16 PM] <Transition> webchick: you mean these? http://www.w3.org/TR/html5/forms.html#the-form-element
[5:16 PM] <Transition> jacine: thanks!
[5:17 PM] <NiklasFiekas> webchick, aspilicious: would actually using the the number element be a follow-up? some issues are blocked on the number fields + that would be lot's of use cases, we must identify and thouroughly test, which will take some time
[5:17 PM] <linclark> cosmicdreams: sorry, mom called
[5:17 PM] <linclark> cosmicdreams: did you have a question
[5:17 PM] <webchick> NiklasFiekas: yes, TOTAL follow-up.
[5:17 PM] <webchick> minor priotity + novice
[5:17 PM] <mortendk> why are we talking about transition … besides its awesome
[5:17 PM] <NiklasFiekas> yay!
[5:17 PM] Druplicon throws confetti
[5:17 PM] <jacine> Transition: We've got them listed here. http://drupal.org/node/1183606.  This is a good place to see them in action: http://wufoo.com/html5/
[5:17 PM] <Druplicon> http://drupal.org/node/1183606 => Implement Form API support for new HTML5 elements => 0 comments, 16 IRC mentions
[5:17 PM] <Transition> webchick: I still haven't gotten a strong grasp on the DRUPAL Form API… DESPITE the advice of Diana Dupuis!
[5:17 PM] <webchick> Diana is one of my all=time favourite humans.
[5:18 PM] <jacine> LOL
[5:18 PM] <webchick> Transition: well, you poke around HTML5 issues enough, you will get very familiar. :)
[5:18 PM] <jacine> She's pretty awesome.
[5:18 PM] <cosmicdreams> linclark: it would be great if you could read through the user stories on the data attribute issue.  I remember this issue interests you.
[5:18 PM] <Transition> jacine: webchick Indeed, she is!
[5:18 PM] <cosmicdreams> linclark:  http://drupal.org/node/1090592
[5:19 PM] <Druplicon> http://drupal.org/node/1090592 => [meta] Use HTML5 data-* attributes instead of #ID selectors in Drupal.settings => Drupal core, javascript, normal, active, 13 comments, 7 IRC mentions
[5:19 PM] <jacine> Transition: This might help with the FAPI: http://buildamodule.com/video/drupal-6-development-and-tools-essential-concepts-introduction-to-the-form-api
[5:19 PM] <Transition> jacine: That's my "poking around" goal: To Get Familiar With Stuff I'm NOT Familiar with. :-)
[5:19 PM] <jacine> Transition: awesome :)
[5:19 PM] <jacine> Transition++
[5:19 PM] <linclark> cosmicdreams: I don't work as much with the data-* attributes, which are for internal scripts, as I do with microdata, which is for external scripts... but I know about about it, so I'll take a look
[5:19 PM] <Transition> jacine: The trick is, can I do it WITHOUT "Breaking The Drupal!!" :-O
[5:19 PM] <linclark> *a bit about it
[5:19 PM] <jacine> hi linclark :D
[5:19 PM] <linclark> jacine: hey there :)
[5:20 PM] <jacine> Transition: yeah, don't worry about that :)
[5:21 PM] <Transition> mortendk: Thanks! I do my best to be as awesome as I can. ;-)
[5:21 PM] <Transition> hello linclark :-)
[5:21 PM] <mortendk> Transition: hehe daaaaang hehehe se i didnt see that
[5:21 PM] <mortendk> dammit i have my eyes on to much stuff right now
[5:21 PM] <linclark> Transition: hey there :) it's like a party up in here
[5:21 PM] <Transition> mortendk: That's the problem with having an IRC name that's a 'real' word. :-/
[5:22 PM] <Transition> "Ain't no party like an HTML5 Party cuz an HTML5 party don't stop!"
[5:22 PM] <jacine> LOL :)
[5:22 PM] <Transition> "Also, it's the future of the Web…but nothing really rhymes with that"
[5:23 PM] <mortendk> okay so what do people say to a meetup at drupalcon at a bar ;) tuesday before the official party ?
[5:24 PM] <jacine> definitely :) we can tell people to meet up in your session room.
[5:24 PM] <jacine> bbiab
[5:24 PM] jacine is now known as jacine|afk
[5:24 PM] <Transition> Oh, wait! These are examples of the HTML5 Form API stuff too, right?
[5:24 PM] jhood is now known as jhood|away
[5:24 PM] <Transition> http://drupal.org/node/1174620 and http://drupal.org/node/1315186?
[5:25 PM] <Druplicon> http://drupal.org/node/1174620 => Add new HTML5 FAPI element: email => Drupal core, forms system, normal, fixed, 79 comments, 11 IRC mentions
[5:25 PM] <Druplicon> http://drupal.org/node/1315186 => HTML5 support for form elements => 0 comments, 5 IRC mentions
[5:25 PM] <cosmicdreams> shoot! my comment cleanup patch failed
[5:25 PM] <NiklasFiekas> Transition: http://drupal.org/node/1183606
[5:25 PM] <Druplicon> http://drupal.org/node/1183606 => Implement Form API support for new HTML5 elements => 0 comments, 17 IRC mentions
[5:25 PM] <cosmicdreams> my local testsuite finished before d.o did
[5:26 PM] <NiklasFiekas> Transition: tel, email are in. url, number are probably ready.
[5:26 PM] <Transition> thanks NiklasFiekas
[5:26 PM] <NiklasFiekas> cosmicdreams: d.o however did run the full test suite :P
[5:27 PM] <Transition> davereid: I've got a style question: I'm looking at http://drupal.org/node/1174620 and I'm noticing you've included a link to the Change Summary FOR that issue.
[5:27 PM] <Druplicon> http://drupal.org/node/1174620 => Add new HTML5 FAPI element: email => Drupal core, forms system, normal, fixed, 79 comments, 12 IRC mentions
[5:27 PM] <davereid> yes
[5:27 PM] <Transition> is that something I should do for the Change Summaries I've done? Add a link to them in the originating issue? I've done two Change Summaries already.
[5:28 PM] <davereid> Transition: we don't need additional change summaries for them :)
[5:28 PM] <davereid> maybe I'm confused about what is being asked
[5:29 PM] <NiklasFiekas> Transition: not required, but yeah ... why not backlink summaries in the issue
[5:29 PM] <cosmicdreams> aspilicious: ping
[5:29 PM] <cosmicdreams> aspilicious: as a result of your comment http://drupal.org/node/1217054#comment-5697352 it sounds like we need manual testing.  Am i right?
[5:29 PM] <Druplicon> http://drupal.org/node/1217054 => Clean up the CSS for User module => Drupal core, user.module, normal, needs work, 26 comments, 2 IRC mentions
[5:29 PM] <Transition> davereid: NiklasFiekas No, that makes sense. I think what I did with mine was I added a comment in the issue that I was working on a Change Summary. But adding it to the Issue Summary makes more sense. It's easier to see/find.
[5:29 PM] <aspilicious> cosmicdreams, yeah and I don't think the patch is complete
[5:30 PM] <aspilicious> and I think you're adding some unneeded css on some forms
[5:30 PM] <Transition> NiklasFiekas: So, I'd created a link, but not as clear/easy to find as the type davereid created.
[5:30 PM] <davereid> Transition: yeah I'd rather have all the html5 fapi stuff together in one change notice rather than having to manage multiple notices
[5:31 PM] <cosmicdreams> aspilicious: interesting, typically I'm not trying to *add* css to these implementations.
[5:31 PM] <Transition> davereid: Oh, I wasn't talking specifically about the HTML5 API stuff. I was talking about Change Notices in GENERAL.
[5:31 PM] <davereid> Transition: that section in the issue summary gets automatically added if you reference the issue from http://drupal.org/node/1315186
[5:31 PM] <Druplicon> http://drupal.org/node/1315186 => HTML5 support for form elements => 0 comments, 6 IRC mentions
[5:32 PM] <aspilicious> cosmicdreams, you need to look at the form and than look what css it needs
[5:32 PM] <aspilicious> sometimes you add theme.css and admin.css
[5:32 PM] timplunkett is now known as timplunkettAFK
[5:32 PM] <aspilicious> (just an example dunno if thats the case)
[5:32 PM] <aspilicious> and sometimes you only need one of them
[5:33 PM] jacine|afk is now known as jacine
[5:33 PM] <davereid> Transition: so I think what you're saying is you wanted the issue summary to look like I did, and I'm saying that text is automatic if you reference the correct issue from the change notice node :)
[5:34 PM] <Transition> davereid: wait, what? So, if I just REFERENCE the issue from the Change Notice…a "Change Notice" section gets added to the original issue?
[5:34 PM] <davereid> yep
[5:34 PM] <Transition> davereid: I must have done something wrong…I don't think that happened with mine...
[5:34 PM] Transition goes to check...
[5:35 PM] <NiklasFiekas> davereid: oh ... awesome. i didn't know that
[5:37 PM] <Transition> davereid: Hmm…I must not have referenced the issue FROM the Change notice. No, wait, I think I did!
[5:38 PM] jhood|away is now known as jhood
[5:38 PM] <Transition> davereid: the issue is http://drupal.org/node/1183250 and the change notice is http://drupal.org/node/1441334 and there's a reference to the original issue...
[5:38 PM] <Druplicon> http://drupal.org/node/1183250 => Add a theme_datetime() function to consistently theme dates and datetimes => Drupal core, theme system, normal, fixed, 224 comments, 47 IRC mentions
[5:38 PM] <Druplicon> http://drupal.org/node/1441334 => Add a theme_datetime() function to consistently theme dates and datetimes => 0 comments, 10 IRC mentions
[5:38 PM] <Transition> davereid: What'd I do wrong/leave out?
[5:39 PM] <aspilicious> html5 sprint?
[5:39 PM] <Druplicon> html5 sprint is http://bit.ly/html5-sprint
[5:39 PM] <davereid> Transition: I see it right in 'Change records for this issue'
[5:39 PM] <Transition> davereid: D'Oh!! I didn't scroll down far enough!
[5:40 PM] <Transition> NOW you see why i'm scared to break the Drupal?!? :-(
[5:40 PM] <NiklasFiekas> Transition: davereid won't let you :P
[5:41 PM] <Transition> NiklasFiekas: That's good to know!
[5:41 PM] <Transition> Ah! I see it on the OTHER issue I did a Change Record for too! Ok!
[5:42 PM] <Transition> Ok, now to make notes of the stuff I'm supposed to be working on as a result of this meeting!
[5:42 PM] <aspilicious> jacine, rerolled shortcut
[5:42 PM] <aspilicious> now I need some sleep
[5:42 PM] <jacine> aspilicious: cool, good night :)
[5:48 PM] davereid is now known as davereid|brb
[5:55 PM] jhood is now known as jhood|away
[6:05 PM] <Transition> jacine, Ok, I think I've got my assignment: an Issue Summary for http://drupal.org/node/1252178#comment-5697644
[6:05 PM] <Druplicon> http://drupal.org/node/1252178 => Add a polyfill loading solution => Drupal core, javascript, normal, needs work, 29 comments, 13 IRC mentions
[6:05 PM] <Transition> jacine: I
[6:05 PM] <jacine> Transition: great, thank you :D
[6:05 PM] <Transition> jacine: I'M ALSO going to look into the Form API, so I'll have a better understanding of what's going on with the HTML5 Forma API stuff.
[6:06 PM] <jacine> Transition: have fun! :)  If you have questions, feel free to ask.
[6:06 PM] <Transition> jacine: No problem. I think there's a Drupalize.me video on the Form API too.
[6:06 PM] <Transition> jacine: Enjoy your trip to Aruba!!
[6:07 PM] <Transition> jacine++
[6:07 PM] <jacine> Ah, it's not until the end of April, but thank you :D
[6:07 PM] <jacine> Transition++
[6:07 PM] <Transition> :-D I'm outta here!