Wednesday, November 26, 2008

Australian Prime Minister Kevin Rudd has told the House of Representatives that the federal budget may need to fall into “temporary deficit” if the global economic crisis impacts upon Australia further. The Prime Minister said it would draw upon its budget surplus to stimulate growth and jobs.

The Prime Minister said the Australian economy had changed significantly over the past few months and warned that there were hard times to come for many people. Mr Rudd said the situation will worsen before it gets any better.

Mr Rudd said that the government will go into temporary deficit and spend on infrastructure to stimulate growth if required and not to do so would be irresponsible.

“If Australian economic growth slows further because of a further deepening of the global crisis then it follows that Australian Government revenues will reduce further,” he said.

“Under those circumstances, it would be responsible to draw further from the surplus and if necessary to use a temporary deficit to begin investing in future infrastructure needs including hospitals, schools, TAFEs, universities, ports, roads, urban rail and high speed broadband.” He added, “Such action would support growth would support families and jobs and would be undertaken in the national interest.”

If the budget fell into deficit, it would be first time the federal budget has gone into deficit since 2001. Previously, the government has refused to concede the budget would go into deficit, contrary to predictions by economists.

The admission by the government follows claims on the weekend by the Prime Minister that he did not expect the budget would go into deficit “in the current circumstances.” Today Mr Rudd told parliament that the global economic crisis is accelerating.

“The world economy is deteriorating rapidly,” Mr Rudd told parliament.

“The impact of the global financial crisis … has grown from a trickle to a flood. It is now sweeping across the world from China to Chile, from Germany to Japan.”

The government slashed its budget surplus forecast earlier this month by AUD15 billion to $5.1 billion and revised down revenue for the next four years by a further $40 billion. Mr Rudd blamed part of the downgrade to falling commodity prices.

Figures recently released by the OECD predict that Australia will manage to avoid a recession this year; economic growth is predicted to be 1.7%.

Opposition leader Malcolm Turnbull used the Prime Minister’s announcement to attack the Rudd government’s economic credentials. He said any deficit would be regarded by voters to be a failure in economic management.

Mr Turnbull asserted that it is unlikely that any deficit would be temporary. “Experience and history tell us that Labor deficits are never temporary,” he told parliament. “The last Labor deficit lasted for six years. It only came to an end with the election of a coalition government.”

Mr Turnbull said the government had remained focused on inflation for longer than they should have.

“It was the only government in the developed world that was ignoring the global financial crisis…and was declaring its own war on inflation, when much darker storm clouds were on the horizon.”

The Liberal leader took aim at comments made by Finance Minister Lindsay Tanner and Prime Minister Rudd on the weekend that said the budget would not be allowed to fall into deficit.

“Forty-eight hours [later] and that has been completely abandoned,” said Turnbull.

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)

Tuesday, June 12, 2007

North America’s largest outdoor dog festival came back to Toronto last weekend for its fifth year. It ran from the 9th of June to the 10th of June at Toronto’s historical St. Lawrence Market. A Wikinews reporter was there on Sunday to report on some of the events that happened on the last day.

The “Woofstock” dog festival attracted as many as 140,000 people with their dogs. The festival had tons of accessories, sold under tents, to buy for dogs; food, toys, designer clothes, and more. About 400 vendors and exhibitors were there to promote their products, which also gave private dog companies or groups a chance to show their new products. The local SPCA and some animal rescues were under tents answering questions from visitors. While walking, all visitors could see the CN Tower and other very tall buildings.

One of the local TV stations, Citytv, was there. They hosted a live event at the show which was broadcast on TV. People came up on the stage and asked questions regarding their dogs and the host and co-host answered them.

A man, who called himself the “Chalk Master”, drew two pictures on pavement with chalk. He did it for free but donations were welcome. One was a picture of a girl’s head beside a dog’s head, and another with a wolf.

“Hello Humans. I’ve been invited here to provide your eyeball(s), with some pretty colours. I don’t get paid as I work this weekend strictly for tips… so, if you like what you see please make a DONATION. If you don’t like it simply reach into the pocket of the person next to you and give me their money. CHALK MASTER.”

A contest called “Canada’s top dog” had its own tent with a professional photographer taking pictures of dogs behind a white screen; the winning photo is to be published on the cover of “Puppy and dog basics” magazine.

Large “Gourmet” dog bones were also served from a cart and table.

Next year’s festival is expected to be bigger and better with even more attractions.

Monday, June 1, 2009

In a televised speech from the White House at 16:00 UTC today, President of the United States Barack Obama presented a reorganization plan following the 12:00 UTC announcement by General Motors that it had filed for bankruptcy and Chapter 11 protection from its creditors, the largest bankruptcy of a U.S. manufacturing company.

Describing the problem with the company as one that had been “decades in the making,” Obama explained the rationale behind his proposed reorganization plan for General Motors. He stated that his intent was not to “perpetuat[e] the bad business decisions of the past,” and that loaning General Motors money, when debt was its problem, would have been doing exactly that. His plan, he stated, was for the United States government, in conjunction with the governments of Canada and Ontario (which he thanked for their roles alongside the government of Germany which he thanked for its role in selling a corporate stake in GM Europe), to become shareholders in General Motors. The United States government would hold a 60% stake. The government will give GM a capital infusion of US$30 billion in addition to the funds it has already received.

Of the government ownership he stated that he refused “to let General Motors and Chrysler become wards of the state”, and described the bankruptcy of Chrysler, and the bankruptcy of General Motors that he envisioned as being “quick, surgical, bankruptcies”. He pointed to the bankruptcy of Chrysler as an example of what he envision for General Motors, but stated that General Motors was a “more complex company” than Chrysler.

Responding to challenges voiced by political opponents, before the speech, that the federal government would actively participate in the affairs of the restructured company, he stated that he had “no interest” in running GM, and that the federal government would “refrain from exercising its rights” as a corporate shareholder for the most part. In particular, he stated that the federal government would not exercise its rights as a shareholder to dictate “what new type of car to make.” He stated that he expected the restructured GM to make “high quality, safe, and fuel-efficient cars of tomorrow,” and several times described what he anticipated as “better” and “fuel-efficient” cars, after a streamlining of GM’s brands.

He said to the general public that “I will not pretend that the hard times are over.” He described the financial hardship that some — shareholders, communities based around GM plants, GM dealers, and others — would undergo as a “sacrifice for the next generation” on their parts, so that their children could live in “an America that still makes things,” concluding that one day the United States might return to a time when the maxim (a widely-repeated mis-quotation of what Charles Erwin Wilson once testified before the U.S. Senate when nominated for the position of Secretary of Defense) would once more be true that “what is good for General Motors is good for the United States of America.”

Wednesday, December 27, 2006File:Fidel Castro 102006.jpg

José Luis García Sabrido, the chief surgeon at Gregorio Marañón hospital in Madrid who treated 80-year-old Fidel Castro last week, announced that the intestinal bleeding which led to surgery was not caused from cancer. Rather, he had a “benign illness” with a series of complications. He is currently recovering from a serious operation. When asked if Castro had cancer, Sabrido responded, “From what I know, I absolutely deny it.”

Sabrido refuses to declare which caused Castro’s illness, keeping in the Cuban government’s wishes, however The New York Times says diverticulitis is a common, non-cancerous cause of intestinal bleeding.

US politicians still believe that Castro is seriously ill; there is speculation in Washington and among Cuban exiles that Castro has colon cancer. John D. Negroponte, the United States Director of National Intelligence, told The Washington Post that Castro is “terminally ill” and will be dead in “months, not years.”

Fidel Castro transferred his position to his brother Raul on July 31 due to intestinal surgery. The Cuban government has since kept his health situation relatively secret; this is the first time a medical expert outside the Cuban government has commented on his health since he dropped from the public view in July.

According to recent reports, Castro will be healthy enough to be President of Cuba again.

[edit]

[edit]

The time is 20:00 (UTC) on June 30th, 2006, and this is Audio Wikinews News Briefs.

[edit]

Monday, September 24, 2007

Russ Aegard is running for the Green Party of Ontario in the Ontario provincial election, in the Thunder Bay-Atikokan riding. Wikinews’ Nick Moreau interviewed him regarding his values, his experience, and his campaign.

Stay tuned for further interviews; every candidate from every party is eligible, and will be contacted. Expect interviews from Liberals, Progressive Conservatives, New Democratic Party members, Ontario Greens, as well as members from the Family Coalition, Freedom, Communist, Libertarian, and Confederation of Regions parties, as well as independents.