|[PROCESS] - Increase Users Code Level Contributions [message #3135]
||Mon, 11 October 2004 11:05
Originally posted by: ilias.lazaridis.com|
An user is annoyed by an unprocessed Issue.
The user intents to solve this issue with the action of a patch contribution.
Between intention and action are several barriers.
Increasing User Contributions means essentially:
*barrier:* learn java
- solved: within eclipse.org project, most users are java-developers
- provide: collaborate with e-learning vendor, provide java teaching tools (for total newcomers).
*barrier:* get team tools
- solved: all neccessary tools included in the eclipse SDK
- provide: simplified automated download of SDK (when using non SDK eclipse)
*barrier:* setup access to central repository
- provide a wizard within eclipse
- to gain access keys (e.g. SSH)
- to create an contributors account [for future use, as new contributors usually send patches instead of directly writing to the CVS]
*barrier:* setup local Project
- solved partly: some projects provide ProjectSetFiles (PSF)
- provide: all projects should publish PSF
- provide: autogeneration of PSF
- provide: automated retrieval of the PSF
- solved: creation of local project based on the PSF
*barrier:* detect the location of the Issue (in the sources / CVS)
- provide: automated mechanism to detect relevant location of an issue in the source-code
- manual process: ITS (issue tracking system) has an entry
- protocol: the team's issue manager should enter the location of the defect within e.g. 5 working days
*barrier:* reading and understanding code
- ?: clear documentation of source codes
- provide: source code visualization tools
*barrier:* switch eclipse ide (or the relevant part) into debug mode
- ?: simple mechanism to switch eclipse into self-debug mode
*barrier:* generate patch, write some docu, commit note
- provide: patch generation wizard
*barrier:* transfere patch & docu to the relevant destination
- provide: automated method to bring patch where it belongs too (e.g. Issue Tracking System, component lead, ...)
The lower the "Barrier Strength", the higher the "intention to action" ratio!
Currently, the Barrier Strength is very high.
If 10 users plan to become long term developers, most possibly 10 will take the barriers.
If 10 users want to contribute just one patch, how many will take the barriers?
[Of course much more barriers (in this example and within eclipse.org in general)]
Powered by FUDForum
. Page generated in 0.11098 seconds