‹ Reports
The Dispatch

OSS Report: posthog/posthog


GitHub Logo GitHub Logo

PostHog Development Focuses on Enhancing User Experience and Data Handling Amidst Active Community Engagement

PostHog, an open-source product analytics platform, continues to prioritize user experience improvements and robust data handling features, as evidenced by recent development activities and community engagement.

Recent Activity

The recent issues and pull requests in the PostHog repository highlight a strong focus on enhancing user experience and addressing technical challenges. Notable issues include feature requests for improved filtering options (#24576) and enhancements to session replay features (#24570). Bug reports such as local deployment failures (#24568) indicate areas needing urgent attention. The development team has been actively working on both new features and bug fixes, with significant contributions from members like Tom Owers, Ben White, and James Greenhill. Recent commits include improvements to data warehouse mechanics, plugin destination migrations, and enhancements in data handling.

Recent Issues

Team Contributions

Of Note

  1. Feature Enhancements: Recent PRs introduce new features like error handling improvements (#24572) and custom soft deletes for events (#24582).
  2. Dependency Management: Frequent updates to dependencies (e.g., #24578) ensure security and leverage third-party improvements.
  3. Community Engagement: Active discussions on features like RBAC (#20864) indicate responsiveness to community needs.
  4. Performance Optimizations: Efforts to optimize data ingestion processes (e.g., #24488) highlight a focus on system efficiency.
  5. Stale PRs: Some pull requests have been closed due to inactivity, suggesting potential prioritization challenges.

Quantified Reports

Quantify Issues



Recent GitHub Issues Activity

Timespan Opened Closed Comments Labeled Milestones
7 Days 30 10 48 2 1
30 Days 86 39 95 7 1
90 Days 318 134 351 32 1
All Time 5802 4381 - - -

Like all software activity quantification, these numbers are imperfect but sometimes useful. Comments, Labels, and Milestones refer to those issues opened in the timespan in question.

Quantify commits



Quantified Commit Activity Over 30 Days

Developer Avatar Branches PRs Commits Files Changes
Sandy Spicer 4 3/2/0 24 44 51900
github-actions 20 0/0/0 71 433 36339
Marius Andra 5 7/2/0 43 115 9865
Oliver Browne 3 7/6/0 15 134 9586
Michael Matloka 5 10/7/0 27 286 8024
Ben White 4 15/13/1 24 297 7926
Brett Hoerner 4 6/3/2 9 126 7342
Dylan Martin 7 5/1/1 31 40 4307
Julian Bez 5 9/8/0 31 206 3582
Thomas Obermüller 4 9/7/0 17 205 3575
David Newell 6 11/7/1 21 129 2900
Robbie 5 7/5/0 18 60 2743
Eric Duong 6 7/3/2 13 60 2500
ted kaemming 4 2/0/0 45 15 2141
Tom Owers 2 16/16/0 22 51 2113
Georgiy Tarasov 2 3/3/0 9 20 1858
Juraj Majerik 3 6/6/0 10 42 1623
Paul D'Ambra 3 6/4/0 14 22 1520
Tomás Farías Santana 3 18/16/0 19 30 1425
James Greenhill 4 7/5/0 13 32 1415
Frank Hamand 3 4/3/0 15 24 812
Anirudh Pillai 1 5/5/0 7 34 650
Zach Waterfield 2 5/5/0 10 26 522
Nikita Vorobev 1 0/0/0 1 17 391
timgl 1 2/2/0 3 60 372
Neil Kakkar (neilkakkar) 1 1/0/0 4 3 195
PostHog Bot 7 11/6/2 14 5 191
Marcus Hof 2 2/1/0 3 4 135
Phani Raj 3 3/2/1 4 6 67
None (dependabot[bot]) 4 4/0/0 4 5 66
Mukesh 1 0/0/0 1 2 50
Ady H 1 1/1/0 1 2 39
Raquel Smith 2 3/2/1 3 9 29
Matthew Bridges 1 1/1/0 1 1 7
thisames 1 0/0/0 1 2 6
Hamir Mahal 1 1/1/0 1 1 2
None (muscache) 0 1/0/0 0 0 0
Ben Haynes (benhaynes25) 0 1/0/0 0 0 0
Joseph Lenton (JosephLenton) 0 1/0/0 0 0 0
Charles Cook 0 0/0/0 0 0 0

PRs: created by that dev and opened/merged/closed-unmerged during the period

Detailed Reports

Report On: Fetch issues



Recent Activity Analysis

The PostHog GitHub repository currently has 1,421 open issues, indicating a high level of ongoing activity and engagement from the community. Recent issues highlight a mix of feature requests, bugs, and enhancements, with several relating to user experience improvements and technical challenges in the platform's functionality.

Notably, there are several recurring themes among the issues, including requests for improved filtering options in dashboards, enhancements to session replay features, and better handling of user data privacy. There are also multiple reports of bugs affecting the functionality of insights and queries, particularly around the handling of filters and visualizations.

Issue Details

Recent Issues

  1. Issue #24585: Feature Request: Option to display totals on funnels (in addition to percentages)

    • Priority: Enhancement
    • Status: Open
    • Created: 0 days ago
    • Updated: N/A
  2. Issue #24576: Ability to apply global filters to notebooks

    • Priority: Enhancement
    • Status: Open
    • Created: 0 days ago
    • Updated: N/A
  3. Issue #24570: Replay filter to allow finding recordings by number of windows

    • Priority: Enhancement
    • Status: Open
    • Created: 1 day ago
    • Updated: N/A
  4. Issue #24568: Posthog Local Deployment Fails: Container Restarts and Database Errors

    • Priority: Bug
    • Status: Open
    • Created: 2 days ago
    • Updated: N/A
  5. Issue #24567: Expanding Data Collection Capabilities in the Hobby Version

    • Priority: Enhancement
    • Status: Open
    • Created: 2 days ago
    • Updated: N/A
  6. Issue #24561: [Replay] UX feedback

    • Priority: Feature Request
    • Status: Open
    • Created: 3 days ago
    • Updated: N/A
  7. Issue #24560: [Try insights button] Open filters pane on page load

    • Priority: Feature Request
    • Status: Open
    • Created: 3 days ago
    • Updated: N/A
  8. Issue #24555: Avg time spent on page in Web analytics

    • Priority: Enhancement
    • Status: Open
    • Created: 4 days ago
    • Updated: N/A
  9. Issue #24554: Clarity about date range selection when defining action, using data table

    • Priority: Feature Request
    • Status: Open
    • Created: 4 days ago
    • Updated: N/A
  10. Issue #24553: [Actions] Button getting clipped in header

    • Priority: Bug
    • Status: Open
    • Created: 4 days ago
    • Updated: N/A

Analysis of Themes and Issues

Several themes emerge from the recent issues:

  • User Experience Improvements: Many feature requests focus on enhancing user experience, such as adding global filters to notebooks (#24576) and improving funnel visualizations (#24585). This indicates a strong desire from users for more intuitive interfaces and functionalities that streamline their workflows.

  • Technical Bugs: There are multiple reports of bugs related to local deployments (#24568) and issues with session replays (#24570). These technical challenges can significantly impact user satisfaction and may require urgent attention from the development team.

  • Data Handling and Privacy: Issues like expanding data collection capabilities (#24567) reflect ongoing discussions about how to balance feature richness with user privacy concerns, especially in light of regulations like GDPR.

  • Feature Requests for Enhanced Analytics: Requests for better filtering options in insights and dashboards (#24554) suggest that users are looking for more granular control over their analytics data, which is crucial for effective decision-making.

Overall, the current state of open issues highlights an active community engaged in improving PostHog's functionality while also pointing out critical areas that need immediate attention or enhancement.

Report On: Fetch pull requests



Report on Pull Requests

Overview

The dataset contains a total of 77 open pull requests (PRs) for the PostHog project, with a wide range of changes including new features, bug fixes, and dependency updates. The PRs reflect ongoing development efforts to enhance functionality, improve performance, and maintain code quality.

Summary of Pull Requests

  1. PR #24586: feat(capture): handle empty string UUIDs for /batch endpoint

    • Created: 0 days ago
    • Updates the RawEvent serializer to treat empty strings in the UUID field as None, improving robustness for user-defined UUIDs.
  2. PR #24584: feat(hog): bytecode versions

    • Created: 0 days ago
    • Introduces a version field to Hog bytecode, allowing future support for optional arguments and improving function call handling.
  3. PR #24583: fix: wild card domain check in firefox

    • Created: 0 days ago
    • Adjusts URL parsing to ensure compatibility across browsers by replacing wildcards before parsing.
  4. PR #24582: feat: Use our own soft deletes for event deletes

    • Created: 0 days ago
    • Implements custom soft delete functionality to improve performance and control over event deletion processes.
  5. PR #24581: feat: Add soft delete column to events

    • Created: 0 days ago
    • Adds an is_deleted flag to events, facilitating better management of deleted records.
  6. PR #24580: fix: refactor the inspector list filtering

    • Created: 0 days ago
    • Refactors filtering logic in the inspector list to improve clarity and maintainability.
  7. PR #24578: chore(deps): Update posthog-js to 1.158.1

    • Created: 0 days ago
    • Updates the PostHog JavaScript library to the latest version for improved features and bug fixes.
  8. PR #24577: chore(deps): Update posthog-js to 1.158.0

    • Created: 0 days ago
    • Similar update as above but for an earlier version.
  9. PR #24575: feat(hog): parser updates for lambdas

    • Created: 0 days ago
    • Enhances the parser to support lambda functions, improving query capabilities in HogQL.
  10. PR #24574: feat(hogvm): serialize the stack between async operations

    • Created: 0 days ago
    • Modifies serialization of stack data structures for better handling in asynchronous contexts.
  11. PR #24573: chore(deps): bump tj-actions/changed-files from 43 to 45

    • Created: 1 day ago
    • Updates a GitHub action dependency for improved functionality.
  12. PR #24572: feat(errors): Add support for handling chained exceptions

    • Created: 1 day ago
    • Enhances error reporting by supporting chained exceptions in the UI, improving debugging capabilities.
  13. PR #24569: feat(cyclotron): Change dead-letter strategy, adopt in fetch and janitor

    • Created: 2 days ago
    • Implements a new strategy for handling dead-letter queues in processing tasks.
  14. PR #24565: feat(flags): add group property overrides

    • Created: 3 days ago
    • Introduces functionality for overriding group properties in feature flags.
  15. PR #24564: feat: Added button to help sidebar to report bug on GitHub

    • Created: 3 days ago
    • Adds a button in the help sidebar for users to report bugs directly on GitHub.
  16. PR #24563: chore(cyclotron): change columns to bytes, add blob column

    • Created: 3 days ago
    • Changes column types in Cyclotron to accommodate binary data more effectively.
  17. PR #24562: chore(deps): bump micromatch from 4.0.5 to 4.0.8

    • Created: 3 days ago
    • Updates a dependency related to pattern matching in JavaScript.
  18. PR #24558: chore: remove event properties from subquery

    • Created: 3 days ago
    • Cleans up unused code related to event properties in queries.
  19. PR #24493: chore(deps): Update posthog-js to 1.157.2

    • Closed without merging; similar update as previous PRs but not pursued further due to overlap with other updates.

20-77 Various other PRs focusing on bug fixes, feature enhancements, dependency updates, and refactoring efforts that showcase an active development cycle aimed at improving product stability and functionality.

Analysis of Pull Requests

The current set of pull requests reflects several key themes and areas of focus within the PostHog project:

Feature Enhancements

Many recent PRs introduce new features or enhance existing functionalities, particularly around error handling (e.g., PRs #24572 and #24583), data processing (e.g., PRs #24582 and #24581), and user experience improvements (e.g., PRs #24564 and #24492). This indicates a strong commitment to enhancing user interaction with the platform while also addressing technical debt through refactoring efforts (e.g., PRs #24580 and #24496).

Dependency Management

There is a noticeable trend towards maintaining up-to-date dependencies (e.g., PRs like #24578, #24577, and others). This is crucial not only for security but also for leveraging improvements made by third-party libraries that can enhance PostHog's performance or capabilities.

Bug Fixes and Stability

A significant number of PRs are dedicated to fixing bugs (e.g., PRs like #24491 and #24490), indicating ongoing efforts to stabilize the platform as it evolves with new features being added regularly. The focus on improving error logging (#24534) also suggests an awareness of the need for better diagnostics as complexity increases.

Performance Improvements

Several PRs target performance optimizations (e.g., PRs like #24488), particularly around data ingestion processes which are critical given PostHog's focus on analytics where speed can significantly impact user satisfaction and system efficiency.

Community Engagement

The presence of discussions around features such as RBAC (Role-Based Access Control) (#20864) indicates that there is active engagement with community feedback and needs, suggesting that PostHog is responsive to its user base's requirements.

Stale Pull Requests

A few pull requests have been marked as stale or closed due to inactivity (e.g., PRs like #20936). This highlights a potential area of concern regarding contributor engagement or prioritization of work items within the team, which could affect long-term project sustainability if not addressed promptly.

In summary, PostHog's current pull request activity demonstrates a proactive approach towards feature development, bug fixing, performance optimization, and community engagement while also reflecting challenges associated with managing an active open-source project.

Report On: Fetch commits



Repo Commits Analysis

Development Team and Recent Activity

Team Members and Recent Contributions

  1. Tom Owers (Gilbert09)

    • Recent Activity:
    • Fixed issues in the data warehouse, including better mechanics for resyncing tables and limiting DWH sources during chunking.
    • Contributed to the migration of filters to queries.
    • Collaborations: Worked alongside other team members on various fixes and features.
  2. Ben White (benjackwhite)

    • Recent Activity:
    • Added documentation links for hog functions and made improvements to the CDP.
    • Worked on automatic migration of plugin destinations.
    • Collaborations: Collaborated with multiple team members on various features.
  3. James Greenhill (fuziontech)

    • Recent Activity:
    • Bumped version of CH for local development and fixed issues related to soft deletes in events.
    • Involved in several migrations and enhancements related to data handling.
    • Collaborations: Engaged with team members on batch exports and other tasks.
  4. Robbie (robbie-c)

    • Recent Activity:
    • Added new session bounce rate calculations into HogQL and worked on cyclotron-related features.
    • Fixed bugs related to insights and session handling.
    • Collaborations: Co-authored several features with other developers.
  5. Oliver Browne (oliverb123)

    • Recent Activity:
    • Contributed significantly to cyclotron features, including fetching metrics and janitor run migrations.
    • Involved in ongoing work related to the cyclotron project.
    • Collaborations: Frequently collaborates with Brett Hoerner on cyclotron tasks.
  6. Thomas Obermüller (thmsobrmlr)

    • Recent Activity:
    • Refactored insights logic and worked on migration tasks for filters to queries.
    • Fixed various issues related to insights caching and query handling.
    • Collaborations: Worked closely with other developers on insights-related tasks.
  7. Tomás Farías Santana (tomasfarias)

    • Recent Activity:
    • Focused on batch exports, including exception handling and retry mechanisms.
    • Made several fixes across different modules, enhancing overall stability.
    • Collaborations: Collaborated with multiple team members on batch processing tasks.
  8. Julian Bez (webjunkie)

    • Recent Activity:
    • Engaged in various fixes related to insights and caching, along with improvements to scheduled tasks.
    • Contributed to the enhancement of alert functionalities within the application.
    • Collaborations: Worked with other developers on improving user experience through insights.
  9. Matthew Bridges (Itsindigo)

    • Recent Activity:
    • Fixed UI issues regarding spacing in insights tooltips.
    • Collaborations: Minimal collaboration noted in recent commits.
  10. Georgiy Tarasov (skoob13)

    • Recent Activity:
    • Worked on migrating PersonsNode to ActorsQuery and made several fixes related to insights filtering.
    • Collaborations: Collaborated with others on insights-related enhancements.
  11. Dylan Martin (dmarticus)

    • Recent Activity:
    • Focused on feature flags, enhancing their evaluation logic, and improving session tracking functionalities.
    • Collaborations: Engaged in collaborative efforts for feature flag enhancements.
  12. David Newell (daibhin)

    • Recent Activity:
    • Made various contributions towards improving UI components and fixing bugs across different modules.
    • Collaborations: Actively collaborated with team members on UI/UX improvements.
  13. Anirudh Pillai (anirudhpillai)

    • Recent Activity:
    • Contributed fixes related to API access scopes and improved query handling for cohorts.
    • Collaborations: Minimal collaboration noted in recent commits.
  14. Frank Hamand (frankh)

    • Recent Activity:
    • Focused on enhancing capture functionalities within the application, particularly around replay capture mechanisms.
    • Collaborations: Collaborated with others on capture-related features.
  15. Sandy Spicer (aspicer)

    • Recent Activity:
    • Engaged in various bug fixes and enhancements across different modules, particularly around hogql functionalities.
    • Collaborations: Worked closely with other developers on improving query handling.

Patterns, Themes, and Conclusions

  • The development team is actively engaged in both feature development and bug fixing, demonstrating a balanced approach to maintaining existing functionalities while introducing new features.
  • Collaboration is evident among team members, especially in complex areas such as cyclotron features, insights logic, and batch processing tasks, indicating a cohesive working environment focused on shared goals.
  • There is a strong emphasis on improving user experience through UI enhancements, performance optimizations, and ensuring data integrity across various modules of the application.
  • The frequency of commits suggests that the team is consistently iterating on their work, which is crucial for maintaining momentum in an open-source project like PostHog that relies heavily on community contributions and feedback.

Overall, the recent activities reflect a dedicated team making significant strides in enhancing the PostHog platform while addressing user needs effectively.