Recent Updates Toggle Comment Threads | Keyboard Shortcuts
There’s been some confusion over the past forever on the best way to submit a payment request for a WordCamp Vendor. That confusion is a thing of the past! Here’s a step by step how to on submitting your payment requests. If there are additional questions or you feel something could use a bit of clarification let me know so I can update!
The most popular choice was to let organizers build a new theme to meet the specific needs of WordCamps. We’ll also be able to add new page templates to the theme in the future, provided that they meet the criteria discussed earlier.
Once the theme is done, it’ll be reviewed by the Meta team for any security issues, and by the Deputies for general appropriateness, and then made available to everyone on WordCamp.org.
Building a Team
The first step will be to put together a team of organizers who want to build the new theme. Obviously it should have designers and developers, but it could also benefit from UX and accessibility specialists, and of course lots of people to test it.
If you’re interested in being on the team just leave a comment below, and if you know someone who may be interested, please send them a link to this post.
We’ll need someone from the team to take the lead role, and make sure everything is organized and moving forward. Once we see who’s on the team and what everyone’s skills are, I’ll look for someone who’d be a good fit for that.
The team will have the freedom to build whatever they think is best, but I think we should also agree on some guidelines to ensure the project reflects our community’s values and standards.
- The team should be welcoming and open.
- It should be a collaboration from across the community, rather than a small group from one city or company.
- In practical terms, that means development should occur on an open platform like GitHub, and communication should take place on this p2 and in the #events channel on Slack.
- The theme should serve the many, not the few.
- The goal should be to make something that meets the needs of most organizers, rather than just the needs of the individuals on the team.
- The focus should be more on making it a flexible starter theme for organizers to customize, rather than just something that looks beautiful when it’s first activated. It can (and should) have a great initial design, but the primary goal is to let organizers take it and easily create something that looks totally different.
- The team should solicit feedback from lots of camps to make sure that their needs are addressed.
- The project should not be a design-by-committee.
- Input from organizers and contributors should be weighed heavily, but ultimately the team lead should be the one making the final decision on what choices will have the best outcomes for the entire community.
- The theme should meet the relevant standards:
- It should be a theme only.
- It shouldn’t bundle custom post types, shortcodes or other functionality.
- Having said that, the team should feel free to contribute as much as they’d like to the existing plugins, provided those contributions will also work with the other themes on WordCamp.org.
- It should be thoroughly tested.
- Because it will be customized by lots of organizing teams, we’ll need to maintain backwards compatibility, which will limit the kinds of changes that can be made in the future. That makes it very important to test well up front.
- “Testing” in this case doesn’t just mean testing the theme’s internal correctness, but also testing how easy it will be for other organizers to create new designs on top of the theme.
- It should be beta-tested with a handful of camps before launching to everyone. If fixing any problems are found during the beta period that would require breaking backwards compatibility, then we’ll be able to do that and manually update the beta sites.
If anyone thinks there should be any changes to those guidelines, please leave a comment so we can all discuss it.
Everyone is encouraged to participate in the discussion, but I’m pinging the people who took part in the previous discussions to make sure they don’t miss the post: @ryelle, @harbormark, @chanthaboune, @nvwd, @kovshenin, @rafaehlers, @davidjlaietta, @dimensionmedia, @iandstewart, @miss_jwo, @topher1kenobe, @jenmylo, @georgestephanis, @valeriosza, @jb510
- The team should be welcoming and open.
- Deputy agreements
- Purpose of chats/timing
- New deputy onramp plan/update
- Budget proposal
We may or amy not get through everything, depending on who attends. Add other agenda items in the comments.
Way back in October at the community summit and then during the team meetup days, we talked about how to deal with inappropriate behavior by people at WP events and contributors on WordPress.org. We talked about the need for an escalation team that could handle sensitive issues like harassment reports or complaints around “poisonous people”/ongoing bad behavior in the project, but we didn’t actually create it. In the past week or two we’ve had a few issues come up that fall into this category, so we’re firing up an escalation team.
I assembled a group of people from various contributor teams who have been involved in discussions around this stuff and/or related issues like sexism, racism, or homophobia in the project community. We’ll all sign a deputies’ confidentiality agreement (once we finalize that agreement today after the team chat), so that people reporting things can rest assured that sensitive issues being reported won’t wind up on Twitter. The people on the first round escalation team will be: me, Sam Sidler, Helen Hou-Sandi, Tammie Lister, Aditya Kane, Morten Rand-Hendriksen, and Jenny Wong.
We’ll set up a reporting form on a new make blog so that the form responses will only be seen by the escalation folks who’ve signed confidentiality agreements. We will publicize it once it’s in place, and add it to the code of conduct as a reporting tool.
We have WC organizers sign agreements outlining some shared assumptions and rules. As we have started more deputies, we discussed having deputies sign a similar agreement but tailored to the role (most importantly, confidentiality). I wrote up a draft agreement here:
We would have deputies digitally sign these the same way we do WC organizer agreements to ensure that everyone is on the same page. Take a look and let me know if you see anything you thing ought to be changed, or anything you think should be included. We can discuss further in the team chat tomorrow, but comments here would be helpful in advance. Thanks!
Applications for WordCamp US 2015 have officially closed! We received submissions from Chattanooga, Chicago, Detroit, Orlando, Philadelphia, and Phoenix. All applications are being reviewed and carefully considered and we’ll be responding to organizers as soon as possible. I’ll keep you all updated as more details are available.