Friday, December 19, 2008

Camera company Polaroid has filed for Chapter 11 bankruptcy protection in the United States. The firm, famed for the introduction of instant photography, says alleged fraud by the founder of their parent group is to blame.

Owned since 2005 by Petters Group Worldwide, Polaroid says that the group’s founder Tom Petters is “under investigation for alleged acts of fraud that have compromised the financial condition of Polaroid.” Authorities believe Petter, currently in police custody, was running fraud worth £3 billion, something he denies.

Petters Group, itself, filed for bankruptcy in October. Both firms now face restructuring, which Polaroid is confident won’t affect daily operations — in fact, the company is “planning for new product launches in 2009,” and claims to have “entered bankruptcy with ample cash reserves sufficient to finance the company’s reorganization under Chapter 11.”

Polaroid has further said that employees will be paid without interruption, and that while members of Petters Group are under investigation for fraud, Polaroid’s management is not. The company, based in Minnesota, also has subsidiaries which will enter bankruptcy with it.

Wednesday, September 20, 2006

A population study, released by Statistics New Zealand titled A History of Survival in New Zealand, highlights that the life expectancy of New Zealand males born in the mid 1890’s would have been five years higher without the impact of the two world wars, as 10% of males died in war. Also males born in the late 1910’s would have had a three year higher life expectancy, without the impact of the two world wars as well. The new study is an international study of survival and mortality.

The study also reveals that a male born in the late 1870’s would have had an average life span of 51-years-old and in the 1930’s the average life span was 69-years-old. And in females the life expectancy is 75-years-old, previously 55-years-old.

Kim Dunstan, Statistics NZ demographer, said: “The dramatic lifespan changes were attributed to many factors, including improved hygiene, sanitation, medicines and infectious disease control. Changes in lifestyle had also made an important difference.”

People born in the late 1870’s had a 23% chance of not making it to see their 15th birthday, people born in the 1900’s had a 15% chance, people born in the 1930’s had a seven percent chance, people born in the 1960’s had a three percent chance and those born around the 1990’s had a one percent chance.

Mr Dunstan said: “The study provided the most complete picture of how long New Zealanders lived and showed for the first time the impact of war deaths on the population. Death comes to us all and it does affect us at a lot of levels. A lot of people have had family members who died in the war and can relate to their own experiences.”

A History of Survival in New Zealand also shows that New Zealand is one of the few countries in the world that has an almost complete and detailed history of births, deaths and migration information dating back to the late 1800’s. This study is a historic book full of births, deaths and external migration for the population of New Zealand. It will also be used in the future relating to health, population and mortality areas. It is also unique because it follows the population from birth right through to death. “We see the study very much as the basis for further work … across other organisations in New Zealand and, indeed, internationally,” Mr. Dunstan said.

See the discussion page for instructions on adding schools to this list and for an alphabetically arranged listing of schools.

Due to the damage by Hurricane Katrina and subsequent flooding, a number of colleges and universities in the New Orleans metropolitan area will not be able to hold classes for the fall 2005 semester. It is estimated that 75,000 to 100,000 students have been displaced. [1]. In response, institutions across the United States and Canada are offering late registration for displaced students so that their academic progress is not unduly delayed. Some are offering free or reduced admission to displaced students. At some universities, especially state universities, this offer is limited to residents of the area.

Friday, May 19, 2006

This interview intends to provide some insight into OpenSync, an upcoming free unified data synchronization solution for free software desktops such as KDE, commonly used as part of the GNU/Linux operating system.

Hi Cornelius, Armin and Tobias. As you are now getting close to version 1.0 of OpenSync, which is expected to become the new synchronisation framework for KDE and other free desktops, we are quite interested in the merits it can provide for KDE users and for developers, as well as for the Open Source Community as a whole. So there’s one key-question before I move deeper into the details of OpenSync:

What does OpenSync accomplish, that no one did before?

Cornelius:

First of all it does its job of synchronizing data like addressbooks and calendars between desktop applications and mobile devices like PDAs and cell phones.

But the new thing about OpenSync is that it isn’t tied to a particular device or a specific platform. It provides an extensible and modular framework that is easy to adopt for application developers and people implementing support for syncing with mobile devices.

OpenSync is also independent of the desktop platform. It will be the common syncing backend for at least KDE and GNOME and other projects are likely to join. That means that the free desktop will have one common syncing solution. This is something really new.

How do the end-users profit from using synching solutions that interface with OpenSync as framework?

Cornelius:

First, the users will be able to actually synchronize all their data. By using one common framework there won’t be any “missing links”, where one application can sync one set of devices and another application a different one. With OpenSync all applications can sync all devices.

Second, the users will get a consistent and common user interface for syncing across all applications and devices. This will be much simpler to use than the current incoherent collection of syncing programs you need if you have more than the very basic needs.

How does OpenSync help developers with coding?

Cornelius:

It’s a very flexible and well-designed framework that makes it quite easy for developers to add support for new devices and new types of data. It’s also very easy to add support for OpenSync to applications.

The big achievement of OpenSync is that it hides all the gory details of syncing from the developers who work on applications and device support. That makes it possible for the developers to concentrate on their area of expertise without having to care what’s going on behind the scenes.

I have written quite a lot of synchronization code in the past. Trust me, it’s much better, if someone just takes care of it for you, and that’s what OpenSync does.

Tobias:

Another point to mention is the python wrapper for opensync, so you are not bound to C or C++, but can develop plugins in a high level scripting language.

Why should producers of portable devices get involved with your team?

Cornelius:

OpenSync will be the one common syncing solution for the free desktop. That means there is a single point of contact for device manufacturers who want to add support for their devices. That’s much more feasible than addressing all the different applications and solutions we had before. With OpenSync it hopefully will become interesting for manufacturers to officially support Linux for their devices.

Do you also plan to support applications of OpenSync in proprietary systems like OSX and Windows?

Cornelius:

OpenSync is designed to be cross-platform, so it is able to run on other systems like Windows. How well this works is always a question of people actually using and developing for this system. As far as I know there isn’t a real Windows community around OpenSync yet. But the technical foundation is there, so if there is somebody interested in working on a unified syncing solution on Windows, everybody is welcome to join the project.

What does your synchronisation framework do for KDE and for KitchenSync in particular?

Cornelius:

OpenSync replaces the KDE-specific synchronization frameworks we had before. Even in KDE we had several separate syncing implementations and with OpenSync we can get replace them with a common framework. We had a more generic syncing solution in KDE under development. This was quite similar from a design point of view to OpenSync, but it never got to the level of maturity we would have needed, because of lack of resources. As OpenSync fills this gap we are happy to be able to remove our old code and now concentrate on our core business.

What was your personal reason for getting involved with OpenSync?

Cornelius:

I wrote a lot of synchronization code in the past, which mainly came from the time where I was maintaining KOrganizer and working on KAddressBook. But this always was driven by necessity and not passion. I wanted to have all my calendar and contact data in one place, but my main objective was to work on the applications and user interfaces handling the data and not on the underlying code synchronizing the data.

So when the OpenSync project was created I was very interested. At GUADEC in Stuttgart I met with Armin, the maintainer of OpenSync, and we talked about integrating OpenSync with KDE. Everything seemed to fit together quite well, so at Linuxtag the same year we had another meeting with some more KDE people. In the end we agreed to go with OpenSync and a couple of weeks later we met again in Nuernberg for three days of hacking and created the KDE frontend for OpenSync. In retrospect it was a very pleasant and straightforward process to get where we are now.

Armin:

My reason to get involved (or better to start) OpenSync was my involvement with its predecessor Multisync. I am working as a system administrator for a small consulting company and so I saw some problems when trying to find a synchronization solution for Linux.

At that point I joined the Multisync project to implement some plugins that I thought would be nice to have. After some time I became the maintainer of the project. But I was unhappy with some technical aspects of the project, especially the tight coupling between the syncing logic and the GUI, its dependencies on GNOME libraries and its lack of flexibility.

Tobias:

Well, I have been a KDE PIM developer for several years now, so there was no way around getting in touch with synchronization and KitchenSync. Although I liked the idea of KitchenSync, I hated the code and the user interface […]. So when we discussed to switch to OpenSync and reimplementing the user interface, I volunteered immediately.

Can you tell us a bit about your further plans and ideas?

Cornelius:

The next thing will be the 1.0 release of OpenSync. We will release KitchenSync as frontend in parallel.

Armin:

There are of course a lot of things on my todo and my wishlist for opensync. For the near future the most important step is the 1.0 release, of course, where we still have some missing features in OpenSync as well as in the plugins.

One thing I would really like to see is a thunderbird plugin for OpenSync. I use thunderbird personally and would really like to keep my contacts up to date with my cellular, but I was not yet able to find the time to implement it.

Tobias:

One thing that would really rock in future versions of OpenSync is an automatic hardware detection mechanism, so when you plugin your Palm or switch on your bluetooth device, OpenSync will create a synchronization group automatically and ask the user to start syncing. To bring OpenSync to the level of _The Syncing Solution [tm]_ we must reduce the necessary configuration to a minimum.

What was the most dire problem you had to face when creating OpenSync and how did you face it?

Cornelius:

Fortunately the problems which I personally would consider to be dire are solved by the implementation of OpenSync which is well hidden from the outside world and [they are] an area I didn’t work on 😉

Armin:

I guess that I am the right person to answer this question then 🙂

The most complicated part of OpenSync is definitely the format conversion, which is responsible for converting the format of one device to the format that another device understands.

There are a lot of subsystems in this format conversion that make it so complex, like conversion path searching, comparing items, detection of mime types and last but not least the conversion itself. So this was a hard piece of work.

What was the greatest moment for you?

Cornelius:

I think the greatest moment was when, after three days of concentrated hacking, we had a first working version of the KDE frontend for OpenSync. This was at meeting at the SUSE offices in Nuernberg and we were able to successfully do a small presentation and demo to a group of interested SUSE people.

Armin:

I don’t remember a distinct “greatest moment”. But what is a really great feeling is to see that a project catches on, that other people get involved, use the code you have written and improve it in ways that you haven’t thought of initially.

Tobias:

Hmm, also hacking on OpenSync/KitcheSync is much fun in general, the greatest moment was when the new KitchenSync frontend synced two directories via OpenSync the first time. But it was also cool when we managed to get the IrMC plugin working again after porting it to OpenSync.

As we now know the worst problem you faced and your greatest moment, the only one missing is: What was your weirdest experience while working on OpenSync?

Cornelius:

Not directly related to OpenSync, but pretty weird was meeting a co-worker at the Amsterdam airport when returning from the last OpenSync meeting. I don’t know how high the chance is to meet somebody you know on a big random airport not related at all to the places where you or the other person live, but it was quite surprising.

Tobias:

Since my favorite language is C++, I was always confused how people can use plain C for such a project, half the time your are busy with writing code for allocating/freeing memory areas. Nevertheless Armin did a great job and he is always a help for solving strange C problems 🙂

Now I’d like to move on to some more specific questions about current and planned abilities of OpenSync. As first, I’ve got a personal one:

I have an old iPod sitting around here. Can I or will I be able to use a program utilizing OpenSync to synchronize my calendars, contacts and music to it?

Cornelius:

I’m not aware of any iPod support for OpenSync up to now, but if it doesn’t exist yet, why not write it? OpenSync makes this easy. This is a chance for everybody with the personal desire to sync one device or another to get involved.

Armin:

I dont think that there is iPod support yet for OpenSync. But it would definitely be possible to use OpenSync for this task. So if someone would like to implement an iPod plugin, I would be glad to help 🙂

Which other devices do you already support?

Cornelius:

At this time, OpenSync supports Palms, SyncML and IrMC capable devices.

Which programs already implement OpenSync and where can we check back to find new additions?

Cornelius:

On the application side there is support for Evolution [GNOME] and Kontact with KitchenSync [KDE] on the frontend side and the backend side and some more. I expect that further applications will adopt OpenSync once the 1.0 version is released.

Armin:

Besides kitchensync there already are a command line tool and a port of the multisync GUI. Aside from the GUIs, I would really like to see OpenSync being used in other applications as well. One possibility for example would to be integrate OpenSync into Evolution to give users the possibility to synchronize their devices directly from this application. News can generally be found on the OpenSync web site www.opensync.org.

It is time to give the developers something to devour, too. I’ll keep this as a short twice-fold technical dive before coming to the takeoff question, even though I’m sure there’s information for a double-volume book on technical subleties.

As first dive: How did you integrate OpenSync in KitchenSync, viewed from the coding side?

Cornelius:

OpenSync provides a C interface. We wrapped this with a small C++ library and put KitchenSync on top. Due to the object oriented nature of the OpenSync interfaces this was quite easy.

Recently I also started to write a D-Bus frontend for OpenSync. This also is a nice way to integrate OpenSync which provides a wide variety of options regarding programming languages and system configurations.

And for the second, deeper dive:

Can you give us a quick outline of those inner workings of OpenSync, from the developers view, which make OpenSync especially viable for application in several different desktop environments?

Cornelius:

That’s really a question for Armin. For those who are interested I would recommend to have a look at the OpenSync website. There is a nice white paper about the internal structure and functionality of OpenSync.

Armin:

OpenSync consists of several parts:

First there is the plugin API which defines what functions a plugin has to implement so that OpenSync can dlopen() it. There are 2 types of plugins:

A sync plugin which can synchronize a certain device or application and which provides functions for the initialization, handling the connection to a device and reading and writing items. Then there is a format plugin which defines a format and how to convert, compare and detect it.

The next part is a set of helper functions which are provided to ease to programming of synchronization plugins. These helper functions include things like handling plugin config files, HashTables which can be used to detect changes in sets of items, functions to detect when a resync of devices is necessary etc.

The syncing logic itself resides in the sync engine, which is a separate part. The sync engine is responsible for deciding when to call the connect function of a plugin, when to read or write from it. The engine also takes care of invoking the format conversion functions so that each plugin gets the items in its required format.

If you want more information and details about the inner workings of OpenSync, you should really visit the opensync.org website or ask its developers.

To add some more spice for those of our readers, whose interest you just managed to spawn (or to skyrocket), please tell us where they can get more information on the OpenSync Framework, how they can best meet and help you and how they can help improving sync-support for KDE by helping OpenSync.

Cornelius:

Again, the OpenSync web site is the right source for information. Regarding the KDE side, the kde-pim@kde.org mailing list is probably the right address. At the moment the most important help would be everything which gets the OpenSync 1.0 release done.

[And even though] I already said it, it can’t be repeated too often: OpenSync will be the one unified syncing solution for the free desktop. Cross-device, cross-platform, cross-desktop.

It’s the first time I feel well when thinking about syncing 😉.

Armin:

Regarding OpenSync, the best places to ask would be the opensync mailing lists at sourceforge or the #opensync irc channel on the freenode.net servers.

There are always a lot of things where we could need a helping hand and where we would be really glad to get some help. So everyone who is interested in OpenSync is welcome to join.

Many thanks for your time!

Cornelius:

Thanks for doing the interview. It’s always fun to talk about OpenSync, because it’s really the right thing.

Armin:

Thank you for taking your time and doing this interview. I really appreciate your help!

Tobias:

Thanks for your work. Publication and marketing is something that is really missing in the open source community. We have nice software but nobody knows 😉

Further Information on OpenSync can be found on the OpenSync Website: www.opensync.org

This Interview was done by Arne Babenhauserheide in April 2006 via e-mail and KOffice on behalf of himself, the OpenSource Community, SpreadKDE.org and the Dot (dot.kde.org).It was first published on the Dot and is licensed under the cc-attribution-sharealike-license.A pdf-version with pictures can be found at opensync-interview.pdf (OpenDocument version: opensync-interview.odt)

Wednesday, September 19, 2007File:SELENE.jpg

An H-IIA rocket, carrying the SELENE lunar orbiter and several smaller satellites, was launched on Friday, September 14 from the Tanegashima Space Center in Japan.

The launch, conducted at 01:31 GMT by Mitsubishi Heavy Industries for the Japan Aerospace Exploration Agency (JAXA), begins the voyage of SELENE to the Moon, and Japanese space officials say that the mission has been going smoothly.

“The flight has been proceeding smoothly to this point. We haven’t had any reports of problems with any of the equipment,” said JAXA spokesman Seiji Toyama who also added that the probe is about to finish its first of two orbits around Earth.

SELENE will be placed in orbit 60 miles (100 kilometers) above the Moon‘s surface where two smaller probes will be released and then begin to orbit the Moon at both poles. Scientists are hoping that the data will shed more light on how the Moon was formed, and how it has evolved through time. They also hope to study the composition of dust samples from the surface and are planning on taking 3-D images of the Moon’s surface.

JAXA was forced to delay the launch by one day, with the launch originally scheduled to occur on September 13.

Sunday, October 10, 2010

Residents of a Leeds, England neighbourhood have requested help from a council because their neighbourhood is plagued by crime, overcrowding, and community tensions.

Leeds City Council received a request for help from residents of Hyde Park, who said they were worried about the increasing level of anti-social behavior and worsening community relations. A report will be unveiled on Wednesday by a council delegation, highlighting the problems in the area. “The people living in Hyde Park come from widely different population groups… these groups have very different customs, needs and living styles and this can provoke high levels of tension in the area,” the delegation said.

The council claims that because of the 28 per cent ethnic minority population and the 40,000 students living in the neighbourhood, there are tensions between residents. They added, however, that they are actively encouraging people to work together, citing a multi-faith forum, a cricket competition and activities which bring old and young together.

The report says that the council are trying to build relationships between Muslims and police, something which they said is “particularly important after the area’s connection to the London bombings on 7th July 2005.” A local newspaper reported that “the Shebab project introduces young Muslims to role models from sport and culture and also runs scholars’ talks to counter extremist ideologies.”

Crime has increased by 7% in the past year in Hyde Park, and residents noted that anti-social behaviour was getting worse. The council said that an anti-burglary task force had helped to reduce the number of thefts from homes. Residents complained that there was a lack of pride in the area, and at the end of the academic year in the summer, large piles of rubbish were left in streets, yards and alleyways. The report adds that the council operates a recycling scheme aimed towards teenagers, and that rubbish collections have increased.

The Guardian reported on Wednesday that campaigners are attempting to “take control of a derelict school building and transform it into a community hub are appealing for sponsors and partners in a bid to turn their dreams into reality.” They say that the unused building, owned by the council, could be used for meetings and events. A volunteer group of residents have been working on a business plan, and have gained support from local businesses to create “a vision of an open, accessible and valuable resource for all.”

A member of the commitee, however, said he was “frustrated” with the council’s attitude towards the plans. “The RPCC is slightly frustrated with certain communication issues that we’ve had with the council, but we’re working with them and hoping to gain further assistance going forward,” he said. “It’s a shame that certain setbacks could have been avoided.”

The deputation added that “a major factor in Hyde Park’s suffering is its high level of population density”, which they conceded is something they are unable to change. The council responded to complaints that streets are “cheap and unhealthy takeaways, letting agents and boarded-up shop fronts,” by saying that Hyde Park Corner and Headingley are, according to the Yorkshire Post, “thriving shopping areas and work had taken place to ensure a good mix of outlets.”

The report concludes: “The council acknowledges that because of the very particular circumstances which exist in the neighbourhood, Hyde Park faces difficult challenges which affect the quality of life of residents and that ‘normal’ service levels may not be sufficient to tackle some of these. The council will do more to enable local people to influence how services work and how local problems are tackled. Local community and voluntary groups will be invited to play an active role.”