1
edit
Changes
I'm pwning Mark.
'''THIS PAGE IS A DRAFT. The title of this page is not meant to reflect any branding. It's just a place to keep notes developed from the post-panel discussions at the Teaching Open Source track of [http://2008.fsoss.com FSOSS 2008].'''
== Apprentice and teaching models ==
* How do open source projects contribute time, energy
* Financial models
* Bringing open source into humanities/social sciences
System Biz model vs. Practice ????
* List of ???? that need to be written (????)
* Hand holding to point contributors to a better (????) place
* Application of projects to ???? (????) requires additional tasks that need work
* Profiling of projects
* Creation of "safe plpaces" where ????
* ?????
== Professional incentives ==
* Skills to teach OS
* How to embed in a community
* Offices of technical transfer
* Tenure, research, training
* Teach open source culture to students earlier in program
* Adopt open source software
== What can we do together going forward? ==
* Academics
* Business
* Foundations
* Open source communities
* Outline who is out there doing what
* Consortium of "us" -- people serious about growing teaching model (funding)
* Identify 1 or 2 new places where open source can be taught
* How do you educate government?
** Get serious partners
== Key lessons ==
* Publications != open source participation
* Develop understanding of value
* No incentive (personal)
* Sponsors
** Real contribution
** Reading of talent
* Have open source contributors "in residence" at universities
* Generate confidence by participating
* Trust and validation
* Expanding academics involved + business schools
* How do we evaluate students?
* How do we get involved?
* Senior open source people mentored the professor and conveyed reputation
* What do programs need to competent
* Community's investment in teaching or helping teaching
* What's the upper limit of a community/growth?
** Godfrey
* How do open source communities structure themselves to be open to participation and scalable?
* Involve technical writing program
* Colleges vs. universities == teaching vs. research
== Apprentice and teaching models ==
* How do open source projects contribute time, energy
* Financial models
* Bringing open source into humanities/social sciences
System Biz model vs. Practice ????
* List of ???? that need to be written (????)
* Hand holding to point contributors to a better (????) place
* Application of projects to ???? (????) requires additional tasks that need work
* Profiling of projects
* Creation of "safe plpaces" where ????
* ?????
== Professional incentives ==
* Skills to teach OS
* How to embed in a community
* Offices of technical transfer
* Tenure, research, training
* Teach open source culture to students earlier in program
* Adopt open source software
== What can we do together going forward? ==
* Academics
* Business
* Foundations
* Open source communities
* Outline who is out there doing what
* Consortium of "us" -- people serious about growing teaching model (funding)
* Identify 1 or 2 new places where open source can be taught
* How do you educate government?
** Get serious partners
== Key lessons ==
* Publications != open source participation
* Develop understanding of value
* No incentive (personal)
* Sponsors
** Real contribution
** Reading of talent
* Have open source contributors "in residence" at universities
* Generate confidence by participating
* Trust and validation
* Expanding academics involved + business schools
* How do we evaluate students?
* How do we get involved?
* Senior open source people mentored the professor and conveyed reputation
* What do programs need to competent
* Community's investment in teaching or helping teaching
* What's the upper limit of a community/growth?
** Godfrey
* How do open source communities structure themselves to be open to participation and scalable?
* Involve technical writing program
* Colleges vs. universities == teaching vs. research
