Job opening for an artist/graphical designer at openSUSE Team at SUSE
- The openSUSE distribution
- Different artwork needed for the project like merchandising, banners, etc.
This work will be done together with the openSUSE community so, besides good technical skills, it will be welcome previous experience in FLOSS communities. We have at SUSE several senior graphical designers, so the candidate will work in coordination with them too.
The candidate might work in Nuremberg, Prague (preferred) or even remotely (if you have previous experience working this way). Must be available to travel internationally three to four times per year, beside some regular visits to our offices in Nuremberg, where most of the openSUSE Team at SUSE currently works.
We are an international team so English is a requirement. Other languages will be welcome. The candidate will give talks, presentations, workshops, etc. so good communication skills will be also required.
We are looking for somebody that can join us soon since we would like to begin working on our release, to be published this fall, as soon as possible.
If you are willing to work at SUSE for openSUSE, please send us your CV through our career website. Please include external and internal (SUSE/openSUSE) references, if you have them, along with links or examples of your work.
My openSUSE 12 Journal - 10: Chinese text input (fcitx)
How do you add secondary language input capabilities?
This section applies to all openSUSE and SUSE Linux Enterprise versions. Thanks to YaST, the way to enable this functionality has remained consistent over the years.
In YaST, find and select Language (under System).In the Secondary Languages section, select and put a check mark next to Simplified Chinese... and any other language of your choice.
Click Ok button and YaST will install the proper software and language package to enable this functionality.
(Optional): You might want to log out and log back in to your account, just to be sure there is a new language input icon in your System Tray. In my experience, the icon shows up without a need to log out and back in again.
Frustration #1: Where is the configuration panel?
Read more »
And here comes a gnome-panel fork...
Last week-end, just before leaving for some travel, I became aware that gnome-panel was being forked into consort-panel (btw, I commented on that post, but I guess it was a bit too late since it's stuck in the moderation queue).
Now, let me start by stating clearly that I have nothing against forks: people are free to go this way, and that's cool with me. However, I quickly got confused for three reasons: I thought it was clear that volunteers are welcome to maintain gnome-panel, I thought I had explained to Ikey in June 2012 why some changes would be blocked from entering fallback mode but could hopefully happen in a not-too-distant future, and I'm getting explicitly blamed here and there for putting roadblocks.
I usually don't mind being blamed, but I prefer when it's for good reasons ;-) Of course, as a maintainer, I reject patches. There are usually good reasons, including the fact that there's a design philosophy that a module like gnome-panel had to follow since it was fully part of GNOME. Rejecting patches is part of the maintainer job. It doesn't mean that contributions are not welcome, but I guess it can be perceived as such... Another task of a maintainer is to enable people to keep the code alive, and in the case of gnome-panel, it was clear to me that having the fallback mode as part of GNOME 3 was a blocker to do so. It took more time than I would have liked, but this is something that got fixed when the fallback mode got dropped of GNOME 3.
With this in mind, and to clarify why I got confused by the fork announcement, here's a quick timeline of events in 2012, related to the fate of gnome-panel, covering what I was aware of until the blog post from a few days ago:
- June 24th & 25th: I get a mail from Ikey about some patches he wrote to revert changes that were done in gnome-panel 3.x. I answer that this can't get in at the moment, due to the fact that the fallback mode is an official part of GNOME 3 and has to work the GNOME 3 way. I also mention that this direction of gnome-panel could change if the fallback mode is dropped from GNOME (and that I would step down as maintainer if gnome-panel becomes actively developed again). As far as I know, this mail discussion (six mails) is the only time I've interacted with Ikey until I commented on his blog post a few days ago (no other mail, nothing in bugzilla; there might have been some irc chat, but I don't keep irc logs).
- June 25th: I start a thread on desktop-devel-list to see if we still need to keep the fallback mode as part of GNOME 3.6, and I invite Ikey to participate in the thread (in the private mail discussion mentioned above). A decision is taken, and it's to keep the fallback mode for now.
- end of August: I start the DropOrFixFallbackMode feature page for GNOME 3.8, because I feel the fallback mode in GNOME is not getting enough love. This feature page explicitly mentions that
some people would like to improve components of the fallback mode to work differently
, and that dropping the fallback mode would enable these people to step up and push for what they'd like to do.
- November 9th: the release team announces that the fallback mode is being dropped from 3.8.
- November 21st: I blog about the fallback mode being dropped, and invite people to become maintainers.
- December 5th: I send a mail to a small group of people who I know might be interested in keeping some fallback components maintained, to help them start on their work. Clearly, I failed to include Ikey in the discussion, but only because I had forgotten about our discussion from June.
The ironic point here, at least to me, is that it's Ikey's mail that triggered my push for the fallback mode to be dropped from official GNOME so people could work on gnome-panel with more freedom. Which is what seems to be wanted.
Anyway, let me take this as an opportunity to remind everyone that people are welcome to become maintainers of gnome-panel. It'd be preferable to maintain it in the GNOME infrastructure, but I guess even just forking it with full history on gitorious/github would work. No need to rename, no need to follow the GNOME 3 design, etc. If full forking+renaming is preferred for some reason, in the end, that's fine; I'd be curious to know what good reason exists, though.
And as usual, you're welcome to blame me for X, Y or Z :-)
My openSUSE 12 Journal - 9: Upgrading to Stable Kernel 3.7.4
You know what? This is the best thing I could have ever done for my laptop!!!
Special Thanks to Mike Veltman, appreciate your guidance and encouragement.
What made me do it?
I have been using openSUSE 12.2 for over 3+ weeks and have noticed some performance issues from a desktop productivity perspective. This was confirmed when speaking with Mike and also confirmed by a comment from Jack Bauer on my previous blog entry.
Scenario: Try copying a large amount of files (total file size of say over 1Gb) from your hard disk to an external USB drive. During the file transfer (doesn't matter if you initiate the transfer via commandline or GUI), the rest of the desktop (except the mouse pointer) is practically dead and unresponsive. At best, a simple task of opening a new tab on Firefox to surf will take over 10 seconds. If you want to open LibreOffice to read a doc/spreadsheet, you can forget-about-it.
This was initially tolerated because I would schedule large file backups in the evening after work. However, it is starting to get to me because I don't recall earlier openSUSE 11.3, 11.4 and 12.1 ever giving me such issues. The final straw came this week and its my Windows VM... it was running well but I have to put PGP whole disk encryption on the VM. As expected the Windows VM slowed down but I also noticed its slowing my host as well.
How I did it?
Read more »
Run over by a truck.
I spent a little over a week in the hospital. They implanted metal rods into the fibula and tibia as opposed to casting it. I prefer the rods since I think that'll make things more usable quicker. So now I have to be pushed around in a wheelchair, or hobble about with a walker. The latter I can't do very much of at this point. I imagine I'll be more mobile in about a week.
I've had some articles brewing. Among them you can anticipate the following:
How to make Gnome 3 act more like Gnome 2 simply using extensions.
Crossover for Linux vs. WINE, is it worth it?
Fluendo DVD player review.
Fluendo Codec Pack review.
Steam on Linux beta review.
ownCloud Sync Client 1.2.0 final
Yesterday, ownCloud Client 1.2.0 was released. You can get it from here. We worked on this since end of november last year, you might have seen my other blogs about the beta versions we had for this release.
What is interesting about the release from a more technical point of view? Here are a couple of examples.
One of the things which often was complained about was the performance of the client. Performance is a very broad term, so we have to examine the details: Many people felt like its a performance problem that former clients polled the local file system for changes on the MacOSX and Windows platform. That was recommended from other projects which have experience with going through large file collections. QFileSystemWatcher seemed not to be designed for this usecase.
Polling was ok for desktop computers with up-to-date hardware, but on devices running from batteries this was a energy drain. Good that we could fix that with 1.2.0 using native implementation of change detectors on Windows and MacOSX. They detect changes within a file system tree. If a change is detected, a sync run is started. But note, this is only for local file systems. Detection of changes on the server is a different story which has to be told as well.
Another performance problem was within the file upload which is done by a HTTP PUT request. Month ago (pretty after my start at ownCloud) I implemented it using a tmp file in between. That means, the source file was copied to a tmp file, and from that it was processed to the request body. Improvement was needed and we changed the code to directly read from the file descriptor of the opened source file.
Another thing that was improved with 1.2.0 is the error reporting to the user. Former versions of the client sometimes provided error messages which were not really accurately describing the problem. The reason for that was that csync uses errnos (yes, the ones from errno.h) to name errors as csync maps everything to a POSIX file interface. That surely works as long as you’re on a kind of file system. But it’s hard to map HTTP communication problems onto that. So we decided to add our own “custom” errnos and enhance the whole idea to use these to describe problems. That works more accurate now.
The next things on the list are for example a more convenient setup dialog for the client. Also we will get away from the kind of hard coded target file name on the cloud. A better network recognition will also be next as well as better handling of big files. And more…
Thanks a lot to all who helped to get 1.2.0 finished! It is big fun to work in such a great community :-)
openSUSE Conference 2013: Geeko se prepara!!!
Hoy la comunidad de openSUSE se alegra y se enorgullece al anunciar la Conferencia de openSUSE 2013 , oSC13. Desde el 18 de Julio , la comunidad de openSUSE se congregará en la tierra donde hace 2500 años, los filósofos comenzaron la Época del Razonamiento. Humildemente tomando ejemplo de esos grandes hombres, trabajaremos, disfrutaremos del ambiente de camaradería de unos con otros, debatiendo y disfrutando de la tecnología para el futuro de la humanidad. Los filósofos griegos formaron parte de una revolución que cambió el mundo. TTambién nosotros somos así, y por lo tanto ,bajo de la lema “Power to the Geeko”, nos reuniremos y trabajaremos en nuestra propia revolución del Software Libre!
Sobre la conferencia
Desde el próximo 18 de Julio de 2013 y hasta el 22 de Julio, Tesalónica la segunda ciudad más grande de Grecia y el lugar donde ha tenido lugar “ 15 UNESCO World Heritage Sites” será la ciudad anfitriona de la quinta Conferencia del openSUSE . Una vez más, hablaremos y discutiremos sobre temas relacionados con nuestra distribución, la tecnología libre y de código abierto y todos aquellos temas relativos al “mundo abierto” en general, invitando a participar a las personas tanto de dentro como de fuera de nuestra comunidad de openSUSE.
El lema de la conferencia de este año es “El poder de Geeko ‘, queriendo hacer hincapié en la naturaleza ascendente de nuestro movimiento de Software Libre (un tema que cuadra perfectamente con el país donde crecieron las primeras democracias.). Tesalónica ofrece muchas oportunidades de divertirse un montón! La ciudad cuenta con hermosas playas y una animada vida nocturna, así como también cuenta con buena comida y bebida. Esperamos mucho de socializar entre las sesiones técnicas y código fuente. Esperamos compartir juntos entre sesiones técnicas y de programación.
Sobre Tesalonica y la communidad Griega
Grecia, o la República Helénica, es un país del sur de Europa, al sur de la península de los Balcanes. Se encuentra en la encrucijada de Europa, Asia y África, y está rodeado de mar – el mar Jónico, el mar Egeo y el mar Mediterráneo – con una gran cantidad de islas, es el destino ideal para las vacaciones de verano.
Salónica
Tesalónica es la segunda ciudad más grande de Grecia y la capital de la región central de Macedonia. El tráfico aéreo hacia y desde la ciudad es servido por el aeropuerto internacional de Macedonia tanto para vuelos internacionales como más cercanos. La ciudad es famosa por sus festivales, eventos y una vibrante vida cultural en general, y es considerada como la capital cultural de Grecia. Eventos como la Feria Internacional de Salónica y el Thessaloniki International Film Festival se celebran anualmente, mientras que la ciudad también alberga la más grande reunión bi-anual de la diáspora griega. En 2014 Salónica será la Capital Europea de la Juventud. Para 2013 la revista National Geographic incluye Salónica entre los primeros puestos como destino turístico en todo el mund. Tesalónica es bien conocido tanto por la vida nocturna como por la comida deliciosa.
Comunidad
La comunidad griega, conocida cariñosamente como “Greekos” dentro de la comunidad de openSUSE, se unieron de una manera semi formal hace aproximadamente 3 años. Este grupo de dedicados seguidores locales se reúne de forma regular y promueve el uso de openSUSE y el software libre dentro y fuera de Grecia. Con la experiencia de la organización de los “openSUSE Collaboration Summer Camp”, que se ha repetido varios años y la participación de los “Greekos” en la puesta en marcha de las conferencias anteriores de openSUSE, fue una decisión fácil para la junta openSUSE apoyar a Salónica para realizar la primera conferencia de openSUSE que es organizada únicamente por la comunidad.
El equipo local de voluntarios está trabajando con gran dedicación para proporcionar una experiencia increíble para todos los asistentes a oSC13.
Apoyo a los viajes
El Programa de Apoyo al viaje de openSUSE volverá a ofrecer ayuda a aquellos contribuyentes de openSUSE que deseen asistir a la conferencia de openSUSE, pero tienen limitaciones financieras. Siguiendo el procedimiento descrito en la wiki del programa de ayuda al viaje http://es.opensuse.org/openSUSE:Programa_de_ayuda_al_viaje puedes enviar tus solicitudes de ayuda al equipo de TSP desde el 23 abril al 3 mayo. Puedes mandar tu solicitud antes, pero ten en cuenta que el equipo de viaje asignará financiación para viajes de acuerdo con las directrices e informará a todos los solicitantes antes del 13 de Mayo. Esto debería ser tiempo suficiente para hacer tus reservas.
Financiación y registro de asistentes de apoyo
La conferencia de openSUSE es un evento muy grande para la comunidad para organizar y orquestar. Además de innumerables horas de trabajo voluntario para hacer este gran evento, el apoyo financiero de los patrocinadores es muy valioso y necesario. La financiación de dinero se utiliza para pagar la ubicación del evento, pagar los costos de los principales ponentes, material de marketing y otros gastos de la conferencia. La comunidad openSUSE es muy inclusiva y eso se nota en nuestros eventos, en la participación de muchos que no están directamente involucrados en openSUSE. Además, la conferencia openSUSE proporciona una oportunidad única a los patrocinadores no sólo se pongan en contactocon miembros de la comunidad de openSUSE, sino también con otros miembros de las distintas comunidades de software libre
Tienes la disponible la oportunidad de participar en la financiación de la conferencia. Para más información por favor póngase en contacto con nuestro Gerente Conferencia openSUSE patrocinio con consultas (solo en ingles):
Izabel Valverde
Sponsorship Manager
openSUSE Conference Organization
Más adelante se pondrá a disposición de quien quiera un folleto con más información y las opciones predefinidas. Sin embargo, le animamos a trabajar con nosotros para satisfacer sus necesidades de patrocinio.
Registro y entradas
Al igual que en años anteriores, la inscripción y asistencia a la conferencia de openSUSE es totalmente gratuita. Las entradas para apoyar el evento se pueden adquirir al precio de $ 50 para las entradas de aficionados y $ 250 para las entradas de profesionales. Compra tus entradas en la tienda SUSE:
América del Norte, América Latina y Asia Pacífico: Ticket de soporte, ticket Profesional
Europa, Oriente Medio y África: billete y billete de Apoyo Profesional.
El dinero de la venta de estos billetes se utilizará para financiar el evento y ayudar con el Programa de Asistencia de Viaje openSUSE para posibilitar que acudan tantos simpatizantes como sea posible al evento. Los partidarios y los titulares de boletos profesionales recibirán una sorpresa especial gracias a la llegada. El apoyo del evento a través de la venta de entradas es parte vital de la financiación del evento.

El sitio web de la conferencia se puede encontrar en conference.opensuse.org y será actualizado regularmente con nueva información. La organización de oSC13 requiere la estrecha colaboración de muchas personas que están distribuidas por todo el mundo. Este es un ambiente emocionante y si te gustaría participar en la organización del evento eres más que bienvenido. Suscríbete a nuestra lista de correo o presentate en una de nuestras reuniones de IRC (anunciado en la lista de correo).
Los filósofos griegos formaron parte de una revolución que cambió el mundo. Así somos, y así, bajo el lema de “Poder para el Geeko”, nos reuniremos y trabajaremos en nuestra revolución. Estate atento a próximos anuncios y más adelantos y noticias sobre este gran evento!
Power to the Geeko!
Post original
Post victorhck
LibreGraphicsMeeting 2013 coming soon
Once a year all or most of the applications around graphics from the free software world come together and work on new ideas and features for there software. The event where they come together is called LibreGraphicsMeeting. Oyranos participated always the last years in that meeting and got a lot of feedback and ideas from it. This year the LibreGraphicsMeeting will take place in Madrid/Spain and there is still time to submit interesting presentations around free software and graphics. As always the LibreGraphicsMeeting tries to collect some money for travel costs of the participating developers.
But there is more, last year we tried to get Gustav Gonzalez to the LGM and it didnt happen. This year Sirko started an campaign very early, as Gustav needs an visa for Spain he has to show flight tickets and accomodation for get it until 15th of February. Now we have nearly the sum for the flights, we looked for flights and we only need arround 200$ for them and another 150$ for accomodation. In case you dont know who Gustav Gonzalez is….
He is the main developer of Tupi, an cool QT 2D animation tool. Which makes it very easy to draw animations. Tupi is an fork of KToon where nobody works on anymore
But what he has achieved since he forked it, is amazing. Meeting other developer from graphic applications would surly good for him and bring him new ideas for Tupi. SO it would be definitly a benefit to send him to LGM.
















