The last week it was a little hectic around the Chromium webbrowser. Initially I announced that the Chromium webbrowser would move from the openSUSE OBS to Packman due to dependencies on ffmpeg. Shortly after my announcement I was contacted by Ludwig Nussel from SUSE with the question what exactly the issue was and if it was not possible to find another solution in order to keep it part of the openSUSE Distribution. 

• to the kernel (many of those features are in 3.7 or in upcoming 3.8):

• convert the kernel as a EFI executable (it will be used to store kernel signature)
• UEFI variable access
• UEFI clock support (nice to have)
• UEFI getvideomode (if we want flicker-free boot)
• UEFI reboot (we already have 4 other way to reboot a system, why not add yet another one ;)
• KMS drivers (for old chipsets like Matrox, AST).
• sign main kernel
• sign all in-tree kernel modules
• generate a private/public key pair to be used out of tree modules
• add Secure Boot support in KExec / KDump and Xen (optional)
• disable hibernation in Secure Boot mode (or have a secure way to save / restore suspended system)
• add signature check in kernel
• to bootloader:
• package shim loader
• modify grub2 so it uses shim loader to check kernel signature at boot
• to Build Service:
• to be able to build external kernel modules (think KMP) using the private/public key generated at kernel build
• but do not allow this key to be used for any random KMP build (otherwise, you defeat the purpose of signing the module)
• to userspace tools:
• package xf86-video-modesettings, for graphics chipset with non-accelerated KMS drivers
• add support for signature check in modutils / kmod
• package tools to sign kernel / modules
• package tools to manage UEFI variables and keys
• to the installer / DVD image
• maybe display some warnings about installing a system in Secure Boot mode (not 100% sure we should do this)
• maybe signing the initial installer (and make sure it can't load non-signed modules)
• ensure the DVD image has shim + grub2 as bootloader when booting on UEFI system
• and we also need to do the signing part:
• if we want Secure Boot to be transparent to users, we need our shim loader to be signed by the authority handling UEFI key, ie Microsoft
• this requires some legal paperwork (getting MS developer account, getting a Authenticode certificate, etc..), some obligation (making sure you can't circumvent Secure Boot once Linux is booted) and once it is done, sending shim loader to be signed by MS and package the result.

What about creating  an airline company called “Geeko Air”? Is an awesome idea , isn’t it?

Well , this post is neither a thought about creating a new company nor a new way to make money.

So let’s see what it is. Before 10 days i had to travel from Madrid to Paris for my Practicum. At this case casual dress is a mandatory , so i wore a Geeko shirt (thanks Bruno :)). While passing the security control , the security guy (named Josue) saw the openSUSE badge (the front one) on my shirt and asked me ” Do you work for openSUSE?” my response was “No i contribute to the openSUSE Project”. The security control stopped and an interesting conversation begun. Josue told me that he was an Ubuntu user , but now  uses openSUSE and he is very satisfied. Without any thought i gave him the only openSUSE Promo DVD i had.

So Geekos , we have to know that our Project is great and also please make the Geeko Shirt available at openSUSE Shop (for more info ask Bruno)

Introducción

El proyecto openSUSE ha participado con éxito en la conferencia LinuxCon Europa 2012 [durante 5 y 8 noviembre 2012]. Dos embajadores [Zoumpis, Diomidis] estuvieron como representantes de la comunidad de openSUSE durante la conferencia. Vamos a ver lo que sucedió allí!

La víspera de la conferencia

El domingo por la tarde hicimos nuestra primera visita a la sede LinuxCon. Nuestra primera misión fue visitar el estand de registro y obtener el ID y T-Shirts, luego fuimos al stand de SUSE / openSUSE y empezamos a desempacar los premios SUSE. Allan Clark también se unió a nosotros para ayudar con la preparación de stand.

On Sunday evening we made our first visit at the Linuxcon Venue. Our first mission was to visit the registration desk and get our ID’s and T-Shirts, then we went to the co-hosted (SUSE/openSUSE) booth and started to unpack the SUSE goodies. Mr. Allan Clark also joined us to help with the booth setup.

Dia – 0 [05/11/2012]

Nuestro día comenzó temprano, a las 7.30 horas. Fuimos directamente al Hotel Fira Palace, donde se celebró la LinuxCon. Asistimos a las conferencias magistrales de la zona por la mañana: Fomento de la experiencia del usuario por Mark Suttleworth Evernote y por el que ejecuta sus propios servidores Linux en lugar de “La Nube” por Dave Engberg.

No hemos asistido a más presentaciones , porque tuvimos que colaborar en el stand. En el estand, nuestro trabajo principal fue dar la bienvenida, ayudar a los visitantes. También tuvimos mucha promoción con las personas el día lunes y obsequiamos: openSUSE dvd, gorras, pegatinas, mecheros, folletos openSUSE comunitarios y memorias USB. Finalmente tuvimos un concurso para ganar 4 bolsas para portátiles de SUSE y el sorteo se realizó el miércoles.

La retroalimentación que recibimos de los asistentes en la conferencia fue muy bueno y amigable sobre la distribución openSUSE y la comunidad, por supuesto. Las preguntas más comunes que la gente hizo fué:

a. ¿Cuál es la diferencia entre SUSE y openSUSE?

b. ¿Qué software y cuales son las características que están incluidas en el openSUSE 12.2 DVD Promo?

c. ¿El openSUSE 12.2 tiene soporte para la arquitectura ARM?

d. El material promocional es libre?

Además nos dieron una sugerencia muy buena y prometedora sobre el Open Build Service (OBS).

Presentaciones-Asistencia

1) Abrir Métricas de fuente comunitaria: Consejos y Técnicas para la Medición de la participación de Down [] Puppet Labs Foster

2) El gigante de TI Vending Machine por Daniel Roberts Ridruejo [BitNami]

Dia -1 [06/11/2012]

A medida que pasó el primer día y nos encontrábamos en el standad, fué el momento adecuado para asistir a más presentaciones.El día comenzó como el anterior, asistiendo a las conferencias magistrales: Abierto Plataformas de Nube Fuente Marten Mickos por [director general de Sistemas de eucalipto] y la importancia de Linux en Intel por Imad Sousou [OTC, Intel]. A medida que la fiesta de lanzamiento de openSUSE estaba a punto de tener lugar informamos a la gente.

Tiempo de la fiesta!

Después del día de la conferencia, nos fuimos de fiesta. Muchas personas de la comunidad de KDE locales asistieron a la fiesta, pero gente de la Conferencia, así (Alan Clark, empleados de HP SUSE, Director de Linux Magazine [edición Española]). Además gente que ha leído el anuncio que estaba allí. En total éramos 15 personas hablando sobre el openSUSE 12.2, de las nuevas características y, por supuesto, nos divertimos mucho haciéndolo..

Presentaciones-Asistencia

1) (Tutorial) Edificio FOSS Nubes, Parte I – Sebastien Goasguen, Citrix

2) (Tutorial) Edificio FOSS Nubes, Parte II – Sebastien Goasguen, Citrix

3) OpenStack Pruebas de integración continua en servidores Cloud – James E. Blair, HP

4) Arrastrero: un nuevo enfoque para el almacenamiento en caché SSD – Hannes Reinecke, SUSE

5) El proyecto OpenStack y la Fundación OpenStack – Eileen Evans, HP

6) Desastres Resiliencia en Linux – Lars Marowsky-Brée, SUSE

7) Escala de un Open Source Community: La forma en que creció el Proyecto OpenStack – Monty Taylor, Gerente de Automatización e implementación de HP

8) Declaraciones a futuro el desarrollo: la próxima evolución en Enterprise Linux Desarrollo de Software – Ralf Flaxa, VP de Ingeniería de SUSE

Dia – 2 [07/11/2012]

El día comenzó con una entrevista a Linus Torvarlds, sin necesidad de presentación! Muchas preguntas se hicieron, muchas de ellas fueron de cómo Linus ve el futuro de Linux, que incluye o que tendrá el próximo núcleo y, por supuesto, hubo un debate acerca de los dispositivos embebidos brazo.

Presentaciones-Asistencia

1) Linux: ¿Hacia dónde vamos – Linux creador Linus Torvalds y Linux de Intel y Tecnólogo de código abierto, Dirk Hohndel

2) Tomar el miedo a la Contribución: Mentoring de código abierto – Stephen Hemminger, Vyatta

3) CouchDB y CouchApps – Roman Geber, B1 Systems GmbH

4) Gestión de recursos con Linux – Bruno Cornec, HP

5) CONFERENCIA MAGISTRAL: Got Talent de Linux (sesión de clausura)

Al final del segundo día de la conferencia era el momento de desmontar stand y hacer el sorteo de las bolsas de SUSE. Cuatro (4) bolsas para portátiles fueron regaladas!

Dia – 3 [08/11/2012]

Como no existía puestos o sitio libre para asistir a cualquiera de las presentaciones que se llevan a cabo.

Así que elegimos asistir a talleres y Gluster Día yocto Desarrollador del proyecto.

Conclusión

Así pues, tenemos tantas cosas que compartir, muchos recuerdos y mucho entusiasmo para transmitir a todas las personas de la comunidad openSUSE. Pero nosotros no vamos a ser chicos Chatterbox. LinuxCon es una de las mejores experiencias que un fan de Linux / desarrollador / usuario, etc puede conseguir. Discursos motivacionales, gente entusiasta sobre el software libre y equipamiento, talleres de primer nivel de los desarrolladores de todo el mundo, literalmente, todo lo relacionado con Linux y sus derivados. Dispositivos integrados y yocto tuvieron mucha afluencia o visitas.

Todo lo que podemos decir es que LinuxCon es un sueño que se hizo realidad para nosotros!

Aquí usted puede encontrar fotos de la conferencia [1] , [2].

No fallback mode in GNOME 3.8

As announced by the release team two weeks ago, the fallback mode will be gone in GNOME 3.8. The decision was taken after some discussion on the mailing list back in June and in October, as well as some discussion during Boston Summit 2012. We also have a wiki page detailing the discussion arguments.

In my opinion, the biggest issue we had with the fallback mode is that, with only a few cycles, it quickly became clearly not tested enough, and lacked manpower for proper evolution along with other GNOME 3 changes. This resulted in a much lower quality than what we expect from GNOME. Moreover, several applications actually started requiring Clutter, and therefore didn't work anymore in a real fallback manner (ie, where you have no proper 3D acceleration); this means the fallback mode, when really used as a fallback, was not offering a fully usable desktop, and would be considered more like an alternative shell than a fallback mode.

Where does this leave us?, you might ask.

Well, for a start, GNOME 3.x had several iterative cycles to bring tons of improvements. Many users who were using the fallback mode because they didn't like the GNOME Shell experience are now happy with 3.6. But we're going an extra step starting with the next version: there is an explicit goal of having the project provide a set of extensions to help even more people preferring the fallback mode experience. The tentative list of what the extensions would provide is classic alt-tab, task bar, minimize/maximize buttons, and a main menu. This effort is being publicly tracked, so everyone can participate: if you're interested in contributing to these extensions, don't hesitate, I have no doubt help will be welcomed! Update: this topic is being discussed on desktop-devel-list right now!

There will also be work on improving GNOME 3 when running with software rendering. Of course, llvmpipe was a good start, and llvmpipe itself is getting better and better. But in addition, there are plans to offer a reduced resources mode, with fewer animations, that would be used in different circumstances, including when using software rendering. This should really improve the performances under llvmpipe.

There might be cases where these improvements will not be good enough in 3.8 (or with the Mesa and llvmpipe versions available at that time), resulting in a GNOME version that people might not consider acceptable in terms of performance or hardware support. Things will improve with time, obviously, and 3.10 will solve more and more issues; hence I would recommend to people hitting such issues to stay with 3.6 for a few more months.

All in all, the community is working on having future versions of GNOME, starting with GNOME 3.8, offer an improved alternative to the fallback mode.

Future of gnome-panel (and other fallback components)

Of course, this raises the question of what happens to the components of the fallback mode: gnome-applets, gnome-panel, gnome-screensaver, metacity, notification-daemon, polkit-gnome, etc. These components don't necessarily have to go away: they're just not part of what the GNOME project officially releases, and people are welcome to keep working on them. It's really up to each maintainer.

As for myself, I do not intend to keep maintaining gnome-panel after 3.6.x. I did a 3.6.2 release a few days ago, and it might well be what I consider my final release. If there's a strong push for some patches, there could be a 3.6.3 tarball... So, if you want to keep gnome-panel alive, contact me and you can become maintainer. As long as I either know you, or I can see that you have some minimal coding abilities, you'll get the maintainer hat for free :-)

Now, I believe a group of people could well adopt all the fallback components and keep building a great desktop, on top of other GNOME 3 bricks. They wouldn't even have to restrict themselves to what the GNOME 3 vision is (which is something that blocked some people from seriously contributing to gnome-panel). I don't think it'd be actually too much work: the code is already there! Of course, there would be some compatibility bits removed from other GNOME modules that would need to be moved elsewhere, but in most cases, it's really just about moving the code, not re-implementing things.

To be honest, I would really have loved if the MATE people had taken such an approach (maybe it's not too late?). I think it's a more reasonable effort than effectively forking all of GNOME 2, including obsolete technologies, as the amount of work is much more reasonable.

I'm eager to see if a group will step up to keep alive this old code, which represents thousands of hours from many of us! I wouldn't use it, but it would still make me happy :-)

Almost three years passed since latest release of QJson. A lot of stuff happened in my life and QJson definitely paid for that. I have to admit I’m a bit ashamed.

So here we go, QJson 0.8.0 is out!

What changed

A lot of bugs has been smashed during this time, this new release will fix issues like this one and this in a nicer way.

QJson’s API is still backward compatible, while the ABI changed.

Symbian support

Some work has also been done to get QJson work on the Symbian platform. The development happened a long time before Symbian was declared dead.

Currently I do not offer any kind of support for the Symbian platform because IMHO Symbian development is a mess and given the current situation in the mobile world I don’t see any point in investing more efforts on that.

Obviously Symbian patches and documentation are still accepted, as long as they don’t cause issues to the other target platforms.

QMake support

QJson always used cmake as build system but since some Windows developers had problems with it I decided to add some .pro files. That proved to be a bad choice for me since I had to support two build systems. I prefer to invest my time fixing bugs in the code and adding interesting features rather then triaging qmake issues on Windows. Hence I decided to remove them from git.

If you are a nostalgic you can still grab these files from git. They have been removed with commit 66d10c44dd3b21.

Relocating to Github

I decided to move QJson’s code from Gitorious to Github. Github’s issue sysyem is going to replace Sourceforge’s bug tracking system.

I currently use Github a lot, both for personal projects and for work, and I simply love it. I think it offers the best tools in the market and that’s really important to me.

QJson’s website and mailing lists are still going to be hosted on Sourceforge.

I think that’s all from now. If you want more details about the changes introduced take a look at the changelog or checkout QJson’s website.

Quem já precisou recortar uma imagem no OpenOffice sabe que não é tão simples como no micro$oft office. Por exemplo, se você está usando o Impress (editor de apresentação), é necessário clicar no Menu >> Formato >> recortar imagem e, então, na janela que abrirá, você deve ir clicando ou digitando os valores para que o corte da imagem possa ir sendo feito. Não é coisa de outro mundo, mas para um iniciante no OpenOffice isso pode ser uma dor de cabeça, já que no concorrente é muito simples (não preciso descrever aqui ….)..rs

Para facilitar esta tarefa, existe uma extensão para o OpenOffice que é a CropOOo, que nos permite trabalhar como no concorrente… ela instala uma barra de ferramentas que te permite clicar na imagem e ir selecionando com o mouse a área a ser cortada. Uma vez que selecionou a área basta apertar a tecla ENTER que a imagem é cortada.

Abaixo uma imagem da ferramenta na minha barra de tarefas. Espero ter ajudado. um abraço!

Oi pessoALL! tudo bem? estou “meio sumido” devido estar trabalhando em muito projetos e, por isso, acabei tendo pouco tempo para escrever no blog.

Devido alguns problemas de compatibilidade com a suíte de escritório LibreOffice om alguns documento do Micro$oft Office, resolvi experimentar o OpenOffice. Pesquisei um pouco sobre comentários de outras pessoas e resolvi tirar o LibreOffice que é padrão no Linux Mint 13 e instalei o OpenOffice na versão 3.4.1.

A suíte de escritório Apache Openoffice é uma boa opção para uso no lugar da suite office da Microsoft. ela conta com muitos recursos para texto, planilhas, apresentações, desenhos e apossui até um editor de fórmulas matemáticas.

Através do Synaptic (gerenciador de pacotes) a versão disponível é a 3.3.0, mas, como eu gosto muito de ter as versòes mais atuais, eu resolvi baixar direto da página do desenvolvedor: http://www.openoffice.org/download/

Neste link você baixa a versão em português-brasil e abaixo descrevo como proceder para instalar esta versão que é muito simples.

Antes de tudo recomendo que remova o LibreOffice, pois quando tentei instalar o Open junto com o Libre tive alguns problemas e somente o Libre abria. Então com o libre removido….

1. Reveja os Requisitos de Sistema
2. Baixe a sua versão favorita de Linux Apache OpenOffice
3. Comente informações úteis e opções de instalação no Guia de instalação. (este não é um passo obrigatório, pode pular e fazer depois..)
4. Descompacte a imagem baixada para preparar a instalação.
   O seguinte comando deve funcionar: tar -xvzf "linux package name".tar.gz
   onde “linux nome do pacote” é a parte inicial do arquivo que você acabou de baixar.Isso irá criar um diretório de instalação (pt-BR).
   O nome do diretório de instalação será provavelmente a abreviação do idioma para o conjunto de instalação, por exemplo, en-US.
5. su para root, se necessário, e navegar para Apache diretório de instalação do OpenOffice (o arquivo descompactado).
   Você provavelmente vai precisar ser root para executar o comando rpm para instalar o software.
6. cd para os RPMS subdiretório do diretório de instalação.
   Você deverá ver um monte de rpms aqui e um sub-diretório chamado “desktop-integração”.
7. Instalar esta nova versão, digitando rpm -Uvih *rpm .
   Por padrão, isso irá instalar / atualizar Apache OpenOffice em sua /opt diretório.Alternativamente, você pode usar um pacote de instalação GUI, referência ao diretório de instalação e instalar todos os rpms no nível superior. Isso também pode ajudá-lo na determinação quaisquer problemas de dependência, se existirem.
8. Instale os recursos de integração de desktop para sua configuração.
   cd para desktop-integration no diretório de instalação,
   e, dependendo do seu gerenciador de pacotes / sistema, instale a interface do desktop apropriado usando RPM.
9. Finalmente, inicie o Apache OpenOffice 3.4.x para garantir que ele está funcionando.

Com poucos minutos de uso, percebi que o OpenOffice tem um desempenho melhor e abriu as planilhas melo do que o LibreOffice, pelo menos em meu notebook.

Fica a dica… teste e use por sua conta e faça seu comentário.

Uma abraço!!