<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">🎉 Hooray! That’s wonderful news! Thank you, <a href="http://Haskell.org" class="">Haskell.org</a> committee, for supporting the survey. <div class=""><br class=""></div><div class="">I plan on releasing this year’s results in the same fashion as last year. <br class=""><div class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Oct 26, 2018, at 5:31 AM, Jasper Van der Jeugt <<a href="mailto:m@jaspervdj.be" class="">m@jaspervdj.be</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hi Taylor,<br class=""><br class="">Yes, we're happy to support it from <a href="http://Haskell.org" class="">Haskell.org</a>.<br class=""><br class="">One additional ask from our side would be that the raw results are<br class="">published as well, but I saw in the issue you're already planning on<br class="">doing that.<br class=""><br class="">Cheers<br class="">Jasper<br class=""><br class="">On Thu, Oct 25, 2018 at 11:18:30AM -0400, Taylor Fausak wrote:<br class=""><blockquote type="cite" class="">We’re one week out from the release of the survey. I plan on spending this weekend putting the finishing touches on it. Can I plan on announcing it as the official state of Haskell 2018 survey, supported by both Haskell Weekly and <a href="http://Haskell.org" class="">Haskell.org</a> <<a href="http://haskell.org/" class="">http://haskell.org/</a>>? <br class=""><br class=""><blockquote type="cite" class="">On Oct 17, 2018, at 7:00 PM, Jasper Van der Jeugt <<a href="mailto:m@jaspervdj.be" class="">m@jaspervdj.be</a>> wrote:<br class=""><br class="">Hi Taylor,<br class=""><br class="">Just a small comment: I would like to keep the survey open a bit longer -- I would suggest two weeks. This gives us a bit more time to push it out twice to as many channels as possible (once at the start and a reminder after a week or so). My intuition is that we'll be able to gather significantly more responses that way.<br class=""><br class="">Thanks again for organizing this!<br class=""><br class="">Cheers<br class="">Jasper<br class=""><br class="">On Thu, 18 Oct 2018 at 00:55, Taylor Fausak <<a href="mailto:taylor@fausak.me" class="">taylor@fausak.me</a> <<a href="mailto:taylor@fausak.me" class="">mailto:taylor@fausak.me</a>>> wrote:<br class="">Thank you all for the wonderful feedback so far! I greatly appreciate all of it. <br class=""><br class="">I didn’t mean to be exclusionary with my language before, and I thank y’all for correcting me there. “We’re doing this together for the benefit of all” is an excellent way to say what I’m shooting for here. <br class=""><br class="">My goal for the survey is to be useful to many different groups of people: the GHC team, library authors, application developers, repository maintainers, prospective employees, hiring managers, community organizers, and no doubt many more groups that I’m not thinking of right now. I want to avoid results that are neat but not useful. I also want to avoid results that simply throw fuel onto common flame wars.<br class=""><br class="">Last year I announced the survey results and provided some commentary. I suspect I’ll do something similar this year, although reading your comments here makes me want to do less analyzing in favor of simply publishing. I am not particularly adept at analyzing survey results and am bound to make some rookie mistakes. In fact, one of the reasons that I published the results last year was so that someone who actually knew what they were doing could slice and dice the data. <br class=""><br class="">As far as scheduling is concerned, I plan to keep the survey open for a week, from November 1st to 7th. Publishing the results should happen relatively quickly after that. I slowed myself down last year by rendering a bunch of graphs, and even so I published on November 15th. <br class=""><br class="">It sounds like the <a href="http://Haskell.org" class="">Haskell.org</a> committee is broadly in favor of backing the upcoming Haskell Weekly survey. Is that correct? In either case, what are the next steps? <br class=""><br class=""><blockquote type="cite" class="">On Oct 16, 2018, at 5:10 PM, Boespflug, Mathieu <<a href="mailto:m@tweag.io" class="">m@tweag.io</a> <<a href="mailto:m@tweag.io" class="">mailto:m@tweag.io</a>>> wrote:<br class=""><br class="">Since I was pinged up-thread, might as well chime in. If only to say<br class="">"I agree": selection bias is what it is. Taylor's efforts to come to<br class="">this committee are laudable. And really could help mitigate some<br class="">issues we've seen with other surveys. Selection bias isn't something<br class="">worth agonizing over, provided we're careful to say in the analysis of<br class="">the results: "We found that X% of the respondents of this survey use<br class="">Y", not "X% of Haskell devs use Y".<br class=""><br class="">On Tue, 16 Oct 2018 at 21:02, Simon Peyton Jones via Haskell-community<br class=""><<a href="mailto:haskell-community@haskell.org" class="">haskell-community@haskell.org</a> <<a href="mailto:haskell-community@haskell.org" class="">mailto:haskell-community@haskell.org</a>>> wrote:<br class=""><blockquote type="cite" class=""><br class="">| Hi Taylor. I like the way you pose things here: "I don't expect that<br class="">| to remove selection bias, but it will let me (us, really) say: We're<br class="">| doing this together for the benefit of all sides". I think that's a<br class="">| better place to start from.<br class=""><br class="">I like this too -- and like Gershom, I'd delete "sides". We aspire<br class="">to work together, not on different sides.<br class=""><br class="">| earlier I've been thinking about a bit, where you wrote: "My goal is<br class="">| for this survey to be *the* authoritative Haskell survey and for the<br class="">| community to broadly accept it's results."<br class=""><br class="">This sounds a bit too exclusive to me, and implicitly critical of other<br class="">work. Better to stick to the positives: you simply want the<br class="">opinions of a broad constituency on a broad range of questions.<br class=""><br class="">| Anyway, this is all a long-winded way of suggesting that it might be<br class="">| good if the purpose of the survey was explicitly set out as trying to<br class="">| inform developers of haskell libraries and tools (and educational<br class="">| materials) regarding the systems their potential users work on and<br class="">| develop, and their habits and practices in doing so, and where they<br class="">| encounter difficulty. That is explicitly as a way of learning rather<br class="">| than as any sort of horse-race or popularity contest.<br class=""><br class="">That sounds good to me -- but again in drafting the goals I'd stick<br class="">to the positives, and not speak about horse-races.<br class=""><br class="">Simon<br class="">_______________________________________________<br class="">Haskell-community mailing list<br class=""><a href="mailto:Haskell-community@haskell.org" class="">Haskell-community@haskell.org</a> <<a href="mailto:Haskell-community@haskell.org" class="">mailto:Haskell-community@haskell.org</a>><br class=""><a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-community" class="">http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-community</a> <<a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-community" class="">http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-community</a>><br class=""></blockquote></blockquote><br class="">_______________________________________________<br class="">Haskell-community mailing list<br class=""><a href="mailto:Haskell-community@haskell.org" class="">Haskell-community@haskell.org</a> <<a href="mailto:Haskell-community@haskell.org" class="">mailto:Haskell-community@haskell.org</a>><br class=""><a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-community" class="">http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-community</a> <<a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-community" class="">http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-community</a>><br class="">-- <br class="">Jasper<br class=""></blockquote><br class=""></blockquote></div></div></blockquote></div><br class=""></div></div></body></html>