I apologize for the short notice, this came together last-minute. The F36 retrospective will be much better planned. :-)
We don't have to start on the 12th, but since we have the release party, that seems like a good time to start promoting the survey.
LSS file attached <img alt="limesurvey_survey_f35retro.lss" src="/mindshare/issue/raw/files/f28efa8ea33ac56ff8fe591011f90c2cede32b31db065a41f5c25f705e9fd73a-limesurvey_survey_f35retro.lss" />
+1 to the idea. The lss file is not readable for me, I don't have access to LimeSurvey, so I cannot give any feedback about the questions.
I agree with what @till said.
Here are the questions for reference:
+1
this looks good to me! +1
@bcotton This looks good except the first question on how did you participate seems to miss a lot of types of folks who work on Fedora release bits and I am wondering why were those specific activities chosen, is there a specific goal with the question I am not aware of?
It's primarily focused on the process of building and shipping the release, which is why the activities are relatively narrow. It's not meant to diminish the work of other contributions. I didn't want to add too many choices and increase the complexity or try to lump many disparate activities under a single banner, which might be confusing and also cause people to self-select out.
The F36 retrospective survey will be better planned, so if there are specific areas you think should be included, I'm happy to discuss those outside of this ticket.
Metadata Update from @siddharthvipul1: - Issue assigned to siddharthvipul1 - Issue tagged with: limesurvey
@bcotton Hey Here is the link for you (and others) to review: https://fedoraproject.limequery.com/231354
Please let me know if it looks good and then I will remove all the test entries Warning: Responses to this survey are NOT anonymized
We discussed this in chat, but for the public record, it looks great. Thanks!
Metadata Update from @siddharthvipul1: - Issue close_status updated to: Complete - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.