| 30 Mar 2023 |
 felixfontein | your module apparently depends on a docs fragment called 'my_namespace.my_collection.my_doc_fragment_name', which ansible-core cannot find | 09:50:11 |
| felixfontein | also better use this link: https://docs.ansible.com/ansible/latest/dev_guide/developing_modules_general.html | 09:50:37 |
| felixfontein | the link you are using is pretty old (2019) | 09:51:04 |
 Martin Møller Skarbiniks Pedersen | ok. thanks | 10:43:43 |
 Gwmngilfen | newsbot:
Contributor Summit & Community survey results for Feb
After CfgMgmtCamp and Contributor Summit, we ran our usual post-event survey, which also asks more general questions about the state of the community too.
I've now closed the forms and done the analysis, and you can find the results here. In general it's fairly consistent with previous surveys (which you can find here.
Overall we're seeing more of the themes we've already discussed in the community strategy so I hope the plans for the year ahead will positively impact that. Check it out, and let me know your thoughts!
| 10:44:41 |
 newsbot | ✅ Hey Gwmngilfen, thanks for your report! I'll store it safely for the next Bullhorn review! | 10:44:42 |
| Gwmngilfen | 
Download image.png | 10:44:48 |
| felixfontein | these 2.10 blocks scare me :) | 10:45:40 |
| Gwmngilfen | it's still in RHEL though | 10:46:35 |
| Gwmngilfen | so I expect it won't go awat entirely for a while | 10:46:44 |
| Gwmngilfen | * so I expect it won't go away entirely for a while | 10:46:57 |
| felixfontein | you sure you mean 2.10 and not 2.9? | 10:48:01 |
| Gwmngilfen | eh, perhaps I should have put 2x | 10:48:18 |
| Gwmngilfen | mostly I'm happy to see a big chunk of 7.X given it came out since the last survey. I know we have a regular schedule, so it's good to see folks upgrading. | 10:49:13 |
| Gwmngilfen | (worth noting there were more categories, I strip the zero-response ones) | 10:49:35 |
| Gwmngilfen | in general the response rate was pretty low, I think we have a bit of survey fatigue | 10:50:05 |
| felixfontein | let's do a survey on that! | 10:50:19 |
| Gwmngilfen | 🤣 | 10:50:27 |
| Gwmngilfen | I think a yearly model with a wider call-to-action is the way to go. we don't put it on the docs page, for example, because it's somewhat specific to the event. | 10:51:03 |
| Gwmngilfen | (the one time we did a docs survey, back in 2020/1, we got 900 replies) | 10:51:50 |
| Gwmngilfen | I'd really love some data from somewhere else on something like what version people use or how long they've been using it, so I can weight the survey properly. But I don't think it exists. | 10:52:42 |
| Gwmngilfen | maybe ssbarnea can get me some of that VSCode telemetry 🙂 | 10:53:09 |
 tremble | Trouble is that when you're getting the info from something like VSCode you're tying it to a group of folks who're also using another specific technology and it's probably going to be oddly skewed | 11:37:31 |
| Gwmngilfen | well, possibly, yes. the question is "does the userbase of VSCode distribute well over other characteristics like type-of-user or version-used?" and you're right, it doesn't but nothing does, really, and if you have a few you can weight with all of it | 11:59:46 |
| Gwmngilfen | this is why so often you'll see deomgraphic questions on surveys - because they already know the % of religion/ethnicity/sports-affiliation/etc for a given area from census data, and can use it to weight/ | 12:01:01 |
 remindbot | @room It's Bullhorn release day! Please share your news items with newsbot by 18:00 UTC to be included in this week's issue. Thanks! | 13:10:20 |
|  @diegorba:matrix.org left the room. | 16:00:24 |
|  wheatbeer joined the room. | 17:51:07 |
|  El y3rbA joined the room. | 22:29:22 |
| 31 Mar 2023 |
| El y3rbA changed their profile picture. | 01:21:27 |
