From Fedora Project Wiki

Revision as of 19:58, 13 May 2009 by Quaid (talk | contribs) (adding a quick checklist useful to community consulting)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

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 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
Retrieved from "https://fedoraproject.org/w/index.php?title=How_to_parachute_a_community_consultant_in_to_a_project&oldid=101484"