-
Notifications
You must be signed in to change notification settings - Fork 43
Surveys: Initial Drafts #173
Comments
This looks good - I'll be happy to be involved in the iteration process. |
I'd like to be involved, but am confused as to what that looks like. I'm more looking to review the survey questions, not to take the survey. |
I know... my bad, it's kinda how my head feels most of the time... Rest assured, once the first set of tangible question is ready for critique, additions, rewording, reworking, even removing, it will be open for all of us to work on as we normally do. |
I'm very interested in this, please count me in. |
I believe @seldo would be interested in helping to promote the survey via
npm.
I'm sure the foundation could help with this as well.
I believe survey monkey is what they had used.
…On Wed, Aug 29, 2018, 8:25 PM Gus Caplan ***@***.***> wrote:
I'm very interested in this, please count me in.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#173 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAecV9rkiz_flGelLjz7MdL9Gkwv8OqLks5uVurEgaJpZM4WSIvC>
.
|
Me too. |
I think we can now have 2 iterations (I think 2-3 days per iteration). I would like to recommend the following pairings, but leave it up to those mentioned to indicate if they want to go first of in 2-3 days. Awesome: @GeoffreyBooth @MylesBorins This pairing ensures each iteration has input from someone who is too close and another who is a newer to Node.js organizational culture. Does that work for everyone mentioned? |
@inidaname & @sendilkumarn It appears we have everything we need to do the follow up. I recommend we have shared Skype or Hangouts session to review and revise the survey for the next two participants. Can either please take lead on scheduling this and setting us up? Round 0 — A1: @inidaname @sendilkumarn (and myself) |
Scheduling for 2-3 days will be Friday or Saturday so which do you choose @SMotaal |
I would anti-recommend surveymonkey; they have absurdly naive anti-XSS protection that prevents including the word "JavaScript" in a survey question; this is still not fixed. |
Lets find a suitable timing, created a doodle |
How will the be the form circulated? Is the "event" mentioned, Node+JS Interactive? or the collaborator Summit? |
@mcollina I would assume and would like it to be both "events", but this really is up to the group as a whole. We're just trying to pick up momentum to make it possible. |
I guess the A1 post-survey review can be Friday with myself, @inidaname and @sendilkumarn (please check doodle Aug 31 7PM GMT) Any preferences between Skype or Hangouts? I know sometimes the region sort of determines that for us, so please let me know which works best. |
I think Hangouts is fine 👍 |
I’m not clear on what’s being asked of me. I’m supposed to do something in the next day or two? |
@GeoffreyBooth Sorry about that... I will up this thread with next steps and figure out a how to make sure our efforts stay coordinated as we proceed. |
Re #175 Survey: Initial Draft Incremental Rounds Everyone taking part the incremental rounds of the (pubic) survey, as things start to move forward we will try to coordinate our efforts through #175 using direct mentions only. Given the ad-hoc nature of this organically evolving process and how it is different from how normally collaborate, the direct mentions rule should help us stay up to day with our individual next steps. @nodejs/modules-observers |
I hope we can discuss this issue to:
|
This initiative is intended to yield Google Form based survey to be able to prioritize group decisions. The goal is to build a survey that feels right to developers across the Node's ecosystem, which requires more effort than just being able to write some good questions from one's own perspective.
Please note that the efforts related to this thread are now concluded. Please look forward to updates on next steps.
Next Steps open to anyone interested in collaborating on this
We're shifting gears to a more manageable facilitated questionnaires with 3-4 participants at a time in Vancouver. The "public" developers survey will now only be feasible after the summit.
Here is an open link to the most recent "ongoing" draft: C1:
DevelopersCollaborators Survey✋ Internal Surveys (Bx)
🔨Collaborator's Facilitated Questionnaires (Cx)
🔨Developers Surveys (Dx)
The text was updated successfully, but these errors were encountered: