Welcome to the official blog of the community/outreach team for the WordPress open source project!
This team oversees official events, mentorship programs, diversity initiatives, contributor outreach, and other ways of growing our community.
If you love WordPress and want to help us do these things, join in!
Getting Involved
We use this blog for policy debates, project announcements, and status reports. Everyone is welcome and encouraged to comment on posts and join the discussion.
You can learn about our current activities on the Team Projects page. These projects are suitable for everyone from newcomers to WordPress community elders.
You can use our contact form to volunteer for one of our projects.
Communication
We have Office Hours four times a week in the #community-events channel on Slack: Mondays & Wednesdays 22:00 UTC, Tuesdays and Thursdays 9:00 UTC.
We also have regular Community Team meetings on the first and third Thursdays of every month at 11:00 UTC and 20:00 UTC in #community-team on Slack (same agenda).
Events Widget
If you have questions about the Events and News dashboard widget that came out in WordPress 4.8, please read this FAQ!
Yes yes yes
Thanks!
No idea about how to phrase it, but definitely yes to not leave people hanging
I love this – better and more immediate communication with applicants would be hugely valuable.
Using the API would require a bunch of dev time that we don’t really have available, but this same thing could likely be achieved by simply emailing the applicant and then CCing (or BCCing) support@wordcamp.org, then we use an HS workflow to tag and handle appropriately. It would have the same effect with essentially zero development hours.
I like this approach! Not only because we don’t have dev time, but also because it simplifies the functionality overall. The only thing we lose when not using API is automatically updating the HS ticket link to tracker.
Hopefully, you didn’t mean that we’d send those emails manually 😅
+1 – I like this approach too!
I think this is a great idea. We can see a lot of people complaining lack of action. In fact the action is being taken in the background. A quick email to inform them the status will be very helpful.
+1
I was unable to handle many of the reviews and was worried about making the applicants wait.
I think this is good idea!
Yes, it would be a great idea!
Giving this another +1! Not everyone understands the vetting process, and people can be impatient. More communication, the better!
Thanks a lot for brainstorming about this @sippis & @adityakane
About:
I’ve just checked the WordCamp/Meetup application code from the Meta repository because I was almost sure we already receive a notification when the application has been successfully saved in database. Here’s the message built by
Event_Application->notify_applicant_application_received()
:You can probably edit this method to add a
Bcc
header. So far the existing header is setting the Reply to:$headers = array( 'Reply-To: support@wordcamp.org' );
You could simply edit this in favor of:
$headers = array( 'Reply-To: support@wordcamp.org', 'Bcc: support@wordcamp.org' );
To automatically update the WordCamp/Meetup post type with the HS ticket url, this probably require some more development to use their API.
About the other parts, as I’m not used so much to HelpScout, I don’t really see the benefits, but I trust your expertise 🙂
I do see a benefit about having all the log data in the WordCamp/Meetup Post Types: you can directly view the chronological informations about the city, searching in HS is not that great for this part imho (but I’m probably off topic 🙂 ).
Ha, true! Even easier to add those automated messages when the only real dev time needed is to add that Bcc. Thanks for digging this information 🙂
If deputies agree that BCCing
support@wordcamp.org
would help with coordination and communication, and if that can be done without leaning on our limited developer time, then I think we should go ahead with it! Who can volunteer to report back on whether the experiment was successful in 3-6 months? 🙂I could volunteer to report back in 3-6 months 🙂
I really like this process! Great job, Timi! @sippis
Now that I think of it, I feel we have also a small gap between vetted application that is moved to orientation and sending the email to schedule the orientation. Should we send a message to the applicant when their application is moved? Telling that someone will contact them shortly to schedule the orientation.
That might be another process change and another p2 post I think. Would it be useful to actually see how this change goes and tweak it further with more changes to the workflow?
Yup and yup! Let’s keep this in mind and check back in 3-6 months after we have implemented the first step.
I think it’s fantastic. It has to be done.
I love the amount of interest in this topic, but I’m now confused about the new “final” process that we’ve collectively landed on. 🙂 Can someone re-state it for me? #lazyweb
I was thinking the same. Really in favor of improving communication with applicants though as I know how frustrating the process can be when it’s a busy application time.
Additionally it sounds like some things that could help keep us on our toes in terms of getting those responses out.