chaoss
Collecting Feedback for CHAOSScon 2022
We have successfully shipped CHAOSScon 2021, and we need a place to collect thoughts and feedback for next time. This issue will serve that purpose ✨ .
For our reference, the feedback survey is here: https://docs.google.com/forms/d/e/1FAIpQLSd6kzyyafJRTSa1D_xEH_T4tICbSJ-24j0dqsOVvlmOsLZwcw/viewform?usp=sf_link.
Other feedback is welcome in the form of comments on this issue. Thanks!
Summary of feedback survey is here.
Takeaways/Suggestions:
- More communication before event: in-person/virtual formats, use of Slack, schedule updates, coffee/lunch breaks, after conference activities, social media hashtag
- Increase promotion of the virtual live stream. Sign-ups for email reminders and additional information like slack channel and schedule.
- Make easier to find the Slack channel. Maybe show the slack channel on a screen so everyone can see what's happening there without having to open it on personal device.
- Have the schedule printed and posted in the room.
- More breaks: Add 2 minutes between sessions in schedule for changing speakers
- Shorten virtual talks: Keep virtual talks to 5-7 minutes only. The energy in the room dropped with each virtual talk. It's a great way to include more speakers who can't travel, but it's hard to do.
- More interactive sessions: Have more interactive, workshop-style, sessions for getting into the weeds on CHAOSS work. Maybe do 1/2 day talks and 1/2 day hands-on sessions.
- Roles - Have a dedicated social media person who shares pictures and tidbits throughout the conference and engages with others who are posting about the conference.
- Roles - Slack manager: Similarly, have someone dedicated to watching the Slack channel, compiling questions for the QA session, and seeding conversations there.
This is great feedback. I added it to the Handbook for next time: https://handbook.chaoss.community/community-handbook/community-initiatives/chaosscon#feedback-and-suggestions-from-chaosscon-na-2021
On Tue, Nov 2, 2021 at 8:04 AM Elizabeth Barron @.***> wrote:
Summary of feedback survey is here https://docs.google.com/presentation/d/1LDstSDo-vgRod0qVaYgVKaFVcXemoyPVVmEq3JMvkNs/edit#slide=id.gfb3032837d_0_0 .
Takeaways/Suggestions:
- More communication before event: in-person/virtual formats, use of Slack, schedule updates, coffee/lunch breaks, after conference activities, social media hashtag
- Increase promotion of the virtual live stream. Sign-ups for email reminders and additional information like slack channel and schedule.
- Make easier to find the Slack channel. Maybe show the slack channel on a screen so everyone can see what's happening there without having to open it on personal device.
- Have the schedule printed and posted in the room.
- More breaks: Add 2 minutes between sessions in schedule for changing speakers
- Shorten virtual talks: Keep virtual talks to 5-7 minutes only. The energy in the room dropped with each virtual talk. It's a great way to include more speakers who can't travel, but it's hard to do.
- More interactive sessions: Have more interactive, workshop-style, sessions for getting into the weeds on CHAOSS work. Maybe do 1/2 day talks and 1/2 day hands-on sessions.
- Roles - Have a dedicated social media person who shares pictures and tidbits throughout the conference and engages with others who are posting about the conference.
- Roles - Slack manager: Similarly, have someone dedicated to watching the Slack channel, compiling questions for the QA session, and seeding conversations there.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/chaoss/community/issues/291#issuecomment-957772287, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACDTSRO3Z5U6VTUVSWRAKK3UKADYHANCNFSM5FYOWKIQ .
-- Georg Link, PhD (he/him) TZ: US Central Time: US/Chicago
For the TODO Group OSPOlogy sessions, Ana has implemented the CFP as a GH Issue template. I wasn’t sure how well this would work until I really looked at it, and it’s fantastic! It has drop down boxes and everything you’d want for a CFP. You can see it by going here.
I was thinking that maybe we should try this for the next CHAOSScon? It has the advantage of putting everything where everyone can see it, so other people from the community could also comment on proposals or give them :thumbsup: :thumbsdown: . It might make our work as the selection committee a bit harder, since it doesn’t dump them into a nice spreadsheet for us to use for voting, but I don’t see that as a big barrier.
Here's a quick screenshot of part of it:
Interesting idea to use GitHub issues for CFPs.
Would all communication with submitters be through the issue or would we also ask for an email contact?
How would we deal with questions that ask for personal information and should not be public?
Interesting idea to use GitHub issues for CFPs.
Would all communication with submitters be through the issue or would we also ask for an email contact?
How would we deal with questions that ask for personal information and should not be public?
There are definitely pros and cons to either our existing approach or this one. The con for this one is that we can't really request confidential data, and we would probably need to ask people if they wanted to provide an email address publicly or whether they would prefer to receive communications via the issue. We could have a link to an accompanying Google form where people could reference the issue number and give us their email address and other personal info, but having people fill out 2 forms seems complicated.
The pro is that it provides more transparency and the opportunity for people outside of the selection committee to provide feedback on proposals.
I'm ok with using our usual method of Google Forms, but I thought it was an interesting idea to think about and discuss.
I also like the idea of a simple CFP process. Maybe we can design the process so we don’t need demographic details and are okay with only receiving submissions of what people are comfortable with sharing publicly. (I just saw Sophia's comment in Slack about CFP's sometimes containing information that is not public before the conference.)
@germonprez if it's ok I'd like to leave it open while we are still in the planning phase. There is other valuable feedback apart from the CfP process that I don't want to get lost.
No problem
On Mon, Apr 11, 2022 at 7:45 AM Elizabeth Barron @.***> wrote:
@germonprez https://github.com/germonprez if it's ok I'd like to leave it open while we are still in the planning phase. There is other valuable feedback apart from the CfP process that I don't want to get lost.
— Reply to this email directly, view it on GitHub https://github.com/chaoss/community/issues/291#issuecomment-1095005642, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFAGUDVRDNDCJLBO67QQP3VEQNGTANCNFSM5FYOWKIQ . You are receiving this because you were mentioned.Message ID: @.***>
--
Mutual of Omaha Distinguished Chair of Information Science & Technology Professor of Information Systems and Quantitative Analysis College of Information Science & Technology University of Nebraska Omaha CV: https://bit.ly/2kftONr
Vice President Omaha Parks Foundation
CHAOSS Board Member https://chaoss.community/ @.***
he / him / his