Topic: Contributor recognition, .org sites
Agenda: Updates re activity in this area.
- Theme directory Featured page
- Other? Add it in comments.
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!
We use this blog for status reports, project announcements, and the occasional policy debate. 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. There projects are suitable for everyone from newcomers to WordPress community elders.
You can use our contact form to volunteer for one of our projects.
Each week is devoted to a specific area:
• 1st — Meetups/other local events
• 2nd — Mentorship, diversity
• 3rd — WordCamps/conferences
• 4th — Contributor recognition, .org sites
• (5th — Virtual party)
Topic: Contributor recognition, .org sites
Agenda: Updates re activity in this area.
It’s short, and none of the questions are mandatory. Please post, tweet, tell your co-contributors/community members via any/all communication methods. Thanks. Here’s the link: http://wordpressdotorg.polldaddy.com/s/wordpress-contributor-experience-poll
Good news on the meetup.com front: the personnel change that had us in flux has turned out to be a good thing. Now that Laura at Meetup.com is handling the chapter program, she has agreed to let us do existing group roll-ins monthly rather than quarterly. This is great news, because the once-every-3-months thing was a pain in butt logistically, and sometimes meant that dues came up for renewal before the next roll-in (though meetup.com has generally been good about prioritizing people in that situation). With this new schedule, we can keep forward momentum going a lot easier from the moment someone applies to join the program.
Emails were sent from meetup.com to everyone on the current quarterly roll-in list. So far in this round, these meetup groups have been added to the WordPress account:
These groups were sent the opt-in form at the same time by meetup.com on 4/21 but have not yet responded.
I’m very pleased to announce this year’s cohort of Google Summer of Code students. We’ll be working with 5 students for the summer, spanning several areas of the project. Please join me in congratulating the following students on their acceptance into the program:
Once we’ve had a meeting with each of the students and their mentoring teams, a revised scope will be published so the community can check out the proposed projects. Each student will post weekly updates to an appropriate team blog to keep everyone up to date and to get feedback:
We’ll set up some livestreamed prototype demos at midterm so everyone can see the projects in action. In the meantime, congratulations to all the students!
The quarterly roll-in is a little behind. For some reason we didn’t get confirmation of our payment until April 8 (about a week later than expected), and the person who does the roll-ins of existing groups hasn’t been in touch (normally that happens immediately upon payment of the quarterly bill). I contacted that person and the person who runs the chapter program yesterday expressing my nervousness about the timing, especially since a couple of the groups joining the program had expiring dues and were marked in red on the spreadsheet. I’ll do everything I can to make sure no group has $$ trouble because of this delay.
There are 18 existing meetups waiting to be rolled in (some were from the last time who filled in the application so close to the end that they didn’t make it in that round). There are about half a dozen new meetup (no existing group) applications in process.
We’ll try a few different topics and time slots over the next couple of weeks to see what works best.
For organizers of existing groups who want to join the chapter account (or have questions because they’re not sure):
For people who want to start a new group on the chapter account:
Back in December, I proposed that instead of trying to recreate the 2012 community summit event, we try something different, and combine it with the official annual conference, WordCamp San Francisco (WCSF), for a variety of reasons (rather than restate those reasons now, I suggest re-reading that post). For the most part, people seemed to like the idea (as seen in comments), but there were a few people who did not like the idea, citing various concerns, so I tabled the discussion rather than start a big debate right before the holidays. Un-tabling!
The community summit in 2012 was an experiment on my part as to what an annual event could look like that centered on discussions rather than lectures (which fill the annual WCSF program). There were a lot of positive aspects to the event, in line with what was expected. However, there were some negative effects as well:
To that end, I’m proposing that instead of organizing another retreat-based, invite-only event at a separate time/place than the annual conference, we expand the annual conference to be more than just lectures. As I handed the WCSF planning mantle off to Andrea Middleton in 2012, I’ve been talking with her and Matt Mullenweg about how we could improve the WCSF event to incorporate some of the good things from the 2012 summit to make WCSF a true annual community event. Here’s the proposal:
With these two changes, WCSF would be the same amount of time it has been for years — 3 days — but would have more interactivity built into those days for people involved with the project than we’ve had in the past.
In addition, I would have us set up an extra 2 days for contributor teams to work together and talk about their goals, and to talk to other teams. Needless to say, this would be optional, but anyone deemed necessary to the team should be able to attend regardless of finances via the scholarship program. This brings us to 5 days. Both Andrea and Matt were amenable to this plan for WCSF this year — knowing that whatever we do this year we will learn from and iterate on in the future — so I’d like to address the concerns raised by Siobhan and others.
At the very least, I think it is worth trying it this way; if it feels like there’s a still a big hole after the event, we can revisit. That said, this is what I think is right for the project, and where I think the energy should be focused right now re annual events. If someone else believes an invite-only retreat-style event is necessary for the project’s success, I wouldn’t stand in the way of someone else taking that on and pitching their ideas to Matt.
We can discuss this proposal in the team chat today.
Team chat agenda for today, WordCamp/conferences-focused meeting.
@andreamiddleton: What else do you want on the agenda for today? Does anyone else have things related to WordCamps/conferences to discuss with the team?
We are now in the de-duplication period of the GSoC application process. This means we’ve submitted to Google our choices for which students we’d like to work with over the summer, as have the other 189 mentoring organizations, and now we’re in the process of figuring out which students should work where, in cases where a student was accepted by more than one project. We are not allowed to say anything about whom we’ve chosen until Google announces the accepted students, as the de-duprication period often shakes up those lists.
As each organization contacts other organizations and the students in question and choices are made, organizations that “lose” a student get to choose another to fill the slot. This can lead to a new duplication, which is why nothing gets announced until there are no remaining duplications. This process will last until Friday, April 18th, when the final de-duplication meeting will happen in IRC at #gsoc at 19:00 UTC.
Based on the outcome of that meeting, the official student list will be announced by Google on Monday, April 21, and at that point the community bonding period begins. If we don’t have any duplication issues, we’ll be accepting six GSoC students this year, but the final number won’t be set until that last de-duplication. When Google announces, we’ll announce our student/mentor matchups on our own team blogs as well.
You may have notices that the new profile design has slowly started making it’s way onto the live servers. Please note that it’s getting on there a little at a time, so please don’t start creating trac tickets to fix things, since chances are the thing you’re reporting just hasn’t been deployed yet. We’ll do a big public announcement when we’ve got the full design in place and a solid v1 backend working properly. Thanks!