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.

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

Add Volunteers post type #887

Closed
3 tasks done
iandunn opened this issue Jun 2, 2023 · 8 comments
Closed
3 tasks done

Add Volunteers post type #887

iandunn opened this issue Jun 2, 2023 · 8 comments
Assignees

Comments

@iandunn
Copy link
Member

iandunn commented Jun 2, 2023

Related #550

Pilot sites want to take volunteer stats into account when measuring success, so we'll need a volunteer post type for that.

@StevenDufresne StevenDufresne added this to the Pilot Events: MVP milestone Jun 7, 2023
@StevenDufresne
Copy link
Contributor

StevenDufresne commented Jun 7, 2023

automatically draft volunteer posts

We save the w.org username to the volunteer post and that's all we do for tracking?

@iandunn
Copy link
Member Author

iandunn commented Jun 7, 2023

I was thinking there'd be another ticket that'd focus on generating any related reports; this ticket would just be where we create the post type so that the raw data exists in the system.

@StevenDufresne
Copy link
Contributor

Yep sure, just trying to understand how this ties together. Thanks.

@iandunn iandunn self-assigned this Jun 9, 2023
@iandunn
Copy link
Member Author

iandunn commented Jun 9, 2023

I've started building this, but I'm wondering how often organizers will actually use it. It could end up being seen as extra work to manage, if the only purpose is for stats. If they don't use it, though, then it wouldn't be useful for stats.

Adding the automation could make it easier to process the call for volunteers form, and have a canonical database of folks, but it'd have the same shortcomings as the speaker automation.

What specific stats do we want to have around volunteers? Another approach might be to ask organizers to just give us that aggregated data in the post-event survey. That way they could use whatever system works best for them. That might also have a low participation rate, though, and also inconsistent collection methods, etc 🤔

Do you have any thoughts @naokomc , @StevenDufresne ?

@naokomc
Copy link
Collaborator

naokomc commented Jun 12, 2023

We'd like to collect 2 things:

  • first-time vs returning volunteer
  • self-reported diversity data

From what it looks like currently, some pilot events will be using the current WordCamp website, Meetup.com event tool, or something completely different (e.g. Rosetta site news post + external form) for signup. Those events will need to use a survey.

For the pilot events that will use the new event website, we could ask them to use a certain method specified. For example:

  • Create separate ticket types for volunteers/attendees/organizers/sponsors
  • Include questions about past experience and diversity by copying the exact question & answer and making them mandatory

Does this sound like a good solution?
Will we need anything else for the stats to be pulled later?

@iandunn
Copy link
Member Author

iandunn commented Jun 12, 2023

🤔 if we use volunteer tickets, and the person marks themselves as a first time attendee, then we could assume that they're also a first-time volunteer. if they're not a first-time attendee, though, then we can't infer if they've volunteered before or not. So, we'd need a separate question for first-time volunteer if we take that approach.

We'd also need to ask for their w.org username too, in order to get the diversity data from their profile, and complete #550. Those aren't hard, but it is starting to feel like we'd be shoehorning the volunteer data into CampTix. I'm guessing many camps will also want to put out call for volunteers long before they're ready to start selling tickets, too. We'd probably have more flexibility and easier maintenance with a separate post type after all?

If we do use a separate post type, then we could have the site automatically create tickets for volunteers (and speakers) that are accepted. That'd take some work off of organizers, which may offset the added working of managing the post type. The automated ticket would require them using the built-in Call for Volunteers/Speakers forms and the process to publish accepted submissions, so updating the docs/mentoring would help.

🤔 I guess I'm leaning more towards going ahead with the post type. If there's not enough usage, can ask why organizers why, and iterate to remove pain points etc. What do you all think?

@naokomc
Copy link
Collaborator

naokomc commented Jun 13, 2023

We'd probably have more flexibility and easier maintenance with a separate post type after all?

This is true.

Maintaining the WP.org username information for each role will enable us to verify if a person previously held that role. This is a more reliable method compared to checkboxes.

If we do use a separate post type, then we could have the site automatically create tickets for volunteers (and speakers) that are accepted.

This ability will be very helpful (for speakers/sponsors too), since having people manually switch their tickets after being accepted has been very cumbersome and unreliable.

For pilot events, especially those ones happening in the early phase, we can be more flexible with the website and its tools. As I mentioned, organizers can always share the information via survey results.

@iandunn
Copy link
Member Author

iandunn commented Jul 26, 2023

I updated https://make.wordpress.org/community/handbook/wordcamp-organizer/first-steps/web-presence/custom-tools-for-building-wordcamp-content/ with info on the new post type.

That was the last thing needed for this.

@iandunn iandunn closed this as completed Jul 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: ✅ Done
Development

No branches or pull requests

3 participants