Screen Reader Mode Icon

Welcome to an exciting opportunity to shape the future of KernelCI

We've partnered with a UX specialist to enhance our Web Dashboard for displaying test results. Your feedback is crucial, so please take our survey.

We also have a few spots left for UX interviews via video conference—let us know if you're interested!

We're in the process of designing a new Web Dashboard for KernelCI and building a robust core infrastructure to replace our existing system. Imagine a CI pipeline that extends beyond KernelCI labs, allowing tests to run externally with results contributing seamlessly to a shared database. Our goal is a powerful dashboard for the community to evaluate test results effectively.

For a quick overview of the UX redesign project, check our blog post: UX Redesign Project Summary.

Engage with us through our mailing list post: KernelCI Mailing List.

Ready to share your thoughts? Talk to us at: kernelci-webdashboard@groups.io.

Your input drives our progress!

Question Title

* 1. Please provide your name (optional)

Question Title

* 2. Provide your email (optional)

Question Title

* 3. What role do you play in relation to Kernel Linux?
Are you an upstream developer or maintainer? Which area or subsystem? Do you develop any products or hardware and maintain downstream branches? Or is your role more around tests and bug fixes? Or something else not listed here?

Question Title

* 4. How long have you been involved in the Kernel community?

Question Title

* 5. Within your workflow to play your role, could you walk me through your testing journey step by step?
(ex. 1. Code Review; 2. Integration Testing; 3. Performance and Regression Testing; 4. Bug Resolution; 5. Final Approval and Integration)

Question Title

* 6. What specific data do you look for in failing tests? What specific data do filter by to find tests relevant for you?

Question Title

* 7. What indicators do you consider crucial to include in the KernelCI Dashboard?

  Irrelevant Little important Nice to have Should have Indispensable
Real-time Status (Immediate updates on builds, test results, and regressions)
Number of failing tests
Test scheduling status (e.g., whether it ran, scheduled time)
Relevant snippet from the test log
List of platforms, configurations, and variants encountering the same failure
Status of the regression (e.g., found, reported, under discussion, fix available, merged, backported, etc.)
Code Coverage and Style (Visual representation of code coverage and adherence to style guidelines)
Notifications (Customizable alerts for code reviews, build failures, and regressions)
Integration with Version Control (Seamless tracking of code commits, merges, and branch integrations)
Performance and Security (Metrics on code impact on performance and indicators for security issues)
Documentation Integration (Links to impacted documentation and updates)
Collaboration Hub (Integration with communication channels for discussions and feedback)
Historical Metrics (Historical data on code quality, test results, and performance)
Feedback Loop (provide feedback and communicate with maintainers)
Security Status (Indicators for any security-related issues or vulnerabilities in the code)

Question Title

* 8. Feel free to include additional indicators that haven't been highlighted but are crucial for a comprehensive KernelCI Dashboard:

Question Title

* 9. Do you currently use KernelCI Dashboard in your routine?

Question Title

* 10. If you are using it, what aspects does the KernelCI Dashboard currently address, and what would you like it to address in the future?

Question Title

* 11. How likely is it that you would recommend KernelCI Dashboard to a friend or colleague?

NOT AT ALL LIKELY
EXTREMELY LIKELY
0 of 11 answered
 

T