Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Collecting Feedback for CHAOSScon 2022 #291

Closed
ElizabethN opened this issue Oct 11, 2021 · 9 comments
Closed

Collecting Feedback for CHAOSScon 2022 #291

ElizabethN opened this issue Oct 11, 2021 · 9 comments
Labels
chaosscon Anything related to CHAOSS's conference

Comments

@ElizabethN
Copy link
Member

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!
@ElizabethN ElizabethN added the chaosscon Anything related to CHAOSS's conference label Oct 11, 2021
@ElizabethN
Copy link
Member Author

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.

@GeorgLink
Copy link
Member

GeorgLink commented Nov 2, 2021 via email

@geekygirldawn
Copy link
Member

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 👍 👎 . 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:
image

@GeorgLink
Copy link
Member

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?

@geekygirldawn
Copy link
Member

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.

@GeorgLink
Copy link
Member

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
Copy link
Collaborator

@ElizabethN can this issue be closed now that we have the CFP all done?

@ElizabethN
Copy link
Member Author

@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.

@germonprez
Copy link
Collaborator

germonprez commented Apr 11, 2022 via email

@ElizabethN ElizabethN mentioned this issue Sep 2, 2022
Closed
5 tasks
This was referenced Sep 5, 2022
Closed
Closed
@ElizabethN ElizabethN mentioned this issue Sep 12, 2022
Closed
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
chaosscon Anything related to CHAOSS's conference
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@ElizabethN @germonprez @geekygirldawn @GeorgLink