flightctl/flightctl
Oct 2024 – Mar 2026
17 Months active
Languages Used
GoMarkdownBashYAMLbashyamlMakefileShell
Technical Skills
API DevelopmentBackend DevelopmentCachingConfiguration ManagementGit IntegrationGo
Avishay Traeger
PROFILE
Avishay Traeger
Over 17 months, Andrew Traeger engineered core backend systems for the flightctl/flightctl repository, focusing on scalable device management, event-driven architecture, and robust API design. He delivered features such as Redis-backed queues with exponential backoff, granular event emission, and deterministic resource versioning, all while maintaining strong data integrity and observability. Using Go, Kubernetes, and Redis, Andrew refactored service layers for maintainability, enforced security best practices, and improved developer onboarding with comprehensive documentation. His work addressed reliability, governance, and integration challenges, consistently reducing operational risk and streamlining workflows. The depth of his contributions reflects a thoughtful, systems-oriented engineering approach.
Overall Statistics
Feature vs Bugs
77%Features
Repository Contributions
128Total
Bugs
20
Commits
128
Features
66
Lines of code
66,855
Activity Months17
Your Network
2760 peopleShared Repositories
38
Work History
March 2026
2 Commits
Mar 1, 2026March 2026: Delivered critical data integrity and external workflow improvements for flightctl/flightctl. Implemented TemplateVersion Fleet-scoped Uniqueness Enforcement to prevent cross-fleet name collisions by incorporating fleet name into the primary key and adjusting retrieval logic. Fixed ReplaceResourceSync validation to allow repository updates when status is set, aligning with external request handling and non-internal flows. Added automated test coverage for the repository update scenario. These changes reduce error conditions, improve reliability of fleet-agnostic lookups, and strengthen integration points with external systems.
2 Commits
Mar 1, 2026March 2026: Delivered critical data integrity and external workflow improvements for flightctl/flightctl. Implemented TemplateVersion Fleet-scoped Uniqueness Enforcement to prevent cross-fleet name collisions by incorporating fleet name into the primary key and adjusting retrieval logic. Fixed ReplaceResourceSync validation to allow repository updates when status is set, aligning with external request handling and non-internal flows. Added automated test coverage for the repository update scenario. These changes reduce error conditions, improve reliability of fleet-agnostic lookups, and strengthen integration points with external systems.
March 2026
February 2026
2 Commits • 1 Features
Feb 1, 2026February 2026 — flightctl/flightctl Key features delivered: - Developer onboarding and documentation: Introduced AGENTS.md across root, api, docs, deploy, and test areas and a CONTRIBUTING.md to guide new contributors, standardize practices, and improve project maintainability. This work, documented in commits including ddcf4eead73f8df7b5ad94e8779b034a19d24461, lays the foundation for faster onboarding and consistent coding standards. - Deterministic application status output: Implemented deterministic sorting for applicationsSummary.info messages to avoid nondeterministic map iteration, with tests to ensure stable summaries regardless of input order. This was implemented and committed as EDM-3409 (e589786d9a9a2db582ba1abfeadf3c94388ff56f). Major bugs fixed: - Replaced nondeterministic map-driven status construction with deterministic ordering, eliminating flaky status updates and ensuring consistent user-facing summaries. Coverage includes regression tests to guard against input-order dependencies. Overall impact and accomplishments: - Significantly improved developer onboarding, governance, and project maintainability through structured documentation and contribution guidance. - Increased reliability and predictability of status reporting, reducing noise and bugs related to non-deterministic outputs. - Established a solid baseline for future features with documented conventions around API design, codegen, linting, and testing. Technologies/skills demonstrated: - Documentation strategy and governance (AGENTS.md, CONTRIBUTING.md), cross-area guidance (root/api/docs/deploy/test) - Deterministic programming patterns for map-derived data - Unit and integration testing practices to validate deterministic behavior - Repository organization and contribution workflows aligned with Kubernetes-style API design and lint-before-commit practices
February 2026
2 Commits • 1 Features
Feb 1, 2026February 2026 — flightctl/flightctl Key features delivered: - Developer onboarding and documentation: Introduced AGENTS.md across root, api, docs, deploy, and test areas and a CONTRIBUTING.md to guide new contributors, standardize practices, and improve project maintainability. This work, documented in commits including ddcf4eead73f8df7b5ad94e8779b034a19d24461, lays the foundation for faster onboarding and consistent coding standards. - Deterministic application status output: Implemented deterministic sorting for applicationsSummary.info messages to avoid nondeterministic map iteration, with tests to ensure stable summaries regardless of input order. This was implemented and committed as EDM-3409 (e589786d9a9a2db582ba1abfeadf3c94388ff56f). Major bugs fixed: - Replaced nondeterministic map-driven status construction with deterministic ordering, eliminating flaky status updates and ensuring consistent user-facing summaries. Coverage includes regression tests to guard against input-order dependencies. Overall impact and accomplishments: - Significantly improved developer onboarding, governance, and project maintainability through structured documentation and contribution guidance. - Increased reliability and predictability of status reporting, reducing noise and bugs related to non-deterministic outputs. - Established a solid baseline for future features with documented conventions around API design, codegen, linting, and testing. Technologies/skills demonstrated: - Documentation strategy and governance (AGENTS.md, CONTRIBUTING.md), cross-area guidance (root/api/docs/deploy/test) - Deterministic programming patterns for map-derived data - Unit and integration testing practices to validate deterministic behavior - Repository organization and contribution workflows aligned with Kubernetes-style API design and lint-before-commit practices
January 2026
1 Commits • 1 Features
Jan 1, 2026January 2026 monthly summary for flightctl/flightctl focused on strengthening API reliability and developer-facing feedback. Implemented precise HTTP error handling in the console service to replace generic 500 responses with specific status codes based on device availability and state conflicts, improving clarity for clients and reducing troubleshooting time. This work aligns API behavior with product requirements and supports smoother integrations with partners.
1 Commits • 1 Features
Jan 1, 2026January 2026 monthly summary for flightctl/flightctl focused on strengthening API reliability and developer-facing feedback. Implemented precise HTTP error handling in the console service to replace generic 500 responses with specific status codes based on device availability and state conflicts, improving clarity for clients and reducing troubleshooting time. This work aligns API behavior with product requirements and supports smoother integrations with partners.
January 2026
December 2025
3 Commits • 1 Features
Dec 1, 20252025-12 Monthly Summary — flightctl/flightctl: Key deliverables focused on correctness, data integrity, and safer fleet synchronization: - User-Defined Annotations Preservation in Fleet Synchronization: prevents overwriting user-defined annotations during fleet sync; ensures system-managed vs user-defined annotations are respected. (EDM-2748; commit a7426c918efe96e12b90afccb4219cc0003f465f) - Fleet Ownership Update and Validation Bug fix: preserves owner fields, prevents manual edits to fleets, and introduces integration tests to validate ownership behavior. (EDM-2781; commit eb19b9e58aa7ed332bb574199c25ebccf8f78e05; additional integration testing described in the same change) - ResourceSync ownership bypass refinement: adds context-key to allow updates with existing owners by bypassing the owner check while maintaining external context semantics; short-term solution with noted TODO to move ownership validation to the service layer. (EDM-2800; commit 4fa9d5ca1ca9dd872582c83e0a8845eae3ea06e6) Overall impact and business value: - Strengthened data integrity in fleet synchronization, reducing risk of accidental annotation loss or unauthorized ownership changes. - Increased reliability and maintainability through targeted fixes and integration tests. - Demonstrated advanced context handling, ownership semantics, and test-driven improvements across the ResourceSync flow. Technologies/skills demonstrated: - Context management across resource updates (external vs internal contexts) - Annotations handling and preservation strategies - Store-layer ownership validation mitigation and integration testing - End-to-end test coverage for critical update paths
December 2025
3 Commits • 1 Features
Dec 1, 20252025-12 Monthly Summary — flightctl/flightctl: Key deliverables focused on correctness, data integrity, and safer fleet synchronization: - User-Defined Annotations Preservation in Fleet Synchronization: prevents overwriting user-defined annotations during fleet sync; ensures system-managed vs user-defined annotations are respected. (EDM-2748; commit a7426c918efe96e12b90afccb4219cc0003f465f) - Fleet Ownership Update and Validation Bug fix: preserves owner fields, prevents manual edits to fleets, and introduces integration tests to validate ownership behavior. (EDM-2781; commit eb19b9e58aa7ed332bb574199c25ebccf8f78e05; additional integration testing described in the same change) - ResourceSync ownership bypass refinement: adds context-key to allow updates with existing owners by bypassing the owner check while maintaining external context semantics; short-term solution with noted TODO to move ownership validation to the service layer. (EDM-2800; commit 4fa9d5ca1ca9dd872582c83e0a8845eae3ea06e6) Overall impact and business value: - Strengthened data integrity in fleet synchronization, reducing risk of accidental annotation loss or unauthorized ownership changes. - Increased reliability and maintainability through targeted fixes and integration tests. - Demonstrated advanced context handling, ownership semantics, and test-driven improvements across the ResourceSync flow. Technologies/skills demonstrated: - Context management across resource updates (external vs internal contexts) - Annotations handling and preservation strategies - Store-layer ownership validation mitigation and integration testing - End-to-end test coverage for critical update paths
November 2025
6 Commits • 4 Features
Nov 1, 2025Month: 2025-11 Overview: Delivered security hardening, reliability, and troubleshooting improvements for flightctl/flightctl. Focus was on business value: reduce risk, streamline operations, and improve developer experience while keeping customer-facing APIs stable during migrations. Key features delivered: - Security hardening: Added HTTP headers (Strict-Transport-Security and X-Content-Type-Options) to Flight Control API to enforce HTTPS and prevent MIME sniffing. - Automation and hygiene: Implemented GitHub Actions workflow to automatically close stale PRs, reducing PR backlog and maintenance overhead. - UX and reliability improvements: Enhanced error handling and UI messaging for ResourceSync status and repository status to improve troubleshooting. - Reliability uplift: Introduced a shared Redis publisher to resolve queue instance conflicts and improve recovery logging and event emission. Major bugs fixed / stability work: - Stability workaround: Temporarily disabled backward compatibility tests during schema migration to focus on maintaining current functionality and progress migration tasks. Overall impact and accomplishments: - Strengthened security posture and reduced operational risk for API interactions. - Lowered maintenance burden through automation and cleaner repository hygiene. - Improved troubleshooting with actionable error messages and reliable event emission in distributed components. - Demonstrated cross-functional collaboration across security, CI/CD, backend, and ops to accelerate migration readiness. Technologies/skills demonstrated: - Go, HTTP security headers, GitHub Actions, Redis with a shared publisher, error handling, UI messaging, and go-git error handling.
6 Commits • 4 Features
Nov 1, 2025Month: 2025-11 Overview: Delivered security hardening, reliability, and troubleshooting improvements for flightctl/flightctl. Focus was on business value: reduce risk, streamline operations, and improve developer experience while keeping customer-facing APIs stable during migrations. Key features delivered: - Security hardening: Added HTTP headers (Strict-Transport-Security and X-Content-Type-Options) to Flight Control API to enforce HTTPS and prevent MIME sniffing. - Automation and hygiene: Implemented GitHub Actions workflow to automatically close stale PRs, reducing PR backlog and maintenance overhead. - UX and reliability improvements: Enhanced error handling and UI messaging for ResourceSync status and repository status to improve troubleshooting. - Reliability uplift: Introduced a shared Redis publisher to resolve queue instance conflicts and improve recovery logging and event emission. Major bugs fixed / stability work: - Stability workaround: Temporarily disabled backward compatibility tests during schema migration to focus on maintaining current functionality and progress migration tasks. Overall impact and accomplishments: - Strengthened security posture and reduced operational risk for API interactions. - Lowered maintenance burden through automation and cleaner repository hygiene. - Improved troubleshooting with actionable error messages and reliable event emission in distributed components. - Demonstrated cross-functional collaboration across security, CI/CD, backend, and ops to accelerate migration readiness. Technologies/skills demonstrated: - Go, HTTP security headers, GitHub Actions, Redis with a shared publisher, error handling, UI messaging, and go-git error handling.
November 2025
October 2025
1 Commits
Oct 1, 2025Monthly summary for 2025-10 focusing on CI reliability and backport governance in flightctl/flightctl. Delivered a fix to target branch detection in commit message checks, improving accuracy of backport operations across GitHub Actions and local environments.
October 2025
1 Commits
Oct 1, 2025Monthly summary for 2025-10 focusing on CI reliability and backport governance in flightctl/flightctl. Delivered a fix to target branch detection in commit message checks, improving accuracy of backport operations across GitHub Actions and local environments.
September 2025
12 Commits • 4 Features
Sep 1, 2025September 2025 monthly summary for flightctl/flightctl: Delivered core reliability, observability, and developer tooling enhancements that improve uptime, issue detection, and deployment consistency. Key features include robust queue processing with Redis resilience, Prometheus metrics for worker visibility, and device status/rendering improvements. Also shipped packaging consistency fixes, a containerized linting environment, and test reliability improvements to stabilize Redis-related workflows. Overall impact: higher system resilience, faster root-cause identification, and smoother deployments with measurable business value.
12 Commits • 4 Features
Sep 1, 2025September 2025 monthly summary for flightctl/flightctl: Delivered core reliability, observability, and developer tooling enhancements that improve uptime, issue detection, and deployment consistency. Key features include robust queue processing with Redis resilience, Prometheus metrics for worker visibility, and device status/rendering improvements. Also shipped packaging consistency fixes, a containerized linting environment, and test reliability improvements to stabilize Redis-related workflows. Overall impact: higher system resilience, faster root-cause identification, and smoother deployments with measurable business value.
September 2025
August 2025
12 Commits • 4 Features
Aug 1, 2025August 2025 monthly summary for flightctl/flightctl. Delivered architectural refinements and reliability improvements across the platform with a strong focus on observability, resilience, governance, and operator usability. Implemented an event-driven architecture with Redis-backed event emission, added granular events for devices, fleets, and repositories, and deduplicated device disconnects to improve reconciliation and incident response. Strengthened the Redis-backed queue with exponential backoff retries and Redis Streams consumer groups, accompanied by integration tests to validate end-to-end resilience and message tracing. Enforced governance for ResourceSync by preventing fleet spec or label updates on owned fleets, with test coverage. Enhanced alerts with human-readable summaries and API message annotations, and fixed documentation navigation. Fixed NodePort connectivity issues by correcting hardcoded URLs in Helm templates for Alertmanager and CLI artifacts, improving reliability during deployments.
August 2025
12 Commits • 4 Features
Aug 1, 2025August 2025 monthly summary for flightctl/flightctl. Delivered architectural refinements and reliability improvements across the platform with a strong focus on observability, resilience, governance, and operator usability. Implemented an event-driven architecture with Redis-backed event emission, added granular events for devices, fleets, and repositories, and deduplicated device disconnects to improve reconciliation and incident response. Strengthened the Redis-backed queue with exponential backoff retries and Redis Streams consumer groups, accompanied by integration tests to validate end-to-end resilience and message tracing. Enforced governance for ResourceSync by preventing fleet spec or label updates on owned fleets, with test coverage. Enhanced alerts with human-readable summaries and API message annotations, and fixed documentation navigation. Fixed NodePort connectivity issues by correcting hardcoded URLs in Helm templates for Alertmanager and CLI artifacts, improving reliability during deployments.
July 2025
29 Commits • 20 Features
Jul 1, 2025July 2025 monthly summary for flightctl/flightctl: Delivered deployment and observability enhancements with measurable business impact, refactored core workflows for reliability, and advanced security and performance improvements. The work focused on shipping high-value features, stabilizing the platform, and enabling faster incident response through standardized events and improved metrics.
29 Commits • 20 Features
Jul 1, 2025July 2025 monthly summary for flightctl/flightctl: Delivered deployment and observability enhancements with measurable business impact, refactored core workflows for reliability, and advanced security and performance improvements. The work focused on shipping high-value features, stabilizing the platform, and enabling faster incident response through standardized events and improved metrics.
July 2025
June 2025
14 Commits • 5 Features
Jun 1, 2025June 2025 monthly summary for flightctl/flightctl. Deliveries focused on establishing a robust alerting capability, improving device event handling, and strengthening spec comparison and versioning reliability, while cleaning up deprecated paths and standardizing API documentation. These efforts improved proactive incident detection, data correctness, deployment reliability, and developer experience in a scalable, Kubernetes-driven environment.
June 2025
14 Commits • 5 Features
Jun 1, 2025June 2025 monthly summary for flightctl/flightctl. Deliveries focused on establishing a robust alerting capability, improving device event handling, and strengthening spec comparison and versioning reliability, while cleaning up deprecated paths and standardizing API documentation. These efforts improved proactive incident detection, data correctness, deployment reliability, and developer experience in a scalable, Kubernetes-driven environment.
April 2025
7 Commits • 3 Features
Apr 1, 2025April 2025: Delivered a comprehensive Event System for flightctl/flightctl, including API endpoints with OpenAPI schema, persistent storage with a database schema and service logic for creating/listing/deleting events, CLI support to list events, end-to-end event logging for auditability, and a retention policy to purge old events. Also improved selector resolution robustness by prioritizing hidden selectors and gracefully falling back to visible selectors. In CI, updated log collection by removing the --previous flag from kubectl logs to capture current container logs. These changes collectively improve auditability, data lifecycle management, resource reliability, and observability.
7 Commits • 3 Features
Apr 1, 2025April 2025: Delivered a comprehensive Event System for flightctl/flightctl, including API endpoints with OpenAPI schema, persistent storage with a database schema and service logic for creating/listing/deleting events, CLI support to list events, end-to-end event logging for auditability, and a retention policy to purge old events. Also improved selector resolution robustness by prioritizing hidden selectors and gracefully falling back to visible selectors. In CI, updated log collection by removing the --previous flag from kubectl logs to capture current container logs. These changes collectively improve auditability, data lifecycle management, resource reliability, and observability.
April 2025
March 2025
3 Commits • 2 Features
Mar 1, 2025March 2025 highlights: Implemented ServiceHandler-based centralization for service logic and validation, standardized request IDs via chi middleware, and hardened EnrollmentRequest status to prevent client manipulation. These changes unify API and async task behavior, strengthen multitenancy enforcement, and improve observability, security, and maintainability.
March 2025
3 Commits • 2 Features
Mar 1, 2025March 2025 highlights: Implemented ServiceHandler-based centralization for service logic and validation, standardized request IDs via chi middleware, and hardened EnrollmentRequest status to prevent client manipulation. These changes unify API and async task behavior, strengthen multitenancy enforcement, and improve observability, security, and maintainability.
February 2025
5 Commits • 3 Features
Feb 1, 2025February 2025 milestones focused on API robustness, internal architecture improvements, and user-facing fleet listing enhancements in flightctl/flightctl. Delivered a major API layer refactor and standardization effort that aligns groups to flightctl.io, updates OpenAPI definitions, splits transport and service layers for maintainability, and refreshes docs. Implemented Fleet Listing Output Enhancement to display DEVICES column only when relevant. Completed Internal Task Management Architecture Decoupling by extracting the callback manager into a new tasks_client package to break import cycles and enable scalable task-service interactions. No critical bugs fixed; the month was primarily about refactors and architectural improvements that deliver long-term business value including improved API consistency, maintainability, and operator experience.
5 Commits • 3 Features
Feb 1, 2025February 2025 milestones focused on API robustness, internal architecture improvements, and user-facing fleet listing enhancements in flightctl/flightctl. Delivered a major API layer refactor and standardization effort that aligns groups to flightctl.io, updates OpenAPI definitions, splits transport and service layers for maintainability, and refreshes docs. Implemented Fleet Listing Output Enhancement to display DEVICES column only when relevant. Completed Internal Task Management Architecture Decoupling by extracting the callback manager into a new tasks_client package to break import cycles and enable scalable task-service interactions. No critical bugs fixed; the month was primarily about refactors and architectural improvements that deliver long-term business value including improved API consistency, maintainability, and operator experience.
February 2025
January 2025
12 Commits • 6 Features
Jan 1, 2025January 2025 monthly summary for flightctl/flightctl. Delivered multiple features and reliability improvements with measurable business impact: expanded dynamic configuration handling, enhanced fleet visibility, a streamlined task pipeline, and clearer error handling and documentation. Key features and outcomes include dynamic configuration variable substitution across inline and git-mounted configs, enabling correct dynamic value resolution and reducing config-related deployments issues; added device counts and status summaries to fleet listings in CLI/API, improving fleet management visibility and decision making; migrated the task queue from RabbitMQ to Redis to simplify architecture, boost reliability, and reduce latency; enhanced device status reporting by annotating the last rollout error, improving failure diagnosis; and data persistence improvements ensuring full resources are returned after updates and removing redundant ownership checks for simpler update flows. Supporting improvements include fixing fleet updates resource naming to target the correct fleet, implementing an OpenAPI error handler for clearer, longer-path errors, and updating Go template syntax documentation to help users access labels with hyphens. These changes collectively reduce toil, improve deployment reliability, and strengthen API/data consistency.
January 2025
12 Commits • 6 Features
Jan 1, 2025January 2025 monthly summary for flightctl/flightctl. Delivered multiple features and reliability improvements with measurable business impact: expanded dynamic configuration handling, enhanced fleet visibility, a streamlined task pipeline, and clearer error handling and documentation. Key features and outcomes include dynamic configuration variable substitution across inline and git-mounted configs, enabling correct dynamic value resolution and reducing config-related deployments issues; added device counts and status summaries to fleet listings in CLI/API, improving fleet management visibility and decision making; migrated the task queue from RabbitMQ to Redis to simplify architecture, boost reliability, and reduce latency; enhanced device status reporting by annotating the last rollout error, improving failure diagnosis; and data persistence improvements ensuring full resources are returned after updates and removing redundant ownership checks for simpler update flows. Supporting improvements include fixing fleet updates resource naming to target the correct fleet, implementing an OpenAPI error handler for clearer, longer-path errors, and updating Go template syntax documentation to help users access labels with hyphens. These changes collectively reduce toil, improve deployment reliability, and strengthen API/data consistency.
December 2024
8 Commits • 5 Features
Dec 1, 2024December 2024 monthly summary for flightctl/flightctl focused on security hardening, reliability, and maintainability improvements with measurable business value. Delivered centralized KV storage with password authentication and an official Redis runtime, introduced a configurable HTTP server for API and agent services, added CI/CD debugging support via Kubernetes logs collection, expanded deployment flexibility with alternate PostgreSQL images and secret encoding for Redis and RabbitMQ, and refactored the data store layer to a GenericStore abstraction. No explicit bug fixes were logged as separate issues this month; changes addressed known security, observability, and maintainability gaps to reduce risk and accelerate issue resolution.
8 Commits • 5 Features
Dec 1, 2024December 2024 monthly summary for flightctl/flightctl focused on security hardening, reliability, and maintainability improvements with measurable business value. Delivered centralized KV storage with password authentication and an official Redis runtime, introduced a configurable HTTP server for API and agent services, added CI/CD debugging support via Kubernetes logs collection, expanded deployment flexibility with alternate PostgreSQL images and secret encoding for Redis and RabbitMQ, and refactored the data store layer to a GenericStore abstraction. No explicit bug fixes were logged as separate issues this month; changes addressed known security, observability, and maintainability gaps to reduce risk and accelerate issue resolution.
December 2024
November 2024
6 Commits • 3 Features
Nov 1, 2024Month 2024-11 – Consolidated delivery and security improvements for flightctl/flightctl with a focus on repository handling, templating, ignition reliability, and ACM onboarding. The work reduced operational overhead, improved configuration dynamism, and strengthened security for onboarding and data access.
November 2024
6 Commits • 3 Features
Nov 1, 2024Month 2024-11 – Consolidated delivery and security improvements for flightctl/flightctl with a focus on repository handling, templating, ignition reliability, and ACM onboarding. The work reduced operational overhead, improved configuration dynamism, and strengthened security for onboarding and data access.
October 2024
5 Commits • 4 Features
Oct 1, 2024October 2024 monthly summary for flightctl/flightctl focusing on delivering robust configuration management, cache-first strategies, and improved device deployment consistency across fleets and templates.
5 Commits • 4 Features
Oct 1, 2024October 2024 monthly summary for flightctl/flightctl focusing on delivering robust configuration management, cache-first strategies, and improved device deployment consistency across fleets and templates.
October 2024
Activity
Loading activity data...
Quality Metrics
Correctness91.4%
Maintainability88.6%
Architecture89.2%
Performance83.8%
AI Usage20.4%
Skills & Technologies
Programming Languages
BashDockerfileGinkgoGoMakefileMarkdownRedisSQLShellSpecfile
Technical Skills
API DesignAPI DevelopmentAPI IntegrationAPI InteractionAPI SecurityAPI SpecificationAPI designAPI developmentAPI securityAlertingAutomationBackend DevelopmentBuild AutomationCI/CDCLI Development
Repositories Contributed To
Overview of all repositories you've contributed to across your timeline