You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once a survey closes, the prominently linked blog entry and all other announcements/invitations to the surveys quickly become dead ends. It sometimes takes a while until the results are digested and available in presentable form
(c.f. rust-embedded/wg#782 (comment)).
Info about results availability, timeline info, and ultimately a link to the results in the announcement post would help a lot.
The two surveyguides only refer to a previous post as the blog post template. That post does not mention anything about the results of the survey that is announced.
Maybe the recommendation above could be added to the guides.
The text was updated successfully, but these errors were encountered:
We pretty much never know when will the results be available before launching the survey, so it's hard to make promises. For the annual survey, in some years it took days, in some weeks, in some months :) Hopefully now with the new automation in place, it should be days, max. weeks this time.
But what we should improve is to add the link to the results to the announcement blog post, that's a very good point! Would you like to add these instructions to the annual survey guide in a PR? If not, I'll add it there.
Once a survey closes, the prominently linked blog entry and all other announcements/invitations to the surveys quickly become dead ends. It sometimes takes a while until the results are digested and available in presentable form
(c.f. rust-embedded/wg#782 (comment)).
Info about results availability, timeline info, and ultimately a link to the results in the announcement post would help a lot.
The two survey guides only refer to a previous post as the blog post template. That post does not mention anything about the results of the survey that is announced.
Maybe the recommendation above could be added to the guides.
The text was updated successfully, but these errors were encountered: