Project Description
Keeping a consolidated view of a project's progress is a non-trivial endeavor. There are far too many moving parts from its inception, such as planning, issue tracking, development, and testing. All the while one must keep track of some form of metrics to ensure that there's progress, and that the progress is happening in the right direction (or whatever is considered the right direction at the moment).
Traditionally we have enough tools to keep track of a project's progress in terms of planning, work planned, and work finished. Issue trackers are ubiquitous, and we're all used to using them and obtaining rough metrics out of them. However, just because work gets done doesn't mean the work being done is the right kind of work.
At its infancy, the s3gw project is going through a turmoil of development: we know where we want to go, we have a good idea how we'll get there, but we know a lot of things are going to be broken while we're on the road to get there.
While issue trackers help us keep track of work being done, these are not the right tools to keep track of how much of an API has been covered, for instance, or what kind of performance we can get out of the software at any given point in time. Even though one can keep track of these things in the form of issues, establishing baselines for different metrics and comparing against them then becomes a laborious, mind-numbing manual task that often has to involve spreadsheets.
Instead, we are proposing a dedicated web-based tracker, focused on running coverage and performance tests against the project at several points in time, keeping a history of results against known baselines, that we can then rely on when making decisions going forward and to evaluate where we are and how far we've come.
Goal for this Hackweek
The scope of this project is a bit far too broad for a one week development cycle. Being reasonable in goal setting, by the end of this hackweek we intend to have basic testing functionality and result reporting via a web interface.
Resources
Project's repository: github
Demo: TBA
This project is part of:
Hack Week 21
Activity
Comments
Be the first to comment!
Similar Projects
Bring to Cockpit + System Roles capabilities from YAST by miguelpc
Bring to Cockpit + System Roles features from YAST
Cockpit and System Roles have been added to SLES 16 There are several capabilities in YAST that are not yet present in Cockpit and System Roles We will follow the principle of "automate first, UI later" being System Roles the automation component and Cockpit the UI one.
Goals
The idea is to implement service configuration in System Roles and then add an UI to manage these in Cockpit. For some capabilities it will be required to have an specific Cockpit Module as they will interact with a reasource already configured.
Resources
A plan on capabilities missing and suggested implementation is available here: https://docs.google.com/spreadsheets/d/1ZhX-Ip9MKJNeKSYV3bSZG4Qc5giuY7XSV0U61Ecu9lo/edit
Linux System Roles: https://linux-system-roles.github.io/