From Fedora Project Wiki

(adding a quick checklist useful to community consulting)
 
(Redirected page to Project engagement)
 
Line 1: Line 1:
When a community consultant parachutes in to a new project, such as an upstream, these are the trail markers to look for:
#REDIRECT [[Project_engagement]]
 
* Ease of install, configuration                                                                     
* Ease of getting help in a jam                                                                       
* Attraction to participation -- can I do things on freeipa.org 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
 
[[Category:Community cookbook tips]]
[[Category:Community Architecture]]

Latest revision as of 10:31, 18 May 2009

Redirect to:

Retrieved from "https://fedoraproject.org/w/index.php?title=How_to_parachute_a_community_consultant_in_to_a_project&oldid=102120"