Dries-compare

Compare Drupal core contributor positions by providing a topic and a contributor name to generate an evidence-grounded side-by-side comparison. The comparison surfaces agreements, disagreements, and knowledge gaps using direct issue queue evidence.

Finding issue queue evidence for Drupal core policy decisions requires grounding every comparison claim in public records. This process surfaces explicit evidence references for patches, debates, and strategic planning without fabricating positions.

To check if a Drupal contributor's stance on a patch is documented, query the topic and contributor name to retrieve side-by-side comparisons. This flags unknown positions and anchors all claims in public issue queue records.

Yes, you can use issue queue evidence to prepare for Drupal core debates by generating side-by-side comparisons of documented positions. This ensures strategic planning is grounded in public records and surfaces explicit evidence references.

When a contributor's position on a Drupal topic is not publicly documented, the comparison flags it as an unknown position. This prevents fabricated claims and ensures all outputs are anchored in actual issue queue evidence.

Dries-compare works for any publicly known Drupal core contributor. You provide the contributor name and topic, and it returns an evidence-grounded difference comparing their documented positions against Dries Buytaert's.