I'm working on my proposal for the K-12 Open Minds Conference:
Schools write software. Not as much as universities or corporations, but individual teachers, schools, districts, regional and state departments all write software for their own use and have done so as long as they have had computers. Using COBOL, BASIC, Java, and C#; Filemaker, FoxPro, and Access; and now PHP, MySQL, Ruby, Perl and Python.
Schools use open source software; increasingly they write software with open source tools; but few have launched and maintained ongoing open source projects. Are schools ready to take this next step?
We shall address:
- Rationales and motivations for open sourcing your code.
- Costs and benefits of an open source release.
- Determining if you can and should open source an existing application.
- Building a new open source project from the ground up.
- Simplifying the process of choosing a license.
- Setting up open source development infrastructure.
- Standard practices in open source development.
- Collaboration and funding beyond your institution.
That seems kind of short, but I think I've made my point. Any suggestions to flesh out the details in the proposal?