Less Expectations for LES
The 217th GA is being hailed as the first "paper-less" general assembly for PC(USA). This will certainly save a lot of trees -- if not a forest -- judging from the amount of documents that are traditionally needed to transact the church's business. (It would be good if someone actually crunches the numbers and figure out how many trees are saved) .
The core is a network called LES, which must stand for something or is perhaps the name that the staff have given the electronic system in an attempt to anthromorphize it. If it is the latter, I am also guilty of it since I will be bringing Bobot -- my laptop -- to the general assembly.
The concept behind LES is theoretically cool. LES will not only be a repository of documents, but will also enable users to track changes, it has a section for notes, and a calendar. During the assembly, recorders will be able to post reports as changes happen or decisions are made. After the assembly, it becomes an archive. Reality is, however, far from cool.
I applaud any effort to save trees, but the problem is that LES is turning out to be a klutz. Never mind that it's design is non-existent; especially if compared to the ease of navigation and graphic design of the PC(USA) website. I have a broadband connection at home, but LES keeps on crashing or worst, freezing -- that is, of course, if you can access it. If I use my wifi, I encounter the same problems. I thought it was just me, but I have heard from other commissioners who have similar problems.
The excuse that the staff is giving is that it is a work in progress, but after it was allegedly beta tested at the 216th GA, one would expect that the bugs will have already been resolved as it is rolled out.
Now imagine 534+ commissioners plus dozens of advisory delegates, overture advocates, observers, and staff accessing LES simultaneously over a wireless network during the 217th GA. The system will crash or freeze. LES' developers better have several 24/7, on-site techies -- and not out-sourced to a company in Bangalore.
Last March, I emailed the PC(USA) staff at AskLes@ctr.pcusa.org regarding problems I had logging in. They are unable to do anything other than forward my email to the computer rental company which they contracted to develop LES. From their response, and from what I am experiencing, the contractor, ABS Computer Rentals, Inc. should just have focused on their core competence -- renting out computers for conferences.
I suggested to Sharon Youngs, communications coordinator of the Office of the General Assembly, that we be provided with a CD containing all the documents we will need to transact business as a back-up when LES crashes or freezes. So far, no response.
Needless to say, I am hoping that LES gets sorted out soon so that s/he can interact well with Bobot and the other laptops during the general assembly.
The core is a network called LES, which must stand for something or is perhaps the name that the staff have given the electronic system in an attempt to anthromorphize it. If it is the latter, I am also guilty of it since I will be bringing Bobot -- my laptop -- to the general assembly.
The concept behind LES is theoretically cool. LES will not only be a repository of documents, but will also enable users to track changes, it has a section for notes, and a calendar. During the assembly, recorders will be able to post reports as changes happen or decisions are made. After the assembly, it becomes an archive. Reality is, however, far from cool.
I applaud any effort to save trees, but the problem is that LES is turning out to be a klutz. Never mind that it's design is non-existent; especially if compared to the ease of navigation and graphic design of the PC(USA) website. I have a broadband connection at home, but LES keeps on crashing or worst, freezing -- that is, of course, if you can access it. If I use my wifi, I encounter the same problems. I thought it was just me, but I have heard from other commissioners who have similar problems.
The excuse that the staff is giving is that it is a work in progress, but after it was allegedly beta tested at the 216th GA, one would expect that the bugs will have already been resolved as it is rolled out.
Now imagine 534+ commissioners plus dozens of advisory delegates, overture advocates, observers, and staff accessing LES simultaneously over a wireless network during the 217th GA. The system will crash or freeze. LES' developers better have several 24/7, on-site techies -- and not out-sourced to a company in Bangalore.
Last March, I emailed the PC(USA) staff at AskLes@ctr.pcusa.org regarding problems I had logging in. They are unable to do anything other than forward my email to the computer rental company which they contracted to develop LES. From their response, and from what I am experiencing, the contractor, ABS Computer Rentals, Inc. should just have focused on their core competence -- renting out computers for conferences.
I suggested to Sharon Youngs, communications coordinator of the Office of the General Assembly, that we be provided with a CD containing all the documents we will need to transact business as a back-up when LES crashes or freezes. So far, no response.
Needless to say, I am hoping that LES gets sorted out soon so that s/he can interact well with Bobot and the other laptops during the general assembly.


0 Comments:
Post a Comment
<< Home