Maker Party: Launch user feedback survey

[damiankay]

Purpose: identify bugs and gather feedback for success metrics

[ScottDowne]

@damiankay I think I'll need more details as to how we want to do this.

[ScottDowne]

@damiankay or an example from a previous mozilla project where we did this would also be a good replacement to (or with) more details. (I'm pretty visual)

[damiankay]

I'll try to wrangle something @ScottDowne

[damiankay]

@simonwex do you know where we might find a user feedback survey that we could re-use from another project?

[ScottDowne]

In the past, I have just created a form, and dumped results into google sheets.

I'm happy to put them into google sheets again, as it's pretty simple.

This is what it looked like, but we shouldn't reuse any of the code from this:

[damiankay]

Sounds good @ScottDowne - we can put this aside until we know what the survey questions will be.

[damiankay]

@shaghdoosti @geroter can you please review the survey that @ScottDowne posted above and let us know if this type of form would be acceptable?

Who should be responsible for drafting the questions?

[ldecoursy]

If this is a survey for all Maker Party attendees, 270 has planning doc here: https://docs.google.com/document/d/1p1BVUXIZnUgByyAUxceVLMSOyGj5NtNjtY6V8R_yQuY/edit#heading=h.hridd9hf41l4

Here's a version specifically for Maker Party hosts: https://docs.google.com/document/d/14U0nbfeoXuDWl9hpMbv_v0GUIwGJYf3vx17bchhNiyk/edit#

[ScottDowne]

Is this expected to have the pages done on the 16th, and I guess localized too? Or just a decision made as to what we're going to build.

It's a serious tight timeline to have this done by the 16th, given decisions need to still be made, and then built and localized, along with everything else we're doing.

[damiankay]

Hi @ScottDowne - those are great questions. I would say that the survey doesn't need to be complete until we launch. We're also finalizing the best format for the surveys (in terms of technology) so sit tight on this for now.

In the meantime, we should really figure out whether these need to be localized. @ldecoursy do you know?

[ldecoursy]

I'd assume so, but going to loop 270 in too (not sure github usernames so will email them). Do you know what our resources are to translate responses by chance? ;)

[damiankay]

@ldecoursy great question. I think that having the surveys localized in time for the Maker Party launch will be a big challenge, to be honest.

[smartinez270]

I think we will want to have standardization in questions asked across maker parties, so I'm not sure we need a lot of localization (if i'm understanding this correctly). If it is possible to add a drop down field to the survey that indicates which Maker Party an individual attended would be great for analyzing results by party.

[ldecoursy]

@smartinez270 This is also a question about whether or not we need the survey translated into the priority languages aside from English.

[smartinez270]

@ldecoursy Ah gotcha. Yes, we'd want this translated into the priority languages.

[damiankay]

@ldecoursy @smartinez270 if that's the case we should finalize the copy for the post-sign-up survey asap. We might need to look into using our external contractor vs. L10n as time will be very tight, but I can check in with them once we have copy finalized.

[smartinez270]

Given we want to move as fast as possible to finalize, what is the rough timeline for translation?

[damiankay]

@smartinez270 there's no set timeline for a given localization. We prefer to involve our localization community whenever possible, but they work on a large range of projects within MoFo and MoCo, so there's the base time required for translation, plus the issue of prioritization. There is also a process that includes an initial translation, peer review, and final adjustments, so I'd say that it's 4-5 days at a minimum.

The general rule is that we should give that team 2 weeks, however, if we think we can limit to one survey for launch I'd like to see if the localization team can handle it.

[geroter]

Jumping in to say that we could also pay for translation and then have community reviewers. This is not expensive.

On Mon, Sep 12, 2016 at 11:04 PM, Damian Kuehn notifications@github.com wrote:

@smartinez270 https://github.com/smartinez270 there's no set timeline for a given localization. We prefer to involve our localization community whenever possible, but they work on a large range of projects within MoFo and MoCo, so there's the base time required for translation, plus the issue of prioritization. There is also a process that includes an initial translation, peer review, and final adjustments, so I'd say that it's 4-5 days at a minimum.

The general rule is that we should give that team 2 weeks, however, if we think we can limit to one survey for launch I'd like to see if the localization team can handle it.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/MozillaFoundation/Advocacy/issues/145#issuecomment-246492952, or mute the thread https://github.com/notifications/unsubscribe-auth/AKP84Lbj7XwZw4vcSkQ2MeSPxzkbRHi5ks5qpb5mgaJpZM4JTO5R .

George Roter Head of Core Contributors, Participation

irc: geroter | skype: geroter Cell - Germany: +49 172 714 2439 Cell - USA: +1 650.210.6953 <650%20308%208443>

[damiankay]

Thanks @geroter - we're working with Kontextor for some other localizations. I'm CC'ing @valianttry as she's the main point of contact.

@smartinez270 @ldecoursy when do you anticipate we'll have approval on the survey copy?

[valianttry]

@geroter we've already used a company called Kontextor for a lot of copy -- either as drafters, reviewers, or both depending on the need. We have been having weekly join meetings about localization for Copyright work with L10N leadership (Flod and / or Peiying), and Kontextor project managers assigned to our account. So far we've been paying for Kontextor out of the Foundation's budget on a standard contractor contract.

[kpars270]

@damiankay We're planning to have final recommendations/draft by Friday EOD. @ldecoursy can you advise on approval timing? It might make sense to loop Sara for her approvals wizardry.

[ldecoursy]

I think we'll need @geroter on approvals since @shaghdoosti is at a Fellows offsite this week :)

[damiankay]

@valianttry noted that we've used SurveyGizmo in the past for surveys

@ldecoursy @geroter

[ScottDowne]

Any thoughts on user google forms for this? Make one fore each language?

[valianttry]

@ScottDowne we should just use SurveyGizmo, and ask Flod at L10N the best way to localize (they usually set process depending on the type of content and amount of text). We have used Google forms but I would consult with them.

I have not used SurveyGizmo for non-EN surveys so it is worth inquiring how SurveyGizmo works with localization.

[geroter]

I can do final approval on content next week as Lainie suggested.

For tool/implementation, let's go with lowest friction :)

[damiankay]

What's the desired launch date for this survey @ldecoursy @smartinez270 ?

[ScottDowne]

This fell off my radar, once I was under the impression we were not building a survey.

For l10n on this, we'll be creating multiple surveys, and updating the links in the live pages based on the locale.

The raw strings can be put into pontoon out of context, if we so desire, but we won't be getting in context translations with this. From there, it becomes a manual process.

[kpars270]

adding @valianttry

[ScottDowne]

@valianttry I thought this was being reassigned?

[valianttry]

Closing this ticket. L10N work is being tracked now in #565