WordCamp Incubator Program v2: input on a new role name and a call for volunteers

When we launched the experimental WordCamp Incubator program, we didn’t know what to expect. We hoped that after attending a WordCamp where there wasn’t already a WordPress chapter account meetup group, WordPress enthusiasts would be galvanized into forming a community that would sustain itself in the future. This certainly happened in two of the three communities that hosted incubator events in 2016. Plus, SIX communities that applied to be part of the program ended up organizing new WordCamps with the support of our amazing mentors!

New iteration, new challenge

In 2018, we’d like to launch a v2 of the WordCamp Incubator program, but we have an added challenge this time: finding people to support/co-lead/oversee each Incubator event.

In the first iteration of this program, we assigned 3 fully-sponsored volunteer staff to provide leadership and support to our incubator communities. But since the number of events and communities that the global community team supports continues to grow so quickly, our full-time sponsored volunteer staff is already fully committed for next year (and then some), mostly with maintenance projects. Therefore, we need to come up with another way to provide the support that made the incubator program successful in 2016.

The job

This is a time-intensive volunteer role. We estimate that lead organizers spend about 170 hours on a WordCamp, and I figure that the folks working to support the growth of an Incubator event needs to dedicate about 200-250 hours over the planning cycle. The job is that of co-organizer, mentor, and ambassador — since it’s probable that no one you’re working with has ever actually attended a WordCamp. You’re working as a community founder in a community that isn’t your own, which requires a lot of sensitivity, experience, and wisdom. The person absolutely must have experience organizing WordCamps, preferably more than one, as well as experience mentoring WordCamp organizers. Experience collaborating with people from other cultures is also very important.

What do we call this job?

Because this is such a distinctive role, I think that going forward, calling these folks “incubator mentors” isn’t a good idea. Mentorship is part of this job, but typically I think a mentor probably spends 1-4 hours a month working with their “mentee” WordCamp, whereas this role is more likely to require 25 hours a month. So! we need a new name for this program role. Here’s some very initial brainstorming that happened in Slack today.

1) Please comment below with your suggestions for a good name for this organizer-coach-midwife-counselor-guide role! I’m certain the right word is out there, just waiting to be found.

Where do we find these people?

My hope is that this challenging job will be an exciting opportunity for experienced WordCamp organizers that particularly enjoy the “start up” phase of the community, and who have successfully transitioned out of active leadership in their local community. (This is frequently “start a community from scratch” work, and the communities have to be self-sufficient at for the project to be effective.)

As mentioned above, this role is very time-intensive and high-touch. Not everyone can commit 250 hours in a year to a volunteer role, and I suspect that we may need to lean on volunteers who might be sponsored part-time to work on the incubator program. Maybe we could even help interested volunteers pitch their companies on sponsoring a certain number of hours a week to work on an incubator event.

Alternately, perhaps a team of 5-6 people would be interested in working with multiple incubator communities over a period of a year, and share some of the workload. (This makes me a little nervous, because sometimes when everyone is in charge, it means no one takes responsibility, but maybe there could be a rotating lead position on that team?) I’m open to suggestions.

2) Do you have some ideas of ways we could recruit people to take on this work and ensure their success? Please share your ideas in a comment on this post!

3) Interested in this role for 2018? Please also comment on this post to let us know!

Next steps

Once we figure out A) a name for this incubator-mentor-guide-organizer role and, B) a solid plan for recruiting enough incubator-mentor-guide-organizers to support a v2 of the Incubator program, then we can open up a call for communities who’d like to be considered as sites for a 2018 incubator WordCamp.

I’d like to set us a goal of completing our discussion by October 6, with an eye to publishing the results by October 11, and maybe we can even make the call for incubator communities by October 16.

 

#community-mentors, #incubator, #wordcamps

Gutenberg on WordCamp sites?

A couple of weeks ago, @jorbin suggested that we install and activate Gutenberg on the WordCamp.org network. This would make it available on every WordCamp site to use for creating/editing posts and pages. It would not be initially available to use for other post types, like speakers and sessions, because these use meta boxes for some of their content, which are currently an unresolved issue in Gutenberg.

Some WordCamp sites only have a couple of users (generally the lead organizers), while others have scores. It would be an opportunity for these folks to try out the new editor with a real use case, get a feel for how it works, and help the Gutenberg team as it continues to improve the plugin.

It would, of course, be completely optional. Since the Gutenberg plugin is intended for testing and feedback, it lives on a separate screen and the normal editor would still be available.

So the question for the community is, should we activate Gutenberg on WordCamp sites?

Weekly Updates

Hello to all our Deputies, WordCamp organizers, Meetup wranglers, and WordPress Community builders! You were probably hard at work this weekend. Tell us what you got accomplished in our #weekly-update!

Have you run into a roadblock with the stuff you’re working on? Head over to #community-events or #community-team in Slack and ask for help!

X-post: Agenda for WordCamp.org ticket scrub on September 26th

X-post from +make.wordpress.org/meta: Agenda for WordCamp.org ticket scrub on September 26th

Weekly Deputy Report: 15 – 21 September 2017

The stats for this report are taken from the weekly Help Scout reports and, as such, only reflect the activity inside Help Scout. While this covers the majority of our community work and interaction, it excludes a few things: most WordCamp mentorship discussions, all WordCamp application processing, and any interactions in Slack (Office Hours, general chatter, answering questions, etc.) – those are all handled on other platforms.

Here are the stats for this past week (15 – 21 September 2017):

This week we sent 104 emails and helped 66 individuals. Of those, 48 of the tickets were successfully resolved.

The deputies who handled those tickets in Help Scout this week are:

@adityakane
@andreamiddleton
@camikaos
@coreymckrill
@courtneypk
@hlashbrooke
@jerrysarcastic
@psykro
@chanthaboune
@kcristiano
@laryswan
@leogopal
@enigmaweb
@mariaojob
@imnok
@remediosgraphic
@_dorsvenabili

A huge thank you to all of these individuals for their hard work in supporting the WordPress community this week – especially some of the new names in there!

#deputies #report

WordCamp regulation OK/NG case study to handbook

Hello, Community Team!

I have a suggestion to add examples, (virtual) case studies, or FAQs about the WordCamp rules in the handbook. Case studies in real life or simulation questions and answers can help people understand things better.

I’m particularly concerned with “Agreement among WordCamp Organizers, Speakers, Sponsors, and Volunteers”, especially this line “don’t promote companies or people that violate the trademark or distribute WordPress derivative works which aren’t 100% GPL compatible.” There’s been discussion what “promote” means exactly.

I discussed with @mayukojpn and @nao about this.
If you think that this proposal is good, I will gather examples.

Thoughts and comments welcome.
Thank you all!

Community Team Chat Agenda | 21 September 2017

Howdy, Team!

Our bi-monthly Community Team chat is happening this Thursday, 21 September. Meeting times are 08:00 UTC and 20:00 UTC in #community-team on Slack – we use the same agenda for both meetings in order to include all time zones.

Heads up! Many of the people who usually lead discussion in these chats will be away tomorrow (including me, Hugh, and Rocio). So I’m making an open invitation for any deputy who plans to attend, to leave a comment on this post (or just speak up in the chat) if they’re willing to lead the discussion. 🙂

Agenda

  1. Deputy check-in (progress and blockers to progress)
  2. Decision making process discussion summary and proposal
    This post is still open for discussion; if you have not already commented, please do so! 🙂 Another big thanks to @francina for putting his proposal together.
  3. P2 posts:

If you have anything else to add to the agenda, please add it by commenting on this post! 🙂

X-post #ccoc meeting notes from…

X-post #ccoc meeting notes from today. Please leave all comments on the original post.

CCOC project meeting notes –19th September

GPL/Trademark primer proposal

UPDATE: It would appear this primar already exists, and already covers things that this proposal was going to manage, so please ignore this.

As more and more people become aware of WordPress and the GPL, it would be useful that the often difficult to understand legal terms of the open source license be documented in some form of GPL/Trademark primer.

primer (n) an elementary textbook that serves as an introduction to a subject of study or is used for teaching.

(I mostly posted the above because I had to look it up myself)

This was highlighted even more to me in a discussion about a WordCamp sponsor request between myself and @kristiano, where he raised the idea of a GPL/Trademark primer. As I see it the primer would serve multiple purposes, but the two that stand out the most are

  • as a way to better educate those new to the GPL
  • as a tool to be used by meetup/WordCamp vetting processes to confirm 100% GPL compliance

At the moment we have the 100% GPL Vetting checklist, this would probably serve as a companion document to that, and it might even be useful to link to sections of the primer at each step in the checklist.

I’d be happy to start writing such a document but I will need some assistance from my more experienced community members. It would also be useful to have a discussion around what format it should be in and where best to keep this primer.

Comments/suggestions/questions welcome.

 

Proposal for permanent change of word for Code of Conduct

A couple of days ago, there was a discussion on Slack #community-events about how communities in India address anti-caste discrimination for Meetups and WordCamps. Currently the word “caste” is not part of or mentioned in the Code of Conduct.

Discrimination on caste basis has been a historical problem for societies across India and much of South Asia. For example, in India there is a law against discrimination, yet bias and exclusion happens regularly. More context and information can be found at the Wiki article Caste System in India and Affrimative action.

I propose we add the word “caste” in the code of conduct wording.

The change will be from:

WordCamp CITYNAMEHERE believes our community should be truly open for everyone. As such, we are committed to providing a friendly, safe and welcoming environment for all, regardless of gender, sexual orientation, disability, ethnicity, religion, preferred operating system, programming language, or text editor

to

WordCamp CITYNAMEHERE believes our community should be truly open for everyone. As such, we are committed to providing a friendly, safe and welcoming environment for all, regardless of gender, sexual orientation, disability, ethnicity, religion, caste, preferred operating system, programming language, or text editor

This change will acknowledge that discrimination or exclusion on caste basis is not acceptable at meetups, WordCamps and other WordPress events. Apart from serving as a deterrent, it would empower participants of WordPress events to be able to address violations in a more formal way.

Thoughts and comments welcome.

#code-of-conduct