Skip to content

feat: bootstrap the engineering workflows page #27

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
48 changes: 48 additions & 0 deletions docs/engineering/workflows/intro.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,48 @@
# Engineering Workflows

**Central Tenet**: **Simplicity through Automation**. Our aim: lean on CI/automation and eliminate manual rule enforcement.

**Disclaimer**: Our workflows will adapt and evolve as automation capabilities expand. Our vision is a future with fewer manual interventions and increased reliance on bot integrations.

**Guiding Philosophies**: We believe in **Flexibility** and **Polar Adaptability**, fostering processes that offer adaptability without stifling creativity.

**Workflow Principles**:
- **Composable & Adaptive**: These workflows can be combined, adjusted, or created from scratch. They’re tools, not constraints.
- **Continuous Optimization**: We encourage constant refinement of workflows to suit changing needs.
- **Freedom to Override**: When a workflow feels restrictive, it's encouraged to bypass it and assume responsibility for the results.

## Workflows

1. **Infinito Tablero**
- Ideal for: Complex projects in small to medium teams seeking a continuous flow approach.
[Details](./infinito-tablero.md)

2. **Solo Voyager**
- Ideal for: High-autonomy tasks, specialists, side projects, or teams operating outside daily routines. Emphasizes high responsibility.
[Details](./solo-voyager.md)

3. **Rigorous & Deliberate**
- Ideal for: Deep collaborative efforts. Suitable for inclusive participation, from part-timers to external contributors.
[Details](./rigorous-deliberate.md)

4. **Rapid Prototyping**
- Ideal for: Fast-paced development phases where swift iteration and adaptability are paramount.
[Details](./rapid-prototyping.md)

5. **Taskforce/Warzone**
- Ideal for: Intense focus scenarios, like hackathons, critical bugs, or product launches. Temporarily bypasses standard procedures.
[Details](./taskforce-warzone.md)

6. **Criteria-Based**
- Ideal for: Projects with clear, quantifiable objectives, especially when deeper project goals are less visible.
[Details](./criteria-based.md)

### Propose a Workflow
Identified a gap? Feel free to innovate and suggest.

## Key Takeaways

- **Hierarchy in Projects**: Projects are streamlined with a hierarchical structure ensuring cohesion across sub-projects.
- **Uniqueness & Unity**: While each team tailors its rules, a foundational common ground is maintained to foster unity.
- **Effective Communication**: We prioritize clear, concise communication over excessive chatter.
- **Ultimate Flexibility**: Processes serve as guidelines, not strict rules. Adaptation in the best interest of the mission is always prioritized.
6 changes: 5 additions & 1 deletion spell-check-dictionary.txt
Original file line number Diff line number Diff line change
Expand Up @@ -105,4 +105,8 @@ Gnodaos
dApp
Berty
Dev
devs
devs
Kanban
Infinito
Tablero
roadmaps