Difference between revisions of "Challenges"
→Education System: (Added last para)
(→Patching FOSS in India: lawgon's blog added) |
(→Education System: (Added last para)) |
||
Line 130: | Line 130: | ||
* Encourage industry to talk: Encourage and in fact aggressively court the industry to be part of both the curriculum designing process as well as the curriculum content delivery methods | * Encourage industry to talk: Encourage and in fact aggressively court the industry to be part of both the curriculum designing process as well as the curriculum content delivery methods | ||
* Teach the methods: Teach the methodology for collaboration of content | * Teach the methods: Teach the methodology for collaboration of content i.e. be it documentation, source code or patches. Teach students how to do it, wherefrom to learn, whom to turn to and why it is important to have peers review the work | ||
* Teach FOSS: Put in a module for FOSS that talks about programming techniques rather than programming languages. Think about integrating and incorporating pieces from SICP and HTDP along with the GNU Coding Standards in order to ensure the output of quality of code | * Teach FOSS: Put in a module for FOSS that talks about programming techniques rather than programming languages. Think about integrating and incorporating pieces from SICP and HTDP along with the GNU Coding Standards in order to ensure the output of quality of code | ||
* Setup Linux Labs: Deceptively simple to setup if one has servers and reasonable bandwidth. Includes setting up of a Version Control System for code commits, a staging server and a development server, a couple of OS mirrors or at least their update mirrors (local) and a few workstations. Set them up on the network, get the network services up and running, put in place a nice printer (one that will take in duplex heavy duty print jobs) and you are reasonably done | * Setup Linux Labs: Deceptively simple to setup if one has servers and reasonable bandwidth. Includes setting up of a Version Control System for code commits, a staging server and a development server, a couple of OS mirrors or at least their update mirrors (local) and a few workstations. Set them up on the network, get the network services up and running, put in place a nice printer (one that will take in duplex heavy duty print jobs) and you are reasonably done. | ||
* Encourage content sharing between institutions: Take a look at OCW from MIT and figure out if the same can be easily applied in the current context | * Encourage content sharing between institutions: Take a look at OCW from MIT and figure out if the same can be easily applied in the current context | ||
* Allotment of marks, could be avoided, and an end term / semester project with viva-voce to grade the student is better. Marks for theory, marks for practicals, marks for assignment / tutorial, isn't better for teaching / learning FOSS. | |||
==Financial Constraints== | ==Financial Constraints== |