NPO-Accounting/npo-accounting-ikiwiki
6
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

How many developers?

Browse source
This commit is contained in:
Bradley M. Kuhn 2013-11-15 13:55:19 -05:00
parent 777e223c40
commit 25a4833b4c
2 changed files with 13 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
ExistingProjects/EvaluationTemplate.mdwn
View file

@ -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]]? - Is the [[license GPL-compatible||UseCases/CommunityHealth#gpl-compatible]]?
- Does the project - Does the project
[[require assignment of copyright or a CLA to get code upstreamed|UseCases/CommunityHealth#no-cla-for-profit]]? [[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]]? - Is there good [[developer documentation|UseCases/CommunityHealth#dev-docs]]?
- How easy it to [[engage as a developer with the community|UseCases/CommunityHealth#dev-welcoming]]? - How easy it to [[engage as a developer with the community|UseCases/CommunityHealth#dev-welcoming]]?

11
UseCases/CommunityHealth.mdwn
View file

@ -29,7 +29,7 @@ aligned.
Given that the project is going to solicit support and contributions from Given that the project is going to solicit support and contributions from
501(c)(3)'s, this issue is particularly important. 501(c)(3)'s, this issue is particularly important.
## Developer Documentation ## Developer Documentation and Community
<a id="dev-docs"></a> <a id="dev-docs"></a>
@ -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 core developers should be possible and interactive. The project should
be willing to accept new contributors who might want to make substantial be willing to accept new contributors who might want to make substantial
changes to the codebase. changes to the codebase.
<a id="dev-count"></a>
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.