If you are not attending WCSF this year, you can ignore this post. If you are coming and planning to participate as part of the support team, please click through and read it all.
Updates from Jen Toggle Comment Threads | Keyboard Shortcuts
Anyone planning to attend WCSF this year from the support team, please read the post at https://make.wordpress.org/updates/2014/09/08/wcsf-tickets-and-stuff/ for information about WCSF ticket sales and the contributor days following the main conference. Please click the link and read that post *before* asking questions on this thread.
If you are planning to attend the support team meetup but I have not been in touch with you regarding hotels/travel dates, please ping me in IRC (jenmylo) or shoot me an email (same username @wordpress.org) so I can include you in the planning.
Howdy again, folks. We’re working on making sure we have enough room blocks to make sure all the contributors who are coming in October can get a decent rate (or have a room provided by us if needed). Some of you replied to my post from last week and filled in the survey so I’d know you were planning to come, but some haven’t. I just want to make sure we count everyone. For example, @jdembowski, @podz, @clorith, and @jerrysarcastic didn’t fill in the survey. Maybe you guys don’t plan to attend due to timing conflicts or other reasons, or maybe you do but didn’t fill in the survey. Help me help you!
Hit the survey if you are an active member of this team so we can count you and see if you’d be able to stay for the whole time etc while we are creating room blocks. If you are not going to attend at all, please leave a comment on this post saying that and I won’t bug you anymore. If you would come but are concerned about the cost, hit the survey to be counted, and then go fill in the application for travel assistance. We have a budget for this, so let’s not allow money to prevent active contributors from attending.
If you didn’t read the post before, the plan is:
Sat/Sun — WCSF conference
Monday — community summit
Tues/Wed — team meetups (i.e. the support team being together in a place to talk issues, make plans, work together, etc)
Heads up, support team! We’re getting ready to publish details about the plans for WordCamp San Francisco this October (which includes a mini team meetup), so if you’re thinking of attending, please read the post at https://make.wordpress.org/updates/2014/06/12/wordcamp-san-francisco-travel-contributor-days/ and take the short survey linked at the end of it so I’ll know how many team members to plan for (don’t worry, this isn’t a commitment or anything, I just need to get some rough numbers for budgeting purposes). Thanks!
I saw Jan’s mention of the wp-forums list in the weekly update, and as I’m on the list I’ve paid attention to how it’s used, both as a call for a gut-check/backup, and as a bit of a place to vent. As one subscriber mentioned recently, the list is not just moderators, and anyone can join, and all of it’s archived. So what feels like it’s more private than this blog maybe isn’t really. Any time I see language there that’s a little more insulting or dismissive (generally about bozos/bad actors in the forums) than is really comfortable/appropriate for something being publicly archived I cringe a little bit.
There are 331 subscribers to the wp-forums list, and there are 259 subscribers to this blog. Given that the mailing list is publicly archived, but in a way that makes it a pain to look things up and has no connection to this site, I wonder if it might be time to transition away from the list to something that actually gives you the privacy-among-moderators you desire when something more sensitive needs to be discussed and keeps the discussion in one main place?
What we do over on the make/systems blog has kind of the same compromise. We post most things publicly, but when there’s something sensitive, we post it as Private so that only people with x role on the blog can see it. Maybe that would be a good alternative? Just wanted to throw it out there as an option.
Cross-posting to multiple teams, so apologies if you’ve seen this on another Make site already.*
There are a few days left to submit proposals to OSCON. It would be great to see the sessions there that are about WordPress actually being presented by people involved in the project, so I’d like to encourage/urge/beg some of you to submit a proposal based on your involvement in the project and/or the issues you’ve tackled on the team in the past year.
Almost everyone there has heard of WordPress, and many OSCON attendees use it for personal sites, but the way it gets talked about by the people giving WP-centric presentations, you’d think we were still the little blogging tool that could from 2003. It would be awesome if this year we could change that impression of the software and the project.
The submission deadline is January 30, and the event itself is in Portland, OR July 20-24, 2014. To apply to speak at OSCON, go to http://www.oscon.com/oscon2014/public/cfp/308
*If you are active enough on Make that you’ve seen this post in a couple of places, that suggests to me that you are super-involved in the WordPress project and probably have some interesting stories/insights/experiences worth sharing at OSCON, so go apply!
Howdy support folks! I was just talking to @coffee2code about .org profiles, and one of the things I’d like to see happen this year is for there to be one .org profile instead of 2 to reduce user confusion. To that end we’d need to be able to do all the current support profile stuff, and to *that* end, I think we’d need to be on up-to-date bbPress.
We’ve talked about updating a number of times in the past since the plugin came out. The last time we had this conversation, the high-level agreement was that yes, running current software is good, but the current bbPress plugin has changed some of the workflow stuff that would be annoying for the support team to have to work around. Let’s kick this off!
@ipstenu: you ran down the things that made you say no to bbPress upgrade last time, could you repeat them so we can identify the things we’d need to discuss and/or put in a plugin to make upgrading bbPress on the support forums feasible from the team’s perspective? Let’s not talk about infrastructure stuff here, that’s the /meta domain. Just want to identify any features/workflow changes that would be a problem if we upgraded, so we can spec out a plugin to address those things before we do anything else.
Hi support team. I would like to include Support in our Gnome participation this summer if there are any applicants interested in working in the forums etc over the summer. @ipstenu and/or other experienced team members: Head over to https://codex.wordpress.org/Gnome_Summer_Program_for_Women#Support and fill in project ideas (optional, I made a default idea that basically covers answering questions and beefing up support docs) and info on whoever from this team is willing/able to mentor an intern (ideally we put more than one mentor with each student so the time commitment isn’t too heavy). No idea yet how many student slots we’ll get.
People seemed to like the idea when I pitched it. Can we pick a weekend to do it? Having at least 2 weeks notice would be good so people can clear time in schedules, read up on docs if they want, etc. Maybe weekend of February 15?
Hi Support Team! A bunch of things today….
Welcome Training to Support
At the community summit, we went a little bit team-creating-crazy. As such, we splintered people into groups (like docs out of support) rather than splintering into projects within larger teams. For Support, this meant that electing team reps was especially hard, since the people getting votes were repping other teams.
One of these new teams, Training, started with excitement but then petered out with no activity for a couple of months. The solution to these two issues seemed pretty clear: merge Training back into Support, and have Christine Rondeau serve as the 2nd team rep. @ipstenu was in favor, so there we go. Welcome Christine back to the fold!
Christine will be working closely with the Community Outreach group, and we’re starting to plan our first training project already. It’l be focused on Troubleshooting WordPress, aimed at leveling up people to the point that they can do more with WP professionally, and could be more confident contributing to forums. She’ll undoubtedly be asking you all for ideas and help. Note: in line with the diversity initiatives, we’re going to do this first workshop for women, a la railsbridge. It’ll also get posted online for all and sundry.
I’ve been scouring every open source project’s community sites to see how they approach things, and one had a great concept that I want us to
stealmodify, use, and redistribute. The idea was this:
Weekend Project: Become a Contributor
We’ve done things like this at WordCamps (usually on dev day, and mostly focused on contributing to core), but what I was thinking of for support was something not too intensive: 20 Questions.
20 Questions Proposal:
- Publicize the weekend project to become an official wp forums contributor, called 20 Questions.
- People can sign up to be part of the weekend contributor drive. Current volunteers (approved as knowing their stuff) will be the mentors.
- Their goal is to answer 20 questions successfully (mentor says yes, good answer) during the weekend before the cutoff time.
- Keep at least 1 support person in IRC channel for team at all times during the weekend (make schedule in advance).
- At cutoff, tally the results! People who got at least 20 right are officially congratulated and welcomed as support contributors. We can make a graphic they can put in their sidebars or something maybe. People who didn’t make it are thanked for their efforts, and pointed to resources to help them level up. The person with the most questions answered gets a prize. The person who answered the hardest question gets a prize (so they aren’t incentivized to just do easy ones). We can do wp swag and/or WC tix for prizes.
What do you guys think? I think it would be super fun.