From Fedora Project Wiki
(choosing to transclude the 'parachute' bits because those currently are nice as a stand-alone tip that can be associated with the future Community Cookbook) |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 5: | Line 5: | ||
=== Initial engagement === | === Initial engagement === | ||
When a community consultant parachutes in to a new project, such as an upstream, these are the trail markers to look for: | |||
* Ease of install, configuration | |||
* Ease of getting help in a jam | |||
* Attraction to participation -- can I do things on $FOO as a potentially new contributor? | |||
* Joining the project -- how easy, what does it entail, what do I get? | |||
* Barriers to commit rights in the code | |||
* Clarity of a public roadmap | |||
=== Quick wins === | === Quick wins === | ||
| Line 12: | Line 19: | ||
=== Measuring success === | === Measuring success === | ||
Latest revision as of 21:28, 16 October 2009
Engagement with Red Hat projects
This is a draft!
This page is a very early outline of what will be a longer document.
This page is a very early outline of what will be a longer document.
Initial engagement
When a community consultant parachutes in to a new project, such as an upstream, these are the trail markers to look for:
- Ease of install, configuration
- Ease of getting help in a jam
- Attraction to participation -- can I do things on $FOO as a potentially new contributor?
- Joining the project -- how easy, what does it entail, what do I get?
- Barriers to commit rights in the code
- Clarity of a public roadmap