Sources and methods

A trend can be a change in collection rather than a change in the community. This page lists the source families WordPress contributor work leaves a record in, and what this site collects from each.

What this site collects, and from where

A trend can be a change in collection rather than a change in the community. This page lists every source family WordPress contributor work leaves a record in, and what this site collects from each.

23 source families: 3 partial, 13 not collected, 7 access required, 0 complete. A percentage of project coverage isn't shown because the full source population is unknown.

Source families, what this build collects, and why.
SourceStateWhat this build doesCounting unitAccess and limits
Contributor Dashboard aggregatesAccess requiredNo public export exists. A versioned aggregate needs the dashboard maintainers' agreement.Allowed imported event rows; distinct numeric WP.org contributor IDs; registration-month cumulative averages
Details

Wrapped public read succeeded; About read returned429; source inspected

  • Core, Meta, GitHub and Slack are explicitly not comprehensively integrated.
  • 31 registered types are not proof of ingested coverage.
  • updated_profile excluded; unregistered types omitted.
  • Cohorts includes known registration dates and at least one matching event; not all signups and not retention.
  • README/About status reference differs from inspected ladder code; deployed SHA unverified.
WordPress.org activity eventsAccess requiredCollection isn't implemented upstream and the events import endpoint needs an administrator.Upstream activity event with a stable event ID and WP.org contributor ID
Details

documented; collection not implemented

  • Profile timeline is not all contribution history.
  • Do not assume numeric IDs from unrelated systems share the dashboard event namespace.
  • Event types need origin/alias mapping and test-event review.
  • No profiles or raw contributor-event dump collected.
Make team posts and public discussionPartialPost titles, links and dates reach the feed. Public comments and revisions don't.Published post; public comment as a separate action; canonical cross-post relation
Details

REST discovery and minimal post read verified; comments access restricted

  • RSS is a recent window, not complete history.
  • Glossary expansion and cross-posts pollute extraction.
  • Deleted/moderated/private content excluded.
  • Author account metadata is not a complete contributor roster.
Handbook and documentation publication/revisionsNot collectedDocument metadata was verified once. Revision history isn't collected.Published document; separately verified revision/review action
Details

One current-document metadata record verified200

  • Latest modified time is not an editing event ledger.
  • Last author need not be sole author or reviewer.
  • A GitHub issue close and document publish may describe one outcome.
WordPress Trac instancesPartialRecent ticket activity reaches the feed for tracked milestones. Full ticket history and actors don't. Some endpoints returned 403 in the research check.Ticket, comment, change, attachment, changeset relation
Details

Read blocked403 here; source existence and workflow documented

  • Core-only coverage omits Meta/Themes work.
  • Latest comment is not ticket creation.
  • Closed does not necessarily mean accepted or fixed.
  • Notification copies and mirrors must deduplicate.
SVN canonical history and Git mirrorsNot collectedThe public root answers, but no history is downloaded. Git mirrors must be reconciled with SVN, not counted twice.Canonical revision and separately attributed contributors/props
Details

Public root200; no historical log download

  • Committer is not every contributor.
  • Build/release copies and Git mirrors duplicate work.
  • Plugin/theme author publication is not automatically Five for the Future contribution.
Team-linked GitHub repositoriesPartialIssues and pull requests in tracked repositories reach the feed as latest-update records. There is no event timeline, review history or actor data.Issue, PR, review, comment, commit, explicit workflow event
Details

Connector read verified for dashboard code; other collectors not deployed

  • Documentation uses issues rather than hosting docs in PRs.
  • GitHub account does not guarantee WP.org identity mapping.
  • Bots, issue imports, squash merges and renamed accounts affect counts.
  • Existing proposal keyword collection is not a general contribution collector.
WordPress release credits and propsNot collectedA public endpoint was verified. Credits aren't stored here, and the payload carries identities.Recognition in a named release; explicit props relation
Details

Public JSON endpoint verified; identity payload not retained in artifacts

  • Credits are not effort hours or all attempted work.
  • Some non-code props manually gathered.
  • Missing credit does not prove no contribution.
  • Minor-release recognition needs documented release semantics.
GlotPress and PolyglotsNot collectedPublic summaries exist. A full activity export is unverified, and snapshot totals can't rebuild the past.Suggestion, review, approval; project/locale status; organized translation-event metadata
Details

Public summaries and event metadata verified; full activity export unverified

  • Public profile activity not tied to locale.
  • Local sites/Slack work omitted.
  • Multiple locales per person can overstate locale capacity.
  • Organized translation_event posts are not individual string audit events.
Support forums and moderationNot collectedNo collector was verified. Help seekers and responders need separate populations.Topic/reply, helper response, resolution, authorized aggregate moderation action
Details

Workflow and pilot use documented; no full collector verified

  • Question authors are not necessarily support providers.
  • Replies can be follow-up questions.
  • Deleted/moderated records and private work missing.
  • Resolution is not a uniform measure of quality.
Training content and learningAccess requiredPublic content is readable. Learner activity needs authorized aggregation.Created/reviewed/translated/maintained learning item; workshop; learner completion separately
Details

Public methodology/workflow verified; private learning analytics not accessed

  • Learning completion is not teaching output.
  • Viewer retention is not contributor retention.
  • Mentorship and review work may be absent from publication authorship.
  • Training /pledges says tracking absent there; this is a separate system from Dashboard course/content event types.
Public event metadataNot collectedPublic event metadata only. Attendance and check-in data need organizer access.Event record, published role/session, public aggregate report
Details

Metadata public200; no attendee records requested

  • The wordcamps collection includes a Campus Connect event; do not classify everything as a WordCamp.
  • A scheduled event is not proof it occurred.
  • Public attendee lists are opt-in, not attendance census.
Community program operationsAccess requiredAn owner-supported aggregate route is proposed and not accessed.Approved aggregate application, support, mentoring or attendance outcome
Details

Owner-supported aggregate route proposed, not accessed

  • Registrations differ from check-ins and unique people.
  • Attendance does not measure organizing work.
  • Do not collect accessibility/dietary/contact data.
  • Do not migrate attendee data merely because an organizer can view it.
Plugin review workloadNot collectedA public aggregate report exists. Review conversations and security reports are private.Submission/review decision, first response, queue stock, interval flow
Details

Public aggregate report verified; no review conversations accessed

  • Queue stock and weekly throughput are different.
  • Pending author and pending reviewer are distinct bottlenecks.
  • Plugin submission is not itself equivalent to review service.
Photos and OpenverseNot collectedPublic workflow documented. No moderation access.Published photo, metadata work, authorized aggregate moderation, catalog/issue work
Details

Public workflow documented; no moderation access

  • Approval date differs from creation/submission.
  • Syndication is not a second independent contribution.
  • CC0 photo content does not make moderator/submitter private information reusable.
Design artifacts and researchNot collectedDesign tool data and research files aren't accessed.Published design artifact/review/research result linked to work item
Details

Public handbook read; design tool data not accessed

  • Do not infer contribution from a Figma seat.
  • Comments are not inherently accepted design work.
  • Do not collect private research participant material.
Public Mailman archivesNot collectedThe archive indexes are public. No messages are parsed, and notification lists duplicate tickets and commits.Original message/thread or notification reference
Details

All three archive indexes public200, with gzip text links observed

  • Stopped/stale indexes are coverage limits.
  • Quoted replies duplicate content.
  • Old email identifiers should not be republished or inferred into cross-platform identity.
  • Notifications are not independent additional contribution events.
Historical public IRC logsNot collectedA public log index exists. No transcript backfill has run, and nicknames need explicit handling.Public message or explicitly documented meeting outcome
Details

Public index verified; no transcript backfill

  • Nicknames are not stable verified identities.
  • Bots, netsplits, renames and missing logging matter.
  • Historic Freenode logs differ from current Libera support.
WordPress Slack and published summariesAccess requiredDocumentation only. No Slack message is read here, and direct messages are never contributor evidence.Published summary/decision; authorized aggregate participation if agreed
Details

Documentation only; no Slack messages accessed

  • Being a workspace member is not a blanket export permission.
  • History and thread replies need distinct retrieval.
  • Message volume is not impact, wellbeing or agreement.
  • Do not reconstruct deleted/private conversations from mirrors.
Five for the Future pledgesNot collectedThe public declaration method was verified. Pledges aren't collected, and a pledge isn't a confirmed commitment.Self-reported pledged hours, teams and accepted sponsorship relationship
Details

Public current declaration methodology verified

  • Pledged hours are not actual hours worked or money paid.
  • Company product work is not automatically in program scope.
  • Unknown sponsor does not imply unpaid.
  • Current affiliation cannot be assigned retrospectively.
Reported funding, roles and available capacityAccess requiredA collection contract is proposed. No funding record is accessed.Time-bounded declared funding/availability; role verified date; aggregate responsibility coverage
Details

Collection contract proposed; no private records accessed

  • Badges do not establish current capacity.
  • Activity silence is not burnout or unavailability.
  • Do not derive hours from counts.
  • Use effective-dated roles and sponsorship; retain unknowns.
  • Meta /pledges describes a shipped-work ranking; do not inherit it as a sustainability metric.
Mentorship and contributor programsAccess requiredA public report exists. Participant-level data needs the program owner's aggregate release.Consented enrollment, supported first contribution, completion, follow-up participation, mentor capacity
Details

Public report verified; no program participant export

  • WordPress Credits education program differs from Core release credits.
  • People leaving before first recorded event absent from activity-derived cohorts.
  • Program anecdotes do not prove causal retention effects.
  • Suppress small cells and respect non-participation/opt-out.
Other team and local-community workNot collectedProposed for team onboarding. This is not a claim of existing coverage.Team-agreed deliverable/review/support outcome with source evidence
Details

Proposed source onboarding, not a claim of existing coverage

  • Current28-site directory is not the full historical project.
  • Cross-team work should not inflate unique-person totals.
  • Offline care, facilitation, prevention and maintenance may never produce a public event.

Collection tools considered

17 integration families were checked, and none runs in this build. Perceval and GrimoireLab can supply Git, GitHub, Slack, mail and IRC collectors. Neither has a Trac or SVN collector, so those need an adapter or a verified export. LFX Insights offers public project aggregates, with its own scope and methodology. We don't republish its headline score or add its totals to ours.

  • GitHub: core source inspected. No collector ran here.
  • Git repositories: core source inspected. No collector ran here.
  • Trac instances: not present in inspected Perceval core. No collector ran here.
  • Subversion: not present in inspected Perceval core. No collector ran here.
  • WordPress public posts and taxonomies: not a native WordPress REST backend in inspected Perceval core. No collector ran here.
  • RSS feeds: directory and README documented; source module not audited. No collector ran here.
  • Local mail archives: core source inspected. No collector ran here.
  • Mailman/Pipermail archives: core source inspected. No collector ran here.
  • HyperKitty mail archives: core source inspected. No collector ran here.
  • Saved IRC logs: core source inspected. No collector ran here.
  • Slack: core source inspected. No collector ran here.
  • Discourse: core source inspected. No collector ran here.
  • Bugzilla REST: core source inspected. No collector ran here.
  • GitLab: directory and README documented; source module not audited. No collector ran here.
  • Gerrit: directory and README documented; source module not audited. No collector ran here.
  • LFX Insights public aggregate API: contract inspected; one public HTTP GET succeeded. No collector ran here.
  • WordPress contributor dashboard: source inspected; no public export endpoint established. No collector ran here.

Updated 19 Nov, 03:22 UTC. Source states describe this build, not the sources: a family listed as not collected may be well documented upstream. Research checks of 18 November 2026 are bounded and don't establish complete history for any source.

Rendered with Sources and methods | WP Status Signal from page at route /sources