Schevo Audit
Jan. 2006 to Apr. 2006.
This Audit demonstrates mainly:
- Change Resistance within Open Source Projects
- Developer Dependency of Open Source Projects
- Failure of existent Developers to share workload and responsibilities
- Leadership Failures
Summary
- The product does not keep what the website promises
- simplicity, automations, ...
- The project has several deficits
- Missing contribution processes
- Project participation is not engouraged
- Attemps to simplify product/project entry were surpressed
- By existent Developer
- By Failure of Leadership to Split Subsystem Responsibilities
Reworks
Audit / Rework
Post Analysis
Nov. 2006
The oversensivity of the existent developer can be explained simply:
Developers can get a very close 'relation' to a code repository. Touching this repository with commits can disrupt the thinking flow of existent developers.
Getting a branch location with commit access is not that easy, see e.g. the trac-project as an example. Thus the offer of the developer to move developement into a branch location was an acceptable on. This is independent of favorizing more agile methods which do direct trunk development - and it's independent of the 'chirugical' non-intrusive nature of the commits. In order to avoid conflicts, the method of base:wiki:PlanDecentralBranching can be used.
This method goes one step beyond branch development. I frees the central repository from increased revision numbers, giving each developer a fully dedicated repository with a web-front-end.