June 2008
You are currently browsing the articles from Chorr Blog written in the month of June 2008.
I enjoyed the conversations discussing my position on NBA Players in the Olympics. The sports world is its own social network where much is said , written and quickly forgotten about anything and everything that can be argued about. My last post included.
The sports world however is on an amateur scale when it comes to arguing for the sake of arguing compared to the world of technology fanboys. They are about to see just how overmatched they are
It all starts with this
"No Olympics video is allowed to be shown online on any website other than NBCOlympics.com"
Translated, this means that no Olympics video is allowed on Youtube, Veoh or any video sharing site. It means that if you are an Olympic athlete and you want to post video of your Gold Medal winning, world record performance on your Facebook or Myspace page, those sites may just get a takedown notice saying you dont have those rights, leaving the dreaded "this video has been removed....." text in its place.
If you stayed up all night to watch an amazing finish to an event that you wanted to share with friends, forgettaboutit. Unless you plan on making an expensive fair use legal argument, you re going to be running afoul of the NBC legal department.
For all things Olympics video online, its NBCOlympics.com or nothing.
All of which is fighting words to the very vocal the internet and Youtube can do no wrong fanboys. They will scream, yell and comment spam and response video to the point of hyperventilation. They will do interviews on every sports, technology and cable news show. It will become a multi platform, multi media issue. They will be loud
It will also send the message to the sports world that the Olympics is driven by money. A fact that will resonate every time someone watches the Olympics, except hopefully between the gun and the tape and the starting and ending whistles of events. Which of course means it will be sports talk radio fodder 24x7 on every radio dial in every city in America with ESPN segments everywhere covering the "controversy"
The Olympics will of course be a major topic of conversation this summer, it will be interesting to see how much of the conversation will be about the athletes and which world, technology or sports will have more influence on NBC and their policies.
Permalink |
Email this |
Linking Blogs |
Comments
Written by Mark Cuban on June 29th, 2008 with no comments.
Read more articles on Uncategorized.
This blog post frames our approach in IE8 for delivering trustworthy browsing. The topic is complicated enough that some context and even history (before we go into any particular feature) is important, and so some readers may find this post a bit basic as it’s written for a wide audience. In previous posts here, we’ve written about IE8 for developers: the work in standards support, developer tools, script performance, and more. In future posts, we’ll write about IE8 for end-users (beyond the benefits of improved performance, activities, and Web Slices). This post starts a series about trustworthy browsing, a topic important for developers and end-users and everyone on the web. By setting the context and motivation with this post, the next posts that dive into the details of IE8 will build on this foundation.
Trustworthy refers to one of our overall goals: provide the most secure and most reliable browser that respects user choice and keeps users in control of their machine and their information. For reference, Microsoft’s framework for Trustworthy Computing in general spans four areas: security, privacy, reliability, and business practices.
Security is often where the trust discussion begins. Narrowly, security in this context means “as the user browses the web, the only code that runs on the user’s machine is code that the user allows to run". For example, when the user visits “www.somebadsite.com” the site should not be able to just run “virus.exe” and infect the user’s machine with malware. IE7 made a lot of progress on security, starting with Protected Mode and developing IE to be “secure by design, secure by default” as part of the following SDL requirements. IE7 was the first browser to support Extended Validation certificates to help protect users from deceptive websites, as well as delivering anti-phishing protection, International Domain Name support with protection from deceptive websites, a richer SSL experience and support for stronger SSL cipher algorithms, ActiveX opt-in, and great integration with Parental Controls in Windows Vista. We have done even more security work in IE8 to address the evolving threat environment.
Privacy is a complex topic that more often than not puts one party in conflict with another. If security boils down to “the user is in control of what code runs on the machine,” then privacy boils down to “the user is in control of what information the browser makes available to websites". Many people immediately think of “cookies” at this point because so much discussion and early work around privacy focused on the specific implementation of cookies. Cookies and cookie protection are definitely one aspect of the online privacy discussion. IE6 included innovative work implementing the P3P web standard (from the W3C), and both IE6 and IE7 use it to block cookies from websites that don’t have a privacy policy that complies with the user’s settings. It’s a great example of a privacy protection in use today on the web. In IE7, deleting cookies as well as other information that shows where the user has been on the web is much easier. That said, there’s more to online privacy than cookies, as cookies are only one implementation of content that can disclose information to websites. In some discussions, people have also described IE7’s Phishing Filter as a privacy feature because it helps protect users from sharing information. The larger challenge here is notifying users clearly about what sites they’re disclosing information to and enabling them to control that disclosure if they choose. As we talk more about privacy, we will broaden the discussion to include additional protections from sharing information that the browser can offer users.
Reliability is relatively simple: the browser should always start, find the Internet, and show web sites without crashing. We define reliability to mean “as the user browses the web, the browser performs well and does not terminate unexpectedly". End-users really don’t care about the cause of instability in the system – malformed web pages (see the old Slashdot article that this post refers to, for example) or third-party extensions (like toolbars; see this post about IE7’s “No Add-ons” functionality) – they just want the browser to work. In addition, when something does go wrong, an important part of reliability is how gracefully the browser recovers from the unexpected. Another aspect of reliability is that sites continue to render correctly. We’ll post more here about the work we’ve done to make IE8 more robust, as well as more interoperable and compatible at the same time.
Business practices guide decisions we make in designing and distributing our products. The key principle here is respecting user choice. For example, when a user installs a new version of IE, IE respects the user’s choice of default search engine. In IE, the user can add or remove different search providers using OpenSearch, a public and open standard that some other browsers have chosen to support as well. IE respects the user’s choice of system defaults (Windows Vista’s “Default Programs” functionality, as well as Windows XP’s Set Program Access Defaults). Explicitly asking the user before installing a new version of IE is key to respecting the user’s browser choice.
Ultimately, trustworthy browsing is about enabling users to be in control and respecting the choices users make. Specifically, it’s about enabling users to be in control of their machine, of their browser, of their settings, of their experience, of what data they share with whom when. Each part of trustworthy browsing involves an industry-wide challenge. For example, security is an industry challenge; every browser on the web faces attacks.
While all these statements may sound inherently obvious to some readers, these topics are so important that we thought it would be good to talk in general about how we think about them overall. Over the coming weeks this blog series will talk about how we’re making progress against these challenges, to set the stage for the release of IE8 Beta 2 in August.
Thanks,
Dean Hachamovitch
General Manager
Internet Explorer
Edit: removed hyperlink
Written by ieblog on June 25th, 2008 with no comments.
Read more articles on Uncategorized.
Today we released the IE June Cumulative Security Update for Internet Explorer 8 Beta 1 for Developers on Windows Update. For detailed information on the contents of this update, please see the following documentation:
If you are using IE8 Beta 1 for Developers, we encourage you to download this security update through Windows Update or the Microsoft Download Center today.
Terry McCoy
Program Manager
Internet Explorer Security
Edit: removed "today" from first sentence
Written by ieblog on June 24th, 2008 with no comments.
Read more articles on Uncategorized.
As I mentioned in my post on Cross Document Messaging, client side cross domain request is an important area of interest for AJAX developers looking for ways to avoid expensive server side proxying calls. While Cross Document Messaging is useful for allowing third party components or gadgets embedded in a page to communicate/converse using script on both sides, other cross domain scenarios like web services require access to cross domain content using network requests from a client side web application. For example, you may want to use your client side map based mashup to pinpoint Chinese restaurants for your current neighborhood. This could require the mashup to request a text file from Zagat.com with the locations of Zagat rated restaurants in the area which can then be superimposed on the map.
Along those lines, a few proposals and implementations exist like XDomainRequest in IE8, JSONRequest and the W3C’s Web Applications Working Group’s Cross Site XMLHttpRequest (CS-XHR) draft specification, which combines an Access control framework with XMLHttpRequest or other features. While XDomainRequest is focused on enabling anonymous access of third party public data, Cross Site XMLHttpRequest has added functionality and consequently enables a broader set of scenarios that may appeal to the developer who may choose to use cross domain authentication and access control among other features. As can be expected with securing a large cross section of cross domain scenarios, a number of concerns have been identified with the CS-XHR draft by the web development community, the IE team members and members of the Web Apps Working Group. For a list of our recent feedback on security on CS-XHR and our take on important security principles in cross domain, please read our Security Whitepaper on Cross Domain. The paper also covers best practices and guidance for developers who will choose to build on the current draft if it’s supported by a future browser. Note that issues here are currently being discussed and some concerns may be mitigated as the draft evolves.
Meanwhile, your participation in the Web Apps Working Group can add a broader perspective and help raise further issues in the draft so that browser vendors like us can implement it in the future, so if you want to help, sign up with the Web Applications Working Group public alias!
For all those of you who would like cross domain public data and want it soon, there’s XDomainRequest in IE8. We’d love to hear feedback on XDR, and from projects that have been built using it. Hit the comments section with links or just email them to me. I’ll be blogging more about this feature in a few weeks!
Sunava Dutta
Program Manager
Written by ieblog on June 23rd, 2008 with no comments.
Read more articles on Uncategorized.
As I mentioned in my post on Cross Document Messaging, client side cross domain request is an important area of interest for AJAX developers looking for ways to avoid expensive server side proxying calls. While Cross Document Messaging is useful for allowing third party components or gadgets embedded in a page to communicate/converse using script on both sides, other cross domain scenarios like web services require access to cross domain content using network requests from a client side web application. For example, you may want to use your client side map based mashup to pinpoint Chinese restaurants for your current neighborhood. This could require the mashup to request a text file from Zagat.com with the locations of Zagat rated restaurants in the area which can then be superimposed on the map.
Along those lines, a few proposals and implementations exist like XDomainRequest in IE8, JSONRequest and the W3C’s Web Applications Working Group’s Cross Site XMLHttpRequest (CS-XHR) draft specification, which combines an Access control framework with XMLHttpRequest or other features. While XDomainRequest is focused on enabling anonymous access of third party public data, Cross Site XMLHttpRequest has added functionality and consequently enables a broader set of scenarios that may appeal to the developer who may choose to use cross domain authentication and access control among other features. As can be expected with securing a large cross section of cross domain scenarios, a number of concerns have been identified with the CS-XHR draft by the web development community, the IE team members and members of the Web Apps Working Group. For a list of our recent feedback on security on CS-XHR and our take on important security principles in cross domain, please read our Security Whitepaper on Cross Domain. The paper also covers best practices and guidance for developers who will choose to build on the current draft if it’s supported by a future browser. Note that issues here are currently being discussed and some concerns may be mitigated as the draft evolves.
Meanwhile, your participation in the Web Apps Working Group can add a broader perspective and help raise further issues in the draft so that browser vendors like us can implement it in the future, so if you want to help, sign up with the Web Applications Working Group public alias!
For all those of you who would like cross domain public data and want it soon, there’s XDomainRequest in IE8. We’d love to hear feedback on XDR, and from projects that have been built using it. Hit the comments section with links or just email them to me. I’ll be blogging more about this feature in a few weeks!
Sunava Dutta
Program Manager
Written by ieblog on June 23rd, 2008 with no comments.
Read more articles on Uncategorized.
As I mentioned in my post on Cross Document Messaging, client side cross domain request is an important area of interest for AJAX developers looking for ways to avoid expensive server side proxying calls. While Cross Document Messaging is useful for allowing third party components or gadgets embedded in a page to communicate/converse using script on both sides, other cross domain scenarios like web services require access to cross domain content using network requests from a client side web application. For example, you may want to use your client side map based mashup to pinpoint Chinese restaurants for your current neighborhood. This could require the mashup to request a text file from Zagat.com with the locations of Zagat rated restaurants in the area which can then be superimposed on the map.
Along those lines, a few proposals and implementations exist like XDomainRequest in IE8, JSONRequest and the W3C’s Web Applications Working Group’s Cross Site XMLHttpRequest (CS-XHR) draft specification, which combines an Access control framework with XMLHttpRequest or other features. While XDomainRequest is focused on enabling anonymous access of third party public data, Cross Site XMLHttpRequest has added functionality and consequently enables a broader set of scenarios that may appeal to the developer who may choose to use cross domain authentication and access control among other features. As can be expected with securing a large cross section of cross domain scenarios, a number of concerns have been identified with the CS-XHR draft by the web development community, the IE team members and members of the Web Apps Working Group. For a list of our recent feedback on security on CS-XHR and our take on important security principles in cross domain, please read our Security Whitepaper on Cross Domain. The paper also covers best practices and guidance for developers who will choose to build on the current draft if it’s supported by a future browser. Note that issues here are currently being discussed and some concerns may be mitigated as the draft evolves.
Meanwhile, your participation in the Web Apps Working Group can add a broader perspective and help raise further issues in the draft so that browser vendors like us can implement it in the future, so if you want to help, sign up with the Web Applications Working Group public alias!
For all those of you who would like cross domain public data and want it soon, there’s XDomainRequest in IE8. We’d love to hear feedback on XDR, and from projects that have been built using it. Hit the comments section with links or just email them to me. I’ll be blogging more about this feature in a few weeks!
Sunava Dutta
Program Manager
Written by ieblog on June 23rd, 2008 with no comments.
Read more articles on Uncategorized.
This is my original post on the NBA and the Olympics. One thing I will add to it is for each and every blogger who so desires to undertake a simple test. On your blog, add a picture of the Olympics 5 Rings and a picture of your favorite player in their Olympic uniform. Underneath the pictures, add the caption, "My Official Olympics Update" and then chronicle that player in the Olympics with pictures from the official Olympics website. Show your patriotism and pride... that is until the you get a takedown letter or a Cease and Desist ordering you to take it down.
Thats how much about country and pride the Olympics is these days....
A 2nd item to generate some thought is the concept of players and coaches "And 1ing" their nationalities in order to be able to participate or to better market themselves. Whats "And 1ing" ? Being born and/or raised in one country but leveraging a ancestral link to another country where your odds are better to make the team. So for instance, your great, great grandfather was born in Upper Slobobia. in order to play on the Upper Slobobian basketball or handball team, you get a passport from there. Thats "And 1ing". Adding a nationality so that you can play on their team.
Or what about giving up citizenship from your native country to come here and play on our team. Is that what we want to root for as we face an onslaught of commercials on one of who knows how many cable networks that GE will be filling with Olympic programming ?
Are we sure the Olympics is about patriotism and pride ? Or is it about commercialism ? Im certaintly not against GE and the US Olympic Team making as much money as they possibly can on the game. More power to them. But lets not lie to ourselves about what is going on.
Here is my original post from more than 4 years ago.
NBA and the Olympics
Apr 7th 2004 10:54AM
Once again I was asked about my position on NBA players and the Olympics. One question from 1 reporter usually leads to followups form 100 more. So in the interest of disclosure, fairness and time, I decided to post the response here and save myself some time.....
In the sports marketing world, advertisers usually have a set sports marketing budget. Each advertiser gets pitched by all the different sports entities competing for those dollars. Among those competitors are both the Olympics and NBA. One of the beauties of the NBA pitch is that our athletes are so recognizable, personable and respected. The ability for an advertiser to connect their products to KG, Tim Duncan, Shaq, Dirk, etc, individually, or by buying sponsorship or commercials in game, is a huge selling point for us. It should be a huge selling point exclusively available to the NBA, but unfortunately that is no longer the case.
When the NBA was broadcast on NBC, it was far less of an issue. With NBC as the home of the Olympics and the NBA broadcast partner, there were a ton of cross promotional and selling opportunities. NBC could promote the Olympics in NBA games, and promote the NBA in the Olympics broadcasts. NBC could require advertisers to buy NBA advertising in order to get Olympic advertising,or vice versa. There were untold win - win scenarios by having both the Olympics and the NBA together at NBC.
That obviously is not longer the case. The NBA is now on ESPN/ABC and TNT. They are paying us a lot of money in a deal that has been working well for all invovled. What in the world are we doing helping our partners competition ? Why are we giving our most valuable manpower to a huge business, the Olympics so they can try to take revenue away from the NBA and our partners ?
Lets put this in basketball terms...Would you trade KG, TD, Peja, Jermaine and 10 more all stars , and pay their salaries in case they get hurt , for ..........nothing.
In exchange for providing our best players to the Olympics, the value we are supposed to receive is increased visibility and demand for the NBA, its players and merchandise. The value of which can be quantified as the total revenues received annually by each team from international TV and merchandise sales.
I wont tell you what that number is,but I can tell you it wouldnt pay the salary of a player signed for the million dollar exception this year.
So we are subsidizing the US Olympic committee by:
- Providing players that we pay for
- Reducing the amount of advertising dollars available to the NBA and our broadcast partners by allowing advertisers to use our players via Olympic broadcasts and programs
- Putting our most valuable players at risk, with the possibility of having to pay their salaries even if they are unable to perform,or to perform at the previous levels
- Potentially cheating our fans and customers who make investments in our league, teams and products, with players who are worn down or injured from their Olympic experience
- Whats even crazier is that the USA fans who buy our tickets and pay the players salary probably wont even get to see our stars in more than the Gold medal game. If that !
Where is the logic in any of this ?
I understand that players want to represent their countries. Thats great. Lets put toegether an NBA organized and sanctioned international competition that we can control and profit from. We can allow any country to enter a team, and let NBA players represent their country.
If its that important, lets also expand the exhibitions the NBA plays in and against other countries. Im all for international play as long as its in the context of an NBA program that gives consideration to the core NBA fan, customer and partner first and foremost.
If you agree, call your favorite team and tell them you dont want your players participating in the Olympics. You want them getting ready for the next season. And then order your season tickets :)
Permalink |
Email this |
Linking Blogs |
Comments
Written by Mark Cuban on June 22nd, 2008 with no comments.
Read more articles on Uncategorized.
Wondering what to do until we hear back from Guinness? How about taking a moment to celebrate all the hardwork that went into Download Day and the launch of Firefox 3. Check out Mozilla Party Central for a party near you or to host your own.
With the same enthusiasm that went into spreading the word about Download Day, the Firefox community has been planning parties with gusto! There are over 700 parties planned worldwide. Here are some of the highlights:
- Catch a viewing of Kung Fu Panda with its director Michael Osborne in Palo Alto this Saturday.
- Fancy that Firefox 3 robot? Come build one in Dolores Park in San Francisco on Sunday.
- The MVGeeks are planning a huge party in the Maldives on June 26th (editor’s note: the Firefox will need appropriate tropical attire stat!)
- Community members in Bucharest will be toasting Firefox 3 and the Mozilla 10-year anniversary!
- Bob Chao of MozTW will be hosting a Firefox 3 party for the Taiwan community on July 19th!
This is just a sampling…and please be reassured that it’s not too late to plan one!
Thanks to OLPC for throwing a Firefox 3 party on launch day!
Written by Mary Colvig on June 21st, 2008 with no comments.
Read more articles on Uncategorized.
As James and I mentioned in our blog post What’s coming in IE8 for IT Pros?, IE8 can now be slipstreamed into Vista and Window Server 2008 OS images. If you manage the desktop images for your organization, slipstream saves you time by simplifying the task of adding Internet Explorer 8 and any IE updates. If you’re adding Internet Explorer 7 to a Windows XP image you’ll typically install XP and then add IE7 before capturing the image -this can take 2 hours! With IE8 and Windows Vista, you are able to integrate IE8 into the image file of the original operating system in about 15 minutes. No more booting the OS image, manually installing IE and re-capturing the image. The slipstreaming support also extends to IE8 cumulative updates and language packages. Slipstreaming IE8 into an OS image will only be supported on Vista and Windows Server 2008 platforms. Windows XP and Windows Server 2003 do not currently offer a solution for slipstreaming Windows components, which are built using update.exe.
Here are the steps to create a Vista image with IE8 being the out of box browser by default. You can try this yourself with IE8 beta1.
Preparation
1. Install Windows Automated Install Kit
The Windows Automated Install Kit (WAIK) is a tool available for Vista and Windows Server 2008 to manage and customize OS images. This is the tool you’ll be using to slipstream IE8. Download a version of WAIK that matches your local machine configuration (not the image you’ll be slipstreaming IE8 into).
Note: Using a WAIK x64 bit version for a Vista x86 image will not work. For more information, please refer to the WAIK Readme.
2. Create the Vista directory
Copy the Vista directory from the CD onto your local machine.
3. Create 3 temp folders: Mount, Pkg, Sandbox
You can name each folder whatever you want, however remember the purpose of each folder created.
For this example, I created:
c:\slipstreaming\mount
c:\slipstreaming\pkg
c:\slipstreaming\sandbox.
Your final folder structure should look something like this:
4. Download IE8 Beta 1
Download IE8 Beta1 to your local machine from here. For this example, I saved the IE8 Beta1 exe in c:\Slipstreaming\IE8x86en
5. Extract and expand the MSU file
From the IE8 exe file:
- To extract the MSU, in the command prompt run this <IE8.exe path> /x: <folder you want the MSU to be placed>. For example: c:\Slipstreaming\IE8x86en\IE8-WindowsVista-x86-enu.exe /x: c:\Slipstreaming\IE8x86en
- To expand the MSU, in the command prompt run this expand.exe <path to the IE8.MSU> -F:* <pkg folder>. For example: expand.exe c:\Slipstreaming\IE8x86en\IE8.MSU -F:* c:\Slipstreaming\pkg
Slipstream
1. Mount the Vista install image to your temporary location.
In the command prompt, run this imagex.exe /mountrw install.wim <imagenumber> <mountfolder>
For this example: I am slipstreaming IE8 into Vista Ultimate which has the imagenumber = 4. The command I ran is as such "C:\Program Files\Windows AIK\Tools\x86\imagex.exe" /mountrw C:\Slipstreaming\VistaSP1x86en\sources\install.wim 4 C:\Slipstreaming\mount
If you don’t know the image number of the OS image you are using, you can use the arbitrary large number instead of 4 in the command above like this: imagex.exe /dir c:\VistaRTM\sources\install.wim 20. This triggers help information to be displayed. From the output in your command prompt, choose the SKU that you are using and the IMAGE INDEX is the <imagenumber> that you need.
2. Slipstream IE8 into the Vista image.
If you are using Vista Gold image, you need to change a read only attribute flag prior to executing a slipstream command: attrib -R "<mountfolder>\Windows\Offline Web Pages"
For example: attrib -R "C:\Slipstreaming\mount\Windows\Offline Web Pages"
Now, you are ready to slipstream IE8. Run this in the command prompt: pkgmgr.exe /n:<package folder>\WindowsVista-KB#-NEUTRAL.xml /o:”<mount folder>;<mount folder>\windows” /s:<sandbox> /l:<where you want the log file to be stored>. Ensure the pkgmgr.exe you use is the one installed with the WAIK tools.
For example: "c:\Program Files\Windows AIK\Tools\x86\Servicing\pkgmgr.exe" /n:"c:\Slipstreaming\pkg\Windows6.0-KB944036-x86.xml" /o:""c:\Slipstreaming\mount";"c:\Slipstreaming\mount\windows"" /s:"c:\Slipstreaming\sandbox" /l:"c:\Slipstreaming\slp.log"
Once the slipstreaming command is finished successfully, the slp.log will say “exit code 0x00”.
Remember to add the read only attribute flag back after slipstreaming is complete if using a Vista Gold image: attrib +R "<mountfolder>\Windows\Offline Web Pages"
For example: attrib +R "C:\Slipstreaming\mount\Windows\Offline Web Pages"
3. Save the changes.
Use imagex.exe to save the changes: imagex /commit /unmount <mountfolder>
For this example: "c:\Program Files\Windows AIK\Tools\x86\imagex.exe" /commit /unmount c:\Slipstreaming\mount
You are all done!!! The Vista install image on your local machine is the new Vista build with IE8 slipstreamed.
Since IE8 is part of the Vista image, you can customize it by creating an answer.xml file and running Vista setup with unattend option as such: <VistaPath>\setup.exe /unattend:<answer.xml path>
The Unattended Windows install option enables customization of the OS install, and the answer.xml file provides the “answers” for customizations and drives the unattended install.
You can find more about unattend installs and answer files here:
After you install the final image, IE8 beta1 will appear under installed updates as such and can be uninstalled in the same way as when installing IE8 standalone.You will be reverted to IE7 if you choose to uninstall IE8.
Thanks,
Jane Maliouta
IE Deployment Program Manager
Written by ieblog on June 21st, 2008 with no comments.
Read more articles on Uncategorized.
We’re getting close to handing over our download logs to our judges for our Guinness World Record attempt. We’re very lucky and honored to have Paul Vixie of the Internet Systems Consortium and Corey Shields of Indiana University.
Here is a little background on them both:
Paul Vixie has been contributing to Internet protocols and UNIX systems as a protocol designer and software architect since 1980, and was a cofounder of ISC in 1994. Early in his career, he developed and introduced SENDS, proxynet, rtty, cron and other lesser-known tools. Paul is considered the primary modern author and technical architect of BIND8, the most commonly used DNS server on the Internet.
Corey Shields is the Lead Systems Analyst for the High Performance Systems group in University Information Technology Services at Indiana University. Corey has had a long history as an open source software user, advocate, and contributor. He has made contributions to many open source projects including Mozilla and the Gentoo Linux distribution, and spent a couple of years managing the Open Source Lab (OSL) at Oregon State University.
Currently, Corey is working with a team of administrators on the BigRed supercomputer at Indiana University. BigRed is the 42nd fastest supercomputer in the world, and relies on open source software to operate and produce results for researchers across the country.
A huge thanks to them for supporting our effort!
Written by mary on June 19th, 2008 with no comments.
Read more articles on Uncategorized.
« Older articles
No newer articles
Apply your