Making WordPress.org

Opened 6 years ago

Closed 4 years ago

#4344 closed enhancement (fixed)

Remove irrelevant questions from Camptix livestream ticket sale options

Reported by: angelasjin's profile angelasjin Owned by:
Milestone: Priority: normal
Component: WordCamp Site & Plugins Keywords: needs-patch
Cc:

Description

Currently, all WordCamp tickets sold through Camptix ask attendees two questions:

  1. Whether they have any life-threatening allergies
  2. If they have any special accommodation requests

These questions are very important for attendees who attend the WordCamp in person, but they are unnecessary for people who purchase livestream tickets. Having these options for livestream tickets has also caused additional work for WordCamp organizers: if a livestream ticket purchaser ticks either of those options, the organizers need to sort through whether or not they actually need to respond to the requests. For WordCamps with a large number of attendees, this is added work for organizers.

Can we please remove these irrelevant questions for livestream tickets?

Change History (9)

#1 @coreymckrill
6 years ago

  • Keywords needs-patch added
  • Status changed from new to assigned
  • Type changed from defect to enhancement

Thanks @angelasjin !

I think the best way to do this is to implement a ticket “type” that can be selected when a new ticket is created. The types available would be from a defined list. Maybe they would be “physical attendance” and “virtual attendance” or something. We could then use logic to only include the accommodation and allergy questions for tickets with the “physical attendance” type.

#2 @hlashbrooke
6 years ago

Should we also remove the Code of Conduct agreement question from livestream tickets too? The CoC language all focuses on in-person events, so it's largely redundant for livestream tickets.

#3 follow-up: @dryanpress
6 years ago

@hlashbrooke I'd like to see the CoC remain and updated to better encompass online conduct. Someone in the livestream posting inappropriate comments on social media could be just as harmful as someone sitting in the audience posting the same content.

#4 in reply to: ↑ 3 @hlashbrooke
6 years ago

Replying to dryanpress:

@hlashbrooke I'd like to see the CoC remain and updated to better encompass online conduct. Someone in the livestream posting inappropriate comments on social media could be just as harmful as someone sitting in the audience posting the same content.

That's a good point. I guess the only difference there is we can't handle what people say on social media in the same way that we can at an in-person event, but yes - I agree that updating the code of conduct to cover online interactions would be a great thing to do.

#5 @dryanpress
6 years ago

@hlashbrooke Yep, definitely much less within our control, but think it just serves as a good reminder and protects from liability. I wish I was extrapolating from theoretical... but we updated our (independent) Meetup's Code of Conduct last year to include online behavior based on someone's behavior at WordCamp Phoenix and subsequent inappropriate behavior in the Arizona WordPress Slack.

https://arizonawp.net/about/

Last edited 6 years ago by dryanpress (previous) (diff)

#6 @iandunn
6 years ago

If we choose to build in different types of tickets, then this might dovetail with the proposal to add workshops as a special category of registration.

#7 @dryanpress
6 years ago

@iandunn I was originally thinking of making these meta instead of another unique object type. Think there are pros and cons to both approaches, is there a reason you were thinking of making these unique ticket types? I think the main thing, regardless of multiple objects vs. meta values is users should be able to register once and check boxes/select options from workshops during a unified signup process.

Happy to work on this once there's better consensus.

This ticket was mentioned in Slack in #meta-wordcamp by ryelle. View the logs.


4 years ago

#9 @ryelle
4 years ago

  • Resolution set to fixed
  • Status changed from assigned to closed

This was fixed by creating a Remote/Livestream ticket type in PR 386, which tweaks those questions to be more relevant for online viewing.

Note: See TracTickets for help on using tickets.