Monthly Archives: May 2007

Postscript: Chappaqua Memorial Day 2007: Staff Sgt Kyu Hyuk Chay

[The original text of this post can now be found at Postscript: Chappaqua Memorial Day 2007: Staff Sgt Kyu Hyuk Chay.

Please make any future links to that post, and not this one.]

Chappaqua Memorial Day 2007: Staff Sgt Kyu Hyuk Chay

[The original text of this post can now be found at Chappaqua Memorial Day 2007: Staff Sgt Kyu Hyuk Chay.

Please make any future links to that post, and not this one.]

links for 2007-05-25

Location, location, location

Effective writing is like real estate. It is all about location — location, location, location.

I was recently asked to give a presentation on open technologies and k-12 education. When I started I faced the choice of document format. The usual form is Powerpoint charts but this was an external presentation. I also thought of using Open Office, lest someone ask why I was using a proprietary format to present about the various open technologies such as open source and open data formats.

In the end I decided to use the same format I have been using for close to a decade to prepare presentations — plain old HTML. It’s good enough for me.

But once I had finished the presentation — Open Technology Solutions for K-12 Education — I realized that although I had made the choice out of convenience it was also the logical thing to do.

Once you have finished a piece of writing that you would like to be widely read, what is the best thing you can do to make it widely available? You should put it up on the web to give it a location in the form of a URL so if someone asks you how they can get a copy you can just point them to it. You won’t have to send an e-mail with the text or with the document included as an attachment.

There are two kinds of documents: those that are publicly available on the web and those that aren’t. Which do you think will have more readers?

This is the first of the three locations important to your writing — a location on the web.

But it’s not enough just to make the document available on the web. You also want people to be able to locate it. You should make it easy for search engines to locate and scan the text of the document. Which means you don’t want to post the document as an attachment in a format such as PDF or as a Powerpoint presentation or even as an Open Office document since you want the search engines to add your writing to the vast body of available writing so that people will be able to find it.

This explains why plain old HTML is much more effective than PDF or other formats that require posting a separate file. HTML is the language of the web, the one format that all search engines know how to read. Plain old HTML also means that anyone can read your writing once they find it. They won’t have to download or purchase any software to read it since they can just use their browser.

This is the second of the three locations — make it easy for people to locate your document, either directly by searching for it or, more importantly, indirectly when they search on a phrase and one of your writings comes up as one of the matches.

Last, and perhaps most important, since you wrote it you want people to know you are the author when they read it. The best way to do this is to post it on a site associated with you, not your employer or some other organization, either as a post in your blog or as part of a site you own or in which your authorship is evident.

It is only if people know that you are the author that you will get the credit for it. And if you have written something that people find interesting, hopefully so much so that they link to it, then your reputation — and your network — will grow. And of course they can only link to your writing if it has a link, if you have given it a location. And since that location includes your other writings, you have increased the odds that a reader chancing upon just one of your writings will go on to read some of the others.

That is the third location — you. The document’s home on the web should be as part of your home on the web, to help you grow your network.

I suspect this explains in part the power of blogs. A blog post has a location as a web address that exposes the text to the search engines and which is directly associated with you as the author.

“Location, location, and location” and “World Wide Web” each have three words, and to be an effective writer you should join them:

Location: World Publish your writing to the world.

Location: Wide Make your writing widely accessible by making it easy to locate and read.

Location:Web Make your writing part of your own home on the web. You don’t have to pay a dime for that home. Just set up shop on WordPress — it’s a great neighborhood — and start building your own home, word by word.

links for 2007-05-24

A brief history of Sahana by Sanjiva Weerawarana

An IBM colleague just forwarded to me a post by Sanjiva Weerawarana to the humanitarian-ict list that gives a fascinating and compelling history of the Sahana project, an effort dear to my heart that has been discussed in several earlier posts in this blog.

Since humanitarian-ict is a public list but is I expect not one that is very well-known I am taking the liberty of copying Sanjiva’s post here in its entirety to share it with you:


The recent message by Paola on the humanitarian-ict list has made me realize that there now are probably many on this list who don’t know how this all started. So let me take a bit of time to write a short narrative of the story of Sahana .. told from my memory and perspective. My
apologies if I missed any key people (I probably did :(..) and for any other mistakes in my narrative. I’m on a long flight so I don’t have net access to check my old blogs to validate the dates. If anyone is interested you can read the blogs I wrote during the tsunami to see the
gory details of the really early days; Google will help you find those.

Sunday, December 26th, 2004. Tsunami hits Indonesia, Sri Lanka and many other Asian countries. In the first week of the tunami, 1m people (or 5% of our population) was homeless. 2/3rds of Sri Lanka’s coast was affected in some way. Later on we find that nearly 40,000 of our people have died.

Tuesday, December 28th, 2004. Many different organizations in Sri Lanka start efforts to write various bits of software to help manage the disaster. (This bit of the story was repeated in other countries- India, Indonesia, Thailand etc..)

Wednesday, December 29th, 2004. Many of these folks get together at the ICT Agency in Narahenpita, Sri Lanka to discuss ways of putting the software all together to make it easier to manage the situation. That nite I called the US Federal Emergency Management Agency (FEMA)’s CIOs office (after finding the phone number in a powerpoint presentation he had done
proposing developing a disaster management software system) and asked for whatever software they had. I was told that FEMA had no software that could help .. they only had software that was used to cut checks to people after hurricanes.

In the 3-4 weeks that followed, many many individuals, universities and software companies and Sri Lanka Telecom contributed to what became known as Sahana. Amongst the IT companies, Virtusa was the leading contributor with more than 75 of their engineering staff helping at some time or the other. While most contributors to the initial effort were from Sri Lanka, I’d be remiss if I didn’t mention the urgent support we got from folks at Tigris.org (which we didn’t end up using) and later SourceForge. We desperately needed a code repository and other infra (like mailing lists) and these folks willingly and urgently came out of their holiday slumber and got everything that we needed. Special mention also needs to go IBM’s Crisis Response Team lead by Brent Woodworth, who were then regular visitors to Sri Lanka. From day 1 that entire team supported, encouraged and cheered on the Sahana effort. In fact a good part of the initial development was done on 15 notebooks that IBM donated within a week or so of the tsunami.

This joint effort was organized and managed by the Lanka Software Foundation. In the early days we had a 24×7 operation and the first bits of software went into production use in about a week. Over time more and more capabilities were added and used in various ways. After about 3 months this initial phase was completed and the software and its deployment reached a certain level of equilibrium.

In the meantime, it became clear to us that there was a huge hole in the world of disaster management software. The state of the art that the UN team that came to Sri Lanka with was a system called SUMA- something written on FoxPRO. (Anyone remember FoxPRO? Yes, that was the pre-relational desktop database system from Microsoft!) IBM had some stuff based on Lotus Notes but it wasn’t easily deployable, scalable and, most importantly, didn’t embrace the Web. The tsunami gave us a unique opportunity to look at disaster management in the modern world: even though there was sooo much death and damage, the communication network was in tact. Cell phones worked. The IP networks worked. Land-lines worked. A modern disaster management system must work in a connected environment .. and if communication has indeed failed (as often happens in earthquake type disasters) its now quite easy to airdrop a box that sets up a local communication network with a satellite uplink. Clearly, there was a huge need for modern software that could live in this world and help first responders and follow-up recovery folks be more effective at responding and managing a disaster.

We were not going to let Sahana die; we decided we are going to make it into something the world can reuse readily. “We” at the time was primarily Jivaka Weeratunge, co-founder of LSF and its then volunteer COO, and myself. Chamindra de Silva, who had been one of the original people from Virtusa who started the people registry which became a key component of Sahana,
agreed to leave his job at Virtusa and take a 1-year position in LSF to take Sahana forward if we could get the funding for it. Chamindra became part of the “let’s take sahana forward” team.

On February 11th 2005 I wrote the following in a cover letter on the proposal we submitted to Ms. Asa Heijne, First Secretary of the Swedish Embassy in Colombo along with a proposal seeking Rs. 8.548m (approximately $85k) in funding from the Swedish International Development Agency (SIDA) to re-do Sahana:

“Further to our discussions in late January, enclosed please find a proposal to further develop the Sahana Relief Management system into a fully reusable, globalized relief management system. We believe the potential global impact of such software will be tremendous and view this as an opportunity to help the world at a time when the world is helping Sri Lanka so willingly and widely.”

SIDA approved our proposal and Sahana phase II started with that funding on August 1st 2005. I also want to acknowledge the contribution of Per-Einar Troften in getting this funding- Per-Einar is in SIDA in Sweden. He and Asa have (with the grant of $100k to start the Apache Axis2 project and the Sahana grant) singlehandedly (two-handedly?) changed the role of Sri Lanka in the FOSS world. If not for their trust in what LSF was proposing to do Sahana wouldn’t exist in its current shape today.

I must also acknowledge LSF’s co-founder and then COO Jivaka Weeratunge- he’s the one who helped manage LSF and make sure that we ran a superbly tight and clear ship which made it easier for a funding agency to trust us. Oh yeah, Jivaka was a total volunteer doing all of that, as is the entire LSF Board. Jivaka was a key part of the strategy behind LSF overall and then both and Sahana as we took them forward.

I think the following paragraphs we put in the proposal about why open source was a critical component of disaster management may be useful for folks to read:

“Very few countries and organizations today can afford to invest a lot of resources in disaster management when there is no disaster present. While this is obviously true of poor, developing nations, it is also true of richer, developed countries as well because there are always higher
priority items that need the funding. Worse yet, even if there are some national scale systems that may get deployed, it is very unlikely that regional and local level systems will ever get deployed if they cost any significant amount of resources.

Because no one is willing to pay for the software, no one is willing to build it either. This is what we see in the world today – while disaster management software is critically needed, there is no complete commercial or non-commercial software solution that is widely available.
Going the open source way can address both these concerns. Using the open source development model, it is possible to develop this software at a much reduced cost compared to pure commercial development models. This is true because while commercial entities are not willing to invest into these systems, there are hundreds and thousands of well-meaning IT
professionals who are very happy to donate a few hours of effort to helping build such systems. We are already seeing this with the nascent Sahana project. Thus if there was a small team which was driving such a project, then it is possible to get a lot of assistance from the global IT
community to make those systems truly exceptional.

Going with open source approaches can also greatly reduce the deployment cost of this software in peace (i.e., non-disaster) times. The Sahana system, for example, can be deployed on any PC with just a Linux LiveCD (that is, a CD from which the entire system can be booted up and brought on-line). Thus, not only is it possible to run this on commodity, inexpensive hardware, it is in fact possible to not even have dedicated hardware around – just take any office PC and make that the “disaster management center”! In fact, that is how Sahana was first deployed in Sri Lanka – on a borrowed PC. (Later it switched to running on a borrowed
server as the capacity requirements increased.)

Thus, open source is the natural way to providing disaster management solutions.”

So that’s how Sahana Phase II was born.

LSF has managed the Sahana project (and charges 20% overhead on the human resources part of the budget to do it .. a grand total of Rs. 1.008m or around $10k for phase II) with the LSF board being the final authority for how the Sahana team was deployed.

For those of you who know nothing about LSF- the board of LSF consists of local software company senior executives (usually CEOs), heads of CS departments of the 4 main public universities in Sri Lanka) and a few other distinguished individuals. The board is not compensated and everyone participates to help improve Sri Lanka’s position in FOSS- not for direct commercial or personal benefit. We’re of course a non-profit organization legally registered in Sri Lanka. LSF’s finances are annually audited by Ernst & Young in Sri Lanka.

What LSF does is find the funding for and run projects like Sahana.

After the funding for Sahana from SIDA finished at the end of July 2006, we’ve received a few additional grants .. with special thanks again to IBM for both cash and significant hardware donations. Google also donated some funds for LSF/Sahana.

Sahana has of course been a TREMENDOUS success. Kudos go to the core development team (Chamindra, Pradeeper, Ravindra, Mifan and the rest of the gang) for producing superb software, the committed bunch of folks on the Sahana mailing lists (with special mention to Paul, Louiqa, Don and Gav) and to the numerous others who have helped with developing Sahana, deploying it or just talking about it. Special mention must go here to the efforts of the IBM Crisis Response Team in deploying Sahana in numerous disaster and pre-disaster situations. On the recognition side, the recent FSF Award is clearly the high point, being the second recipient of that after Wikipedia. The list of deployments of Sahana is absolutely incredible .. and now includes both poor and rich (richest?) countries.

In this context the LSF Board started thinking last year about how to best take Sahana forward and about the role of the LSF Board. We concluded that the best thing to do was to hand over “reigns” of the LSF part of Sahana to a new team of people who would be focused purely on making Sahana climb as high as it can. In doing that, we CLEARLY separated the successful FOSS project that Sahana is from the LSF managed work in developing and deploying Sahana. In order to further the FOSS project of Sahana, we created the Sahana Project Management Committee, modeled closely on the Apache Software Foundation’s model. The FOSS project and the PMC are purely community efforts- while we created the PMC, the future membership
of the PMC will be determined by the current PMC members. We bootstrapped it and now its off on its own. Good luck!

The board has been appointed by LSF and will take overall charge of all LSF activities related to Sahana, including budgets. Sahana Board members are all volunteers and we’re extremely grateful for their willingness to help take Sahana forward. LSF is the underlying legal authority for the activities that the Sahana Board governs.

The specific roles and responsibilities of the community, PMC and the Board were documented in an email I posted to this list earlier. See:

http://groups.yahoo.com/group/humanitarian-ict/message/2674

I hope this helps people understand how Sahana got started and how it has evolved. Most importantly, I hope it makes clear the governance structure of Sahana and its intrinsically open nature.

I personally drove the creation of this model (in close consultation with a bunch of folks, esp. Chamindra, Louiqa, Paul, Don, Gav, Pradeeper and more) and I used my 10+ years of experience with Apache and other open source efforts to help create what I think is an absolutely open model. That said, there’s always room for improving the structure and activities-
make constructive suggestions and I’m sure the community, the PMC, the Sahana Board and the LSF Board will be willing listeners!

Sanjiva.

Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Director; Open Source Initiative; http://www.opensource.org/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/


Ralph Griswold: “I wish I had done it myself. In the long run I always do.”

I wrote in a previous post Computer History Museum: Preserving Snobol and Spitbol Artifacts about SNOBOL and Spitbol, and noted therein the death of Ralph Griswold late last year.

I took immense satisfaction in his work on the SNOBOL and ICON programming languages though
I never had the good fortune to meet Ralph.Our only dealings had to do with some SNOBOL matter close to three decades ago. I forget the details except that during a phone conversation he made one of the wisest remarks I have ever heard:

Ralph Griswold: I wish I had done it myself. In the long run I always do.

Another was from Jack Schwartz:

Jack Schwartz: Work is a signed quantity.

A picture of Ralph can be found at Ralph E. Griswold Memorial Endowment.

Ralph Griswold – May his memory be a blessing.

Computer History Museum: Preserving Snobol and Spitbol Artifacts

I am one of the small circle of programmers still around to whom the phrases “snow ball” and “spit ball” have special meaning:

  • It’s not about snow or baseball;
  • When I spell them them both end in “bol”, as in “Snobol” and “Spitbol”
  • They are both programming languages
  • Thinking of either makes me think of the color green

Only those who have ever written a program in either of these languages can appreciate the surprise — mixed because it brought both good and bad news — with which I read the following e-mail sent my way by Bob Goldberg, someone I haven’t heard from in well over a decade:

Hi Dave,

It’s been a few years … I hope that you receive this email as I’ve had some trouble locating a live email id for you.

After Ralph Griswold passed away last year I found out that a co-worker at Adobe, Paul McJones, had secured his electronic archives for preservation at the Computer History Museum. Since I have more than a passing interest in preserving Spitbol artifacts I volunteered to assist and have taken on the task of identifying and preserving Snobol artifacts for the CHM.

Do you have any Spitbol (or Snobol) related material that we can preserve? As I remember it you did a Macro Spitbol port for the Cyber, but my memory may be faulty. The CHM can handle all forms of media: paper, mag tape, and even punched cards.

I still have fond memories of the Snobol/Spitbol workshop hosted at NYU about 30 years ago. I remember you and your wife hosted all of us for a dinner at your apartment. I also remember your giving me Jack’s book on compilers, which I still possess today. Thanks again! (I had planned to give it, along with other books, etc, to the CHM, but Al Kossow has already located a copy and scanned it!)

Here are some links that you might find interesting

Computer History Museum: Software Preservation Group

CHM: Cocke and Schwartz

bitsavers.org

Spitbol 360

Regards,

Bob

The reference to Jack is to Jacob “Jack” Schwartz and relates to the preservation of the text of “Cocke and Schwartz,” one of the seminal works on programming optmization. (Most of the text was written out in longhand while Jack spent several months on jury duty, and was then typed up by Connie Engle, who worked magic for many years at CIMS preparing mathematical manuscripts using the now-forgotten technology of the Selectric typewriter and its type balls, back in the days before Knuth’s Tex defined the standard for publishing scientific manuscripts.)

I worked with Robert B. K. Dewar, co-author (with Ken Belcher) of Spitbol/360 and Macro Spitbol (with Tony McCann), on the implementation of Spitbol for the CDC 6600 and later the IBM PC. Macro Spitbol was written in a pseudo-assembly language called MINIMAL, one of the cleverest and best-documented programming efforts I have ever been involved in.

So I ask anyone who may have SNOBOL or SPITBOL artifacts to heed Bob’s request. For my part, I’ll try to dig up a small colllection of programs that I used to balance my checkbook over a period of about fifteen years, and it would also I think be useful to publish at least the specification of MINIMAL, as it is such a fine piece of writing.

During the course of a career a programmer can expect to learn at least a handful of languages quite well, some less so, and a larger number in a cursory fashion. And those who have been in this game a long time, as have I, always look back on only a few with a special affection, as to study and learn them was to gain new insight into the nature of programming iitself, and why it remains such a compelling activity.

Ralph Griswold was the father of SNOBOL, one of my beloved languages, and anything we can do to honor his work is well worth doing.

Ralph Griswold – may his memory be a blessing.

  • Pages

  • May 2007
    M T W T F S S
    « Apr   Jun »
     123456
    78910111213
    14151617181920
    21222324252627
    28293031  
  • RSS The Wayward Word Press

  • Recent Comments

    dave porter on On being the maintainer, sole…
    daveshields on On being the maintainer, sole…
    Paul Tallett on On being the maintainer, sole…
    mrrdev on On being the maintainer, sole…
    KT on On being the maintainer, sole…
  • Archives

  • Blog Stats

  • Top Posts

  • Top Rated

  • Recent Posts

  • Archives

  • Top Rated