From 25a4833b4cfb2d1c4b6921b9035e191863f0633c 2013-11-15 18:55:19 From: Bradley M. Kuhn Date: 2013-11-15 18:55:19 Subject: [PATCH] How many developers? --- diff --git a/ExistingProjects/EvaluationTemplate.mdwn b/ExistingProjects/EvaluationTemplate.mdwn index d9583cda00541751fb51cc5144ad8af34d42bd63..880ebd3755ed682ef68c3e579dc0d7083113a05c 100644 --- a/ExistingProjects/EvaluationTemplate.mdwn +++ b/ExistingProjects/EvaluationTemplate.mdwn @@ -70,5 +70,8 @@ does, so I think it's tough to do it as a list of questions. - Is the [[license GPL-compatible||UseCases/CommunityHealth#gpl-compatible]]? - Does the project [[require assignment of copyright or a CLA to get code upstreamed|UseCases/CommunityHealth#no-cla-for-profit]]? +- How many + [[active developers/companies contribute to the project||USeCases/CommunityHealth#dev-count]]? + * If there aren't many, how hard would it be to take over the project if needed? - Is there good [[developer documentation|UseCases/CommunityHealth#dev-docs]]? - How easy it to [[engage as a developer with the community|UseCases/CommunityHealth#dev-welcoming]]? diff --git a/UseCases/CommunityHealth.mdwn b/UseCases/CommunityHealth.mdwn index a091366ca2f760894b8ef2ced6dd64703235a9d5..f25754700efb8a2ebce97686a171ca04bc7abd43 100644 --- a/UseCases/CommunityHealth.mdwn +++ b/UseCases/CommunityHealth.mdwn @@ -29,7 +29,7 @@ aligned. Given that the project is going to solicit support and contributions from 501(c)(3)'s, this issue is particularly important. -## Developer Documentation +## Developer Documentation and Community @@ -43,3 +43,12 @@ As such, the codebase needs to be accessible. Communication with the core developers should be possible and interactive. The project should be willing to accept new contributors who might want to make substantial changes to the codebase. + + + +A project with just one or two active developers, or where all the current +developers appear to be employed by one company, has serious community health +issues. Building a community around such a codebase is an uphill battle. If +we build on such a project, we should be prepared to become the maintainer of +the project if we have to, since the company or few individuals could move on +with short notice.