HC1: SDLC SIG: Difference between revisions
Add code baseline initiative |
Add more about SDLC |
||
| (One intermediate revision by the same user not shown) | |||
| Line 8: | Line 8: | ||
The Software Delivery Lifecycle (SDLC) SIG contributes to the high level planning, maintenance, and delivery of software in the Zenon Network ecosystem. | The Software Delivery Lifecycle (SDLC) SIG contributes to the high level planning, maintenance, and delivery of software in the Zenon Network ecosystem. | ||
== | == HC1 Software Delivery Lifecycle == | ||
(Work in Progress) | |||
=== 1. Work Definition through SIGs === | |||
The work needed to develop, deliver, and maintain high quality decentralized protocol software involves many different areas of expertise. To provide contributors with working environments that are relevant and actionable to their skillsets, HyperCore One is comprised of Special Interest Groups (SIGs). An HC1 SIG is tasked with defining problems and possible solutions within the scope of a common set of users, stakeholders, skillsets, or technologies. Each HC1 SIG is facilitated by a Chair who has broad discretion on how to best achieve the SIG's desired outcomes. | |||
=== 2. Incentivization is Prioritization (IIP) === | |||
In accordance with our core value of [[HyperCore One#Prosperity|Prosperity]], all critical and desired behavior requires incentives. While HC1 SIGs define problems and possible solutions, the Zenon Network community signals the value of the SIG's facilitation and the completion of defined work. The community should create incentives based on the impact and priority of work rather the time and level of effort required. Contributors can then determine which pieces of work they wish to take on based on the incentives and their skillset. The desired outcome is the completion of high priority items as efficiently as possible. HyperCore One should help develop and maintain software which will facilitate this incentivization process. | |||
== Capabilities == | |||
=== Prioritize work according to community incentives === | |||
As a contributor, I want to know what I will be compensated for completing different pieces of work, so that I can prioritize what to work on. | |||
=== Establish and maintain code baseline === | === Establish and maintain code baseline === | ||
Latest revision as of 20:25, 22 August 2024
Chair: George
Communications: https://matrix.to/#/#sig-sdlc:hc1.chat
Meetings: n/a
Scope
The Software Delivery Lifecycle (SDLC) SIG contributes to the high level planning, maintenance, and delivery of software in the Zenon Network ecosystem.
HC1 Software Delivery Lifecycle
(Work in Progress)
1. Work Definition through SIGs
The work needed to develop, deliver, and maintain high quality decentralized protocol software involves many different areas of expertise. To provide contributors with working environments that are relevant and actionable to their skillsets, HyperCore One is comprised of Special Interest Groups (SIGs). An HC1 SIG is tasked with defining problems and possible solutions within the scope of a common set of users, stakeholders, skillsets, or technologies. Each HC1 SIG is facilitated by a Chair who has broad discretion on how to best achieve the SIG's desired outcomes.
2. Incentivization is Prioritization (IIP)
In accordance with our core value of Prosperity, all critical and desired behavior requires incentives. While HC1 SIGs define problems and possible solutions, the Zenon Network community signals the value of the SIG's facilitation and the completion of defined work. The community should create incentives based on the impact and priority of work rather the time and level of effort required. Contributors can then determine which pieces of work they wish to take on based on the incentives and their skillset. The desired outcome is the completion of high priority items as efficiently as possible. HyperCore One should help develop and maintain software which will facilitate this incentivization process.
Capabilities
Prioritize work according to community incentives
As a contributor, I want to know what I will be compensated for completing different pieces of work, so that I can prioritize what to work on.
Establish and maintain code baseline
As a developer, I want to build off of a well maintained and up-to-date codebase so that my contributions are not blocked by technical debt.
This includes:
- Keeping dependencies up to date
- Reducing linting errors