[sakai-pmc] Executive Summary Sakai 10

[Charles Severance]

I deinately agree with Anthony here.  "Tagging" contributions either under or overstates credit.   We really need a long list of contributors.   The really great contributors benefit from a longer list as it communicates the rich diversity of our community.

/Chuck

On May 22, 2014, at 12:44 PM, Anthony Whyte <arwhyte at umich.edu> wrote:

> We had this debate last year.  I suggested back then that we include a list of contributing institutions/organizations listed independent of the feature set.  I recommended that you crowd source the list in order to surface contributors who may have been missed by the list compiler (as the case of Bryan amply demonstrates).  
> 
> Linking deliverables to specific organizational/institutional contributors is a bad idea for two reasons.  First, it tends to over focus on the "big" contributors and neglects others who assisted getting the deliverable across the line in a variety of ways, some humble, some not.  Take signup tool for instance.  Sure Yale contributed the tool but Michigan prepped it for its move to trunk and inclusion in the release.  Similar examples can be found in a variety of bug fixes and other work flowing into trunk and 10.x from a variety of sources.  The approach ends up downplaying the collective effort that goes into Sakai development.  Second, lists of A did X and B did Y tends to undercut a key message that we should be developing: viz, we are one community, one project, one team, one code base.
> 
> Anth

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-pmc/attachments/20140522/1f46aa3c/attachment.html