Changeset - 25a4833b4cfb
[Not reviewed]
0 2 0
Bradley Kuhn (bkuhn) - 10 years ago 2013-11-15 18:55:19
bkuhn@ebb.org
How many developers?
2 files changed with 13 insertions and 1 deletions:
0 comments (0 inline, 0 general)
ExistingProjects/EvaluationTemplate.mdwn
Show inline comments
...
 
@@ -67,8 +67,11 @@ does, so I think it's tough to do it as a list of questions.
 

	
 
### Evaluation of the [[Community Health|UseCases/CommunityHealth]]
 
- Is the [[license both determined as Free Software by FSF and OSI-approved|USeCases/CommunityHealth#license-approved]]?
 
- 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]]?
UseCases/CommunityHealth.mdwn
Show inline comments
...
 
@@ -26,13 +26,13 @@ Even for 501(c)(3)'s requesting a CLA or copyright assignment, there would
 
need to be a confirmation that the missions of the orgs were sufficiently
 
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
 

	
 
<a id="dev-docs"></a>
 

	
 
The right choice has to have an accessible codebase.  Since no accounting
 
package yet deals with the issues specific to non-profit organizations, this
 
project will have to focus on bringing developers *to* the new project.
...
 
@@ -40,6 +40,15 @@ project will have to focus on bringing developers *to* the new project.
 
<a id="dev-welcoming"></a>
 

	
 
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 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.
0 comments (0 inline, 0 general)