Project Swap Sprint
Developers exchange knowledge and work on apps which they don't normally maintain, elementary-wide, for one week, on bugs and blueprints of any difficulty. Thus, besides understanding other codebases, project leaders will get help from others on bugs they can't fix.
Phase 1: developers assign bugs on which they want somebody else to work to https:/
Phase 2: developers pick bugs and blueprints assigned to ~elementary-driveby and work on them
Phase 3: everybody gets frustrated about different coding styles and ragequits unless a unified coding style is created
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Sergey "Shnatsel" Davidoff
- Direction:
- Approved
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Approved in 3rd contributor meeting
We'll need an explaination of the whole driveby team concept in the sprint announcement, and looks like the only one who understands it is ~shnatsel
