Fedora Planet

I’m currently thinking about going to FOSDEM 2009. Flight’s not too costly and a room for two persons in the Renaissance Brussels Hotels is available for a nice price during weekends.

But before I consider to go to Brussels, I’m looking for someone to share the room with. Who wants to volunteer?

Current I maintain both zhcon and fbterm.

Even zhcon development is inactive at the moment, but it is still remembered and even embraced by many CJK console users. The pros of zhcon over fbterm:

1. Provides vga mode, no need to enter framebuffer mode.


2. Has various buildin input methods.


3. Supports GB2312 GB2312, GBK, etc.

Cons of zhcon

1. Support utf8 through iconv gb2312 -> utf8, it causes characters missing


2. Input methods fails on x86_64

To sum up, if you are using GB2312 encoding on a i386 machine, then zhcon works for you. But if you want utf8, or you have x86_64 machines, then bad luck.

On the other hand, fbterm supports utf8, no need to mock font setting, and the latest version support screen rotation! This is convenient to me, as I no longer need to bend my neck to check the output.

Although fbterm still haven't have officical input methods, but given that fbterm is under active development, and Peng Huang mentioned that he has a successful story of using ibus in fbterm, I am confident that fbterm will replace zhcon.

Hello everybody,

The Galette Team is glad to announce the release of Galette 0.63!

For those who don't know Galette yet, it is a Project to manage the members of your association. Galette is a Free software, licensed under the GPL licence. In French, Galette means Extremely Sophisticated but so Efficient On-Line Membership Manager (in French, a "Galette" is a sort of cake, usually French people eats the "Galette des rois" for the Epiphany).

Here are the updates for the new version:

• Added transaction management,
• Added dynamic fields management, to add more fields and to translate their labels easily,
• Members can now self subscribe to your association,
• Use of the Smarty template engine, for which the rewriting of all the html pages as compliant XHTML was necessary,
• Update ADODB 4.7.1 to 4.9.2,
• Use of gettext for translations,
• Added Spanish translation (the translation is not yet over),
• It is now possible to upload a personal logo,
• So much bugs corrections.

The packaged installation program allows you to update your previous Galette version. The update is then much more easy to achieved.

You can now download the latest version from: http://download.gna.org/galette/galette-0.63.tgz

Here are some links that may be useful:

• official Galette website
• Frequently Asked Questions
• Galette's install howto
• Galette's update howto

In case of problem, you can report bugs through the Gna! interface.

If you are interested in the projet, feel free to join Galette's development team!

I would like to thank all the development team, who made this 0.63 version possible, and I would like to thank Tuxfamily (web hosting service) as well as Gna! (source code repository, tasks, bugs and chat user interface). I also want to thank all the person who have tested this version again and again and which allowed us to correct some unexpected problems.

The very kind Galette Development Team.

Bonjour à tous,

L'équipe de Galette est heureuse de vous faire part de la sortie de Galette 0.63 !

Pour ceux qui ne connaissent pas encore le projet, Galette (qui signifie Gestionnaire d'Adhérents en Ligne Extrêmement Tarabiscoté mais Tellement Efficace) est un projet libre sous licence GPL de gestion d'adhérents à destination des associations.

La liste des modifications pour cette nouvelle version est la suivante :

• Ajout de la gestion de transactions,
• Ajout de la gestion de champs dynamiques, pour ajouter des champs supplémentaires, ainsi que la possibilité de traduire les libellés de ces champs,
• Les adhérents peuvent désormais s'inscrire eux-mêmes,
• Utilisation du moteur de templates Smarty, pour lequel la ré-écriture de toutes les pages html au format XHTML a été nécessaire,
• Passage de ADODB 4.7.1 à 4.9.2
• Utilisation de gettext pour les traductions
• Ajout de la traduction en Espagnol (la traduction n'est pas encore terminée)
• Possibilité d'envoyer un logo personnalisé,
• Ainsi que de nombreuses corrections de bogues.

Le programme d'installation livré permet la mise à jour depuis une version antérieure de Galette, la mise à jour en est fortement simplifiée.

Vous pouvez récupérer la dernière version à l'adresse : http://download.gna.org/galette/galette-0.63.tgz

Et voici quelques liens qui pourraient vous être utiles :

• le site officiel de Galette
• la foire aux questions
• la documentation d'installation
• la documentation de mise à jour

En cas de problème, vous pouvez rapporter les bogues via l'interface de Gna!

Si le projet vous intéresse, n'hésitez pas à rejoindre l'équipe de développement de Galette.

Un grand merci à toute l'équipe sans laquelle cette version n'aurait pas pu voir le jour, ainsi qu'à Tuxfamily (hébergement du site) et Gna! (dépôt du code source, interface de gestion des bogues et tâches, liste de discussions). Merci également à toutes les personnes qui ont testé et re-testé cette version et permis de corriger certains problèmes qui avaient échappé à l'attention de l'équipe

La gentille équipe de développement de Galette.

Não faz muito tempo que lançaram o Fedora 10 e já está aberta a votação para a escolha do codinome do Fedora 11, quem tiver uma conta no FAS, a CLA assinada e estiver participando em algum grupo dentro do projeto, poderá votar, parece que essa eleição vai ser bem disputada. Entre as opções há uma surpresa, o codinome "Brasília" está no meio, esse codinome foi sugerido pelo Tulio Macedo (Teseu). As opções são essas:

1 - Blarney

2 - Brasília

3 - Claypool

4 - Duchess

5 - Euryalus

6 - Indomitable

7 - Leonidas

8 - Zampone

leia mais

Sometimes it happens via dialog, sometimes it happens via notification bubble, but either way my computer can be quite chatty.

I'm wondering if there are any guidelines for designing programs to be good citizens in their chattiness. Some questions that I have that maybe could be used to come up with a set of guidelines if there aren't any:

• Classify the message you're sending out. Is it a critical message, a warning, or simple information? Is it hardware-related, security-related, long-running task related (task failed or task succeeded), do I need to take any action from it or is it not possible to take action from it?


• What should the user do to address the issue, if there is any action to be taken? Can you allow the user to say, "always treat this type of action this way without bugging me?"


• For each message classification, what is the most appropriate iconography needed for the message? Is there any special wording needed? Should it be displayed on a frequent basis? What basis? Or should it be displayed just once?


• Allow users to 'unsubscribe' from particular types of notification. But perhaps don't make it all or none (although I may want to opt-out of all messages from a particular app, I should be able to turn it off at a more fine-grained level.) In each alert dialog/notification bubble, allow users to one-click visit the notification preferences for that (or all?) applications so they can quiet it. Also, should there be both 'shut up now' and 'shut up forever' buttons? If not which should be more prominent?


• Alerts are going to the desktop, to the currently-logged in user. Are there users of the system who aren't logged in who would want to be kept notified of the alerts? Are there users logged in remotely who might want an alert on the shell? How do desktop notifications/alerts translate?


• How do you enable users to take action on alerts? What if there are many alerts from the same application? How do you consolidate them so that users can perform the same action on multiple alerts at once but in a well-informed manner (or at least as informed as the user wants to be)?


• When do you decide to alert a user vs. take action on their behalf without bugging them? To what level should the user be allowed to dictate this if they want more or less notification/control than provided by default?

Just some half-formed thoughts anyway. I would be curious to see if anyone is familiar with guidelines on these. I've looked in a few UI books and guidelines (GNOME HIG, Apple UI guidelines, MS UI guidelines) and haven't found any yet but maybe I'm not looking in the right spots.

OLPC is now working hard on their 9.1.0 release, and their roadmap is very clearly outlined. Well done to all the OLPC people for their ever-increasing efforts to keep external folks in the loop.

There are two items to which interested Fedora contributors should be paying particularly close attention.

First: Rebase 9.1.0 on Fedora 10. This is a big one. OLPC has made a strong commitment to move as much of their work as possible into Fedora packages upstream. At latest count, there are approximately 25 packages in the OLPC-4 repository that are forked from their F10 counterparts. We can use all the help we can get from the Fedora community to help bring these packages into mainline Fedora. Peter Robinson in particular has been a big help, but we can always use more. Remember: every hour an OLPC developer spends maintaining a forked package is an hour they cannot use to save the world.

Second: Run Fedora applications on the XO. This is another big one. Users all over the world love Sugar, but its limitations can be painful. Many users want to run Fedora applications that simply don't look good under Sugar. There are some good approaches to solving this problem -- replacing Matchbox with a tiled window manager, for instance -- but it's a problem that can use more eyes.

If you are interested in helping with either of these problems, leave a comment and find us at FUDCon.

Voici les toutes dernières actualités concernant le monde de l’Open Source et des Logiciels Libres. Au programme cette semaine : le piratage du SSL, Android sur des notebooks, et Wikipédia qui récolte de l’argent.

La news de la semaine concerne un groupe de hackers qui a réussi à venir à bout du protocole SSL. Ces derniers ont utilisé un cluster de 200 Playstations 3 et exploité une faille md5 pour délivrer de vrais certificats SSL. Source.



Les autres news en vrac :

• Le site wordpress-fr propose de télécharger gratuitement un mémento pour Wordpress. On y retrouve la liste des principales fonctions utilisées par le célèbre CMS. Cliquez ici pour télécharger la fiche.
  
  
• Des bidouilleurs ont réussi à installer Google Android sur un netbook. On s'attend donc à retrouver rapidement ce système d'exploitation sur des EeePC et autres mini-portables. La méthode pour y arriver tient en une trentaine de commandes et elle est lisible ici.
  
  
• Wikipédia a ré-collecté 6 millions de dollars pour son fonctionnement. Ce projet a donc encore de beaux jours devant lui. Source.
  
  

Article original écrit par Sébastien Bilbeau et publié sur Tux-planet | ©Copyright - 2005 Toutes reproduction interdites.

I watched the first two episodes of "Leverage" yesterday. I can't decide if it's good or not yet, but there is one conclusion I have reached.

At first, I couldn't put my finger on it. It seemed familiar, yet not.

And then, right in the middle of the second episode, it hit me.

They've brought back The A-Team, but instead of a crack commando unit, the good guys take their parts from Ocean's Eleven.

planet.classpath.org moved servers and if done correctly nobody will notice (except for the new server having a totally sweet favicon ). But if you do happen to notice anything odd with the planet after the move, then please do yell and scream.

Those using Anjuta's Glade3 plugin in Fedora 9 (or GNOME 2.22) and Fedora 10 (or GNOME 2.24) must have found themselves with a frozen Anjuta on more than one occasion. Please update your glade3 package to glade3-3.4.5-2 for the fix. Since this was caused by due to a missing patch in the upstream Glade3 3.4.x releases this has likely affected other distributions too.

GNU Parted got itself the ability to probe Ext4 file systems. Here is the patch against the current Git master.

Thanks to the Fedora Infrastructure team, we have a mailing list for multiseat discussions as well as a Trac instance at multiseat.fedorahosted.org to help get the Multiseat feature into shape for F11.

If you're interested in Multiseat, I invite you to join the mailing list and -- if you can make it -- the hackfest session at FUDCon F11.

Before FUDCon, I'm going to run a set of tests on the current X drivers with various card combinations (at least NVIDIAx2 and multilayer, plus ATIx2 if the equipment arrives in time).

Image by luc legay via Flickr

Este post que encontré a través del twitter de AngelVengador,  trata sobre la conclusión de un padre que “bromeó” en internet (twitter) que mataría a su hija, porque lo estaba hinchando después de un día muy agitado

A parte de toda la discusión sobre si el bromear respecto a un tema tan delicado es correcto o no (que casi todos los comentarios se remiten a eso), es importante notar que al publicar cosas en internet, no tenemos la misma libertad que cuando lo hacemos con amigos.

Las redes sociales son herramientas muy poderosas, pero de doble filo. Hoy mismo las usan para ver perfiles de personas, y buscar gente adecuada para trabajo, pero ya hoy en día pueden ser usadas para determinar comportamientos u otras cosas.

Asique, cuidado con lo que postean o dejan por internet, porque eventualmente, les puede rebotar de vuelta… ¡Y quizas lleguen los carabineros a tu casa!

Watch what you twitter, big sister is watching. « Spin Me I Pulsate.

O Projeto Fedora vem novamente convocar a comunidade para ajudar no processo de escolha do nome para a próxima release dessa distribuição, o Fedora 11.

De forma democrática, como é comum nesses processos de votação do projeto, o nome será escolhido após a apuração das notas oferecidas pela comunidade para cada nome que foi previamente sugerido também pela comunidade.

leia mais

So I'm back to work after several days of blissfully forgetting about the existence of Windows (which I'm required to use on my $DAYJOB laptop). I come back, and within 20 minutes (at least 5 of were spent rebooting since the machine was in a weird state it gets in sometimes with the Contivity client), I come upon this marvelous example of fail. What exactly is the problem here? I'm still scratching my head at how spectacular this error message is. This is not doctored in any way, came straight from Outlook 2003:

東西每次暫時放下了，儘管只是很短的一段時間，都好像重新去理解另一個人的記錄一樣，是不是記憶力開始衰退的跡象？

續上回， add_input() 傳回負值，表示 self.update_candidates() 也傳回否值 (add_input() 最後一行)。

還是不行，必須應用一些 debug 工具去提高效率： pdb

import pdb;
pdb.set_trace()
(when pgm encounters pdb.set_trace() it will start tracing)

彈出 (pdb)

- 'p': print [var]
- 'n': next
- 'l': list
- 'q': quit
- 'c': countinue
- 's': step in
- 'r': return

timechen119 @ #python.tw (freenode.net) 教了顯示行號的方法：

python -m trace -t --ignore-dir /usr/lib/python2.5 xxxdaemon.py

找到了更土法的方法，以 ibus 在 gcode 上的 dev guide 的步驟為依據。 在 consold 裏：

$ ibus-setup （先把 daemon 跑起來）

$ GTK_IM_MODULE=ibus gedit （在 gedit 上測試 ibus）

完成後在 console 殺掉進程：

$ killall python

（或者有更好的命令，殺 python 也許有殺掉的嫌疑 :P）

在 table.py 的任一處加入 print "xxxx" 就能得知到達那一行代碼。

請教了 ibus 作者 phuang ，在 terminal 運行：

$ ibus-daemon && ibus-ui-gtk && ibus-conf && ibus-engine-xxxx

或者 DBUS_DEBUG=true ibus-engine-table ，就會列出 dbus client 的 exception。

（那個 ‘四步曲’ 執行了，不過沒有東西發生。）

ibus-setup = ibus-daemon + ibus-conf + ibus-ui-gtk +ibus-x11 ?

用 ibus-setup -> GTK_IM_MODULE=ibus gedit 的方法加上 pdb.set_trace() 還是不行， gedit 會停在 set_trace() 的地方，不過 (pdb) 沒有在 console 出來，而是死當。

_update_ui() = _update_lookup_table() -> _update_preedit() -> _update_aux()

get_aux_strings() = get_input_chars()

get_input_chars() = self._chars[0] + self._chars[1]

能組字的會一直放在 self._chars[0] 直至不能組的會放在 self._chars[1] ，'*' 還是直接被 commit 。

ok 了，在 table_mode_process_key 裏抓 valid_char 裏加另一個 or 來抓 '*' ，再在 add_input() 裏再加個 elif 把 '*' 加到 self._chars[0] ，現在 '*' 出現在 aux 。

'*' 雖然在 aux ，但是被忽略：應該在以 self._chars[0] 呼叫 select_words 的地方加工：

當 '*' 在 self._chars[0] 的時候，用 select_words_wildcard() 而不是 select_words()，這之後也要改進成使用者選項之一。

... db 好像被弄爛了 ...

The Fedora 8 end-of-life is scheduled for this coming Wednesday. If you haven't made the switch to Fedora 9 or Fedora 10 yet, now is the time!

However, if you're using a Multiseat system, your options are limited, because Multiseat is not well supported iin F9/F10. We're working on improving the situation for Fedora 11. In the meantime, here are some suggestions for those stuck on F8:

• Use virtualization to limit your exposure to network security issues. Create a virtual machine running a newer version of Fedora, and have all outside connections (e.g., ssh, httpd) directed to the virtual machine. This permits you to continue running the Multiseat system on F8 while using updated versions of the network services packages.
• Fully update your system before Wednesday, and test thoroughly.

And from all the F8 Multiseat users: a special plea to the Pulseaudio folks to fix bug 462200 for F8 before EOL -- us Multiseat types particularly need Pulseaudio.

We now have 3 camcorders and 1 mixer with mics lined up for FUDCon. We need another 3 camcorders to cover all the tracks. Any volunteers? -> Please contact Clint Savage (herlo) or myself (ctyler).

As was just announced on the announcement mailing list*, the voting ballots for the Fedora 11 release name are now open. To vote, you just need to be a member of one non-CLA group in our Fedora Account System. Voting ends at 2359 UTC 2009-01-09, so get your vote in quickly! (There’s nothing wrong with campaigning for a name of your choice either, if you’re so inclined.)

The Fedora release name is sort of a fun Easter egg for the community. Ultimately, it’s simply a way that anyone who participates in Fedora can have a say in what we call the next release. For Fedora 10, that name was “Cambridge,” which incidentally was Red Hat engineering’s internal release name for the Red Hat Linux 10 product that never was. That release ultimately became Fedora Core 1, “Yarrow.”

All the names on the ballot were submitted by the community, run through a series of searches to identify probable trademark conflicts, and then approved by the Fedora Board and Red Hat’s legal department, which did a more thorough search for conflicts and risk identification. The entire submission process was recorded on the wiki, where you can find details on all the suggestions.

Each release name is linked to the previous release name, and that link must be different from the link that came before it. We try to keep the links non-obvious and (arguably) clever wherever possible. In the past, the links have become a little more generic, but given the fairly good slate of names that’s on the ballot this time, I hope that will be less of an issue going forward.

Thanks again to Nigel Jones for coordinating our election process and to everyone who submitted a name for consideration!

* Not on it? join here.

Long time no post even though much happened. I had my right hand broken (actually only the ring finger, but that affected it’s neighbors and the whole hand was in plaster. But more to this later. I’ll write this post to summarize some things I wanted to write in the time since my last post but wasn’t really able to (writing continuous text without lots of typos is your enemy #2 with only your left hand - #1 is using any sort of email client since they need lots of changes between mouse and keyboard…unless you use a console based one or know _all_ shortcuts…I do neither).

I organized and conducted the FAD EMEA 2008 in November, together with the help of people like Andreas Rau and Max Spevack. I want to thank everyone who attended this event and made it a (in my eyes) huge success. It’s been a great chance to speak about important topics, see some new faces and have a good time together. Between all the work, we also had good (Chinese and Swiss) food - pretty much everyone loved the Raclette but many left the Vermicelle behind. I’m not sure if people were just stuffed or if they just didn’t like it. I’m sure it was worth the try and at least the table of the fellow Italian ambassadors made sure that their plates were empty to the last bit.

Unfortunately, I was stupid enough to fall down a stone stair on Friday evening during the FAD (i.e. just a few hours after it had begun). Andreas Rau left our working room just to fetch something…I think some cups. When he didn’t return for quite some time I started to wonder where he is or if something happened. So when I had a chance to sneak out (sorry wonderer that it was during your topic) I left the room to give Andi a call. Will it was still ringing on the other side, I made some steps in this and that direction - as I and many others always do in that situation. Unfortunately, the University of Basel does not feature automatic light activation and I was too lazy to look for a light switch because I saw no need for it. I figure I was mistaken in that thought. Taking 2-3 steps in that direction, I stepped onto nothing. Until my brain realized that this is a stair, it was too late to catch myself and so it came that I flew down the stairs (11 hard steps). I’m not sure if I passed out early on or if I have a blackout but between realizing that it’s a stair and getting up from the bottom I don’t remember anything (lucky me). Everything afterwards is a long story not worth telling in detail. I get up, got to a toilet, later called Andi to help me because I felt terrible and my nose wouldn’t stop bleeding, puzzled whether to go to the hospital or not (it’s now been after midnight), walked to the nearby hospital, got some x-ray done. Result: foot broken, finger broken, deep wound on the nose, experienced a major hit against my head. The fixed me up quickly in order to survive the weekend and told me to go to a hospital on Monday to see after my hand which might need an operation.

Next day, I continued with the normal FAD program which finished sometime Sunday afternoon. On Tuesday, I had an appointment with the doctor at the hospital. Monday the week after, I had my finger operated and 6 weeks later I was able to use my full hand again. Today, I hardly notice that I ever broke my foot or finger, where the latter is still a bit sensitive to big pressure.

In the time being at home (because I couldn’t properly do my $DAYJOB with only my left hand) I learnt to create SRPMs/RPMs and got some packages approved while others are still on their way to that point. Shortly before the accident, a friend of mine gave me a job advertisement from the Swiss Federal Institute of Technology Zurich (ETHZ) he found in a newspaper. The ad was titled ‘Red Hat Linux Specialist’ and sure caught my attention (and my friend’s before, since he knew I was looking for a linux engineering related job and that I live in the Red Hat / Fedora world). I didn’t exactly meet what was asked from a applicant to the job but decided to give it a try anyway. I didn’t have anything to lose, right? So I sent them a small letter, accompanied only by my curriculum vitae (CV). I was then invited to a job interview which turned out not too bad in my eyes. I have no professional work experience in the Linux field yet and as I mentioned I didn’t fulfill what they looked for in an applicant. But a huge plus were my connections in the Fedora and with that also Red Hat community as well as my private interest and activity in Fedora/Linux.

Some time passed, until I heard anything new from the ETHZ. I was then invited to a day in their offices in order to get to know the team, see how good we blend, exchange some knowledge and ideas, see the job I’m applying for and so on. I was told they’re doing the same with other applicant as well so I did not yet have the job but at least, I was in step #2. Well, that day was lots of fun and the I liked the job I was applying for even better after seeing better what it involved than before.

About two weeks later, I was invited to step #3 - the final step, actually. I figure that meant I was their choice #1 but I didn’t have the job at that time. It’s been similar to the first interview, but with a bit more details on the important things between an employer and an employee. It went well, similar to the first one and less than 24h later I had the job.

They told me, that they want me no matter whether my current employer lets me go earlier than the contract says or not which was great since there was a huge chance that he would but there was no guarantee for it at that time. I spoke to my employer at the same day (we had a meeting that day anyway) and we agreed on ending it at the end of January (instead of March).

Starting on February, I’ll be an employee of the ETHZ and be part of a Red Hat Linux team. I hope I can bring in some more Fedora things (like EPEL) and also give the community something back (maybe a Fedora install event or a FUDCon or something like that). Apparently, they’ll also send me to the yearly Red Hat Summit in the USA which I wanted to go to for such a long time already.

On another note, this also means that I’ll move from Bern to Zurich - as soon as I find a flat there that suits me and my wallet well.