Tag Archives: proposal

Destiny Kanno 8:04 am on August 14, 2026
Tags: proposal,   

What Comes After WordPress Credits

WordPress Credits is working. Students around the world are contributing to real projects, earning academic recognition, and graduating with a WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ profile they can point to. What we have not built yet is what happens after that.

Right now, graduates leave the program with no defined next step. That means a lot of the momentum we built together such as the onboarding, the mentorship, the contribution work, stops at the exact moment a graduate is most capable of giving something back.

This proposal is our attempt to change that: Proposal: WordPress Credits Graduate Retention Program

The tracking issue for this work is on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/: https://github.com/WordPress/Community-Team/issues/1083

What We Are Proposing

We want to move WordPress Credits from a one-time experience to the first step in a longer contribution and career pathway. The proposal has three phases, starting with lightweight infrastructure changes and building toward a self-sustaining pipeline.

Main takeaways:

Give every graduate a clear next step. Right now the wrap-up flow ends without directing graduates anywhere specific. We want to change that with discipline-specific routing: dev-track graduates get pointed toward a WordPress Developer Certification and jobs.wordpress.net. Other tracks get equivalent routing based on what they contributed during the program.

Build a credential pathway graduates can see. The arc we are working toward: WordPress Credits (contribution program) → continued contribution → Developer credential received → ecosystem opportunity. We want graduates to be able to see the full path at the moment they finish the program, not discover it piece by piece after the fact.

Ensure students see their place in our contributing community. The arc we are working toward: WordPress Credits (contribution program) → continued contribution → peer mentoring → community leadership

Create scoped graduate contribution projects with Make teams. One of the most consistent barriers to returning is not knowing where to start. We want to work with Make WordPress teams to identify and tag real, appropriately scoped tasks that graduates can pick up. These are not new contribution areas — they are existing work made more accessible as a defined entry point.

Connect graduates to ecosystem opportunities. We are in conversations with ecosystem companies who have expressed interest in the WP Credits talent pipeline. The model we are exploring: companies fund certification exam seats for graduates, with one verifiable post-graduation contribution unlocking the seat. In return, companies get first access to graduates who pass and warm introductions to strong candidates. We are also pointing graduates to jobs.wordpress.net, where their WordPress.org contribution profile functions as a verified, public portfolio.

What We Are Looking For from the Community

This proposal touches several parts of the WordPress community, and we would love input before we move into execution:

Make team members: We want to collaborate on scoped graduate contribution projects: real tasks your team needs done, tagged as appropriate entry points for graduates returning to contribution. If you are on a Make team and interested in being part of this, please comment below or reach out in #wpcredits.

Ecosystem companies: If your company hires WordPress talent and is interested in exploring the exam seat model, we would love to talk. You can comment here or reach out directly.

Experienced contributors: If you have been through a structured contribution program yourself, whether WordPress Credits or something similar, we would love to hear what would have brought you back after graduation, and what would not have.

The full proposal includes a phased timeline, a tiered definition of what “returning to contribution” means, a 25% Tier 2 retention target for the dev-track pilot (benchmarked against comparable open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. programs), and a research foundation grounded in what has worked at LFX Mentorship, Outreachy, and GitHub Campus Experts.

We are not building everything at once. Phase 1 is infrastructure and one re-engagement message. Phase 2 is the dev-track pilot. Phase 3 is expansion to other tracks.

Feedback at any of these stages is welcome.

Questions or thoughts? Comment below or join the conversation in #wpcredits on the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.

Props to @peiraisotta for reviewing this post and proposal, and @celigaroe @francescodicandia @roblesloaiza @alanabwarner for reviewing the proposal.

Tags: #wpcredits, #proposal

Corey Hall 8:42 pm on July 24, 2026
Tags: , proposal   

Proposal: Bringing Back the Meetup Organizer Newsletter

The Meetup Organizer Newsletter has been quiet since July 2025. Huge credit to @bjmcsherry, @josvelasco, and @peiraisotta for carrying that one.

As we’re all thinking hard about reconnecting communities, a regular events roundup feels like something worth having again, and I’d like to help bring it back.

I’ve been getting more involved in community events (just got approved to organize a meetupMeetup Meetup groups are locally-organized groups that get together for face-to-face events on a regular basis (commonly once a month). Learn more about Meetups in our Meetup Organizer Handbook. in my area 🙌🏻), and I want to lead the charge on getting a V1 out.

What I’m thinking for V1

Keeping it simple to start: a monthly post highlighting upcoming and recent events across meetupsMeetup Meetup groups are locally-organized groups that get together for face-to-face events on a regular basis (commonly once a month). Learn more about Meetups in our Meetup Organizer Handbook., WordCamps, Campus Connect, and the “next gen” formats, with the cool things organizers are actually doing front and center.

Keeping it sustainable

From what I understand, the old one lapsed partly because it was a lot to put together by hand each month, and that got hard to keep up. One thing I’d like to use is SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/’s built-in AI, Slackbot. It can search across our event channels and pull together a surprisingly solid first draft in minutes. The idea is to let it do the heavy gathering, then a human pass to polish, fact-check, and pick photos, so it never falls entirely on one person to write from scratch.

Next steps

I’m going to build a V1 and get a first issue out. To start, I’m planning to pull event updates from a few channels: #community-events, #campusconnect, #community-team, #student-clubs, and #contributor-day. I’ll share the first draft next week, and I’d love your input, now or once the draft is ready, on two things:

  • What made the old newsletter useful, or what you’d change.
  • Other channels or sources I should add.

And if you worked on it before, I especially want to hear from you.

#highlight, #proposal
Juan Hernando 6:54 pm on July 23, 2026
Tags: coworking, , proposal   

Rethinking our Monthly Team Meetings

The problem

Over the past months we’ve tried two meeting slots at different times, then a 12-hour open window, hoping to catch more people across timezones. Neither change moved the needle. Attendance and participation remain low, and, as we discussed openly in the April meeting, most of the value of these meetings can already be absorbed by reading the agenda or the recap afterward. If a meeting can be fully replaced by a P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org post, it’s not really a meeting anymore.

We (the 2026 Team Reps) have talked this through and want to propose splitting what today is a single monthly meeting into two separate, more focused things.

The proposal

1. A monthly written update (unchanged in spirit, clarified in purpose)

We’ll keep publishing a monthly post at the start of each month summarizing what the team has been working on: policy changes, WordCamps, meetupsMeetup Meetup groups are locally-organized groups that get together for face-to-face events on a regular basis (commonly once a month). Learn more about Meetups in our Meetup Organizer Handbook., Campus Connect recaps, education programs, and anything else worth surfacing for people who can’t follow every P2 post or SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ thread.

What changes: this stops being “the agenda for a meeting” and becomes its own thing: a monthly digest, written by a different volunteer each month. We think this is a great low-friction way for people to start contributing to team coordination without needing to run a live session.

2. Coworking sessions

Instead of a status-update meeting, we want to try live coworking sessions: blocks of 1–2 hours where a group works together, in real time, on an actual team task.

Rough shape:

  • Short kickoff (5–10 min): whoever’s hosting explains what we’re working on that session and why, and takes quick questions.
  • Focused work blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.: everyone works (same or related tasks) with the channel/call open for “does anyone know how…” questions as they come up.
  • Wrap-up (10–15 min): quick share of what got done, what’s blocked, and what needs follow-up.

Why we think this could work

The coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. insight from the discussion was that people don’t show up for information they can get elsewhere, they show up when there’s something to do together, or someone to ask in real time. A status meeting competes with reading a P2 post, and loses. A working session doesn’t have that competition, because you can’t “read” your way into having helped triage the backlog.

We’d love feedback before taking this further:

  • Does the split between “written update” and “coworking” make sense to you?
  • Any specific ideas about the coworking sessions format?
  • Any concerns about coworking sessions being harder to join for volunteers in less common timezones (worse than a single meeting would be, since we’re not proposing multiple slots yet)?
  • Should we pilot this for one or two months before committing, and if so, what would tell us it’s working better than the old format?

Thanks to @adityakane @thehopemonger and @webtechpooja for reviewing the proposal.

#coworking, #meeting, #proposal

Patricia BT 7:56 am on June 28, 2024
Tags: , , international-communities, proposal   

Proposal to integrate Slack workspaces from local WP Communities into Slack Enterprise Grid

As part of our ongoing efforts to enhance communication and collaboration among our local WordPress communities, we propose that WordPress Community SupportWordPress Community Support WordPress Community Support PBC is a Public Benefit Corporation, created specifically to be the financial and legal support for WordCamps, WordPress Meetup groups, and any additional “official” events organized within the WordPress Community Events program. considers adopting our local communities, currently on free SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ plans, into a consolidated Enterprise Grid plan. More information: An introduction to Slack Enterprise Grid and Guide to the Enterprise Grid admin dashboard.

In alignment with @Matt Mullenweg’s proposal at the State of the WordState of the Word This is the annual report given by Matt Mullenweg, founder of WordPress at WordCamp US. It looks at what we’ve done, what we’re doing, and the future of WordPress. https://wordpress.tv/tag/state-of-the-word/. 2023, where he suggested adopting a few polyglot channels by saying about free Slack spaces for local communities: “you shouldn’t need to do that”, this initiative to transition to an Enterprise Grid could be seen as an extension of that vision. By consolidating our Slack workspaces, we not only enhance our ability to support multilingual communication but also significantly broaden the scope for cross-community interactions. This proactive step would further integrate diverse voices and expertise into our global WordPress community, supporting our collective growth. 

It follows a post in December 2023 by @tobifjellner on the Polyglots P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org How can we best handle local channels in WordPress global Slack? and a comment by @mkismy suggesting the Enterprise Grid. It was also mentioned in a Community Team meeting in May 2024, suggesting this proposal. It also follows the pause in the transition to Matrix, see the related post by @akirk.

It’s important to note that many of our local WordPress communities currently operate on free Slack plans. The list of known communication platforms for local communication can be seen here: Local Slack Teams.

These communities, which are pivotal in promoting WordPress and offering support at a local level, are indeed especially important for Polyglots but not only: Support, Community event organization and many more conversations happen in those Slack workspaces. Local communities face significant limitations in terms of message history and integration capabilities under the free plan model, with access to the conversations limited to 90 days. As Slack moves towards deleting older than 1 year historical data for free accounts, our community’s valuable discussions and resources risk being lost. Transitioning to an Enterprise Grid plan would safeguard our archives and enhance our operational capacities, ensuring that every local community has the tools they need to thrive.

Key Benefits of Moving to Slack Enterprise Grid:

  1. Data Continuity and Access: By migrating to Enterprise Grid, we can ensure that all historical data — including messages, files, and customizations — is preserved. This is critical as Slack’s upcoming policy change will delete older than 1-year history for free workspaces starting 26 August​ 2024.
  2. Enhanced Security and Compliance: Enterprise Grid offers advanced security features, compliance settings, and administrative capabilities that are not available in free Slack plans. These include SAML-based single sign-on, and comprehensive user and channel management​.
  3. Improved Collaboration Across Workspaces: Enterprise Grid allows for better integration across different workspaces. This is especially beneficial for communities that are segmented by region or interest group, facilitating smoother communication and resource sharing across the entire network​. 

Implementation Considerations:

  • Timeline: The transition should ideally be completed before 25 August 2024 to avoid any disruption caused by the deletion of message history for free plans. However, we understand that this deadline is short and even if it is not feasible in that timeframe, this proposal is still valid, with the workspaces recovery of 1 year of historical conversations.
  • Community Feedback and Support: It is crucial to involve community leaders and members, as well as free local Slack “owners”, in this transition process to ensure their needs and concerns are addressed.
  • User accounts: Address the concern of user accounts as people might already have accounts in several of those Slack workspaces. See with Slack if some sort of consolidation and merging user accounts are possible without losing user history in all the workspaces they belong to.
  • This change would hugely benefit the communication within the community, but it doesn’t solve all problems. For example, Slack refuses users and domains linked to certain locations, like Iran, Russia, etc.
  • Slack being a third-party proprietary application, we need to take into consideration these concerns, and talk with them about data ownership: Slack’s use of traditional machine learning models. If we move to an open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. solution at a later date, with this proposal we will at least have consolidated the existing Slack workspaces.

Call to Action:

Let’s consider this proposal and provide feedback on the feasibility of this transition, and if this is possible before 25 August 2024, in the comments below before July 12, 2024 for collaborative decision-making. 

This proposal has been written by @patricia70 and reviewed by @markhowellsmead, @mazzomaz, @mielbu and @tobifjellner

The draft was submitted for feedback to other community members as well, with participation/OK from:
@estelaris, @francescodicandia, @kcristiano, @mkismy, @nilovelez, @nukaga, @sippis, @zzap

+make.wordpress.org/polyglots/

#community-management, #community-team, #international-communities, #proposal
Crixu 11:18 am on June 21, 2024
Tags: Flagship WordCamps, , proposal, Sponsor Team, ,   

Proposal for a Unified Sponsorship Initiative

Purpose: This proposal aims to enhance support for WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. organizers by forming a task force focused on streamlining sponsorship efforts, ensuring sustainability, and improving the overall sponsor experience. This is not intended to diminish the autonomy of WordCamp organizers but to offer them additional resources and support.

Flagship WordCamps have become an essential item in all our calendars throughout the year. They are the largest gathering of WordPress folks in the community and attract a lot of attention from the Media and our partners/sponsors. One of the biggest issues with becoming bigger is the need for more money and therefore more sponsoring activity, while still relying on the work of volunteers to organize this. Selling all the required sponsor spots gets harder and harder from year to year due to inflation and corporate consolidation in the WordPress ecosystem.

Those volunteers are facing the same discussions and questions from year to year when it comes to approaching sponsors:

  • What companies to approach for sponsorship?
  • How can we reach them? Is the list shared?
  • What are the sponsorship packages, what are the benefits to sponsors and what are some rules around them?
  • How can we make sure that sponsorship is sustainable for the community and the sponsor?
  • Why is [ACTION] allowed on WordCamp [Flagship Location] but not in WordCamp [Flagship Location]
  • How to approach this topic?
  • How to handle global sponsors for the flagship even if the rules are written down?

Each flagship is organized by those who apply to be an organizer and therefore follow the call. In the worst case, the whole team is different from the previous year’s and needs to rely solely on the documents of the previous year.

This proposal is to create an initial small task force inside the community that supports sponsorship teams; for now, this would focus on the three flagships (WC Asia, WCEUWCEU WordCamp Europe. The European flagship WordCamp event., and WCUSWCUS WordCamp US. The US flagship WordCamp event.) but have relevance to WordCamps and WordPress events, to help streamline the sponsor experience for everyone involved. The proposal is to open a call for volunteers for this task force as well as directly approach community members who might be a great fit. I’ve structured the possible tasks for a task force to work on it:

Sponsoring itself

  • Harmonize sponsoring benefits across the Flagships with fine adjustments to local e.g.: pricing, booth size, local things, …
    • Successful benefit ideas like tweets, social events, booths,…
    • Unsuccessful benefit ideas should be centrally listed.
    • Common & best practice 
  • Establish clear rules for sponsorship
    • Booth regulations
    • Handling larger companies with multiple brands
    • Designing Sponsorship packages for small businesses while ensuring availability
  • Support for Sponsors and WordCamps Global Lead
  • Crafting wording around “Partner” or “Sponsoring” not “Exhibitor” packages

Sponsor Lifecycle

  • CRM of up-to-date sponsoring companies incl. contacts besides the Global sponsors
  • Guidance for first-time sponsors
    • Crafting detailed onboarding and sponsoring documents
  • Support for “frustrated” sponsoring questioning value
    • Example: More visibility by attending than sponsoring
  • Active outreach for potential sponsors outside the current sponsors but benefit from WordPress
  • Crafting detailed onboarding and sponsoring documents

Support for Sponsor Teams

  • Mentorship for Sponsoring Teams, also available as sparring Partners – a global sponsor mentorship team.
    • Focused on Flagships
    • Available for all WordCamps
    • Trainings on learn.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/?
  • Handbooks on how to approach local companies best
  • Collecting testimonials and ambassadors for the flagships
    • Bring them to the Media Partners 
    • Work with PR Team ahead of Call for Sponsor 
  • Support the sponsor team in the reflection of a WordCamp and centralize their feedback. 

Tooling & Processes

  • Align contract and tooling with Sponsoring benefits
  • Streamlined processes and define the same tools to use for all flagship events, or at least for each one of them
  • Include in the process a survey/inquiry for sponsors that didn’t come back to better understand why

Goals: By implementing this initiative, we aim to:

  • Foster better relationships with sponsors.
  • Attract new sponsors and grow the ecosystem. 
  • Provide a consistent, improved experience across all flagship events.
  • Ensure financial support for the growth of the WordPress community, facilitating impactful, inclusive, and rewarding WordCamps.

TODOs:

  • Better Mentoring for New Sponsors: Provide guidance and community insights.
  • Engage Sponsors: Encourage sponsor participation beyond sponsoring as speakers and media partners.
  • Feedback LoopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop: Implement clear communication and feedback mechanisms for sponsor teams.
  • Sponsor Communication: Emphasize the importance of sponsors sharing their work through their booth, recaps and active engagement.

Next Steps

Feedback Deadline: Please provide your feedback on this proposal by July 10th, 2024.

Specific Feedback Needed: Is this initiative worth pursuing? How should the task force be staffed? What are your expectations from this task force?

Post-Feedback Actions: Based on the feedback, if there is general support, we will ask the community team for nominees and open a call for volunteers to form the task force. We aim to establish initial actions before the next sponsorship teams for WordCamp Europe and US begin their work.

Thanks again to @juliarosia @peiraisotta @_dorsvenabili @devinmaeztri for your contributions to this proposal.

#flagship-wordcamps, #global-sponsors, #proposal, #sponsor-team, #sponsorship, #wordcamp
Leo Gopal 1:45 am on January 19, 2023
Tags: , , github, proposal, , team-projects   

Proposal: [Experiment] Adopt Standardised Team-wide Project Management Tools – already utilised by other Make Teams for a Quarter.

This proposal is focused towards improving our project management and goal and progress tracking by using the same transparent tools that other Make Teams already utilise.

Background and Skeleton

Currently we have many spreadsheets, trelloTrello Project management system using the concepts of boards and cards to organize tasks in a sane way. This is what the make.wordpress.com/marketing team uses for example: https://trello.com/b/8UGHVBu8/wp-marketing. boards, slackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ groups and many other disparate ways of working on our various ongoing projects outside of helpscout.

From my personal experience having returned as a Community DeputyProgram Supporter Community Program Supporters (formerly Deputies) are a team of people worldwide who review WordCamp and Meetup applications, interview lead organizers, and keep things moving at WordCamp Central. Find more about program supporters in our Program Supporter Handbook. and now as Community Team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts., I believe that the first action – before further planning and goals discussions – is to standardise and fully utilize the power of the tools already available to us. We can benefit by learning from other teams that already consistently use these tools.

…and possibly this demo of a Make Community Team →

Benefits of adopting GithubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/:

GitHub is a powerful and widely-used platform for project management and issue tracking already in full use by @WordPress.

Adopting GitHub for these purposes within the Community Team would bring a number of benefits, including:

  1. Improved collaboration and communication: GitHub provides a central location for team members to access and work on project tasks and issues, as well as a built-in system for commenting, tracking progress, and assigning tasks. This makes it easy for team members to stay informed about the progress of a project and to contribute to it, even when working remotely.
  2. Increased transparency and accountability: With GitHub, team members can easily see the progress of tasks and issues, as well as who is responsible for them. This increased transparency helps to ensure that everyone is on the same page and that tasks and issues are not falling through the cracks.
  3. Better organization and prioritization: GitHub provides a number of tools for organizing and prioritizing tasks and issues, such as labels, milestones, and project boards. These tools make it easy for team members to understand what needs to be done and when, and to focus their efforts on the most important tasks.
  4. Standardisation: By adopting GitHub for project management and issue tracking, the Community Team will standardize our way of working, making it easier for new team members to get up to speed and enabling more effective cross-team collaboration. This standardization also makes it easier for Community Team members to track progress, identify issues and make data-driven decisions.

Overall, adopting GitHub for project management and issue tracking would bring improved collaboration, increased transparency, better organization, and standardization, ultimately leading to a more efficient and effective team.

Next Steps, the Experiment:

I propose we adopt these tooling methods similar to other make teams, and experiment with its usage for a month, having monthly meetings reviewing its success or not, and gathering data for more data-driven decision making

If after the first Quarter the consensus is that this does not suit our team, we will revert back to initial project and tracking practices and explore more.

Update: Other teams using github already were kind enough to share some of the resources they use and workflows which would be extremely beneficial should we move forward with this adoption standard.

Proposal Adoption Feedback Form

Please comment on this proposal!

What excites you about potential Community Team adoption of GitHub?

What concerns do you have?

Take the Proposal Poll →

Thanks to @mysweetcate @juliarosia @megabyterose @peiraisotta for their help editing, offering invaluable advice, and their support for this proposal by @leogopal

#community-management, #community-team, #github, #proposal, #team-goals, #team-projects

Ryan Marks 10:12 pm on September 11, 2022
Tags: , , proposal,   

Proposal: CampTix Attendee to Google Sheets integration

As a WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. organizer, I would like to see CampTix Attendee data populate in a Google Sheet instead of only being available as a downloadable CSV file. This would allow organizers to make a live set of data available for their needs including but not limited to on-demand badge printing.

Integration with on-demand badge printing solutions

I am an organizer of WordCamp US 2022 and am posting this during contributor dayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. Over the last 3 days, I observed the process we had in place between WCUSWCUS WordCamp US. The US flagship WordCamp event. and the vendor we used to print our badges.

  • About two weeks before the event, a CampTix export was created.
  • Unnecessary columns in the export were removed leaving only the columns the vendor needed: name, pronouns, company, Twitter handle, and ticket type (attendee, sponsor, speaker, media, volunteer, organizer).
  • A review of the export was performed, by hand, and removed characters that the vendor couldn’t print (leaving only UTF-8 characters).
  • About one week before the event, the modified export was sent to the badge vendor.
  • The badge vendor uploaded our CSV file to Google Drive, and mapped the various columns to positions where text would appear on the badge.

Due to last minute changes to ticket details, the export from two weeks before the event was stale in a few cases:

  • Attendees that update their ticket information (name change, company change etc.) caused old information to still appear on the badge.
  • Attendees that refunded their ticket still had a badge available to be printed.
  • Attendees who purchased an available (recently refunded) ticket weren’t able to print their badge.

A manual process was necessary to update incorrect information, or add missing people to the vendor’s Google Sheet.

Organizers only need to create an “export” once

Recent exports I have in my Downloads folder

Over the course of planning a WordCamp, I find I am often pulling a fresh CampTix export. For the same reasons that I spelled out in the section above, an export becomes increasingly less valuable as time passes. While the CampTix Summarize tool is useful when looking for a count of attendees and how they answered a particular question, sometimes more specific information is needed. For example, it’s useful to see the attendee’s name and their answer, especially in the case of:

  • Microsponsors
  • T-shirt sizes
  • Life-threatening allergies
  • AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) needs

For me, the export CSV file isn’t usable until I open it in a spreadsheet application and I don’t have one installed on my computer. So, I end up uploading the file into my WordCamp’s Google Drive and open the file with Google Sheets before I can begin working with it. It would simplify the workflow by having the data immediately available in Google Sheets.

Integration Proposal

We already allow a non-logged user to access CampTix data through the Attendance UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing.. This proposal adds a new tab on the screen below called Export Integration. It would have a radio field titled Enabled and a text area field titled Secret Link similar to the screenshot.

CampTix Attendance UI

Once the Secret Link from the Export Integration is generated, it should be embedded inside the Google Sheets function IMPORTDATA() which would populate the sheet. If there are multiple use cases for Google Sheet integrations, additional Google Sheet files can be created that invoke the IMPORTRANGE() function. If only a select number of columns or rows are needed for a particular use case, the limited access use case could be wrapped by a QUERY(). Here’s an example that might make sense for the microsponsor scenario:
=QUERY(IMPORTRANGE("1gcuSqpN-x1NCn5ZaEKc_IhoBFQAlMhpjtjE1eUL4ZJo"),
"SELECT C, D, E WHERE B='Microsponsor'", FALSE)

Feedback

I’m seeking feedback on this proposal through the end of September. Please let me know if you have any questions or need clarification.

Thanks to @newyorkerlaura, @katiejrichards, and @jyoansah for their help editing this post.

#camptix, #contributor-day, #proposal, #wcus

Hari Shanker R 10:55 am on May 23, 2022
Tags: , proposal,   

Regional In-person WordCamps Going Forward

In March, I kicked off a discussion in this blog on revisiting regional in-person WordCamps. A big thank you to all of you for sharing exciting and diverse perspectives and concerns on regional in-person events. I have attempted to summarize your feedback in the wrap-up comment. The goal of the WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. program is to connect WordPress enthusiasts with each other, inspire them to do more with WordPress, and encourage contribution to the WordPress project. Per your feedback, regional WordCamps would help us achieve this goal in 2022. Hence, the Community Team has decided to simplify the guidelines for regional in-person WordCamps. 

Moving forward, regional WordCamps will not need to go through additional steps (such as writing a proposal), and can directly apply to organize a camp for their region using the regular WordCamp application form. 

Regional WordCamp applications will continue to be evaluated on a case-by-case basis by WordCamp CentralWordCamp Central Website for all WordCamp activities globally. https://central.wordcamp.org includes a list of upcoming and past camp with links to each. deputiesProgram Supporter Community Program Supporters (formerly Deputies) are a team of people worldwide who review WordCamp and Meetup applications, interview lead organizers, and keep things moving at WordCamp Central. Find more about program supporters in our Program Supporter Handbook..

Importance of Local Communities While Organizing Regional WordCamps

I would like to specifically highlight that ongoing regional WordCamps cannot be held at the cost of local WordPress meetupsMeetup Meetup groups are locally-organized groups that get together for face-to-face events on a regular basis (commonly once a month). Learn more about Meetups in our Meetup Organizer Handbook. and local communities. Local communities offer more accessible ways to connect over WordPress, and more supportive pathways to participation in larger, more complex events. If a local community wants to continue organizing regional WordCamps, they should follow these guidelines: 

  • The local meetupMeetup Meetup groups are locally-organized groups that get together for face-to-face events on a regular basis (commonly once a month). Learn more about Meetups in our Meetup Organizer Handbook. groups that constitute the region should continue to meet regularly and be active (they may continue to meet online).
  • A regional WordCamp will not be a replacement for local WordCamps in a location. We strongly encourage local communities to continue organizing WordCamps. As opposed to traditional multi-day WordCamps, they can organize smaller events that are akin to a meetup-day format, yet benefit from WordCamp benefits such as sponsorship, etc. 
  • Local communities should encourage new volunteers, and continue to add new members to positions of leadership. 
  • If a community wants to organize a local WordCamp, it should have adequate representation from all local meetups and should have a fresh set of organizers. The community should be very strict about two-year term limits for lead organizers. 

Request for Feedback

  • First of all, I would like your feedback on this proposal. I continue to appreciate your honest and direct feedback on this new direction for regional camps.
  • Healthy local communities are important for the success of regional events. As such, WordCamp Central will evaluate the health of local communities when assessing a regional WordCamp application. What metrics can be used to measure the health of a region? We would love to hear from you! I have shared a list of indicators that our team has considered below – but I’m sure I would have missed some important pointers. So I would love your input on any additional metrics that could help measure the health of our communities! The indicators we are currently evaluating include:
    • The number of new (and old) organizers.
    • Diversity in the organizing team (age/gender/ethnicity/sexual orientation, etc).
    • Number and frequency of events held by the local meetup groups within the region.
    • Past WordCamps in the region (if any).

Once again, a big thanks to all of our community members who commented on the original proposal and to all our community members planning regional events to revitalize our vibrant community. 

The following fine folks contributed to this post: @angelasjin @devinmaeztri and @juliarosia

#regional-wordcamps #proposal #announcement

Courtney P.K. 9:18 pm on October 8, 2021
Tags: , proposal,   

Proposal: 2022 Global Community Sponsorship program

tl;dr: Due to the unpredictability in what events are happening and where, the global sponsorship program proposal for 2022 is similar to the pared-down 2021 program, with a single package. Sponsorship of WordCamps will be offered as an add-on, billed quarterly.

Below you will find a proposal draft for the Global Community Sponsorship program for 2022, with one package being offered as an annual commitment.

As the WordPress Community transitions to holding in-person WordCamps, the question arises of how the Global Sponsorship program will accommodate those events. Until we have more predictability in what events are happening and where, we will offer WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. sponsorship per event, billed at the end of each quarter.

Questions? Feedback?

If you have any questions, observations, or critical feedback about this proposal or the program in general, please comment on this post, no later than 15 October 2021. We hope to finalize the program details by 28 October 2021, to allow sponsors time to sign up by the end of the year.

Thanks so much for the hard work, input, and feedback by @angelasjin, @kcristiano, @_dorsvenabili, @sippis, and @courtneypk, with help crunching the numbers from @harmonyromo.

Now onto the proposal!

Continue reading →

#global-sponsorship, #proposal, #sponsorship

Ryan Marks 3:18 am on October 1, 2021
Tags: proposal,   

Proposal: Link WordCamp schedule track headings to Pages

While organizing WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. US, I suggested that we link each of the track headings on the schedule page to the pages where attendees would see our YouTube video and chat embeds (Yukon and Columbia). Since we are using the schedule blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience., it’s not possible to edit that part of the page.

To support this feature, I believe two changes are necessary:

1. Add a term metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. field

Add a field to Add Track and Edit Track screens to allow a relative URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org path to be specified. In the case of the Yukon track, the value entered would be “/yukon-track”.

The current Add Track screen.
The current Edit Track screen.

This field should not be required for many reasons including:

  1. The schedule is ready to be published but the track pages are not.
  2. The WordCamp is 100% in-person and doesn’t have a need for track pages.

2. Add the link to the schedule grid

If the a URL path was defined for a track, add a link in the respective grid column headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes..

An example of the schedule grid if only the Yukon track had a URL path defined.

Feedback requested

I would appreciate getting feedback on this proposal.

  1. Would this be useful to WordCamp organizers?
  2. Are there any reasons why not to do this?

Deadline: October 15th, 2021 Extended until October 29, 2021 to gather additional input.

#proposal, #schedule