Archives 2018

Thursday, April 19, 2007

Two fossilized trees with their roots, trunks and heads still attached, and are said to be over 380 million years old, have been found in the state of New York inside a rock quarry near Gilboa, New York in the USA.

Researchers call the extinct tree a Wattieza and this particular tree stood over 30 feet tall and used spores to reproduce rather than seeds. It may have even looked like many palms trees that exist today, but did not have any leaves. Instead they had fronds much like a fern.

“These were very big trees. Our reconstruction shows them to be a lot longer and much more treelike than any of the reconstructions before. I don’t think any of us dared think of them being quite that big,” said paleobotanist at the State University of New York at Binghamton, and one of the researchers who studied the tree, William Stein.

Over 130 years ago in 1870, the same kind of trees, but only the stumps, were also found in Gilboa after flood waters caused the stumps to be exposed. A few decades later in the 1920s, another set of stumps were found in the same area.

In 2004, the researchers found a top to one of the trees that weighed almost 400 pounds not too far from Gilboa.

Researchers say that these trees likely shaped the forests of Earth as we see them today, and that the trees existed long before dinosaurs were roaming the planet.

“In forming the first forests, they must have really changed the Earth system as a whole, creating new types of micro-environments for smaller plants and insects, storing large amounts of carbon and binding the soil together. The rise of forests removed a lot of carbon dioxide from the atmosphere. This caused temperatures to drop and the planet became very similar to its present-day conditions,” said the leader of the research team, Christopher Berry.

Wattiezas were most common during the Devonian period and existed on the planet before fish evolved sufficiently to leave the seas.

Monday, February 1, 2010

A decades-old building collapsed along Ma Tau Wai Road in Hong Kong at about 1:30pm on Friday, local time. That building was located at 45J, Ma Tau Wai Road in Hung Hom. A shop on its ground floor was undergoing renovations when the building collapsed. The street was full of dust afterwards. Firefighters arrived at the scene to search survivors and they asked residents in the buildings nearby to evacuate the area. Those buildings included 45G and 45H.

Chief Executive Donald Tsang called for an investigation into the cause of the building collapse. He aimed at preventing similar incidents. The government required all old buildings with similar structures to undergo inspection, according to Secretary for Development Carrie Lam.

The government has confirmed that four people were dead in the incident. Rescue efforts ended on Saturday morning when the government confirmed that no one was missing. Lam visited the scene on Saturday afternoon and sought advice from the police and Buildings Department. The police has started its investigation into the incident. Secretary for Labour & Welfare Matthew Cheung said that the government would do its best to meet the victims’ needs.

The collapsed building was more than 50 years old. The government had inspected its five-storey structure before the incident and had ordered repairs. After the tragedy, the government announced that it would inspect buildings older than 50 years in one month. The government has restricted access to buildings at 45G and 45H as they were in danger.

Tuesday, April 19, 2005

Denunciations of corruption, bribe, collection of bribes from refugees [1] and of sexual scandal involving the peacekeepers [2], [3] threaten the Organization of the United Nations (UN).

The gravest denunciations involve the aid project to Iraq, called Oil-for-Food. Grave denunciations of bribe exist, superfluous accounting and collaboration with the ex-dictator Saddam Hussein, against staff of the UN, companies and politicians of several countries. Even the secretary of the UN, Kofi Annan was suspicious of participation in the plan of corruption. And also grave doubts still hover about his son, Kojo Annan.

The gravity of the denunciations threatens not only the credibility of the UN, but its existence.

Secretary Kofi Annan said that he is going to promote reforms in the organization. [4]

Wednesday, April 2, 2008

“Localization of ‘SEMI Safety Guideline'”, executed by Safety and Health Technology Center of Taiwan (SAHTECH) and supervised by Semiconductor Equipment and Materials International (SEMI), was announced today in Hsinchu, Taiwan.

This localization included several fields on health and safety of semiconductor manufacturing, certification testing on electrical devices, evaluations on fire or natural diseases, and environmental issues on semiconductor manufacturing devices, etc.. Companies and manufacturers from the semiconductor industry also paid more attentions on this guideline because issues on carbon-savings, earthquakes, fire diseases, and environment-efficiencies were included into this guideline.

	This [safety] guideline was originally promoted by SEMI since 1975 and was set up according to industry infrastructures in Europe, America, Korea, Japan, and Taiwan. Currently, its standards from the S1 to S25 was completely ruled by several world-class executives in semiconductor industry, and the S26 standard for FPD industry, proposed in Taiwan, was also in several arrangements with the other countries.

	The semiconductor industry is a high-value industry in every country. If a fabrication plant (fab) was vandalized with fire or earthquake, how will a company decrease its lossless after a disease? As of some examples from the other countries, several companies didn’t pay more attentions on devices’ safety and finally got a damn trouble on counting lossless after a disease. By the way, voltages on electric using will take effect on energy especially the wasting of CO2. We [the semiconductor industry in Taiwan] hope this announcement will drive on global safety standards.

	Generally, the designs of a fab will take effect on possibilities when a disease take place in, and its scale will chain much wasting on manufacturing devices and materials. For example, when using fluorine in a fab, a company would consider using a gas tank car rather than a steel bottle. But due to environment and carbon-saving issues, some evaluations should be tested in a fab.

On the other side of the incoming trade show of 2008 SecuTech Expo, scheduled after 2 weeks at Taipei World Trade Center, not only main fields on security devices, information security, and fire & disease preventions, the digital monitoring will be a hot topic in security industry. For applications on fire & disease preventions, because its issues contained industrial applications and ESH (Environmental, Safety & Health) managements, if a company want to decrease the ratio of fire disease or earthquake, companies from safety and related industries should pay more attentions on disease preventions.

Wednesday, February 22, 2012

Crown Office are staying quiet about possible prosecutions after an inquiry found medical failures caused three deaths at NHS Lanarkshire.

In response to a specific question as to the possibility of prosecutions, a Crown Office spokesperson told Wikinews today that “The three deaths were fully investigated by the Procurator Fiscal and reported to Crown Counsel [laywers] to consider. Crown Counsel concluded that, given the facts and circumstances of the deaths, a Fatal Accident Inquiry (FAI) was the appropriate forum to consider the circumstances of the deaths.” It was further noted that “[a] FAI cannot make any findings of fault/blame against individuals.”

However, Crown Office did not specifically rule out prosecutions for offences such as cuplable homicide despite the spokesperson noting this was a direct response to such a question. They also declined to comment on National Health Service care as “it would not be appropriate to comment on the provision of NHS services” and entirely ignored questions about Crown Office satisfaction in the inquiry’s outcome and the length of time it took to reach a conclusion. The inquiry wrapped up last week but the deaths were in 2006.

Agnes Nicol, George Johnstone, and Andrew Ritchie died within a three-month period following keyhole surgery to remove their gall bladders.

Later expanded to look at all three deaths, the inquiry initially established to look into the case of Nicol, 50, who received surgery in late 2005. A surgeon at Wishaw General Hospital mistakenly cut her bile duct and her right hepatic artery. Whilst suturing her portal vein, her liver was left with 20% of its normal blood supply; the errors were not discovered until her transfer to liver specialists at Edinburgh’s Royal Infirmary.

By then, her liver was seriously damaged. She developed septicaemia, dying from multiple organ failure in March 2006.

Johnstone, 54, underwent the same procedure at Monklands District General Hospital on May 9, 2006. A consultant surgeon accidentally damaged, possibly severing, his bile duct. He died two days later in intensive care from the combined effects of multiple organ failure and a heart ailment.

Ritchie, 62, died in intensive care a week after an operation in June 2006. He died from intra abdominal haemorrhage caused by errors during the surgery.

Different surgeons were involved each time and the inquiry, under Sheriff Robert Dickson, found no evidence of poor training or inadequate experience. Dickson noted that in each case there was lack of action on a “growing body of evidence that there was something fundamentally wrong with the patient” and surgeons failed to contemplate their own actions as potentially responsible. He agreed with two professors that it may have been possible to save their lives “had the post-operative care been to the standard which they expected, and had there been a proper management plan which staff could have worked to” and noted that all the patients suffered from a lack of adequate medical notes being available after their surgery. He described the care as having “clear faults”.

NHS Lanarkshire apologised and said improvements had been made regarding “these types of cases” as well as with document management. Wikinews got in touch seeking details of the changes made but the health trust failed to respond.

Thursday, November 19, 2009

In a third case of staggering sums billed for “unlimited” Internet access reported this week, a French emergency-room doctor from Fontainebleau beats all records with a €159,212 (US$237,417) bill. The telephone-number-sized bill covers one month’s use of an unlimited 3G dongle on Orange‘s network; the beleaguered Dr Jean Spadaro has been battling this for six months.

“To begin with I thought it was a joke”, said Spadaro, confirming a story from l’Observateur du Valenciennois; The same newspaper that revealed last week a similar case — Eric Gernez, a café owner in Petite-Forêt near to Valenciennes — who received a bill for €45,000. Christophe Aupy-Fargues, head of an insurance brokerage firm in Saint-Herblain, west of Nantes, and another unlimited 3G dongle user, confirmed to Ouest-France on Monday the blocking of payment on a bill for €39,500 demanded by Orange.

“I subscribed in November 2008 to a basic internet access by 3G dongle at €30 per month […] seeing my bills reach sums going up to €860 in April, I decided in May to subscribe to unlimited access by 3G dongle with Orange business at €50 per month. When I saw my bill for May, I couldn’t believe my eyes: €159,212, for one month’s connection, it’s impossible, especially as we don’t use it all of the time” added Spadaro, the father of two children, aged sixteen and nineteen.

On opening the envelope in June, he expected to read an amount neighbouring the cost of his subscription; but, to his horror, it was €159,212; a demand large enough to make an emergency-room doctor’s head spin.

	When I saw my bill for May, I couldn’t believe my eyes: €159,212, for one month’s connection, it’s impossible

Spadaro claims France Télécom (Orange’s parent company) never explained to him that the “unlimited” package only related to the time spent surfing on the Internet — not the volume of traffic — limited to one Gigabyte per month. The package’s quota corresponds to moderate usage (reception of simple emails for example). As normal Internet users, the members of the Spadaro family surfed Facebook, YouTube, sent emails with attachments, received same, &c. That volume of traffic proved to be costly. €0.17 per Megabyte, or €170 per Gigabyte. Until the bills arrived, the Spadaro family were using the Internet, ignorant of the cost being incurred.

The doctor’s bills, not listed in detail, are €53 for February, €346 for March, €860 for April before soaring to more than €159,000 in May. Spadaro also claims, with evidence of his letters in hand, he had increased the number of protest actions and received, in response, “warnings with threats of seizure”.

Battle-weary after six months of contacting his operator, Spadaro has lost all patience. “Since June, I’ve spent hours writing emails, letters or calling Orange to ask for an explanation. I’ve been passed from call centre to call centre, from customer services to debt collection. No one at Orange was able to give me the slightest clarification. A real wall”, he said. He has never contacted a consumer association, “due to lack of time and also because I trusted the people with whom I was speaking”.

At the end of last week he stumbled upon the article on the Observateur du Valenciennois internet site concerning the case of Eric Gernez. He then also threatened Orange with the press. “The result did not tardy”, he continues. “A customer services representative and a debt collector immediately contacted me by email November 16. And immediately afterwards I received a credit for €136,529”. A first credit having already been sent to him in June, Orange now considers the dossier as “definitively resolved”.

HAVE YOUR SAY
Are mobile phone companies “mercenary” and “deceptive”?
Add or view comments

This resolution does not satisfy Jean Spadaro at all, who simply wishes that the bill be cancelled. “I have been a client with Orange for 17 years. I don’t want to attack their image, but here, enough is enough. It’s a question of principles”, he says, highlighting that “on forums, dozens of subscribers tell similar stories”. Furthermore, the two credits do not reimburse him for all of the additional fees he has incurred. “The following months, Orange tried to debit the sum from my account, causing rejection fees from my bank and unpaid fees from the operator. Around €35 each time”.

Exasperated by the whole affair, Spadaro awaits the end of his current contract with Orange in February next year. “I will cancel all of my subscriptions to Orange: 3G+ dongle, but also mobile telephone and internet”, he promises. He has been a client with the operator since 1997.

	We will work with each client

Orange has promised to work with each case of overbilling. Interviewed on France 2 on Wednesday, Jean-Paul Cottet, director of the business market for France, said that the number of problems were marginal. According to him, 4,000 professionals have opted for a package with a 3G key. It is “a 24/24 but not unlimited offer. Out of these 4,000 cases, there are 1% which are a problem” he explained, listing about thirty such “absurd bills”. “We will correct that”, he promised. “We will work with each client”.

Jean-Paul Cottet pointed out that the general public offers better protection to the client. Once the authorised download limit is reached, the service quality diminishes but there is no overbilling.

Asked about the information given to clients about the conditions of billing elements not included in the package, Elizabeth Alvez, communications representative for the regional department for the North of France, said that “all the tarification information is available at points-of-sale and on orange.fr. This information is given as part of the dialogue between the client and the vendor. We are obliged to communicate the prices.” Nevertheless, one must first of all take the time to read the entire contract with the salesperson before signing.

Saturday, April 17, 2010

Journalist, counselor, painter, and US 2012 Presidential candidate Joe Schriner of Cleveland, Ohio took some time to discuss his campaign with Wikinews in an interview.

Schriner previously ran for president in 2000, 2004, and 2008, but failed to gain much traction in the races. He announced his candidacy for the 2012 race immediately following the 2008 election. Schriner refers to himself as the “Average Joe” candidate, and advocates a pro-life and pro-environmentalist platform. He has been the subject of numerous newspaper articles, and has published public policy papers exploring solutions to American issues.

Wikinews reporter William Saturn? talks with Schriner and discusses his campaign.

Wednesday, March 1, 2006

The Sizzler Restaurant franchise in Australia has closed the salad bars in all of its 29 restaurants across the country, after rat poison was discovered in food at two of the chain’s outlets in Brisbane. Self-serve salad bars at the restaurants have been closed in response to a sabotage scare. Sizzler Australia Managing Director Bo Ryan said customer safety was always the restaurant chain’s first priority.

A media release on the Sizzler website states: “As a precautionary measure and because customer health and safety is our number one priority, we have temporarily closed salad bars in all Sizzler Restaurants. We sincerely apologise for this major inconvenience.”

Police said green pellets were found in pasta sauce at a Sizzler restaurant in Brisbane’s inner-west on January 20. A regular customer at the Toowong restaurant told Sizzler staff she had found something odd in her bolognese pasta sauce. Similar pellets were found in a vegetable soup at Sizzler’s Myer Centre outlet in the city about 5pm on Saturday.

Bo Ryan said the decision to close all of its Australian salad bars was made after laboratory tests confirmed that the substance in the pasta sauce was indeed rat poison. He said trainees who tasted the poisoned soup had been been taken to hospital by ambulance as a precaution, but had suffered no ill effects.

Queensland Police Inspector Bob Hytch said no one had been reported ill as a result of eating the poisoned food and there had been no extortion threats. Sarah Kenny, a university student, said she and two friends had eaten spaghetti bolognese that “tasted really weird”.

“The inconvenience to customers and the economic impact on the company and its 1600 employees will be severe, but as a family restaurant our first priority is the welfare of our diners,” said Bo Ryan. “Steak and seafood and a limited range of salads would continue to be available.” He hopes that customers will understand the action was taken in their best interests, and that “they can be patient while temporary product security procedures are developed and implemented in all restaurants.”

The 29 Australian Sizzler Restaurants, along with 107 Kentucky Fried Chicken outlets are operated by the Collins Foods Group, a wholly owned subsidiary of Worldwide Restaurant Concepts Inc. Mr Ryan said Sizzler was assessing measures which could be taken to prevent a recurrence of the sabotage. “As soon as new measures are introduced, over and above existing strict protocols, we will reassess the situation,” he said.

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)