Re: [Haskell-community] 2018 state of Haskell survey

[Francesco Ariis]

On Sun, Oct 28, 2018 at 04:33:44PM -0400, Taylor Fausak wrote:
> Thanks for the suggestions!
> 
> - I plan on releasing the results under the ODbL 1.0 license. I'll be
> sure to update the survey to say that. You can read more about the
> license here: https://opendatacommons.org/licenses/odbl/summary/

Excellent choice!
___
Haskell-community mailing list
Haskell-community@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-community

Re: [Haskell-community] 2018 state of Haskell survey

[Taylor Fausak]

Thanks for the suggestions!

- I plan on releasing the results under the ODbL 1.0 license. I'll be sure to 
update the survey to say that. You can read more about the license here: 
https://opendatacommons.org/licenses/odbl/summary/

- The last question asks for an email address. I wouldn't call it mission 
critical, but it will allow me to follow up on confusing or problematic 
responses. Last year I asked for email addresses and 75% of responses included 
them. This year the question remains optional, and it also explains how it will 
be used. I would prefer not to remove it. 

On Sun, Oct 28, 2018, at 4:06 PM, Francesco Ariis wrote:
> Hello Taylor,
> 
> On Sun, Oct 28, 2018 at 02:42:16PM -0400, Taylor Fausak wrote:
> > Please > take a look at the survey to make sure that you're happy
> > with it! Let me know if there are any questions that you would like
> > to be added, removed, or changed. You can view the survey here:
> > https://airtable.com/shr8G4RBPD9T6tnDf
> > You can deliver feedback to me either in this thread or on GitHub:
> > https://github.com/haskellweekly/haskellweekly.github.io/issues/206
> 
> Suggestions:
> - state under which specific one of the "permissive license"s the
>   results will be available;
> - if it not mission critical, axe the last question.
> 
> ___
> Haskell-community mailing list
> Haskell-community@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-community
___
Haskell-community mailing list
Haskell-community@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-community

Re: [Haskell-community] 2018 state of Haskell survey

[Francesco Ariis]

Hello Taylor,

On Sun, Oct 28, 2018 at 02:42:16PM -0400, Taylor Fausak wrote:
> Please > take a look at the survey to make sure that you're happy
> with it! Let me know if there are any questions that you would like
> to be added, removed, or changed. You can view the survey here:
> https://airtable.com/shr8G4RBPD9T6tnDf
> You can deliver feedback to me either in this thread or on GitHub:
> https://github.com/haskellweekly/haskellweekly.github.io/issues/206

Suggestions:
- state under which specific one of the "permissive license"s the
  results will be available;
- if it not mission critical, axe the last question.

___
Haskell-community mailing list
Haskell-community@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-community

Re: [Haskell-community] 2018 state of Haskell survey

[Taylor Fausak]

We're creeping closer to the release date. I spent some time this
weekend tweaking the survey in response to suggestions from this thread
and also from GitHub. I don't plan on making any large changes to the
survey between now and Thursday, except in response to feedback. Please
take a look at the survey to make sure that you're happy with it! Let me
know if there are any questions that you would like to be added,
removed, or changed. You can view the survey here:
https://airtable.com/shr8G4RBPD9T6tnDf
You can deliver feedback to me either in this thread or on GitHub:
https://github.com/haskellweekly/haskellweekly.github.io/issues/206

On Fri, Oct 26, 2018, at 8:57 AM, Taylor Fausak wrote:
> 🎉 Hooray! That’s wonderful news! Thank you, Haskell.org committee, for
> supporting the survey.> 
> I plan on releasing this year’s results in the same fashion as
> last year.> 
>> On Oct 26, 2018, at 5:31 AM, Jasper Van der Jeugt
>>  wrote:>> 
>> Hi Taylor,
>> 
>> Yes, we're happy to support it from Haskell.org.
>> 
>> One additional ask from our side would be that the raw results are
>> published as well, but I saw in the issue you're already planning on>> doing 
>> that.
>> 
>> Cheers
>> Jasper
>> 
>> On Thu, Oct 25, 2018 at 11:18:30AM -0400, Taylor Fausak wrote:
>>> 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 Haskell.org
>>> ?>>> 
 On Oct 17, 2018, at 7:00 PM, Jasper Van der Jeugt 
 wrote: 
 Hi Taylor,
 
 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. 
 Thanks again for organizing this!
 
 Cheers
 Jasper
 
 On Thu, 18 Oct 2018 at 00:55, Taylor Fausak >>> > wrote: Thank you all for the wonderful 
 feedback so far! I greatly
 appreciate all of it. 
 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. 
 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. 
 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. 
 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. 
 It sounds like the Haskell.org committee is broadly in favor of
 backing the upcoming Haskell Weekly survey. Is that correct? In
 either case, what are the next steps? 
> On Oct 16, 2018, at 5:10 PM, Boespflug, Mathieu  > wrote:> 
> Since I was pinged up-thread, might as well chime in. If only
> to say> "I agree": selection bias is what it is. Taylor's efforts to
> come to> this committee are laudable. And really could help mitigate 
> some
> issues we've seen with other surveys. Selection bias isn't
> something> worth agonizing over, provided we're careful to say in the
> analysis of> the results: "We found that X% of the respondents of this
> survey use> Y", not "X% of Haskell devs use Y".
> 
> On Tue, 16 Oct 2018 at 21:02, Simon Peyton Jones via Haskell-
> community> mailto:haskell-
> commun...@haskell.org>> wrote:>> 
>> | Hi Taylor. I like the way you pose things here: "I don't expect
>> | that>> | to remove selection bias, but it will let me (us, really) 
>> say:
>> | We're>> | doing this together for the benefit of all sides". I 
>>