[sakai2-tcc] More on Institutional Acknowledgements

[Neal Caidin]

Simple solution. Brand as Sakereo (gooey cream filling). Mash logos. done. [just kidding]  

-- N



On Apr 10, 2013, at 11:53 AM, Anthony Whyte <arwhyte at umich.edu> wrote:

> Yes, although a debate over branding (Apereo or Sakai fellows) among the board members has apparently held up the start date for the nomination process.  A couple of weeks ago I let Ian Dolphin know that such delays carry with it the risk that some newly-elected fellows may be left with insufficient time to secure institutional approval to attend the conference.  He shares the concern.
> 
> I myself have retired as the selection committee chair, having passed the baton on to Seth.  
> 
> Cheers,
> 
> Anth
> 
> 
> 
> On Apr 10, 2013, at 11:28 AM, Beth Kirschner wrote:
> 
>> Are we doing Sakai Fellows this year? If yes, a PPT slide with acknowledgements around the same time of announcing the fellows seems like a good time.
>> 
>> - Beth
>> 
>> On Apr 10, 2013, at 10:26 AM, Neal Caidin <nealcaidin at sakaifoundation.org> wrote:
>> 
>>> Hi TCC,
>>> 
>>> I do not yet have a proposal. Working on a strawperson for institutional acknowledgements between July 2012 - June 2013. Would that be a good date range to pick? Another open question is how to publish the acknowledgements. For example: web page, Open Apereo conference (not a presentation, more like projection between sessions, etc), letter to CIOs, etc. And a question of whether individual acknowledgements are also appropriate and, if so, where are they appropriate and what are the threshold contributions for these?  
>>> 
>>> Here are contributions that I think should be acknowledged. Among the challenges for this kind of recognition are what is the threshold for quality and quantity of contribution to these tasks. 
>>> 
>>> Tasks in alphabetical order:
>>> 
>>> Accessibility issue reporting and fixing
>>> Branch Management
>>> CLE Release team participation and bug fixing and patch review
>>> Code contributions and patches
>>> Community outreach ( use cases, pamplets, conference planning, etc)
>>> Documentation ( includes Confluence, Sakai properties, etc)
>>> Early adopter of 2.9
>>> Internationalization issue reporting and fixing
>>> Jira Triage
>>> Load testing
>>> Localizations (Translations)
>>> Participation on Email lists
>>> QA planning
>>> QA testing
>>> Release Management
>>> Security Pen Testing
>>> Security Testing
>>> TCC membership
>>> Tool specific development or enhancements (including bug fixes)  - [Lessons, Samigo, etc]
>>> 
>>> What do you think?
>>> 
>>> Thanks,
>>> Neal
>>> 
>>> _______________________________________________
>>> sakai2-tcc mailing list
>>> sakai2-tcc at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>> 
>> _______________________________________________
>> sakai2-tcc mailing list
>> sakai2-tcc at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>