Sorry. We could have handled that better. I think we will probably do
this again in the future, so we'll have an opportunity to be more
explicit about these things.
Mike
On 07/24/2013 08:37 AM, Phil Elson wrote:
I'm not quite back to normality here after getting back from over a
month out of the office (Scipy'13 taking a chunk of that time) and
didn't manage to fill in the questionnaire. I guess it doesn't matter
too much that I didn't manage to fill it in (I know my own users, all
250+ of them, pretty well after all), but I wonder whether there are
others in a similar situation who didn't get a final social nudge to
get on and fill in the questionnaire because time was running out. If
we do something similar in the future I suggest we publish a deadline
and push the social media streams hard up-until that final deadline,
just to get those final last minute-ers (like me). :-)
Anyway, that aside, having quickly glanced at the results of the
survey, I'm really impressed at the quality of the data and how clear
some of the messages in there have come out (i.e. there are backends
which are clearly dead horses). More on that in a separate thread...
Cheers (its good to be back)!
Phil
On 18 July 2013 14:33, Michael Droettboom <md...@stsci.edu
<mailto:md...@stsci.edu>> wrote:
I'm fine with that. I actually had the same idea yesterday. I don't
think we'll get many more responses than we already have.
I'll go ahead close the survey and then make an official
announcement on
the usual channels.
Mike
On 07/17/2013 06:12 PM, Paul Ivanov wrote:
> Hey everyone,
>
> I hope this email finds you well. I got a request today from
> someone wanting to look at the survey results. How do you feel
> about just sharing the full document? We're at 580 responses
> right now, and it's been really a slow trickle in last couple of
> weeks after the initial splash. Or we could do another round on
> twitter and G+ and say the survey will be closed at the end of
> the month, and then release the results.
>
> Thoughts?
>
> best,
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
<mailto:Matplotlib-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
