Comment Why Our District is Experimenting with Linux (Score 3, Interesting) 427
This is a long tale of woe, but it does get to the point eventually. Bare with me, I suspect other school tech folks have had similar experiences.
I am a District Technology Coordinator. Last summer our small district (3300 students) in the Mid-Atlantic paid Micro$oft over $100,000 in license upgrades. The state had a number of sessions scheduled with the MS Reps who came to explain the new licensing agreement. The company was moving from Upgrade Advantage to Software Assurance pricing schedules.
We were in the process of our Win2K rollout and we were confronted with MS retiring the ability to upgrade certain licenses. Our state contracts with a "Select" vendor who we are required to purchase all MS software. The vendor had conflicting upgrade paths than what MS had explained in the meetings.
At a later meeting when I asked about this they suggested the "School Agreement" as an alternative which is an annual subscription that allows schools to use any number of licenses but you must resubscribe every year.
I explained that I did calculations on purchase upgrades and compared the numbers to this "subscription" license and discovered that it was more expensive. I surmise that conflicting purchase information and random threats of audit in the education community makes choosing the school agreement a no brainer. If this was a marketing decision it is extortion.
During the course of this licensing process I went to the CIO of the district informing him that we could save nearly $40K by using Open Office on student only machines. Even after giving him a copy, and showing the software around to key individuals, he didn't feel that he could support Technology against the inevitable backlash from staff members.
He recommended a pilot before implementation. Since there was a deadline, we bought MS Office licenses. BTW we finally got resolution on the correct upgrade paths.
Now to the Linux in school stuff.
After this experience, the fiddling I was doing with Linux became a higher priority in the investment of my Tech Learning Time.
There is lots of great stuff out there for schools. The Linux Terminal Server Project http://www.ltsp.org/ gets around the windows legacy app problem. Or perhaps Linux Educational Apps could replace windows edutainment titles. A wealth of titles can be found at http://k12os.org/.
Personally I believe that what is best for our district is to get away from managing the desktop. So many rogue initiatives bubble up from the class room.
Example:
Mrs Jones goes and buys "10,000 Handouts Galore" CD-ROM ; ) at the grocery store and then expects technicians to not only install this buggy code from heaven knows where, but also expects poor frazzled "Fred" to divine the arcane structure of how it works, train her on it, and continually fix the pathetic workstation that crashes because the software is not totally compliant to windows standards. All this effort just so she can print a worksheet for the kids to sit and fill out.
How does this fundamentally change education? If you take the computer away can she still create a handout? I suspect that manually she could probably do it in less time with more focus on content and far less frustration.
In my opinion, district administration, curriculum leaders, principals as well as tech coordinators, network folks and programmers should work together to identify what problem really needs to be solved.
The direction we are going in is interactive web applications that provide collabortive opportunities to respond to various activities or projects.
One such Open Source package is the Authenticated User Community -- http://auc.sourceforge.net/. It is essentially groupware for education. Students can review and submit assignments, check email, post comments on a forum and store files. Teachers can track student activities retrieve assignments and initiate discussion. Mom and Pop can see what's going on from home! We are piloting this now.
Our TechTeam is using software called Tutos (http://www.tutos.org/homepage/index.html) to manage projects. This is useful software and since its on the Web it is transparent and ubiquitous.
Imagine if other useful software was converted to the web. The connection of Apache with MySQL (or other DB) could allow us to link every student activity with state standards and some sort of performance evaluation. This would give teachers the ability to make day to day teaching decisions based on DATA that will have real impact on High Stakes Testing.
We also using some network based diagnostic software packages. They are called Accelerated Reader and Accelerated Math and are published by Renaissance learning (http://www.renlearn.com). These programs allow students to interactively and dynamically record their performace on-line.
Unfortunately these programs are Windows apps. They are written in ToolBook and are not even 32bit compliant. Consequently there are frequent network issues since they are being used in manner contrary to their design. I wish there was a version of this software that ran on Apache and MySQL.
If a clear vision of curricular problems drove the purchase/solution implementation decisions rather than random marketing (ed conferences and journals) and individual (rogue) initiatives, resources such as technician support and capital funds for equipment and software would not be caught up in this merry go round of assumpion, consumption, no function and blame.
Micro$oft products give users just enough ability to use computers to be hugely expensive to larger organizations. Products running on this platform are sold as solutions to users problems, but not necessarily one that needs to be solved.
Users devise their own rogue initiatives with the grand ideas sold to them, but rarely are successful without technical help. The minute a technician provides that help they become responsible for the outcome and the initiative becomes sanctified by the organization.
Linux can solve this problem. It forces decisions to be made that focus on the problem. Since every teacher, administrator and student is not familiar (or "Expert" because their nephew works at CompUSA) with this platform they are not dreaming of a panacea like solution where they take off the shrink wrap and all their problems go away with no hardwork or learning curve. District leadership has time to focus on their curricular objectives and devise a plan that has a scope and sequence of events and a series of check points to evaluate progress.
Once the problem is defined and the objectives are spelled out there is lots of stuff in the Open Source community that can be selected as potential "off the shelf" alternatives. But what is even more exciting is the notion that through collaboration with others with similar objectives solutions start to move closer and closer to the needs at hand.
I am a District Technology Coordinator. Last summer our small district (3300 students) in the Mid-Atlantic paid Micro$oft over $100,000 in license upgrades. The state had a number of sessions scheduled with the MS Reps who came to explain the new licensing agreement. The company was moving from Upgrade Advantage to Software Assurance pricing schedules.
We were in the process of our Win2K rollout and we were confronted with MS retiring the ability to upgrade certain licenses. Our state contracts with a "Select" vendor who we are required to purchase all MS software. The vendor had conflicting upgrade paths than what MS had explained in the meetings.
At a later meeting when I asked about this they suggested the "School Agreement" as an alternative which is an annual subscription that allows schools to use any number of licenses but you must resubscribe every year.
I explained that I did calculations on purchase upgrades and compared the numbers to this "subscription" license and discovered that it was more expensive. I surmise that conflicting purchase information and random threats of audit in the education community makes choosing the school agreement a no brainer. If this was a marketing decision it is extortion.
During the course of this licensing process I went to the CIO of the district informing him that we could save nearly $40K by using Open Office on student only machines. Even after giving him a copy, and showing the software around to key individuals, he didn't feel that he could support Technology against the inevitable backlash from staff members.
He recommended a pilot before implementation. Since there was a deadline, we bought MS Office licenses. BTW we finally got resolution on the correct upgrade paths.
Now to the Linux in school stuff.
After this experience, the fiddling I was doing with Linux became a higher priority in the investment of my Tech Learning Time.
There is lots of great stuff out there for schools. The Linux Terminal Server Project http://www.ltsp.org/ gets around the windows legacy app problem. Or perhaps Linux Educational Apps could replace windows edutainment titles. A wealth of titles can be found at http://k12os.org/.
Personally I believe that what is best for our district is to get away from managing the desktop. So many rogue initiatives bubble up from the class room.
Example:
Mrs Jones goes and buys "10,000 Handouts Galore" CD-ROM ; ) at the grocery store and then expects technicians to not only install this buggy code from heaven knows where, but also expects poor frazzled "Fred" to divine the arcane structure of how it works, train her on it, and continually fix the pathetic workstation that crashes because the software is not totally compliant to windows standards. All this effort just so she can print a worksheet for the kids to sit and fill out.
How does this fundamentally change education? If you take the computer away can she still create a handout? I suspect that manually she could probably do it in less time with more focus on content and far less frustration.
In my opinion, district administration, curriculum leaders, principals as well as tech coordinators, network folks and programmers should work together to identify what problem really needs to be solved.
The direction we are going in is interactive web applications that provide collabortive opportunities to respond to various activities or projects.
One such Open Source package is the Authenticated User Community -- http://auc.sourceforge.net/. It is essentially groupware for education. Students can review and submit assignments, check email, post comments on a forum and store files. Teachers can track student activities retrieve assignments and initiate discussion. Mom and Pop can see what's going on from home! We are piloting this now.
Our TechTeam is using software called Tutos (http://www.tutos.org/homepage/index.html) to manage projects. This is useful software and since its on the Web it is transparent and ubiquitous.
Imagine if other useful software was converted to the web. The connection of Apache with MySQL (or other DB) could allow us to link every student activity with state standards and some sort of performance evaluation. This would give teachers the ability to make day to day teaching decisions based on DATA that will have real impact on High Stakes Testing.
We also using some network based diagnostic software packages. They are called Accelerated Reader and Accelerated Math and are published by Renaissance learning (http://www.renlearn.com). These programs allow students to interactively and dynamically record their performace on-line.
Unfortunately these programs are Windows apps. They are written in ToolBook and are not even 32bit compliant. Consequently there are frequent network issues since they are being used in manner contrary to their design. I wish there was a version of this software that ran on Apache and MySQL.
If a clear vision of curricular problems drove the purchase/solution implementation decisions rather than random marketing (ed conferences and journals) and individual (rogue) initiatives, resources such as technician support and capital funds for equipment and software would not be caught up in this merry go round of assumpion, consumption, no function and blame.
Micro$oft products give users just enough ability to use computers to be hugely expensive to larger organizations. Products running on this platform are sold as solutions to users problems, but not necessarily one that needs to be solved.
Users devise their own rogue initiatives with the grand ideas sold to them, but rarely are successful without technical help. The minute a technician provides that help they become responsible for the outcome and the initiative becomes sanctified by the organization.
Linux can solve this problem. It forces decisions to be made that focus on the problem. Since every teacher, administrator and student is not familiar (or "Expert" because their nephew works at CompUSA) with this platform they are not dreaming of a panacea like solution where they take off the shrink wrap and all their problems go away with no hardwork or learning curve. District leadership has time to focus on their curricular objectives and devise a plan that has a scope and sequence of events and a series of check points to evaluate progress.
Once the problem is defined and the objectives are spelled out there is lots of stuff in the Open Source community that can be selected as potential "off the shelf" alternatives. But what is even more exciting is the notion that through collaboration with others with similar objectives solutions start to move closer and closer to the needs at hand.
