Christophe Porteneuve
Christophe Porteneuve
By the way, @stevekane and I had briefly talked through e-mail about my taking over this repo's maintenance, and I'm all for it, but that discussion died out a couple...
Hey Steve, thanks for the vote of confidence! @TimothyGu OK with my merging #40? I vouch for it!
@TimothyGu that's alright: the French L10n was already reviewed. I'm more asking about the code itself, as this upgraded to `workshopper`'s latest infra.
Hey @TimothyGu, @stevekane So I'd love to see FR L10n in a published version… Things are moving forward again, but only Steven can publish on npm. Can we agree on...
I'm concerned 0.2.0 sounds pretty low, but I don't like skipping numbers in a given sequence, so 0.2.0 it is. Moving to ES6 Promises API (either native or shimmed) def...
Hey Tim, Gratz on being steadfast with this work. I haven't looked into the ES2015 rewrite, but I trust this works on recent Nodes without the need for Babel, just...
Hey! @TimothyGu FYI, I'm re-L10n'ing the whole thing to FR. Should be in a PR within 24 hours. I see a couple things in the original EN text that make...
Hey there, A related issue existed about 8 days ago as Sequelize changed stuff since last Fall, I stumbled upon it and fixed it. Are you up-to-date on the latest...
Hey, Ooops, sorry about that, had read "new quiz", not "new question". Will check it out tomorrow and let you know.
Hello, Yup, not your fault, issues with how express-namespace interacted with the new Express 4 code. And when that got fixed, ran into the same Sequelize upgrade issue I had...