April 20, 2014

LibreOffice, the distraction-free way

There is a growing momentum towards specialized “text editors” these days, and these tools are not meant for “geeks” or “hackers”, far from that: there are targeted at people who write long chunks of texts, and only text. You may have already guessed who they might be: fiction writers, journalists, etc. There is now a nice ecosystem of tools, most of them non free software, like Scrivener, that is in full expansion. If I’d tell you office suites can offer just the same benefits, you would call me biased. And indeed I might be. Just a tad…. But it’s true. On the other hand, people having specific needs in the way they write and edit texts are very real, from developers to fiction writers. The question is: should an office suite like LibreOffice accomodate everyone – and does it already?

I will first show how to turn LibreOffice into a distraction-free text editor -yes you can do that quite easily- and then I will try to answer the question above: should an office suite like LibreOffice accomodate everyone? in an attempt at defining what LibreOffice, and especially Writer, is and does as a tool.

LibreOffice Writer as a distraction-free text editor in a few simple steps:

The whole point of the following suggestions is to take away elements from LibreOffice’s writer interface.

  1. Get rid of the ruler: Go to the View top menu then unselect the Ruler
  2. Take away any unwanted toolbar from the same View menu (then use the Toolbar submenu), such as Drawing or WordArt bars. Don’t get me wrong: you could make every bar disappear but it’s not helpful: just get rid of what you think is clutter.
  3. In the Options menu go to Writer, Appearance, then change the Application background to a shade of dark grey (70 up to 90%). Do not mistake this with the document background, there’s a specific entry for the Writer background.
  4. The last step is  optional: get rid of the Stylist vertical integration. Many people do not have this as a default, I do because it makes me save time when I have to select styles as I’m typing a document. To me, it’s not clutter so I left it that way. Below is a screenshot of LibreOffice in distraction-free mode with the stylist nested on the right, while the second screenshot is the same configuration of LibreOffice without the nested stylist. LibreOffice_distractionfree_stylist

Why do I mention the stylist? Because using styles is pretty much the single most important tool you need to be familiar with when using an office suite. Any office suite, that’s to say, otherwise you will end up wondering why office suites are so complex when you just have to type a letter to your insurance company… although there’s certainly a huge userbase for that.

LibreOffice_distractionfree_enneagon

What do styles do? They structure your document visually and logically. They make the difference between a simple text with bold, underlined and italic words appearing from time to time, and an ordered document with chapters, sections, paragraphs that stands both the test of time (and format conversion) and multiple revisions or updates. They also help you create great looking documents and create templates. In a nutshell, using LibreOffice without styles is like driving a car in first gear or using Emacs only through the scratch buffer (that one’s for the geeks). By the way, the same is true for MS Office styles, but LibreOffice and its predecessor OpenOffice.org are known to handle styles in a consistently more powerful way.

But styles cannot  do everything. They cannot magically turn an office suite into a full development environment or code editor for instance. That would be pushing the enveloppe a bit too far. Which prompts the question of what an office suite like LibreOffice can, could and should do.

It is clear to anyone who used an office suite and code editors or IDEs such as Emacs, Cloud9 (code editor in the cloud) , NetBeans or Eclipse, that LibreOffice serves different needs. There is no will, and no point for anyone to turn LibreOffice into a code editor (aside the macro and dialog editor that’s already embedded in the suite, as shown on the right), because an office suite is not and will never be a development environment. LibreOffice_macroeditor

It is not rare to hear that word processors are a thing of a past, but that’s  an ill-informed opinion. It is not that the cloud is supposedly overthrowing everything, but rather it comes, I think, from several misconceptions and prejudices about office suites. Let me first hint at what word processors are not:

  • code editors: Seriously, some people need to drop that ball. I’m the first one to wish for a full blown html editor that works inside LibreOffice, but certainly not for a full suite with compilers and debuggers. These are specific tools, aimed at a specific range of uses.
  • LaTeX editors: I have good friends who use these – in short, these are powerful tools allowing you to focus on text and then frame and format the text the way you want in a programmatic way. These editors require a lot of practice and learning before you can use them. LaTex editors are used mostly in academic fields. They are not word processors, and to be honest, the notion that you must spend years of training to design a document in LaTex even in 2014 strikes me as nonsensical.
  • wordpads, simple text editors: a word processor can definitely do that, but you could of course use  something less complex, if all you need is a simple text editor such as TextEdit or WordPad.
  • online pads; if you were to implement a collaborative stack in an office suite, it could actually be turned into an etherpad/framapad type of tool, although the value of a word processor may lie elsewhere.

At this stage then, it becomes useful to try to define what a word processor does and why it matters.

A word processor edits and handles documents . Not code, not notes (although it could), only actual documents. Faced with this shockingly simple yet – in my humble opnion powerful – assertion, what do we do with it?

Word processors help you read, edit, save, open documents in a very fast and relatively easy way compared to everything else. Documents are not only made up of words and sentences. They come with a structural logic, specific formating, styles, layouts and graphical elements. While it may appeal to one of the broadest audience on the earth (people who have access to a computer and would like to write a document, such as a letter or a book or a shopping list) it does not mean that word processors or office suites are made for everyone else except developers, engineers and fiction writers. It means word processors excel at editing documents in a powerful way without much of training (compared to a full fledged academic or technical cursus in learning vi, emacs, LaTex editors…) and this uncanny ability  does not really exist among any other tool out there. Sure, if you spend four years editing a document in LaTex, you will likely learn enough to make your PhD. thesis look good. Sure, there’s a customized major mode in Emacs enabling some proper visual document to be edited, but you need to know and learn about it beforehand, customize it some more, get acquainted with the custom shortcuts, etc.

I’m not berating these tools: I’m a regular and devout Emacs user myself. But I do love the comfort and smoothness of firing up LibreOffice Writer and write that nice memo or strategic overview for the Document Foundation just by pointing on the stylist, clicking, expressing my thoughts through the text I’m wirting, changing the fonts, run the spell checker, saving the document, closing it. Tomorrow, when I’ll open it, it will look just as good, and I might even make it look crisper for the benefits of my readers. How long will it take me? A couple of minutes. Ten, if I’m in the mood of changing everything. It cannot get any easier than that. Office suites, and especially word processors are powerful tools. They help create and develop one’s intelligence, and by sharing documents enhance the collective intelligence of groups and crowds. They are meant to be what the LibreOffice project strives to provide: engines of creation, tools for intelligence.

April 13, 2014

Brendan Eich, the bigots, and Software Freedom

Last week we learnt the news of the resignation of Brendan Eich from his position as CEO of the Mozilla Foundation/ Corporation. The controversy on Brendan Eich’s donations to opponents and campaigns against same-sex marriage ultimately prompted the inventor of Javascript to resign from the position he had just been appointed to and leave Mozilla. I followed the reactions online and decided to wait for at least a week before writing my opinion in full. Am I reopening a can of worms? Perhaps, but I think what’s at stake here is people missing an important aspect of software freedom. In this sense, this post won’t be about marriage equality or civil rights in general, it will be about the freedoms conveyed by free software and what they can ultimately mean.

For starters, let me remind you of several things:

No system is perfect…. And while Free Software is made of a set of legal norms, a philosophy, a political movement, and a way to produce and expand digital commons, Free Software in itself is something that constantly evolves. Sometimes people make mistakes. Technology changes. Licence evolve. Etc. A perfect system is a fantasy and does not exist in reality.

I have gay friends… And they’re not of the alibi-type of friends. They’re actual friends, buddies, people I have drinks with, people I meet and engage in discussions, people who tell me about their relationships, their work, their lives.

I have heterosexual and socially conservative friends… And they’re not of the alibi-type of friends. They’re actual friends, buddies, people I have drinks with, people I meet and engage in discussions, people who tell me about their relationships, their work, their lives.

When the controversy about Brendan Eich’s views and activism against gay marriage spread in the news, I thought that certainly this would not go much further than people shouting on blogs. I was wrong. While I do support gay marriage, I did not think for a moment that being a CEO of Mozilla meant that your personal views on politics and society would be judged. Everyone has political views and it is, after all, customary everywhere not to voice these opinions, nor to value them, at the workplace. Of course, I have written here and elsewhere that software freedom is political; surely then the board and the CEO of Mozilla must have some political commitment about digital rights and software freedom deeply rooted in their hearts and minds. I am pretty sure Brendan Eich is no different; but aside this, people are different. They have different stories, different ideas, different political views and different sexual orientations.  Free and Open Source Software projects gather and welcome all kinds of people. In fact, the four freedoms at the core of Free Software licenses are explicit on the notion that Free Software is made available for anyone to use, study, modify and distribute as long as the software license is respected. I’m not making that up, the statement is on the Free Software Philosophy page of the FSF web site:

The freedom to run the program means the freedom for any kind of person or organization to use it on any kind of computer system, for any kind of overall job and purpose, without being required to communicate about it with the developer or any other specific entity. In this freedom, it is the user’s purpose that matters, not the developer’s purpose; you as a user are free to run the program for your purposes, and if you distribute it to someone else, she is then free to run it for her purposes, but you are not entitled to impose your purposes on her.

By now you may be wondering where I’m going with this. The point I feel very few people made in the controversy surrouding Brendan Eich is that Free Software does not care who you are voting for as an individual or even as an organization. What matters is respecting the license the software you are studying, using, modifyng and distributing, and to a broader extent, that the development community you are contributing to -if that is the case- is not deprived from its freedom. Now let’s take a few real, yet general cases of Free Software usage around the globe.

  • Free Software such as Linux or Firefox, or LibreOffice (or BIND, or TCP/IP, etc.) is used by corporations actively engaging into child slavery
  • Free Software (again, same example) is used by the U.S. Government for various needs, some of them being of the military and data collection kind. This statement is public knowledge of course. There are some parts of this world where the U.S. Government is not hold in high regard by some peoples and / or their government
  •  Some people from extremist parties around the world use Firefox and LibreOffice
  • Some opponents of same-sex marriage, in the US  and elsewhere, are using Firefox, Thunderbird, LibreOffice, Evolution, Linux, etc.
  • Some proponents of same-sex marriage use the same software.

Where does that take us? For one thing it is abundantly clear that anyone can use and uses Free Software on a daily basis. Even people who you may not agree with on political or social  ideas. Even people you think should be publicly blamed for their ideas or their actions. Back to Brendan Eich. It is easy to point out that he is or was not just a mere user, but was appointed CEO of Mozilla. Before that, for the record, Brendan Eich was the CTO of Mozilla and the inventor of Javascript. Some people demanded his resignation on the basis of his political ideas and asserted that such ideas ought to be banned from Mozilla. Somehow the moral demand made to Mozilla is more important than the one made to other entities. I do not buy that, at least not when it does not concern software freedom and digital rights. Besides that, Brendan Eich as a CEO would not be Mozilla himself. Mozilla is fortunately much bigger than Brendan. The fact that someone denies equal rights to others may make some people uncomfortable. Some others would find such a position outrageous. But Mozilla is not changing because of the political colours of its CEO. Heck, it’s not even voting.

In this regard, I’m afraid I have bad news for all the people who thought Brendan Eich was unfit to be CEO of Mozilla: I know for a fact that there is one contributor of a major Free Software project who is an extreme right activist. He was seen by a friend per chance in an extreme right demonstration, as this friend was crossing a street in Paris. I know for a fact that projects such as LibreOffice have people who have, let’s put it that way, a rather traditional vision of marriage. I know for a fact that there are people who are actively campaigning in favour of gay marriage all around the world and who are active contributors to LibreOffice as well. And I could go on and on.

If you want to deny leadership positions to people who may have completely different views on marriage, gender and race equality inside Free Software projects or foundations, be ready for a witch-hunt. And then ask yourself the question of whether the same people should be expelled from the project. Then the next thing you should consider would be to only accept people who have been individually cleared from any dubious ideas into your project. You may not want to stop there: get new software licenses prohibiting Free Software to be used by certain kind of people. Someone tried this before and the FSF rejected it, by the way, as it was a blatant denial of software freedom. On top of this, you may want to impose a worldwide censorship and surveillance of the network just to make sure people who may have unacceptable ideas never get around to contact your project. What a fine world this would be, wouldn’t it?

Yes, even people who are outrageous bigots and blatant racists have a right to join, participate and use Free Software. We may not love everyone, but we do work with everyone and serve all of them. Free Software is not a party, it is a much bigger and broader movement encompassing technology, society, law, software and hardware, and ultimately some of our most human qualities: empathy, communication, cooperation, and sharing.  The day this will change, software freedom will die – and the true freedom haters, the censors, the real bigots, the extremists will have won.

Caveat Emptor: This post reflects my personal opinion only and not the views of the Document Foundation nor my employers, past and present.

April 04, 2014

Keeping a promise made a long time ago

Some time around 2009 or 2010, the OpenDocument community realized that while it had won the moral battle over Microsoft and its dubious OOXML standard, it had lost the adoption and ecosystems war.
Microsoft Office had been released and with it an undocument format called OOXML which, as far as experts were concerned, had little to do with the ISO 29500 (aka OOXML) standard. While Europe and Brazil were struggling to migrate their public sector’s documents to ODF, any company or government, let alone any individual acquiring Microsoft Office 2010 migrated to the new and shiny OOXML, officially without remorse or complaint. The ODF advocacy groups here and there were launching all sorts of events and meetings to guide and assist migrations to ODF. Results were mixed. We had victories. We had defeats. At the end of the day what was at stake was fear of failure and change from CIOs and IT services. That’s still the case today. But while these are mostly human factors, there is one thing we hadn’t tried yet, or at least hadn’t been tried enough: turning the hundreds of thousands of files that are out there and locked up in various proprietary file formats to ODF documents.Docliberation

This week the Document Foundation announced its second major project, the Document Liberation. Its aims is to pool and collect every file format filters we have and that people are willing to contribute and develop them so that they not only keep improving but are distributed in the largest number of applications. The aim of the Document Liberation is thus simple: to enable everyone to own its content and to bring a solution to vendor lock-in and undocumented file formats. In doing so, the project is keeping a promise made a long time ago, specifially by ODF. But ODF is a format itself, and while it is enjoying a pretty widespread adoption, it has not done what Microsoft did with OOXML: propose a smooth transition through a change people can accept. In the case of OOXML, as lousy as it seems, people accepted the change because they didn’t know better: Microsoft does this for a reason, so things will pan out all right in the end. They’re taking care of my documents. The industry will follow.

In the case of ODF, no one was in such a position, except perhaps Microsoft. The approach we’re taking today is to offer a solution to a very real problem millions of people have: they don’t know what to do with their files if they haven’t migrated them to a more modern, but not necessarily more standard or more open file format. To these users, we offer a range of choices depending on their “predicament”. We will add more filters as time goes by and the community grows. To developers we offer an exciting place to contribute code by improving existing format filters and proposing new ones. To everyone we offer code that will ensure the continuity of access to content locked in countless files scattered across the Internet, personal computers, corporate, academic and governmental archives. In doing so we not only help ODF keep its promise to liberate documents once and for all, we help make the world a better place by empowering everyone to access and create more digital knowledge and unleash creativity. This promise lies at the core of the Document Foundation’s mission.

March 30, 2014

Eyes and Ears

Welcome to this month’s Eyes and Ears issue on the Moved by Freedom Powered by Standards blog!  Today we have a set of electronic tracks that are issued mostly by one artist, “Dreamium”, aka Sam Z. from the US. I’ve discovered this artist and also found out he does not just mix and compose electronic tracks, as he’s a guitarist and a pretty good one too.

The last track is from Laurent Garnier and is called the Man with the Red Face. This is almost a classic but  at the same time it does not sound as minimalistic as his other productions. Enjoy!

 

March 28, 2014

我的老娘(八):我佛慈悲 普度众生

八、我佛慈悲普度众生

 

  天台县很不发达,所以也透着淳朴。入山的门票是10元,另外国清寺的门票由庙里的和尚自己收取,每人5元。据说,县里为了抓经济,曾经要把入山的门票提高到50元,国清寺的方丈不干了,说:寺庙是普度众生的场所,不是挣钱的地方。如果入山门票提高,他就关闭国清寺,并且说到做到。后来,政府官员们拗不过方丈,只好一直维持现状。听这么一说,我对国清寺的方丈充满了敬意:原来还是有真正的佛家子弟的。

  国清寺的朴素更是让人动容。天台山入口处的一大片田地就是寺田,由和尚们自耕自种,当然也雇了些农民。这时正值水稻收获季节,寺里的空地上就正晒着谷子。寺里装修是最典型的低调、奢华有内涵,寺里的方丈、和尚都守着清规,不像五台山到处都是宰客的和尚和庙宇。老娘慢慢的逛,多多娘则是在细细阅读这个隋代名刹的历史。在这个寺庙里,真正的让人体会到了佛家的庄重。

  老娘有自己拜佛的规矩,我们静静地跟在她的后边。从三贤殿出来后,老娘带着点忧伤,幽幽地看着远方:“我给你爸念了那么多的超生经,按理他应该早就投生了,我就是到了那边,还是见不到他。”

  我的鼻子一酸,知道老娘十三年来对老爸的挂念,却也无法真正体会个中的深情和无奈。更何况我早已被唯物主义洗脑,既不知有前世,也无法去信有来生,一时无法接话。内心中只是强烈的感受到,原来我们这一辈子所遇到的所有人和事,都只是一辈子的事……

  我突然间对自己过去被所谓的唯物主义的洗脑教育充满了痛恨:我们真能那么强大吗?可以藐视天、藐视地、藐视世间的一切神佛?藐视世间的因果福报和轮回?我们没有前世、我们没有来生,我们从虚无中来,最后又到虚无中去?

  我以为我自己比老娘懂得多,我以为自己比老娘更加强大。我在这半年中所做的一切,都想把自己的老娘给挽留住。在这一刻,让我放下孤傲,让我知道,这世上有许多我所不知道的事,有许多我根本做不到的事。我应该没有能力挽留住老娘,但我可以护送好自己的老娘,让她在这一世里了无牵挂,让她可以去她自己想去的地方。也许她能找到我的老爸,也许她能在另一个世界里看护着我们,也许来生我还可以是她的儿子……

  多多有点嘻嘻哈哈,并且不合时宜的说了句不敬的话。爸爸急了,严肃地对多多说:“多多,哪怕你有再高的能耐,再好的主义,都不要和佛法争高低,更不要试图和佛祖比肩!”多多有悟性,听爸爸一说,翻身就到三贤殿里恭恭敬敬的跪下来,磕了三个响头。爸爸心里充满了欣慰:我不会要求多多去信仰什么,但一定要多多学会敬畏。

 


  我以前虽然不会明着嘲笑老娘,但有时却真的会对老娘的许多想法有所不屑。记得十几年前,我第一次坐过飞机后,老娘就小心翼翼地向我打听,问我在飞机上有没有看到神仙以及空中亭台楼阁。老娘第一次坐飞机时,自己不停地四处张望,然后失望的看着我。我不忍心看她失望,就告诉她,也许神仙住在比这还高得多的地方,我们人类还不能到达。在爸爸去世后,老娘总是不死心,总希望还能和老爸再聚首。还好,我还保留一点对无知领域的敬畏之心,总是会给老娘保留一点遐想的空间。如今,我也需要了。看着自己深深眷恋着的老娘就在一步一步离我而去,让我如何忍心啊。所谓的科学,又在清楚地告诉我,我对老娘的病根本上是无能为力,我又怎么心甘啊!

  天台山国清寺一游,了却了老娘隐藏在心中多年的奢望,老娘的满足感溢于言表。老娘所不知道的是,她所寄望的来世也让她的儿子从苦苦强求的备受煎熬的痛楚中解脱了出来。也许我们真有来世,也许真的没有,但无论如何我从这一天开始,护送好自己的老娘。




  未完待续~~


 青春就应该这样绽放  游戏测试:三国时期谁是你最好的兄弟!!  你不得不信的星座秘密

March 27, 2014

我的老娘(七):清澈的溪水,洗去一身的疲累

七、清澈的溪水,洗去一身的疲累

 

  自从老娘生病后,我晚上的应酬就开始降了下来,一下班总是想早点回家多陪老娘聊聊。

  陪老娘瞎聊是我们母子俩非常愉快的一件事。我从小爱黏着娘,小时爱听她给我讲故事。在我们小时,还没有电视。老娘虽然不识字,但她会讲许多评书里的故事,比如杨家将、薛家将、岳母刺字等故事,她一气可以讲很多。我现在的价值观基本上就是老娘通过这些故事传给我们这些孩子的。小时候,我、妹妹还有几个小伙伴经常会围着她,老娘便会边织着篾席边给我们讲故事。甚至在我上大学暑假回家时,我也会躺在她正织着的篾席里,和她一起研究评书里的故事;只是那时候,我已经具备帮她丰富评书故事的能力了。当然,更多的时候就是瞎聊。

  老娘在北京的十年,真是让我体会到了家有一老,胜过一宝的含义。十年里老娘包揽了家务活,把多多喂养的高大健壮。于我老娘而言,那也是幸福的十年。让她遗憾的事,自然也有一些,比如,这十年,她原来的村里的老伙伴已渐渐地去了不少。所以,有时,她也会跟我提起那些我也认识的老人。一天,她提起了经发阿婆的一个壮举,一个目不识丁只会东阳话的女人,口袋里就揣着几毛钱,就自个儿去了天台山一次。一开始大家都以为出事了,五天后她回家了大家才知道她去天台山拜佛回来了。话语间,颇有艳羡的意思。我突然间想起来了,在江浙一带,到天台山、到普陀山拜佛是我老娘那一辈人最大的心愿。

于是我就问,我们国庆节到天台山去玩行不行。老娘眼睛一亮,神色一下子振作了起来,但瞬即又被怕自个给子女添麻烦的想法给压抑住了,马上又说算了。我看准了老娘想去,就告诉她我们正在为国庆节到哪去发愁呢,只要她愿意,我们就一起去。

  我赶紧上网了解情况,并跟妹妹联系,多多娘全力支持。大家设计了一条路线,我们从北京飞到宁波,租个车,先游天台,然后游普陀。老娘听说还有普陀山,可以拜观音,这下真的高兴了`,直说真没想过这辈子还能游天台山和普陀山。她儿子这下牛了,拍着胸脯说:这有啥,我马上订机票!

  错过10月1日的高峰,我们订了2日一大早的飞机到宁波,和妹妹约好了到奉化溪口老蒋故居会合。现在的交通方便,等我们到溪口时,也只有中午十一点半左右。只是如今,大家的生活水平高了,到了节假日,只要是有名堂的风景区都是人山人海。老娘看老蒋的故居,自然也是新鲜,只是最难得的是门前的九曲剡溪,溪水清澈见底。老娘见了,心里痒痒的,又见到有人就在水中的石板上浆洗衣服,就脱了鞋,轻轻地踩进了水里。多多爸爸开始鼓捣多多和开开,想让她们也一起到水里去感受一下大自然的恩宠。

  多多却不舒服了起来,觉得不环保(爸爸感觉应该是多多自己不愿意),大声嚷嚷起来:“不行了,奶奶,你一踩进去,这个溪水就变成了洗脚水了!”

  多多的这个理由,让大家觉得匪夷所思,至少是思维过于独特。老娘坐到了水中的青石板上,悠悠的掬水洗脸,直说有十几年没有见过这么清澈的溪水了;脸上写满了惬意。


 

  开开受到鼓舞,也脱了鞋,踩进了水里。多多娘怕水太凉,怕老太太着凉,就催促我叫老娘上来。我见状就赶紧自己踩进水里去试,感觉水温正合适,虽不温暖,但也不凉。就开始和老娘、开开一道继续想说服多多下水。谁知多多嘟囔着嘴,蹦出了一句石破天惊的话:“哼,我可是大城市里来的姑娘!”

  这话太伤人了,在场的一家子其余的六个人都被气笑了。多多爸嘻笑着帮多多分析:“多多,你说的对,咱这一大家子就你一个是大城市的姑娘。咱奶奶一辈子都是农民,你爸、你妈、小姑、小姑父虽然现在算是城里人,但也都是农民出身。就一个开开是个城里人吧,她也只是东阳这个小城市里的姑娘!看来,您这个大城市的姑娘是无法消受这个清澈的溪水了。”

  老娘乐呵呵的,更是戏起了水,开始挑逗多多。我看着老娘的享受,一瞬间明白了过来:我一直会被自己的朋友们誉为疯疯癫癫,原来我的浪漫主义色彩都是我娘遗传给我的。

  约莫过了近半小时,老娘才依依不舍的离开了溪水。多多依然嘟着嘴,一幅爱生气的模样。

  从溪口出来后,一家子两辆车就直奔天台县去了。到了预订的酒店,觉得不太理想。店主很通情达理,说反正也不愁客人,若我们不愿意,可以退。只是来时经过天台城区,感觉比我们东阳落后二十年,想想也就认了。只是需要我和老娘睡同一张床,多多娘逗趣说我又可以喝老娘的奶了。

  国庆节出游的第一天,那九曲剡溪的溪水洗去了老娘的疲累,也让我们情绪都高涨了起来。

    未完待续~~
 青春就应该这样绽放  游戏测试:三国时期谁是你最好的兄弟!!  你不得不信的星座秘密

March 26, 2014

我的老娘(六):化疗之苦

六、化疗之苦

 

  老娘最急迫的两个病灶都已得到了处理,现在摆在我们面前的就是要不要给老娘做化疗。支大夫的建议可以做,刘大夫的建议也是可以做并且应该做。我还是犹豫不决。正好7月6日我在杭州有一个会议,就决定回老家咨询一个同学大夫的意见,我的要求就是要她以我同学的身份带着专业知识给我建议,而不是大夫身份。她的建议比较明确,化疗对病人的生存期并没有明显的延长作用,而且我老娘年纪也大了,建议不做。

  我和哥哥、妹妹、妹夫商量了,大家基本认可不做化疗,采取保守的方式来做后续治疗。哥哥陪着我一起到了舅舅家里,大舅三舅和小舅都在,他们都很当心老娘的身体状况。听我介绍老娘的治疗情况后都觉得还行,对我们兄弟姐妹四个的孝心也表示很满意。

  老娘的胃口开始有所好转。只是姐姐刚做奶奶不久,家里的孩子也需要人照顾。等到妹妹放假后,妹妹带着开开来北京伺候老娘。

  在给老娘做了复检后,老娘的癌胚抗原指标还在升。刘大夫再次建议尝试一次化疗,说如果老人无法耐受,可以随时终止。原本坚决不做化疗的我,还是产生了动摇,和妹妹面面相觑,犹疑着问:“要不先试一次?”生怕错过了哪怕是万分之一的机会啊!在最后时刻,我还是决定采用刘大夫的方案进行化疗。

  我用自己的切身经历去说服老娘。当年我得结肠癌时,老娘是全程伺候,包括手术和六个疗程的化疗。我的化疗中间跨一个春节,持续了半年,所以这样的切身说法还是有点效果。老娘勉勉强强接受了。

  现在看来,也是我自己贪心,一次性采取了较强的周期,尤其是加了恩度药,一个疗程变成了输液十五天。头两天,老娘的反应并不强烈,渐渐的她的胃口越来越坏,老娘也开始有了怨言。渐渐地老娘的手上的静脉也越来越脆弱,护士扎针也越来越难找地方。我只好拿出我自己红润的手跟老娘比划:当年我的手也被化疗摧残的青紫脆弱,如今不是也恢复的完好如初了。老娘能记起十几年前我化疗的惨样,所以也能咬着牙坚持。只是到了第十二天,护士无法下手扎针了。大夫来找我商量,看看能否在静脉里埋个软针。

  我理解错了,以为就是向我当年在医院那样,在我肩膀静脉处埋个软管,也就同意了。后来据妹妹说,我走后,医生把家属支开,在胳膊肘弯下方处割了小口,那软管一直埋到肩膀附近,所以也流了很多血。这次事件对老娘有点刺激,老娘坚决反对再输液,在勉强把这个疗程输完后,就宣称坚决不再进医院了。医生埋的这个软管,本来可以使用一年的,后来在出院时,顺着老娘的意思,还是给拆了。

  从效果看,这次化疗不仅让老娘身体更虚弱了,而且让她对进一步的治疗有了很强的抗拒心理。

  化疗不能再做了,妹妹在我家里每天商量着给老娘做饭,身体元气也开始恢复。老娘除了人参皂苷和灵芝孢子粉外,再也没有用药,这样也实在不行。我就开始给她找中医。在老娘查出问题不久,我就找东直门中医院看过,并且给她开了半个月的中药,因老娘觉得药太苦,吃着没效果就停了。这次就找了广安门中医院的专家帮开了半个月的药,开始自己煎着吃。

  学校要开学了,妹妹只好回东阳。从4月开始,一直有哥嫂、姐姐和妹妹轮流着来照顾老娘,我和多多娘间或也能支应一下,老娘的身体也逐渐恢复了,她又要开始干活了。多多娘就催着我找了个保姆。但这保姆只能来下午不到半天的时间,一时也只能凑合。

  老娘渐渐地对中药也开始反感了,总觉得吃了中药占了她的胃,让她吃不下饭。我无奈也只好随她。断了中药后,老娘吃的果然多了些,脸色开始红润了起来,头发也开始长了出来。老娘的心情也渐渐地好了起来。

  只是连中药也不吃,就等于束手无策。无法可想,最是受煎熬。有时看着老娘开始有说有笑,自己却清楚病情并没有缓解,总感觉到自己是那么的无助,内心深处充满了挫败感。按月去航空医院给老娘开防骨转移的针时,刘大夫感觉到了我的挫败感,正色对我说:“胡先生,你千万不要觉得你做错了什么。事实上,在给你老娘治病的过程,你的每步决策都是对的。你看看,你给她脑部放疗了,解决了她最大的危险;你给她做了射频消融技术,摘了肿瘤的司令部;你给她试了下化疗,你娘不能耐受,你就给她终止了。你是典型的工程师,按部就班的给你娘治病。在我看来,你每步都选择了最正确的方法。我们在给病人治病时,最怕的就是家属或病人觉得自己每步都错了。你千万不要有任何自责的心理。”她顿了顿,继续说:“我刚刚在内部刊物里写了篇姑息疗法的文章,说的就是像你娘这样的病人,哪出问题治哪,也是一种积极的疗法;否则你随她的意也是一种方法。”

   未完待续~~

 


 青春就应该这样绽放  游戏测试:三国时期谁是你最好的兄弟!!  你不得不信的星座秘密

March 22, 2014

Freshly Stable

With the release of our new LibreOffice 4.2 version and the new website, people have noticed a small yet quite visual change in the way we label the versions of LibreOffice. You now have the choice between downloading LibreOffice “Fresh” or “Stable”. Of course the version numbers do not go away, however it is expected that the first  information anyone might receive about downloding LibreOffice would be these two tags, Capture du 2014-03-22 12:43:51and not numbers. Let me explain a little bit what we are trying to achieve here, as this is at this stage somewhat of an experiment.

LibreOffice release model works according to a time-based scheme and relies on two distinct production branches. This means that we do release versions that are stable and ready for use by anyone based on a pace and a set of dates that have been agreed upon and planned beforehand. By looking at the diagram on the release plan, one will also notice that these two production branches are both stable, but stand at a different stage of their lifecycle. One of these branches has seen her first stable release (4.x.0) some time ago and has seen several updates and patches. This version is now, say, in its fifth iteration (4.0.4) and is thus very stable, very patched and will see almost no changes anymore. In a Microsoft world we would call this “Service Packs”. Around the same time, a new branch has been open, but it is not a development branch, an unstable branch for development: each of the two branches has its daily testing versions, its pre-releases such as betas and release candidates. These two branches are stable no matter what. But let’s go back to the new branch. It will be released roughly around the same time that the older branch reaches its fourth or fifth iteration, and the first version of its new branch will have a .0 at its third decimal. It will then take one the same lifecycle that the older branch, until it reaches its sixth or seventh iteration at the latest. Then this branch will be entirely discontinued in favour of its successor, and so on.

Confused by the version numbers? We thought so too. This is how the idea of introducing names that would label the two distinct branches came up. Mind you: this is not about the newest release as some people thought at first. It is about drawing the line between the two current branches of the LibreOffice production. We thus  picked “Fresh” and “Stable”. it is not entirely clear whether these are the best terms, but we feel they’re working well so far in that they’re conveying complex concepts with simple terms. These also help us avoid rather long and difficult discussions with people who tend to think that we need to release one stable version when it’s ready (what used to happen and not work too well with OpenOffice.org) and people who think that the new branch was a “dangerous” “development” branch only made for people living precariously on the edge. Nothing of that was and is  true; if one wants to try really unstable versions our development builds, and to a lesser extent the betas are here for that. But it is  true that the new branch introduces the new features, while the older one receives rather corrective bugfixes.

In the end, we hope this new naming scheme will bring clarity while combining freshness and stability for the benefit of all. Let me know what you think!

March 21, 2014

我的老娘(五):第一次住院

五、第一次住院

 

  到宣武医院住院是真正的一个大坎。6月14日周五去医院前,先在我单位附近的宏状元里吃午饭,点的皮蛋瘦肉粥很和老娘胃口,一次吃了两小碗,老娘直说是近来吃到的最好吃的东西。我和哥看着老娘吃的高兴,自然心里高兴。只是到宣武医院办理住院手术却遇到了麻烦,我原本答应老娘晚上还是带她回家住的。但宣武医院管理严格,服务也周到,他们专门为每个病人派了一个护工(几个病人共用),不允许病人晚上回家住。这下没辙了,老娘人生第一次住在医院里,而且没有家人陪护。我和哥两个陪老娘陪到下午六点,医院就不让家属陪着了。这一晚,我实在是放心不下。

  第二天上午过去,老娘过的还行才略微放心一点。医院的饭菜自然不合老娘的胃口,想着昨天老娘喜欢宏状元的皮蛋瘦肉粥,我就去附近的宏状元点买了一份带过来。老娘尝了一口就放下了:太咸了!我尝了尝,果然有点咸,就赶回店里要求退换。店里经理自己尝了一下,也觉得咸。就给我重新做了一份。这次我小心了,自己先尝,还是咸。值班经理态度还行,就跟我商量,用一份白粥来兑一下。我同意了,带回来给老娘。老娘尝了一口,把勺子放下了:味道不对,没昨天的好吃。

  在我的印象中,这是老娘人生中第一次对吃的这么挑剔,知道她正受治疗之苦。就跟她商量,我是不是再回去换。这下老娘觉得太麻烦了,就坚决不同意,端起饭盒勉强吃了几口说自己也就吃这几口。

  看老娘勉强吃着,自己也是没办法。就打开手机地图查找附近的美食,看到宣武门地铁旁有面爱面。晚上就早早带老娘过去吃了,这次老娘对面爱面的招牌面非常喜欢,加上饿,吃了不少,那感觉就像是饿了几顿终于吃到好吃的样子。

  周日带着多多一起到医院看奶奶。多多在病房里看着奶奶穿着病服,眼圈开始发红,我怕多多哭,就赶紧把iPad给多多递过去。我不信邪,想再试试老娘的口味,看是不是因为别的原因。中午就又带老娘到宏状元店吃,老娘依然对上次皮蛋瘦肉粥赞不绝口,对新煮的吃了一口就咬定味道不对。看来,真的是治疗过程把老娘的胃口毁了。下午,怕老娘无聊,就带着一家子陪老娘逛陶然亭公园。正逛着,护士急了,给我打电话催我们回去。而我只想给老娘营造一种轻松的氛围。

  周一,我忙就没过去。哥哥一大早到医院陪,侄女两口子中午过去陪。老娘依然没有找到合胃口的饭菜。下午多多娘过去,就又带老娘到面爱面去,结果老娘对上次觉得好吃的面一点胃口都没了。多多娘就绞尽脑汁地给老娘点了红豆沙,这个符合老娘口味,老娘吃着高兴。

  18日周二,胡牧大夫给老娘做射频消融手术。从结果看应该很成功,老娘也没受什么苦,因为只是背部的微创,所以行动上都不受限。我就按多多娘的经验,给老娘买回了她昨天爱吃的红豆沙,结果这次老娘又是只尝了一口就放下了。

  这次手术很顺利,观察了一晚,医院就通知出院了。哥和嫂子服侍老娘一个多月后,姐姐来京替班。

  未完待续~~

 


 青春就应该这样绽放  游戏测试:三国时期谁是你最好的兄弟!!  你不得不信的星座秘密

March 20, 2014

我的老娘(四):端午节 雨中游北戴河

四、端午节  雨中游北戴河

 

  这期间,老娘肺部的活检结果出来了,不适合靶向药物治疗。这对我的打击很大,真的开始怨恨老天的不公。就在我对老娘的下一步治疗方案束手无措的时候,同学李晖帮我联系到了宣武医院的支修益大夫。支大夫看了老娘的病历后,说可以采用射频消融技术来处理老娘的肺部肿瘤,好的情况下病人可以存活两三年。支大夫的话重新燃起了我的希望。

  老娘放疗结束后,就想安排老娘歇息几天,眼看着端午节要到了,就和支大夫约好了端午节后去宣武医院住院。

  胡老妈粽子在圈里已小有名气,老娘歇了几天,觉着自己力气还行,就又开始惦记是否要给我公司的同事们裹粽子。我跟周顺民一说,他坚决不同意,怕老人累着,后来想了一个主意,说反正我们端午节要出去搞团体培训,可以在培训那天举办裹粽子比赛,让老娘去教大家裹粽子。这样的安排让老娘也有点高兴,只是比赛过程让老娘颇为遗憾:认真裹粽子的没几个,关键是浪费了粮食让老人很心疼。只是总是大家的一番好意,高兴还是高兴。

  老娘的情绪好点,觉得哥嫂在北京干陪着有点过意不去。我就逗娘,要不要带哥嫂到北戴河去玩?老娘身体上自我感觉还行,觉着哥嫂没去过海边,就着兴致答应了。多多娘嘱咐我要注意老娘的身体也同意放行了。6月11日我带着老娘、多多和哥嫂就开着红车去北戴河游玩。

  天空依然不作美,北戴河下着毛毛细雨。多多就是喜欢大海,虽然雨中天冷无法下海,只是能在海边转转也是高兴。




  第二天天晴了,到北戴河我都会去滑沙场,为的是可以滑沙也可以下海。对老娘而言,这是第四次到北戴河,第一次来时,多多正在多多娘的肚子里;第二次是多多娘带着多多、慧慧和老娘一起的;第三次是2010年,我带着一车子九个人的自驾游。那次老娘圆了一个八年的心愿:老娘第一次到北戴河时,人家嫌她年老,不让滑沙。老娘甚是不服,觉着自己身体很好,凭啥不让她滑。第三次那次,老娘在儿子、女婿以及孙子孙女的保证下,说服工作人员放行,自己滑了一次,甚是满意。这次,我不敢让老娘去滑沙了,老娘虽不服也同意了。于是我带着多多和哥嫂去滑沙,结果嫂子连吊车都不敢坐,让老娘很是不屑,觉得还不如让她再去滑一次。我自然不敢。

  海水虽然还是比较凉,但到了海边不下海,那不是多多的风格,可多多下了海,爸爸只在岸上喊也不是爸爸的风格。多多爸只好打起精神强入海,老娘吹着海风,看着多多玩得高兴,她也自然高兴。



  北戴河游至少在很大程度上冲淡了老娘作为病人的压抑心情,为老娘的下一步治疗提升了情绪。

 

     未完待续~~


 青春就应该这样绽放  游戏测试:三国时期谁是你最好的兄弟!!  你不得不信的星座秘密

March 19, 2014

我的老娘(三):五一团聚 脑部放疗

三、五一团聚  脑部放疗

 

  4月25日,我挂了航空医院刘寅主任大夫的号。我还是抱着一线希望,又重新回顾起老娘的病情。刘大夫也是强调必须先做放疗,说脑部的瘤是个炸弹,必须先排除。我还是忍不住问,到底有多严重,到底有多快。刘大夫看着我:“你应该是学理科的吧,肿瘤的发展就是N次幂方的速度,你应该能够理解。”这一瞬间,我再也忍不住了,多日压抑在心中的痛楚爆发了出来;我哇地一声就放肆地大哭了起来,眼泪也是哗地留个不止。哭出一声后,自己也觉得不是很好,就用手紧紧捂住嘴巴,只任眼泪继续流。在那一瞬间,我恨死了所谓的科学,心里也是不停地怪刘大夫:“你为什么要说的那么科学理性,我可是学物理的,你就不能让我保留一点点哪怕是非常渺茫的希冀吗?”

  刘大夫看着我,任我哭了一会,给我找了纸巾,让我擦眼泪:“胡先生,我只能给你说实话。你妈的情况确实需要先处理脑部肿瘤的事,放疗方案你可以多问几家。我也帮你推荐一下北京肿瘤医院的石博士,让他帮你确认一下放疗方案。”

  从医院出来,我就给哥、姐、妹都打了电话,姐就催着哥嫂赶紧到北京来。回家和多多娘商量了一下,又给老娘准备了一个完整的五一团聚计划:打电话要侄儿瑶尧在五一期间过北京玩,哥嫂借口到北京找工作;然后再给多多拍艺术照给老娘留下合影。

  哥哥周六就到了,我跟哥商量后决定等过了五一再去做脑部放疗。那五一节自然就先带着老娘和哥嫂一家子去享受北京的春天。29日先带着老娘到照相馆拍艺术照。

 


















 

  在多多的艺术照里,刻意地多安排了几组多多和老娘的合影,只是希望多多将来意识到今天的时间意义后,能少些缺憾。

  突然接到小姨的电话,虽然她说的有点拐弯抹角,但听得出她已经知道老娘的病了。在哥来北京以前,一直在纠结,要不要告诉四个舅舅和两个阿姨;后来觉得这么重大的事一定得让他们知道,只是要求他们不要直接给老娘打电话。老娘有四个弟弟,两个妹妹。这段时间几个舅舅都给我打过电话了,小姨肯定是舅舅们通知的。小姨比我哥还小一岁,小时也是喝过老娘的奶;现正在天津打工,也要过来看看老娘。小姨过来,就赖着要和老娘一起睡,私下里也是很难受,一直跟我和哥哥说:她出生的头一个月就是靠喝着老姐的奶才活下来的(那是外婆年纪太大,没奶水了),长姐就是娘啊。这样,这个五一一开始是一家子陪着老娘玩和拍艺术照。最好的照片还是多多娘给老娘拍的。





  五一节过后,说服老娘到航空医院住院治疗。只是看过其他病友,我和哥哥答应老娘不让她在医院过夜,每天输液或治疗后就回家住。刘主任也同意了。

  得益于老娘是个文盲,除了自家人的名字外,基本就不认识其他文字的含义;老娘并不清楚自己得的病,更不清楚自己病情的严重性。我们也是尽量往轻了说。只是老娘需要迈过的心理坎也是一个个来了。

  首先,要放疗必须要剃光头发,要不脑部局部放疗就无法精准定位;因此只好带老娘去剃光头发。理发的小伙太聪明,也是见多了,就随意的问了是不是癌症。我只好赶紧用别的语言岔过去,敷衍了事。

  然后,就是病友之间的打听。头几次我自己在场,有人问我就应付,大部分的病人很有善心,能从我的话中知道我们在瞒着老太太的病情,会很配合的从问话中别出去。但有一天早上我因开会让哥陪着老娘在医院排队等放疗,有病友不管不顾直愣愣告诉老娘的病很严重。那天,老娘一下子就有了很大的心事,家里人费了很大的劲才让老娘高兴了起来。

  老娘的光头给她带来很大的压力,多多娘怕老娘害羞,早早就给老娘买了头套和帽子。老娘试了试,头套有点热,出门也就基本上带了帽子。

  在小区里,老娘也有几个老伙伴,老娘怕人问就会自己主动跟人家说自己的病。多多娘事先和楼下阿姨说好了,让她也简单对待,帮老娘宽解。

  脑部放疗总疗程是十五天。在脑部放疗前,给老娘做了个肺部穿刺,主要是要活检一下,看看怎么处理老娘肺部的肿瘤。从老娘的态度,我们无法采取传统手术方式来开刀,就寄希望于能采用靶向药物来处理。

  头十几天,老娘的头发又开始长出,没有掉发现象出现;这让我一直心存侥幸,以为可以挨过去。结果在最后两天,老娘的短发开始大把大把的掉了下来,基本上是老娘自己手抓一把掉一把,只留下中间的一长条没掉,有点像贝克汉姆的某个发型。有时我看着都会忍不住苦笑。

  放疗的最后两天,老娘的胃口也被毁了,见了肉就烦。在老娘朴素的知识里,人只要吃得了饭那就没病,吃不了饭才是麻烦事。所以胃口不香,让老娘感觉很不好,我们也只能宽慰。老娘开始警惕,是不是她的病有点严重?

  未完待续~~


 青春就应该这样绽放  游戏测试:三国时期谁是你最好的兄弟!!  你不得不信的星座秘密

March 18, 2014

我的老娘(二):雨中的欢乐  西湖游

二、雨中的欢乐  西湖游


    4月19日,我和多多娘带着多多和老娘坐动车往杭州赶,参加我的学生毕业二十周年聚会。妹妹一家带着哥哥嫂嫂从东阳往杭州赶(妹妹的车小,带不上姐姐了)。动车还是比较快的,五个半小时到杭州,只是到了杭州后出车站实在忒麻烦,排队排了一个多小时才打到出租车。到了西湖边的海军疗养院时,已近晚上九点。安排老娘和多多、开开一个房间睡。我们六个大人(哥哥嫂嫂、妹妹妹夫和我与多多娘)在一起商量老娘的事。按大夫的建议,脑部肿瘤是必须立即处理的,至于肺部以及化疗就看以后的进展情况。大家心情压抑,大哥了解情况后也比较实在,说哥几个可以轮流到北京来伺候老娘,具体的治疗方案由我拿主意。
    20日,西湖下着蒙蒙细雨,大家簇拥着老娘逛西湖,虽是早春的寒意袭人,一家子还是喜气洋洋。多多爸为了增添大家的兴致,诗兴大发:“远看好像有个湖\近看好像确实是个湖\走近一看\哇塞,果然好大一个湖。”这样的诗自然受到了多多和开开的合理嘲笑与打击,老娘就是在这样的欢快气氛中游西湖。
 


    今年年初,多多的个子已经超过奶奶,在雷峰塔里,多多要展示自己的实力,说要背着奶奶游玩。有开开,有多多,有儿女陪着,老娘真是很兴奋。儿女们知道内情,也是可着劲要让老娘高兴,开开应该知道一些,多多懵懂无知跟着爸爸耍宝,也是变着法让老娘开怀大笑。
 





    雨中的西湖,多一些凉意,也多一些悲伤的理由。在一家子欢聚的同时,偶尔的悲伤总会涌到心头,看着老娘欢笑的脸,真希望时间能就这样持续下去。
 
    中午时分,学生们派车接我到聚会酒店,老娘他们去灵隐寺拜佛。二十年了,我唯一的一批学生还记着我,还把我当成他们之间的重要一员。相识时他们十五六岁,如今已三十五六,这之间差着千里万里啊。我对这次聚会非常期待,因为我很想借此机会向他们表达我深藏在心里的谢意:当年我是在对人生几乎绝望的情境下偶遇他们,是他们对我的期待和欢迎让我重整旗鼓,再次整装出发的。要没有老娘这事,那今天就是我意气风发的时刻。在我发言环节,我真诚地向我的学生们致谢了,也向大家道了遗憾;如今也只能在晚餐吃到一半时刻匆匆赶回酒店。
    回到酒店时,老娘和两个孩子已在房间里,几个大人还没打到出租车。老娘一天内逛了西湖的主要风景,兴致正高。尤其是到灵隐寺的烧香拜佛让她很是兴奋,我也摘重点给她说了我的学生聚会情形,看着老娘高兴,大家也是自然高兴。
    第二天上午先是沿着西湖赏玩,午饭后觉得还是可以去看看钱塘江边的六和塔。我们已经累了,就让大哥大嫂陪着老娘和多多一起去爬六和塔。在入口处,老娘和多多带着墨镜的合影非常有型。
 










 





    从六和塔下来后,两拨人就此分手,哥嫂妹妹她们就从钱塘江桥起步开车回东阳了,事先跟哥商量好了,他们一回家就安排好家里的事,准备到北京来陪老娘。我们因为时间还早,就先去了虎跑泉,老娘依然走的快,多多娘怕老娘累着,所以半真半假喊累。虎跑泉里有许多专门来打水的人,排队老长,但看到老娘也想喝口泉水,马上就让老太太插队接了瓶泉水。那泉水清冽甘甜,老娘说喝了这样的水,病肯定就没了。
    这趟西湖游让老娘情绪高涨,很是满足。回到北京后,我再找了趟梁大夫,梁大夫实话实说,建议我别等301医院的病床,一是等不到,二是我老娘应该先做脑部放疗,而现在北京的成熟医院放疗技术都差不多,可以找一个离家近一点的就行,治疗方案可以多找几个专家来确认。我听着有理,就决定找航空医院。

    未完待续~~

    
 青春就应该这样绽放  游戏测试:三国时期谁是你最好的兄弟!!  你不得不信的星座秘密

March 17, 2014

我的老娘(一):灾难总是在你不经意的时候降临

一辈子 真的只是一辈子

 

    老娘站在天台山国清寺三贤殿前的平台上,带着点忧伤,幽幽地看着远方:“我给你爸念了那么多的超生经,按理他应该早就投生了,我就是到了那边,还是见不到他。”

    我的鼻子一酸,知道老娘十三年来对老爸的挂念,却也无法真正体会个中的深情和无奈。更何况我早已被唯物主义洗脑,既不知有前世,也无法去信有来生,一时无法接话。内心中只是强烈的感受到,原来我们这一辈子所遇到的所有人和事,都只是一辈子的事……

 

一、灾难总是在你不经意的时候降临

 

  4月2日,带着老娘一起去爱康国宾进行年度体检。期间,检查大夫针对老娘的颈部动脉和肺部的一个模糊印象找我沟通了一下,建议仔细检查。我同意了。

  4月3日,爱康国宾的郭大夫大打电话给我,说我老娘的癌胚抗原指标很高,必须进一步检查。因马上是清明节,而爱康国宾的休息日是周一,所以建议4月9日周二早上过去。

  无论如何,还是要过好清明节。期间约了冯伟、金国顺两家人去京东大峡谷了,想在外面住一天。因太冷,桃花也没开,最后都各自回家了。

  4月9日一大早到了爱康国宾,爱康国宾的大夫非常仔细的帮老娘重新检查了腹部彩超和肺部。一个老主任非常严肃地说:“你娘的癌胚抗原指标已900多,肯定有问题,一定要认真检查。”郭大夫说下午她要到301医院,可以帮我联系大夫。下午,带着老娘去了301医院,虽然也看到了大夫,但人家也只是提出要进一步体检,让我先做胸部CT。一到了CT室,人太多,就决定回到王府中西医医院进行检查。

  4月10日上午,王府医院的CT结果表明老娘左肺下叶有大小3.1*3.7*4.7的肿块。问题相当严重了。自己抹着泪,给哥、妹妹都打电话说了基本情况。

  我开始找人帮忙。左小卫一听说是我老娘的事,马上给我联系了301医院的田大夫,让我明天一大早去找他。11日早7点30,我赶到301医院,田大夫帮介绍了胸外科的主任大夫梁先生。梁大夫看了后,比较肯定的说应该基本是肺癌晚期了,若要在301就诊,必须做进一步的检查。他当即给我开好各种检查单子。要我明天一大早过去检查。

  4月12日恰巧又是海淀金融创投基金的答辩会。我只能一大早带着老娘去做各种体检,中间趁着老娘在排队等候的时间去答辩,时间把握的比较巧,两头都没耽误事。

  带着老娘在跑体检时,我脚步冲冲,老娘有点赶不上,只好时不时回头顾看,不时停下来等。突然间发现老娘真的开始变老了,就在前几年,我们一块出去玩时总是老娘在等我,现在需要我停下来等她了。老娘感动了,说:“阿勇,你一会就停下来,一会就停下来,是怕我走丢吗?这么在乎我,我都不好意思了。”我看着老娘,差点哭出声来,嘴里憋着无法出声,冲着老娘点点头,心里想:“像您这么珍贵的老太虽然比比皆是,但属于我的也就只有您一个啊,而我还没把您看住!”

  已经预感结果不是很好,又不想惊动老娘,就在排队的时间里和老娘瞎聊。我因为预定了4月20日要到杭州参加我的学生毕业二十年聚会,事先和老妹策划了一下,想不动声色的带老娘去杭州大家见面商量。就有意识地跟老娘提起去杭州开会的事,老娘突然冒出一句话:“我西湖都没玩过呢。”这话有点让我挠头,老娘在北京十年,进出杭州机场大致也有十来次,细想一下还真没在杭州玩过。每次回家总是急匆匆赶回东阳,每次回北京总是在老家呆到最后一刻直接去机场。我也正好找到话茬:“那我就带你一起到杭州,让兰仙他们一家子也到杭州玩。”这样的安排让老娘很是高兴。妹妹又跟大哥商量好了,让大哥给老娘打电话时,装作首次听娘说要到杭州玩就凑趣要跟着妹妹也一起去,这让老娘很是高兴。这样,一家子就在老娘不察觉的情况下,一起约在了杭州见面。(妹妹车小,捎不了姐姐了)

  4月18日是公司董事会召开的日子,一大早我赶到301医院取得最终的化验结果,梁大夫很明确的告诉我最坏的结果:肺癌晚期,已经脑部肿瘤转移加全身骨转移。我抖抖索索问治疗方案,梁大夫说必须尽快进行脑部放疗,这是要命的地方,同时打防止骨转移恶化的针;至于肺部,若不动手术,就只能维持了。他同时略微婉转的告诉我,这样的病情快的三个月,慢一点六个月,最好最好是一年……

  董事会我是绝对的主角,等晚上回家时,老娘已睡了。我带着这个结果和多多娘说了,躺在床上,自责不已,总是觉得老娘在我身边,我自己居然没有看好,是自己把老娘看丢了。多多娘搂住我,不断劝慰:“你是一个真正的孝子,你对你老娘的孝是发自内心,出乎自然;在我的身边,见过许多孝子,但我没见过一个像你这样的孝子。”多多娘顿了顿,继续说:“你是个伟大的儿子,也是一个伟大的父亲,也是一个好丈夫,但你不能把不是你能承担的责任都往自己身上扛。”老婆这样的评价让我振作了一点,以前多多娘认为我是个好儿子、好父亲,但是不是好丈夫一直成疑,就问:“我也是好丈夫了?”“是的,你不但是好丈夫,你还是好弟弟,好哥哥,好叔叔,好舅舅,好姑父,好姨夫,还是好姐夫,好女婿。我爸妈就一直要我弟弟记住你的好处,要懂得感恩。”其他的好,我都敢自认,但唯有好女婿,我有点愧疚:“我还和你娘吵架呢。说实在的,头些年,我还觉得跟你娘吵架那事我自己占着理,但这几年一想起来就后悔,后悔自己不该跟你娘吵架,有啥事应该好好说的。我就是张不开口跟你爸你妈道歉。”

  第二天天还没亮,我又坐到了床沿上长吁短叹。多多娘也没睡好,伸过手从后面搂住我的腰:“其实,我最担心的还不是你,我担心多多知道会怎么反应呢,真怕她接受不了。”我握住多多娘的手,充满感激:最了解我的还是自家老婆,她一句话已经彻底让我的注意力从深深的自责和悲痛中转移了出来:“是啊,多多怎么办?”

  第二天,老岳父和岳母打电话来宽慰我,顺便又一个劲地夸我,多多娘为了转移我的悲痛和自责,还是费了很大的心。

  未完待续~~


 青春就应该这样绽放  游戏测试:三国时期谁是你最好的兄弟!!  你不得不信的星座秘密

March 12, 2014

Document Freedom Matters

As the Document Freedom Day is approaching I realized that we don’t push ODF and open standards as loudly as before. Certainly most of the battles for the mind and market share are past, at least when it comes to office file formats. But the recent public consultation of the UK government brought back some of the most crucial issues surrounding ODF and it’s useful, I think, to check where stand these days on these matters. dove-logo-2012

Shortly after OOXML had been given the ISO label in the weirdrest and most outrageous way, a representative from Microsoft spoke at an IT conference in Brussels and bluntly declared “ODF has won”. Well, it is true in the sense that the OOXML standardization process had highlighted the -probably terminal- inability of the ISO to tackle IT standards and transparency in an effective way. In this sense indeed, ODF had won the “moral” battle. On the other hand, Microsoft had reached its main goal: to get the ISO’s stamp of approval on the half-baked OOXML specification. What it never achieved however, was the actual mass adoption of OOXML by the users of Microsoft Office and beyond. What’s that you say? OOXML has not reached mass adoption? Well, the actual specification, the standard, has not actually been implemented as the default file format until MS Office 2013, and yet, as an odd, end of the list option called “OOXML – strict”; OOXML – Transitional being a rubberstamp for every undocumented and unpublished sub-spec and binary blob necessary for Microsoft Office’s secret sauce to work its magic.

Of course, it is sad, yet true, to notitce that the mass adoption of ODF has failed until now, and that most companies and government use Microsoft file formats (xml based or not) as their default format. This alone would be enough to claim we haven’t moved an inch closer to true document freedom. At the same time, the IT and the way we use software and data has changed in 5-6 years.

More and more data
Data, big and small has become the new black. It’s all about data these days, and yet amidst all of it, the world does not seem to care a lot about digital documents. Any true reality check would have anyone notice that office suites are used everywhere, not less, not more, but in addition to any online collaborative, social and multi-device service and platform outt here. But most of this data is not wrapped in an office document format though: the office document is an aging, yet useful metaphor that is currently not explored too much. In this sense, the mission statement of OOXML goes against the wind: a standard to represent and encapsulate the information and its representation contained in proprietary documents is not a solution. It’s one more layer of complexity: better open up all the specs of the former proprietary file formats instead!

No growth in the ODF ecosystem
Like it or not, there has not been that much investment in the ODF ecosystem. Of course, work on the further development of the ODF specification has continued at the OASIS Consortium. But that alone is not enough. Once you have about 4 office suites implementing ODF in an good or excellent fashion, you need tools, and you need middleware. I know a few tools, some of which my former company, Ars Aperta, has contributed to, but you also need middleware such as content management systems, specific application servers, data busses, etc. to implement and support ODF. Beyond that, you need good mobile support for ODF. To this day, this has not happened yet. Although I know of serious attempts, this is just not available and won’t be, I guess, until the Document Foundation releases its own ODF viewever for Android and iOS, which is thankfully actively developed. Once you have all this, entities migrating to suites like LibreOffice need to have an actual document exchange policy that takes into account exchanges inside the organization and outside of it. Most of the migrations I know of do not integrate this and as a result I have heard of successful migrations to LibreOffice with no or only partial document migration to ODF.   In a nutshell, ODF is no icebreaker. It is an asset, it is an opportunity and a great standard for office file formats, keeping your data safe, accessible for edition, consultation and archival. This alone is a major advantage. But what was seen as the strategic weapon against Microsoft dominance on the market seems to have failed.

Reasons to hope and fight for
In all this rather grim description, one can wonder why we even have a Document Freedom Day at all. It is perhaps important to realize, first of all, that this is not a grim picture. The very fact that the ODF ecosystem stands the way it does today and has survived until today in the face of aversity and corporate friction (monopolistic practices, poor procurement policies, Sun’s acquisition by Oracle, etc.) is the living proof of the ODF’s ecosystem resilience and strength. Second, ODF is being adopted in many places around the globe, and it works. The Brazilian Government, entire parts of the German public sector including the famous migration of the City of Munich, the French Gendarmerie, the Portuguese and Italian Governments and other public sector agencies all around Europe, as well as small and large companies here and there do use ODF. You can send letters in ODF to most of the European public sector including the European Institutions and they will be read and handled just like .doc or .docx formats. What this means is that while ODF may not have won over proprietary formats we now have a growing place and use for opens standards like ODF. And as the current IT trends towards the reuse and digitization of cultural and public data go, the open data movement as well as major projects such as the Preforma FP7 project are true opportunities for growth, change, software and document freedom.
Last but not least, the advent of the LibreOffice project is probably one of the best news for the advancement of ODF. Because it was succesful in getting rid of the corporate overlords dominating the old OpenOffice.org project, LibreOffice managed to set up an increadibly fast growing project and community that managed to develop innovative features that ultimately benefited ODF and software freedom as a whole. But we cannot stop there.

Software Freedom matters, today perhaps more than ever. We need to regain control of our software, of our data, where it goes, what it says about us, whether we will be able to use this data in 30 years from now  and what we can do with it today. We need Software Freedom and we need Document Freedom. Let’s fight for them.

March 03, 2014

Suffolk County Council’s Nacton Road/Ransomes Way plans are dangerous to cyclists and walkers

Suffolk County Council currently have a consultation running about Nacton Road and Ransomes Way corridor. It is “to meet the projected increase in traffic associated with development in this corridor”. You can find out more on the Cyclescape thread.

Please find below my response to the consultation. I’m hoping that many more people respond with a similar response before the consultation ends on Wednesday 5th March 2014.

 

Nacton Road and Ransomes Way corridor consultation

General comments

Quality of cycling facilities

Has any consideration been given as to why people are driving here even so there are cycling facilities? Could it be that the cycling facilities are of poor quality? Could close passes by motorists be putting cyclists off? Could people annoyed at being put in conflict with another vulnerable road user group? Are people driving between the shops rather than cycling and walking? Cycle Ipswich members are aware of people who have given up cycling due to unclear cycling facilities, or too many near misses or close passes.

The nearby Ravenswood estate is just off the Nacton Road, it has a high level of cycle to school, yet few people will venture out of the estate on their bike to do something like shopping. Why are these people not venturing out of the estate much by bike? You need to look at these issue before implementing designs which will induce even more traffic.

Throwing cyclists on to the pavement with pedestrians should be a last resort, rather than a default action that it seems to be in Ipswich. This creates conflict with pedestrians and doesn’t create a pleasant cycling experience as you have to cycle slowly if there are pedestrians about. Dedicated space for cyclist, and no I’m not talking about a white line down some legalised pavement cycling is what is needed. If shared use pavements, or legalised pavement cycling as I prefer to call them worked so well, significantly more people would be cycling in Ipswich. Light segregation which will be in the next version of London Design Standards, and has already been implemented on Royal College Street in London for example is an option to increase flexibility, and is also fairly cheap to implement.

Would you be happy to have your 8 year old child using these roads on their own or would an 80 year old be happy using the roads? If not, the facilities on the roads aren’t good enough.

You should take a look at the video and information at http://www.protectedintersection.com on protected intersections.

Number of lanes to cross

There are many junctions in the proposals where cyclists and pedestrians are expected to cross two or three lanes of traffic. This is something that is really hard to do, especially if you get one stationary lane and another with faster moving traffic. You end up waiting in front of a stationary vehicle while a gap in the passing traffic opens up, and then the driver gets annoyed as they can’t continue due to the traffic causing them to be stationary having moved on.

The Dutch have spent a lot of time looking into the safety issue of cyclists and pedestrians crossing multiple lanes at an uncontrolled crossing. For any uncontrolled junctions they now narrow the junction down to a single lane so that you only need to cross one lane at a time, and motor traffic is slowed so that it is safer for everyone, thus there are fewer collisions. It also makes it subjectively safer for pedestrians and cyclists thus more walk and cycle. If multiple lanes are needed, a controlled crossing is used, however the timings are very dynamic with very good detection of cyclists and pedestrians, and avoid them waiting for a long time, as currently often happens in Ipswich.

Dog leg crossings

There are many dog leg crossings in the proposals. As both a pedestrian and a cyclist, especially having used a trailer in this area for transporting good from the shops, I find them a total pain to use. Have any of the people proposing these taken a look at how people currently use them. They’ll find that many people just ignore the zig zag and cross straight over and walk over the kerb stones using a more direct route, often ignoring the second signal.

I find it extremely unfair that motor vehicles don’t get the same treatment as pedestrians and cyclists when going through junctions, I’d really like to see a motor vehicle junction where they arrive and have to wind down the window to press a button and then get a green after a bit more waiting. The driver then has to do an awkward maneuver to get through the junction, even if they are going straight on, including pressing another button to complete the passage through the junction.

Mapping

The on the first page could have a more up to date map background, for example OpenStreetMap is much more up to date, with no costs or requirements other than attribution.

Specific comments

A14 junction

As the National Cycle Route 51 travels under the A14 and across the slip roads, consideration needs to be given here too, to make it safer for cyclists crossing the slip roads as it can currently be quite difficult. The slip roads need narrowed to slow motor vehicles and priority is given to cyclists, which is part of the Dutch strategy at encouraging cycle usage, and is perfectly possible to implement here.

Nacton Road (A14 to Thrashers roundabout)

Will cyclists using the legalised pavement cycling have priority over turning vehicles at the junction into Orwell Country Park?

The is the only section where I will accept a shared pavement as a solution for space for cyclists due to it being almost wide enough the whole way, and there are very low expected demand from pedestrians.

Thrashers roundabout

The dog leg crossing needs removed, see explanation above.

Where there’s an uncontrolled crossing there ideally needs to be only one lane of traffic for cyclists and pedestrians to cross, or an absolute maximum of 2 lanes, whereas in places there are 3 lanes. The lanes also need to be kept as narrow as possible to slow motor vehicles to increase safety for cyclists and pedestrians. Minimisation of lane switching is also needed.

The wide corners that can be taken at speed, which makes it even more difficult to cross the road, especially when combined with the number of lanes that need to be crossed. There needs to be clear space for cyclists, without mixing them with pedestrians or motor vehicles. Motor vehicles need to be slowed to prevent collisions. Tighter corners are needed to slow down vehicles and improve sight lines so that drivers can see cyclists and pedestrians and reduce the risk of them being in the driver’s blind spot.

Ransomes Way

Where is the space for cycling along this road? Has anyone questioned why there are so few people walking and cycling along here to access the shops? Will the speed limit be reduced to 30 mph from the current 40mph?

The current legalised pavement cycling is horrible for both cyclists and pedestrians. The Cranes to Felixstowe Road section is particularly bad due to the narrowness particularly on the west side of the road as it gets close to the railway bridge. I’ve cycled along there with a bike trailer on a Brompton and had to wait at a wider section for pedestrians to pass. This places cycling as a second rate mode of transport. Instead of 3 lanes of motor vehicles, there should be some light segregation used to create a safe cycle lane. The light segregation is relatively cheap to install, and will be in the upcoming London Cycle Design Standards. This will do far more to promote cycle use than the current shared footways which discourage many people from cycling as they are so inconvenient.

Why can’t pedestrians and cyclists get from John Lewis on to Ransomes Way using a more direct route that means that they don’t have to go the full length of the car park first?

Ransomes Europark/Cranes

The dog leg crossing over James Bennett Avenue need to be changed to straight over crossing, ideally without having to stop in the middle and press the button again, otherwise you are designing the road environment to promote motor vehicle use instead of sustainable modes of transport.

Similarly the crossing over Ransomes Way needs to be timed that you can cross straight over without stopping. By reducing the length of the middle roundabout, that will help shorten the distance that cyclists have to cross, thus reduce the time for them and the waiting time for motor vehicles.

Ransomes Way/Felixstowe Road roundabout

This is a horrible set of changes for cyclists. As someone who has recently cycled up the west side of Ransomes Way to cross over Felixstowe Road to get to Sainsburys and Homebase with a trailer on the bike, it was a horrible experience. I got stuck in the middle of the road fearing my trailer would get damaged by vehicles passing behind me. The new plans make it even more difficult for cyclists as there will be no crossing on 2 sides of the roundabout. This means that if a cyclist happens to go along the wrong side of Ransomes Way they either have to take a long detour up Felixstowe Road to cross, or dart across the fast traffic, or go back they way that they came.

Crossing the two lanes entrance and exit to the Sainsburys car park is also horrible currently as the cars go so fast, this needs improved for cyclists trying to access the cycle parking for Homebase. There should be a maximum of 1 lane in and 1 lane out of the car park for the best possible safety.

I would recommend changing Murrills Road to be a bus gate near the Homebase, thus reducing traffic at this junction. It also encourages more people who live in the local area to walk and cycle to these shops, as the bicycle or walking is journey is shorter and more pleasant. I don’t see why there needs to be a through road here private motor transport. This is standard practice in The Netherlands.

None of the changes at this junction will encourage more people to get on a bike to get to the shops here, rather it will put them off, and induce even more motor traffic. The position of the pedestrian crossing is significantly off the desire line, thus I expect some pedestrians to be crossing closer to the roundabout.

Lindbergh Road/Nacton Road

I’m concerned about the width of the cycle lane here. Will it be 2 metres wide, thus giving enough space for cycling? Far too many cycle lanes in Ipswich are so narrow you can’t even fit the bike in them while cycling, never mind the passing space so that cyclists feel comfortable with vehicles passing. I’m concerned that there will be pinch points created and many vehicles will pass cyclists too close, thus discouraging people from cycling along this section of road. This road has plenty of space to put in real dedicated space for cycling, whether it be a separate track (not the pavement, which is for pedestrians), or light segregation.

Is the island in the middle of the crossing really needed? Surely giving more time for pedestrians to cross in one go will encourage more people to walk, than if they may need to stop half way on the refuge.

Landseer Road/Nacton Road

As there will be an increase of traffic on Landseer Road the whole of Landseer Road will need to be looked at too. There currently is issues with the cycle lane being too narrow, and in places gets a build up of leaves in the autumn, particularly where it goes past the park. Floating bus stops, where the cycle track goes behind the bus stops are also an option along these roads.

The dog leg crossing needs to be a direct straight across type instead.

Will cyclists turning left be protected from vehicles cutting the corner when turning left? I would much prefer the space used for the right turn to continue on the Nacton Road towards the town centre to be used to protect cyclists going round the corner, however it also needs to be designed to allow them to safely get across and continue on the Nacton Road if they wish to do so.

Nacton Road/Ransomes Way

Show embedded map in full-screen mode

March 01, 2014

LibreOffice: My birthday wish list

This post is a bit unusual. Let me explain: LibreOffice is a bit like my baby, and when I blog about it, I write with passion but also with the notion to get specific points across.
Now, it does not mean that this post will be different in this regard, but that what’s below represents my very own, personal view as a LibreOffice user who, just like many others, has a more or less long wish list for its favourite office suite. And yes I know: if I want something done, I should submit a patch: but I neither have the time nor skill to do it, this is why my post is not a rant, but only a wishlist. And besides, it’s my birthday in two days, so  bear with me.

  • Turn the LibreOffice HTML editor into a nice and powerful web editor

This is something anyone who even knows that LibreOffice has an embedded html editor will know: this tool (a subset of Writer) hasn’t gotten much love since… OpenOffice.org 3.0 something. Which means a very long time. It’s not just about improving the html editor itself, although that improvement alone would be nice. Rather, I was thinking that this editor could have HTML 5, CSS and Javascript added , and perhaps something like a live preview of the page that’s being worked on.

A possible question at this stage would be the reason for such an improvement: After all I don’t use LibreOffice to edit html pages (few people do). Why then? Because I think it’s a feature gap that LibreOffice ultimately suffers from, and it does not have to be excellent at it, but only being able to cater to most common needs in this field. Besides, LibreOffice has an actual IDE that one can use to develop macros and scripts in other languages. I think an improved web editor would complement the IDE just fine as well.

  • A Twitter client for Writer

Yes you’re reading that very well. A Twitter client for LibreOffice Writer would probably be a gadget to many, but a handy tool to some. The idea first appeared during FOSDEM 2013 when Chris Anintscyk, head of Open Source matters at Twitter came to the LibreOffice booth to pick up something (I don’t remember what actually), and we started to joke about that idea. But then I thought about it, and didn’t find the idea to be stupid at all, at least for Writer. The client would be integrated in Writer and be used to tweet entire sentences contained in the document opened by LibreOffice Writer at that moment. So instead of tedious copy and paste operation, the client would have a tool selecting the text and then posting immediately to Twitter. Think “quote of the day” twitter handles etc.

  • A true calendar for Calc

Calc is becoming really powerful with LibreOffice 4.2.x and we’re only discovering the crazy stuff we can now do with LibreOffice Calc. Yet I’m talking about something more “static” in this case. Of course, you can find several calendar templates online for LibreOffice (link) but that’s not really what I have in mind. the idea would be to have a calendar with the ability schedule and mark events, meetings, etc. and notify contacts directly from Calc. On top of this, Calc would be able to export calendard or events as .ics files.

  • STL file export for Draw

If you have never heard of STL don’t worry, only people who are in 3D printing have. (This STL file has nothing to do with LibreOffice STL files, by the way.) Basically, before printing anything in 3D, you need to design your object, and the way you do this is though software. Now I know that there are more powerful graphics and design software out there (the GIMP and Blender being two examples) but frankly today Draw can perform quite well in this field too. Once you have your 3D model of your desin on your computer you need to export it in a file format that will convey the required data for the layering process used by 3D printers. One of the most common, if not the only one, is STL. Ideally then, Draw would be able to have an export to STL, but also perhaps the ability to export to popular 3D modeling formats as well (AMF, DWG or Blender files) . That would not change the need to export everything to STL before turning the design into yet another format (a binary one) : GCode. But it could really be handy.

  • Pattern editor for Draw

I’m not done with Draw. We never seem to be pushing this graphics editor much although it is being actively developed but many people don’t try it and just think it’s something like MS Paint. Back to my wish: a pattern editor for Draw is a tool that lets you edit patterns, aka clothing designs. With these designs you can then start to procure clothing material and then move on to the actual knitting/cutting/ making of clothes. Why does it matter? I don’t cut and design my own clothes but I know many people around the world still do or would like to learn that. A Free and Open Source tool like LibreOffice ought to be able to offer that ability to, well, pretty much everyone out there with a computer and do it with open formats and standards.

All in all, this list would not significantly change the userbase of LibreOffice; but it would also position LibreOffice in places and circles where it’s not really used either, and I feel it’s a welcome set of suggestions that differ from the usual Android/iOS porting and cloud based office suite. On a deeper level, I think it also means that LibreOffice as a tool and office suites in general can change and grow to adapt to new usages even today.

February 28, 2014

[转载]计算机信息系统集成资质将何去何从?

计算机信息系统集成资质将何去何从?

                           ——软交所深度解读国发[2014]5号文

文:软交所企业资质体系建设研究中心

    近日国务院印发《国务院关于取消和下放一批行政审批项目的决定》(国发[2014]5号)(以下简称《决定》),再次取消和下放64项行政审批项目和18个子项。其中,本次取消和下放的行政审批项目中包括计算机信息系统集成企业资质认定、计算机信息系统集成项目经理人员资质评定、信息系统工程监理单位资质认证和监理工程师资格认定。消息一经发出,立刻引起了广大计算机信息行业企业的广泛关注。一时间,北京软件和信息服务交易所(以下简称“软交所”)接到多家会员企业的咨询:计算机系统集成资质认定是否已取消?是否意味着资质设置的门槛已经取消?若资质未取消而由行政许可改由其他主体负责审核是否资质证书含金量降低?新负责机构可能是谁?

     《决定》指示“各地区、各部门要抓紧做好取消和下放管理层级行政审批项目的落实和衔接工作,并切实加强事中事后监管。要继续大力推进行政审批制度改革,使简政放权成为持续的改革行动。要健全监督制约机制,加强对行政审批权运行的监督,不断提高政府管理科学化、规范化水平。” 据新华网《简政放权国务院进一步激发创业主体积极性》新闻报道:工业和信息化部称,“计算机信息系统集成企业资质认定”、“计算机信息系统集成项目经理人员资质评定”和“信息系统工程监理单位资质认证和监理工程师资格认定”等资质取消后将有利于减轻企业负担,降低准入门槛,增加市场活力。同时工业和信息化部将抓紧制定出台相关标准,发挥第三方机构作用,加强事中事后监管。

    软交所认为此次调整并不意味着计算机信息系统集成资质的取消,而是资质的审批权从政府(工业和信息化部)向第三方机构的转移。有消息称,计算机信息系统集成资质的审批权将会像安防工程企业资质和通信信息网络系统集成资质一样,转移到相关行业协会。若此消息属实,软交所预计未来计算机信息系统集成资质的认证流程可能会简化,从而使行业内的企业在市场活动中得到更多的便利。同时市场准入门槛依旧存在,市场仍需要一定标准和规则,招标方还是会在注册资金,公司规模、技术实力、综合能力等方面对投标方进行约束,以保证投标企业承接系统集成工程的实力与水平。企业也需要加强自身的管理和质控能力。所以,建立一套有利于用户选择评价供应商的评价标准仍是必要的。

    工信部强调在发挥第三方机构作用的同时,工信部将加强事中事后监管工作,对下放地方政府的审批项目,将相应加强指导和监督,推动地方政府规范审批行为、提高行政效率。所以,行政审批事项虽然取消了,政府的责任并没有减轻。各部门将适应取消和下放行政审批后的新情况,下工夫创新管理理念、改进工作作风,探索新的管理方式,把精力更多地转到事中事后监管上来,防止出现管理空当和漏洞。所以软交所认为简化流程并不意味着简化每一个环节,资质是企业综合实力的展现,计算机信息系统集成资质由更加专业化的社会主体进行管理,则可能对每个环节的把控的更加细化和深入。

    简政放权激发市场主体创造活力,增强经济发展内生动力是新一轮政府职能转变的核心要务。在小政府,大社会的原则下,充分发挥市场在资源配置中的决定性作用,倡导主体多元化的社会管理方式,将政府以外的其他社会主体社会管理权力、资格及能力提高也是我国社会发展的大势所趋。在一些环节弱化乃至取消行政力量对市场的干预,将会给计算机信息行业营造公平、充分的竞争环境,刺激行业的良性、健康发展。

    目前,计算机信息系统集成企业资质认定和项目经理资质评定的申请和受理全面暂停,具体操作细则不久将会正式出台。软交所作为北京软件和信息服务公共服务平台成员单位之一,将持续关注计算机信息系统集成资质的政策变化情况,并及时进行深度解读,以期助力计算机信息行业企业在政策变更期平滑过渡。

    了解更多企业资质建设相关信息,可登入软交所官网了解。http://www.csix.cn/v5_jyfw/zzgj/gjfw.shtml


 青春就应该这样绽放  游戏测试:三国时期谁是你最好的兄弟!!  你不得不信的星座秘密

February 18, 2014

The quest for the perfect Twitter client on Linux

twitterbirdAfter a few years of announcements, releases and online reviews, I am still out there looking for the right, if not the perfect, Twitter client on Linux. And believe me, this quest is frutstrating.

Why would I want to use a Twitter client on my desktop?

That’s a good question. I could just open a new tab on my browser and have Twitter there. Let’s face it: a good twitter client should bring more value than the web page of Twitter while developing what I feel is the actual raison d’être of an actual client: to make it easy and pleasant to tweet and read the twitter feeds outside of a browser as if Twitter was a separate network. In practice, this means that the way notifications are carried on to the user matters a lot: they must be at the same time non-intrusive yet informative enough while being customizable by the user. The interaction with the browser should be no problem at all while the interface ought to display the twitter feed and a clear interface with additional information (retweets, replies, conversation, favorites…)

If a client is not gearing towards these aims then I actually wonder what good it could provide on the desktop, if any.

In my experience with such Twitter clients on Linux, the issues I faced were often different, and that what contributed greatly to make this a frustrating experience. Basically, several Twitter clients I used had these drawbacks, either several of them at the same time, or at least one of those:

- poor and slow refreshing of the feeds (and I have a fast bandwidth)
- general instability
- inability to customize notifications
- unclear interface
- no real notifications mechanisms

Add to this the fact that for years I really wanted to have a “dual network” client, meaning, I needed to follow both Twitter and Identi.ca . I kind of dropped Identica since last year and I’m now mostly on Twitter (sorry Evan). With this requirement dropped off the choice of clients gets a bit broader but does not significantly change the situation. Let’s turn now to the actual Twitter clients for Linux I’ve tinkered with.

The deskbar

Many years ago, by which I mean those heroic times where people used Gnome 2 and Ubuntu was progressing to the point of reaching the most used Linux distribution on the desktop. There was no Unity, and a bunch of volunteers came up with something really nice for the Gnome DeskBar, which at that time could let you search many things in your system, but not much else. So they developed the ability to tweet from the deskbar, and not just tweet, but dent as well. It worked well… for a while. For one thing, you could not see your twitter feed, but you could post. And then Gnome 3 came in and terminated the deskbar by replacing it with a more central search bar in its new interface. Gone was the deskbar twitter client.

The StatusNet client

Now it was a nice client for the time, but it was only working with Statusnet microblogs and networks, and while it looked sleek at that time, it was also rather slow.
At some point it became obvious it was also not actively maintained. So I went to look elsewhere.

Gwibber

Gwibber appeared as “the” twitter client from Ubuntu. And it works really well on it too. It has a nice integration with Ubuntu’s interface and the client works with Twitter, identi.ca and several other services. In fact it is one of the most complete Twitter client out there. The problem? I don’t use Ubuntu, I use ArchLinux. Arch Linux does not tweak or customize its Gnome desktop in anyway; what is packaged is what comes out of the Gnome project. Gwibber, however, is packaged in the Arch User Repository (AUR) and I can honestly say that in 4 years I have only seen Gwibber’s integration with a vanilla Gnome desktop improve marginally. In other words: Gwibber is at best extremely unstable but most of the time, will just not start. There’s always some component missing or broken, but surely 4 years areenough for either one of the project to fix that mess? While I cannot speak for users of distributions such as Fedora, Debian, OpenSuse, Mageia, etc. Gwibber seems to be working fine on Ubuntu only, just like it took a long time get Nepomunk’s integration working on distribution other than Mandriva Linux. At the end of the day; Gwibber is not usable today for me. Moving on.

Pino

Pino was an interesting attempt, and I’m not sure its original developers ever intended to give it the political twist of being the Twitter client for “the rest of us who don’t use Ubuntu”. Pino is written in Vala, and as such was working pretty well. Helas, it also became rather quickly unusable to the point where it would not start, but reinstalling it would fix that until the next refusal to start, or the next fatal crash. I haven’t tried Pino for a while but perhaps it’s just that I got tired of it.

Hotot

Hotot seemed nice, but by that time I was starting to get wary of these new Twitter clients for Linux. I tried several versions of Hotot, some were a bit problematic, but tended to work. My main pet-peeves with Hotot? It takes a while to refresh and to load feeds, while its interface does not make it clear what became of the message you just tweeted. What ultimately cut it for me was the actual development of Hotot. If you go to the project’s page today you will see that it did stop at some point. It was however unclear to me even at the time of Hotot 1 and 2 what exactly was happening, as the development started of really fast, then seemed to go through a complete code rewrite that generated some more instability. At the end of the day, I still have hotot somewhere on my systems, but I hardly use it, and it seems to be broken anyway.

Qtwitter

This used to be a nice Twitter client. Because it was made on Qt, it was working well on my Mac and my Linux systems, and that made it really interesting. The development stopped though; but the take away here is that its strong points are the fact that it is (was) multi-platform and that its notifications work well. It was however rather unstable (crashes) on Linux.

Choqok
Let me make it straight in one sentence: Choqok works, works well and works fast, it’s too bad it’s not Gnome software as I’m a primarily a Gnome user. But Choqok fits the bill in almost all of the criteria I’ve mentioned above. It’s only issue, I think is that its notifications are just not that relevant. At least, when using KDE it will the number of tweets that are arriving, but in the notification area of the KDE desktop, and that’s about it. I’m sure I could customize it, but I have not found how. So Choqok, which I do use often, is really the client…. if it was not primarily a KDE client.

Birdie

So far, Birdie is a really nice Twitter client for Gnome; and it is really customizable. It does have some instability but the options are really powerful and I’m sure I haven’t taken advantage of everything it can offer yet. I might be wrong but it seems it is a rather young project started in 2013, and one will have to see its “endurance”. I really wish they can improve their stability, but to me Birdie is the hot ticket of the moment for Twitter clients.

Caveat Emptor: this post is not intended as a way to start a flamewar, but only recounts my personal experience with each of the software I’ve mentioned. Something I’d really like to see would be a LibreOffice Twitter client… more on this later. 

February 17, 2014

2014软交所让梦想照进现实

   以下是我在软交所2013-2014软交所“梦想·乐享”伙伴年会的发言,年会高朋满座,在此由衷感谢伙伴们对我们的帮助和支持!

2014软交所让梦想照进现实

 

    二十年前,当我加入软件行业时,中国的软件行业非常弱小,全年的软件产值甚至不如一个跨国软件企业一年的收入。但就在那个时期,在各位软件前辈的带领下,中国软件产业一直就有一个梦想,梦想中国软件产业强盛的一天早日到来。

 

     二十年过去了,中国软件产业的规模已经当之无愧的变成了世界第二。如今,我们有了更大的追求,更大的梦想,我们希望中国能成为世界上当之无愧的软件强国。

 

    年轻的软交所成立已经三年,从成立之初,我们就有一个梦想:建立一个“专业、阳光、透明”的软件交易市场,为中国软件产业的强大尽我们的一分力量。

 

     软交所的成立是在工信部和北京市经信委主管领导策划下成立,也正因为此:是市长催生了我们,还是市场需要我们?就是我们软交所经营团队所必须严肃思考的问题。我们必须回答软交所对企业的价值是什么,软交所对用户的价值是什么,软交所对整个行业的价值是什么,一个具备公信力的软件交易场所必须具备哪些要素?

 

    通过近三年的实践,我们认识到要真正让软件交易更容易,必须实现软件交易的标准化以及交易流程的自动化。我们知道,软件交易和项目交易的“标的物”是典型的“非标准化”产品;软件非标交易的难点在于三点:一是对交易物的简单准确的描述,二是对标的物交易价格的公允确认,三是交易过程的规范透明。

 

    2013年软交所牵头制订的北京市地方标准《信息化项目软件开发费用测算规范》颁布实施,我们着手开始解决公允定价权的问题。同时我们联合中国信息技术服务标准组织(ITSS)、中关村软件联盟、中关村大数据联盟、物联网联盟、云计算服务、青岛软件联盟等组织开始着手制定面向用户的采购标准和交付标准。基于正版软件的标准化交易将逐步推向所有的软件和服务。我们梦想“henrongyi”软件商城终有一天会让用户感受到买卖软件真的很容易。

 

    在科技金融方面,我们在基于知识产权价值量化基础上的抵押贷款已服务了135家企业。我们将在基于企业价值评估以及软件产品价值评估互联网平台上,为企业和金融机构提供简捷的对接通道和专业化的增值服务。结合我们已推出的北软天使基金和并购俱乐部为企业成长所需要的资金,提供全方位的服务。

 

    我们针对企业成长服务而推出的企业资质管家,已服务了286家企业,我们只希望在企业的成长过程也有我们微小力量。

 

    在过去的一年,软交所本身也得到了长足的发展。我们软件的交易额超过了8亿元,替企业的融资额超过了12亿元。软交所的总收入超过了2500万,实现了81万的净利润。这对软交所本身而言,也是一个标志性事件:在服务软件行业的过程中,我们也找到了自我发展的道路。

 

    每一天,我们都在服务他人,每一天,我们都能发现自己的成长。付出爱心,成就他人,就是成就自己!一点点成长,在共同努力的过程中,我们都明白伙伴的意义。2013我们拥有超过了800家企业伙伴,450家金融机构伙伴,通过我们的一同奋斗,我们梦想的一切都将变得很容易。

一个人前行,难免遇有阻碍,和你们在一起,我们共同开启追逐梦想的动力。

   2014,我愿意!

 


 青春就应该这样绽放  游戏测试:三国时期谁是你最好的兄弟!!  你不得不信的星座秘密

February 09, 2014

Eyes & Ears

This week I have picked up two very nice mixes and one nice video of an installation by two artists, Romain Tardy and someone hiding behind the “Squeaky Lobster” pseudo. It’s called the Ark and it’s a beautiful combination of lights, water reflections and structures. Let’s start with these guys:

THE ARK
A site specific installation by Romain Tardy and Squeaky Lobster
Proyecta Oaxaca, Ethnobotanical garden of Oaxaca, Mexico

Café del Mar Summer mix 2013 by Toni Simonen

I’ve written here that I felt José Padilla and a couple others were the only ones who were able to capture the essence of Balearic music. It does not mean others do a bad job, and Toni Simonen is definitely up to something in this mix.

Café del Mar Summer 2013 Mix by Toni Simonen by Café Del Mar Music (Official) on Mixcloud

 

Manuel Göttsching – E2-E4 (part 1)

Now this is a true rarity. It’s been released in the nineties and listening to it will unveil the very soul and underlying characteristics of Balearic music. It’s all in there, in its most abstract, yet crudest form. Only AMCA ( a man called Adam) comes close to this level.

 

That’s all for now, thanks for listening folks!

February 01, 2014

Why LibreOffice 4.2 matters more than you think

On Thursday the Document Foundation released its newest stable branch, LibreOffice 4,2. Don’t let be misled by its number; if we weren’t on a strict time released scheduled alongside a clear number scheme without any nickname for each release, I would have called this one the 5,0. Yes, you read that right, the mighty Five. Why? Mostly for two big reasons.

This is a major code overhaul

Do you remember one of my first posts about LibreOffice, at the end of 2010? I had hinted that one of our goals was to develop a brand new engine for Calc, which had stayed pretty much the same since 1998. Well, the 4,2 just got that: Ixion has been integrated as the Calc engine and that, among other things, such as real-time integration of data feeds, is about to change a lot of things, and not just in terms of performance boosts (over 30% of improvement depending on the cases). This might actually open the door for brand new types of users in professional and scientific venues for instance.

Alongside this rewrite, we also have a major work on the user interface layout and dialog rewrite. As Michael Meeks explains it, we had introduced this rewrite with the 4.0 but now quite many of our dialogs and widgets have been rewritten. Other user interface improvements such as a brand new iconset, document snapshots on Windows bring a fresh and refined user experience to LibreOffice.

More Enterprise-ready than many others

We have heard this song here and there. You cannot be innovative and be successful as an enterprise solution. You cannot be the right choice for companies if you haven’t a major American corporation as your main sponsor/steward/overlord/friend. You cannot deliver a professional grade office suite if you work along a time-based release system. I think that these theories have already been proven wrong, unless you have a twisted definition of what the enterprise market  needs. But with the 4.2, we also have some nice and immediately actionnable features that will appeal specifically to the enterprise market:

  • Integration of the CMIS stack allowing you connect to document repositories on SharePoint, Nuxeo, Tibco, Alfresco, Google Drive and many other CMS.
  • Expert configuration options now all put in one place
  • Advanced deployment options
  • Better group policy controls for deployment and installed user base
  • Improved Microsoft Office (.docx, etc.) and RTF document filters
  • Improved look and feel on Windows
  • Change tracking on ODF and even on OOXML documents

I’m not listing a good dozen of other improvements of importance, but here’s the complete list.

It’s not about success. It’s about what comes next.

And now, I’m going to really explain why LibreOffice 4,2 matters more than what meets the eye. The amount of code clean-up, refactoring, write up, the inclusion of new features and the continued growth of contributors between the moment the Document Foundation released LibreOffice 4.0 and the 4.2 is truly amazing. The 4.0 was a major accomplishment, but this time we did even more, seemingly with less effort (although this comment does not diminishes everyone’s accomplishments for this release).

What’s going here? A giant in Free and Open Source projects is emerging and we are witnessing this unfolding right under our eyes: a growing development powerhouse, increased funding, an effective structure, overworked but growing contributors, an increased presence on worldwide events, improved processes on localization and quality assurance… I guess many observers as well as several insiders were thinking that once we had set up the Document Foundation as a structure and released the 4.0, things would take a course and a pace of their own. That hasn’t happened. On the contrary the word around the project was “Up!” and has not changed ever since. Another  possible reason is that once the founders -with some hindsight, I start to see it more clearly- got the structure, the governance, the main processes going, priorities started to change for the best: Discussions started to be more about resources, funding, sustainability, but the minds were freed from the worry of the next day and were able to focus on developing something great. I realize I’m painting a very nice picture, but I know that the road won’t be short and it will not be easy eiither, but judging by what this community has already overcome I am confident the Document Foundation is going to push the enveloppe on many levels in the years to come. I am truly proud of what we have accomplished so far and I would like to thank everyone who made this release possible. Happy FOSDEM!

January 30, 2014

BBC Reporting Scotland not covering the space to overtake issue on ASA ruling

This evening I happened to catch the short BBC Local News at 20:00 on BBC 1 Scotland between programmes this evening. One of the items featured was the ASA adjudication regarding the Cycling Scotland advert to improve cycling safety.

I then later recorded and watched the late evening news, which covered it in more depth (video below). It’s great that Reporting Scotland has picked up on the story, however it would have been better had they covered the “cycling in the middle of the road” issue much more than the passing remark. As someone who has had many close passes, including being knocked off my bike due to close passes, I have a significantly increased fear of being knocked off my bike by an overtaking vehicle. I am annoyed that the BBC didn’t pick up on the road positioning point more. This is rules 212 and 213 of the Highway Code, and is something that needs to be emphasised more, as often cyclists have to ride further out to avoid pot holes or to prevent a motor vehicle for passing so close that they knock the cyclist off their bike.

KT on twitter has done a little annotation of a video still to highlight why the rider in the advert is as far out as they are:

Namely so that they aren’t riding on the pavement nor in the gutter and are avoiding the potholes as per the highway code, whilst not riding on the pavement, which I’m sure someone else would complain about.

This tweet from icycleliverpool sums this space for cycling issue up succinctly:

I’ve made the relevant segment of the BBC Reporting Scotland late evening news at 22:25 available on YouTube:

It’s also worth noting that much of the cycling blogging community had complained about the original Nice Way Code adverts, however have become united against the ASA, due to both the plastic hat and road positioning issues, as pointed out in these two tweets:

Bez has made a great post on the  problems with the ASA ruling, including links to the original background, thus I don’t need to repeat them all here.

January 29, 2014

Eyes & Ears – February 2014

This month’s Eyes and Ears will not be about books, only about good music and videos.

  • Hanoi: 17 years ago, I made a student trip to Vietnam that lasted 1 month and half.

Hanoi from Matt Devir on Vimeo.

  •  La Grande Dune, by Lemongrass on its Papillon release, one of my favourites so far.

  • Blank & Jones: Don’t let me pass you by, a refine deep house track that shows the variety of genres this duo can come up with. A real massage for the ears!


Enjoy!

January 28, 2014

BBC London News highlighting confusion of Bow traffic lights

The BBC London news this evening (27 January 2014), had a segment on the new eye level cycle lights being introduced at Bow Roundabout today. I think it’s great that they are starting to be used, however the design of the traffic lights at the junction needs an overhaul as it’s extremely dangerous.

The first part of the correspondent Tom Edwards talking about it, highlights the confusing nature of the lights, whereby an average person sees a green cycle light and believes that they can proceed through the junction, as is the case with most junctions in the UK, and doesn’t realise that they have to stop at the second traffic light a few metres later. This is a horrible design and needs to be changed urgently so that it is not confusing to the average user, before someone else is killed at this junction. If the design is not changed I fear there will be another death here as it’s too confusing for the average person. A random person should be able to easily understand the design of the junction and be able to safely navigate it, otherwise the designers have failed.

The current 4 second head start is split into two parts. It’s based on 2 seconds to let the cyclists set off and another 2 seconds between the motorists setting off and getting to the traffic line. If there is a lot of cyclists, there is still potential for a motorist to crush a cyclists if they are turning left.

Ideally a new design for the traffic lights is used, which makes it safe for cyclists and pedestrians. By holding motor vehicles while cyclists get a turn, and vice versa means that pedestrians will also get a chance to cross. It will add a very small delay to motor vehicles, however if the subjective safety of the junction is improved enough then the number of motor vehicles will reduce.

The separator between cyclists and motor vehicles needs to be extended to the final stop line before the roundabout thus increasing the safety for cyclists. Also the traffic lights should be able to be phased dynamically based on the traffic levels. For example if there are suddenly a lot of cyclists and not many cars, give the cyclists more time. If there happens to only be 1 cyclist, then it’s best to change for them with minimal waiting time, but you only need to stay green for a very short time so that they can clear the junction. It will require reliable detection of bicycles, which isn’t the norm in this country at the moment, however will make a huge difference.

Finally when there is heavy rain, giving cyclists and pedestrians more time is a great idea, as it means that they’ll get less wet, and be happier cycling. The people in motor vehicles will stay dry, thus can wait a little longer with no detriment.

BBC London News report:

ITV London News report:

Bow Roundabout

Show embedded map in full-screen mode

January 24, 2014

A new web site for the LibreOffice Project

When we first started the LibreOffice Project, we had a gazilion tasks to work on. Among them, we had priorities, most of them involving the code readiness of our first version, LibreOffice 3.3. Another priority was to make sure that the native-lang communities of the now defunct OpenOffice.org project would be able to find the tools needed to work on the releases, (re)create documentation, QA of their localized builds and several other important tasks. These were some of our most crucial priorities; yet among them, you would not have noted “design a nice website”.

Background

Of course we already had a website -but beyond showing what LibreOffice was about, and presenting what the Document Foundation was about, there was no real reflection. Perhaps more damaging than a lack of in-depth thinking about it, the LibreOffice project had to integrate newcomers early on who ended up having no other interest than imposing the use of one specific CMS platform -and not just for the website, but for pretty much any other community tool. Such an option was the strongest evidence of a complete misunderstanding of community processes, as the LibreOffice project has several online tools used for specific tools (check out a few of them here and there) and keeps on deploying new ones. Long story short – we ended up with a three tiers online presence:

  • “user” or “front facing” website : LibreOffice.org and a smaller one specifically for the Document Foundation.
  • Wiki, + Communication channels such as mailing lists and IRC
  • Online production platforms: Pootle, Moztrap, Gerrit… and a few others.

The first tier, the front facing website was developed by the small website team composed of volunteers who on top of this had other tasks to work on, such as the set up of the wiki, etc. Judging by what we have now, they did a very good job coming up with a proper website. The content was the result of more incremental process. But the content was also, in part of because of a lack of focus or vision, verbose to the extreme, turning what could be a simple page with pointers into a long page of Victorian-age litterature.

Attracting Users and Growing the Community

After a few years, the limitations of the website became obvious. Perhaps more evident was the absolute lack of messaging coherence and focus. We had a standard presentation of the office suite applications; we also had a “Why” page, a concept of inherited from the old days of OpenOffice.org ; but this page was not actually accessible from the menus until you knew its exact URL; and the detailed information on it blurred the frontier with the wiki where you can pretty much find all the content of the website, only three times more detailed. As a result, you could not really tell what was special about LibreOffice until you would be reading pages and pages of text on a website. By the time we released the 4.0, new volunteers worked on a set of additional pages initially made for the release of the 4.0 that aimed to give the website a more attractive and synthetic look, announcing the 4.0 release and presenting the most salient features in an attractive way.

But this new set of pages was a temporary solution as we needed to completely redesign the website. We started with three initial points:

  • keeping the initial base: we sticked to SilverStripe, this time in the 3.0 version
  • we need a really attractive messaging, a simpler and quicker way for people to learn about LibreOffice
  • we want to use this website to attract potential contributors and grow our community.

The Making-Off

Given the amount of work that was needed the Document Foundation decided that to fund this effort. Part of it was the selection for a graphics designer. Our first surprise was that the candidates were for the most part not contributors of the LibreOffice project, but professionals who had heard our call online. We ended up picking the only Italian among the candidates, and we are very pleased with our choice. Eleonora Anzini has been working with me and Christian Lohmaier to develop this website in a relatively short time. In less than three months the specs and sketches were drafted by yours truly, published, feedback collected, a new instance of Silverstripe created so the website was ready to be developed. You can see the result today:

Capture du 2014-01-24 19:42:15

The hurdles we faced were, among other things the complexity of the SilverStripe CMS, which is quite powerful and very effective. It becomes rather complex however for special views and pages creation, although it is very easy to use for daily maintenance and content edition. The other hurdle -although it’s more a challenge than a real difficulty, was the relatively low input from the community. When we showed the website in its staging area -where it still is at the moment I’m writing the blog – most of the people actually discovered it, despite having been presented with specification documents, specs and asked all sorts of questions for several weeks. Granted the URL was not public, but some of remarks clearly came from people who had never even taken a look at the plans. At the very least, growing our community seems like a goal we must achieve, and improving our internal communications and marketing is actually going to be part of that.

Beauty & Style

I do not pretend I can create beauty and style on a website with a snap of the fingers, nor would I claim that I have great taste. But I know what’s bad taste, and I know when it’s time to get serious on style. Many Free and Open Source projects have trouble coming up with beautiful presentations and website; while ours was not bad, it could really be improved given the size and standing of the LibreOffice project. This time, we really tried to achieve just that: beauty, style, but also clarity, simple and appealing information bits, easy access, and lots of pointers to our community platforms and online tools. And while we did not focus too much on screenshots (surprisingly, not a lot of software websites have these) we tried to be really creative with getting to the point and getting our message through with nice and appealing images. So far we have some great feedback and we’re very happy about this. Next week (very likely) the website will be upgraded and enter in production. It’s been weeks of hard work but we’re proud of presenting you this new website, designed in Italy, written and planned in France, forged in Germany… and made for everyone.

January 14, 2014

Good Bye Mandriva

I am no longer working for Mandriva S.A. since the beginning of the year. I was working as a consultant on marketing as well as on the Open Source relations for the company since 2012 and it is time for me to move forward. I had a great time at Mandriva; I met a lot of great people and I learned a lot. I helped reposition the company towards a more professional audience and deeply refresh its image. But I would also like to say a few words  about the OpenMandriva project which I helped build and foster.

The beginnings of the OpenMandriva project were rough. The very rationale for the existence of OpenMandriva were not overly clear to many people. After all, the Mageia project was already booming and the justification for such a project that was aiming at building upon the Mandriva Linux legacy was weak. On top of this, the team behind the project was small, and the mission was overwhelming: to continue, as a community, the development of the linux distribution formerly known as Mandriva Linux. I will not really go into details as to how the project evolved, but  I am proud to have contributed in a significant way to build the home for this project, namely an independent French NGO (the OpenMandriva Association) and to have helped the community with establishing its governance and some of its sound principles and processes. But the question remains: why does the OpenMandriva Project matter? Why should we care?

In the world of linux  distributions you will find dozens of “me-too” distributions and other projects whose goals are ones of a niche audience, to put it lightly. But regardless of what I and others might think of these goals the important part is that the sheer existence of these distributions is a brilliant testimony to software freedom. As such we must respect that. But I do not think the OpenMandriva project is either a me-too project or caters only to a small audience of users. This project was able to build an innovative technological base (different from Mageia) around a highly customized KDE and a unique packaging format that end up giving an innovative, general purpose and user-friendly linux distribution, supported by a friendly and warm community. Will it  hurt Mageia? I know some of the Mageia people very well, and I don’t think so. I don’t even think they think that it could be the case. For one thing, the two projects are at very differtent stages of their growth and lifecycle. Another reason is that while the two projects aim at creating a very user-friendly distribution, they actually managed to do it in different ways (try both, and you will see the differences) which carves out distinctive approaches and “feels”. Assuming the two projects are fundamentally direct competitors would end up meaning that since OpenSuse and Fedora or Ubuntu also cater to broadly similar audiences only one should survive, but it would then prove a deep misunderstanding of how linux distributions work and how, again, software freedom matters in empowering anyone to code and share its code with the human kind.

I wish success and good luck to the OpenMandriva project. The folks there deserve it and I look forward to their rapid growth and a lot more exciting releases.

January 09, 2014

胡才勇:合力共推 智慧城市建设渐入佳境

合力共推 智慧城市建设渐入佳境

媒体:高新技术产业导报  本报记者  张伟报道  发布上架:2014-1-6

智慧城市建设渐入佳境">智慧城市建设渐入佳境">智慧城市建设渐入佳境" name="image_operate_53141389236178465" alt="胡才勇:合力共推 智慧城市建设渐入佳境" src="http://s5.sinaimg.cn/mw690/002DqXcfgy6FEmLYQ8Qc4&690" action-data="http://s5.sinaimg.cn/mw690/002DqXcfgy6FEmLYQ8Qc4&690" action-type="show-slide" />

  在日前召开的全国工业和信息化工作会议上,工业和信息化部部长苗圩在主题报告中指出,2013年我国信息消费规模超过2万亿元,2014年将完成制定智慧城市建设标准,开展第二批信息消费试点市(县、区)建设和智慧城市试点,进一步推动信息消费规模扩大。

  “这一信息释放出一个强烈的信号,未来几年,智慧城市建设将会达到一个新的高潮。”对此,北京软件和信息服务交易所总裁胡才勇向记者表示,智慧城市从概念到落地,从局部试点到全面铺开,在不断向纵深推进的过程中,官产学研用多方面形成合力,使智慧城市建设渐入佳境。

  城市向智慧“变身”

  2013年1月29日,住房和城乡建设部组织召开国家智慧城市试点创建工作会议,会议公布了首批90个国家智慧城市试点名单。此举标志着我国智慧城市发展进入规模推广的阶段。

  记者了解到,无论是试点名单里的城市,还是更多重视经济与信息化并行发展的其他城市,政府部门都无一例外地将智慧城市建设纳入了政务工作中的重点项目。

  在2013年下半年中国社会科学院信息化研究中心发布的《2013中国智慧城市发展水平评估报告》与《2013中国智慧园区发展水平评估报告》中,在智慧城市上布局较早、联手各行业积极推进信息化项目部署的无锡、浦东新区、宁波、上海、杭州、北京、深圳、广州、佛山、厦门,位列智慧城市发展水平评估前10名。

  记者还了解到,近期各地对智慧城市的规划和建设仍在如火如荼地进行。长沙市有关方面表示,长沙洋湖生态新城、滨江商务新城在2013年8月通过住建部审批成为2013年度国家智慧城市试点,未来3年,将投资近78亿元,将其打造成为湖南新型城镇化建设的智慧样板城区,成为中国智慧城市建设典范。与此同时,安徽省住建厅相关负责人透露,安徽省在2014年或将出台智慧城市规划,初步计划利用3-5年时间建成一批示范中心,在智慧城市关键领域取得技术性突破。此外,安徽省正计划与中科院电子所联手,合力建设安徽省智慧城市工程技术研究中心,为安徽的智慧城市建设提供智力支持。

  值得关注的是,智慧城市一哄而上,会不会千篇一律,陷入同质化的尴尬?

  “不用担心‘撞脸’。”中关村物联网产业联盟秘书长张建宁表示,每个城市都有自身的资源积累和亟待解决的问题,智慧城市建设不仅仅可以从传统意义上的“大而全”的城市建设模式上去理解,也可以从“小而美”的智慧社区模式去理解。智慧城市成功与否,关键在于是否解决了这一城市亟待解决的问题。

  “智慧城市没有样板。”张建宁说,每个城市的“脉象”不一样,自然望闻问切的方式就不一样,最后形成的智慧城市的“脸谱”也就不一样。

  “北上广深等一线城市的智慧城市建设的脚步会更快一些。”中国信息协会副秘书长傅伯岩表示,一线城市资源丰富,尤其是信息资源丰富,加上政府助推,会成为城市信息化的先行者。

  需多方发力

  随着各地智慧城市建设的不断推动,这也成为一大批IT厂商、运营商、设备商的主要投入方向。但由谁来主导发展运营,一直尚未形成统一格局。国家信息中心专家委员会主任宁家骏表示,智慧城市的几个要素中首要的基础设施建设属于电信运营商来实施,但并不意味着以电信运营商为主导进行商业推广,而是应该纳入到城市的整体发展规划中,由政府牵头联合各行业以及产业链各方企业,并基于同一标准来实现。

  “在智慧城市建设中,企业间的关系是既合作又竞争。需要整合的时候,互为补充,大家集合成一套完整的解决方案;需要竞争的时候,在同一标准上,优胜劣汰。”张建宁举例说,中关村物联网产业联盟以智慧城市为突破口,在智能交通、城市管理、应急安全、公共服务、绿色节能、技术平台、创新应用为创新成果的产业领域成为推动智慧城市发展的主导力量。联盟在产业链上下游搭建起桥梁,目的在于加强企业间的协作、创新与联动,整合、协调优势资源,促进物联网成员单位与政府的互动,进而促进产业的良性健康发展。

  “智慧城市是一个复杂的系统工程,需要依靠多方力量完成。”胡才勇表示,互联网、物联网和云计算等相关技术的成熟应用,是智慧城市建设的有效支撑;城市信息广泛的自动采集,有线、无线高速宽带无缝网络覆盖,大数据存储与分析,是智慧城市建设的基础。

  “产业链有效协同共享,规范与评价体系统一,才能实现智慧城市的高效落地。”胡才勇表示,作为全国智慧城市的推进示范,北京的智慧城市建设必然成为智慧城市全国性推进的关键点。为此,北京软交所在智慧城市方面进行了整体布局,上线了“智慧北京”的产业对接频道,以更好地推介与智慧城市相关的优质企业及优秀解决方案,促进优质企业的快速成长、优秀解决方案的落地及科技成果产业化。

  “帮助优秀企业推介优秀的示范工程、发掘一些智慧解决方案、激励为‘智慧北京’做出突出贡献的单位和个人、搭建‘智慧北京’的产业平台、促进 ‘智慧北京’的需求和产业对接,是我们努力的方向。”胡才勇说,不遗余力地推进“智慧北京”的落地,是北京软交所的责任,也是其义务所在。

  “智慧城市的IT产业正在向硬件化、垂直化、企业化、平民化发展,同时整个产业链的每一环也面临着巨大的挑战。城市提供公共服务需要众多组织机构的彼此协作。”同方物联网应用产业本部数据资源工程事业部总经理席壮华表示,基于此,城市管理者需要跨越日常机构条块分割的壁垒,跨部门、跨系统地分析问题、解决问题,从而在不增加额外资源的情况下,使城市获得进一步的发展。

  “智慧城市建设,就是要用信息化手段打破壁垒,提升人们对城市的满意度,为人们提供更智慧的服务。”席壮华说。

  信息化企业的“福音”

  不可否认,智慧城市犹如一颗散发着巨大光芒的宝石,让无数信息化企业为之沉醉。

  “‘用数据管理城市体征,用数据驱动城市运行’的城市建设理念正在指引着未来城市的发展方向。”席壮华表示,目前智慧城市建设在全国掀起热潮,同方结合当前城市管理实际需求和信息技术发展趋势,在国内率先提出了基于“大数据城市运行体征管理”理念的“智慧城市”解决方案。其核心是运用物联网、云计算等科技手段,建设基于“大数据城市运行体征的智慧城市监管平台”时刻关注城市生命线的关键要素,保障城市运行安全、平稳、有序,让城市拥有更具智慧的感知能力。

  “通过‘智慧交通’的实施,带给重庆市民的便利之一就是商圈便捷停车。”席壮华以同方打造的重庆的智慧交通为例阐述道,重庆交通路况研判系统现在已经可以通过形象、直观的交通态势图进行实时路况展示和分析,能够对整个城市交通整体运行态势一目了然,可以实时的反应当前的运行状态情况,将来还会借助系统积累的历史数据和关联数据进行预测、预判,更大程度地提高城市交通管理的及时化、科学化和预防化。

  “在智慧城市领域有诸多应用,比如智慧家庭、智慧医疗。通过4G网络建设,实现人人有宽带、处处有宽带。实现智慧教育、智能交通。”华为技术有限公司政府行业市场总监姚健奎表示,愿景很美好,但要想实现还存在很多挑战,比如城市安全、食品安全、PM2.5以及能源短缺等,这些都是在建设智慧城市过程中面临的挑战。基于此,华为公司提出一个观点,信息高速公路是建设智慧城市的必经之路,华为将建设一条信息高度共享、宽带无处不在、业务敏捷灵动、安全固若金汤的信息高速公路。 

  另据了解,在运营商方面,截至目前,中国联通已在全国26个省超过150个城市签订了智慧应用建设;中国电信则与28个省政府、179个地(市)政府签署了“智慧城市”战略合作协议,发展了超过2000万的移动用户。中国移动则以“无线城市”的理念渗透到各地的智慧建设中。

  难以预料的是,在智慧城市建设这片“蓝海”中,信息化企业争相而上,纷纷推出各具优势的“智慧战略”,谁能独占鳌头,还须拭目以待。


 青春就应该这样绽放  游戏测试:三国时期谁是你最好的兄弟!!  你不得不信的星座秘密

January 07, 2014

A New Board for a New Year

Around the turn of the year, starting in fact in November  2013, the Document Foundation had its second election for its board of directors. While this election went well it was not overly advertised either in the press, the blogosphere and even by the Document Foundation itself. It  was however a significant moment in several ways.

The board of directors of the Document Foundation is a very important body and central  point of our governance. Yet you may not  see  it in action everyday, which I tend to believe is a good thing. Basically, the board of directors is made of elected members of the Document Foundation, the actual entity behind the LibreOffice  project, and these board members are in charge, at least formally, of important decisions and of the protection of the LibreOffice project and its assets. As such it puts an important responsibility not just  on the board collectively but on each director as well.

These directors are members of the Document Foundation, and are elected by the members of the Document Foundation themselves. You can see here how you can become a member of the foundation on this page. The duties of the directors are explained in this rather boring, yet fundamental document that is our statutes.

It may be worth pointing out that several directors and founders of the LibreOffice project and the Document Foundation did not run for a second term. The reasons tend to vary among each of them, but  one of them was that as we receive funding to work on specific tasks on behalf of the Document Foundation, it is important we  separate the execution from the decision level and prevent any conflict  of interest. Another reason is that, at least from my perspective, it’s time for the “Founders” to let the ship’s command and steering wheels to our most active and talented contributors. The Document Foundation is  after all not a personal appreciation society, and renewing our directors, even partially must be taken as a good choice and as a sign of  confidence and healthy project. Because of this, this election was not just the only second election ever since the formal incorporation of the foundation (after the glorious time of the “Steering Committee”), it is also the first time where the founders start to withdraw and let the project run itself, so to speak.

Of course the day I wasn’t a director anymore, I felt a bit odd and was unsure about my feelings. But  I must say that I’m truly happy to be helping the project in my capacity today, and I’m just as happy and proud to see this new board elected. They’re all bright and great people, and I’m confident they’ll  continue  to grow and improve our project and Software Freedom on a global basis. Me? Whatever I’ll do, wherever I’ll go, I’ll always  carry LibreOffice and the Document Foundation in me. There are badges that don’t go away, but it’s so much better when you’re proud of them.

Happy New Year everyone!

PS: a big thanks to the other important body of the Foundation, the Membership Committee for its tremendous work during the election!

胡才勇:软件业转型升级需要制度创新

  胡才勇:软件业转型升级需要制度创新

 

    近日,由人民日报社《中国经济周刊》杂志社、国务院国资委新闻中心联合主办的第十三届中国经济论坛25日在北京人民日报社隆重举行。本届论坛以“经济升级与创新驱动”为主题,200多位政府、企业、研究机构人士汇聚一堂,为处于转型升级关键阶段的中国寻求创新发展的动力源,探讨多元化的成长、发展之路。

 

  人民日报社总编辑杨振武、国务院国资委副主任黄丹华作为主办方代表在大会上致辞。全国人大原副委员长成思危、著名经济学家厉以宁、国家能源局原局长张国宝、国务院国资委监事会主席季晓南等领导同志出席论坛,并围绕论坛主题发表主旨演讲。

胡才勇:软件业转型升级需要制度创新

  才勇先生出席十三届中国经济论坛高端对话

 

  受主办方邀请,北京软件和信息服务交易所总裁胡才勇先生作为软件产业的代表,出席了本次论坛,并参加“中国实业转型升级的战略选择”高端对话,与新兴际华董事长刘明忠、格力集团董事长董明珠、中国北方机车车辆工业集团公司副总裁余卫平、曙光信息产业股份有限公司总裁历军、蛟龙号总体与集成课题第一副总设计师崔维成等产业领袖一起,围绕实业转型升级的驱动力、实业创新的 “高铁模式”、 创新技术如何推广以及实业与金融的互动创新等话题开深入讨论。

胡才勇:软件业转型升级需要制度创新

  高端对话:中国实业转型升级的战略选择

 

  胡才勇总裁在发言中指出,转型升级对软件产业具有较深远的含义,因为软件行业具备特殊性,其本身就在不断的转型升级过程中,而与传统行业相融合既可以进行技术和产品创新,更可以激发管理和商业模式的创新;制度的创新尤其是审批制度的放宽更可以让信息行业百花齐放。

 

  在谈到软件产业如何与科技金融更好的结合发展时,胡才勇表示:科技金融在我国已进行了十多年,在科技和金融相结合主要有三种模式:以知识产权为主的股权融资、债权融资以及知识产权成果交易转让方面进展并不让人乐观。在即将过去的一年虽然天使投资比较火热,知识产权的质押贷款也有很大进步,但整体金额并不高。软交所正在努力建设知识产权处置平台,将和基于互联网的软件商城一道,为我国的知识产权交易尽一份力。

 

  胡才勇先生毕业于北京大学物理学系,长期致力于软件和信息服务领域技术、标准以及规范的研究和推广,是我国软件产业发展的重要见证者与推动者。至2011年5月就任北京软件与信息服务交易所总裁以来,胡才勇带领软交所团队专注于软件和信息服务领域的市场化服务平台建设和运营,通过多种方式实现信息和资源高度聚集,营造阳光透明的软件和信息服务交易环境。在他的领导下,2013年软交所的软件交易额已突破8亿,其中O2O类交易额突破2亿,为企业提供了包括交易咨询、交易撮合、交易评估、交易备案等服务,累计交易额突破2亿元,完成政府信息化项目入场交易50余个,入场交易金额超过4.2亿元;在科技金融服务方面,为超过200家企业提供了股权、债权融资服务,累计金额超过12亿。


 青春就应该这样绽放  游戏测试:三国时期谁是你最好的兄弟!!  你不得不信的星座秘密

December 28, 2013

Something new in the land of Linux distros

If you have been following the news and stories on Linux  distributions since over ten years like I have been, you tend to have  a fairly standard view -yet an educated one- about what’s going on with them, why every year since about 2002 this could have been the year of the Linux desktop, how Mandriva almost made it but  was beaten off by Ubuntu, and why Android and likely Ubuntu are triomphing not on the desktop itself but on the phones and tablets.

Going even into more details, the land of Linux distributions is a fertile place where a few seeds give an abundant harvest of derivatives, many of them focused on a particular audience or usage, others ending up becoming something completely different. Usually, this land has its big cities, the Red Hats, Suses, Debian and Ubuntu ones. Around them you’ll have the derivatives. Other distributions exist and also count for  an exciting and important part of the landscape: ArchLinux, SlackWare, Mageia, LFS, and I’m forgetting several of them here. So what’s new?

Some exciting new distributions are  coming of age, but  the best part is that in some sense these new projects validate the way the distribution model and the “economy” of Linux distributions has always been about. Let me introduce you to three new distributions I am excited about: Elementary OS, Nitrux and the Maui Project [full disclosure: I use Arch on my two machines, I've tried and installed Elementary OS several times; the other initiatives I'm talking about here are projects with no stable versions yet].

Elementary OS

Elementary has been around for some time; at least since 2011. Elementary is not yet  another re-spin of elementaryUbuntu “designed to be user-friendly”, to quote the polite description you find on several distros on DistroWatch. Elementary is indeed based on Ubuntu LTS but the top tier is very different. A new graphical stack, carefully selected software (such as Geary and Midori), new ones fully developed by the Elementary team such as the Scratch editor, a new music application give the most polished and beautiful impression a Linux distribution I have ever seen. And I’ve seen a lot, including my own desktop that I tend to tweak a lot. In the end, Elementary comes with a full installation. The system is light-weight and manages the difficult task to create an “Apple-like” experience by not being a clone of Apple. I have installed Elementary OS myself for close friends, and I can say the system is very stable and highly polished. Additional software can be added; in fact you can use the Ubuntu repositories and PPAs with Elementary which should give you no trouble in terms of software choice.

Nitrux

Nitrux seems to have started sometime in 2013. Nitrux is really three things at the same time: a Linux 409a8455f5ac2fd850a3a259a61ddb56-d52t5jjdistribution, a hardware appliance on which this distribution runs and a company. Now that is an ambitious goal to start with, and I wish the Mexico-based company a great success. Nitrux essentially focuses on the user experience to deliver an all in one “package”: an appliance with a beautiful software interface and applications that would ideally fit in a living room. Interestingly, the graphical stack  is based on Qt5 which should make things interesting and maybe somewhat KDEish. At the moment not much aside the appliance itself and part of their business model is visible: Nitrux will give back some of its revenues to the Qt5 developers.

The Maui Project

Technically speaking, the Maui Project seems to be somewhat related to Nitrux, in that its graphicalmaui stack is based on Qt5. Maui claims they’re using Wayland which is also an interesting point. It  is  unclear to me what Linux distribution base, if any, they’re using. I see their roster has several Fedora packagers, but I also see that they have some sort of an “overlay” (to speak in Gentoo terms) for Arch Linux, allowing you to essentially turn your Arch distribution into a Maui distro without installing the actual Maui project disk image. The Maui project also produces icons that are available for pretty much everyone in the Linux community – I should add that so are the Nitrux icons. I’m looking forward to try this Maui overlay on Arch as soon as I’ll have more time .

I am very excited by these three projects because they actually deliver a great user experience to the user, because they’re fun and innovative and because they fare much better than any recent Windows 7 or 8 experience in my opinion. Quite interestingly, their net contributions to the Linux stack works the same way than distributions such as Ubuntu started: the highest-level stack including all the desktop polish and applications receive all their energy and attention, while the lower level stacks such as the distribution base itself comes from elsewhere. After something like 20 years, I am amazed this upstream – downstream model still works, and works well.

Happy New Year to all of you!