La Free Software Foundation ha puesto en marcha una campaña para pedir a Microsoft que publique como software libre Windows 7.

Microsoft ha anunciado que deja de dar soporte a Windows 7, por lo que las personas que estuvieran utilizando este sistema operativo tendrían que actualizar a otra versión para tener un sistema operativo seguro, fiable y con software disponible.

Ya pasó con Windows XP y pasará con las siguientes versiones que publiquen. Muchas comunidades de GNU/Linux han hecho un llamamiento para que ese cambio sea a GNU/Linux.

Pero la Free Software Foundation ha aprovechado esta oportunidad para lanzar un reto a Microsoft y a su campaña en favor del “código abierto” que tanto proclaman y de los pasos que han dado en los últimos años.

Aquí tienes una versión/traducción del artículo que la Free Software Foundation han publicado en inglés en su web

Fue la semana pasada cuando Windows 7 pasó a mejor vida.

Aunque no podemos decir que estemos de luto, hemos pasado este tiempo rememorando en el legado de abusos a los usuarios de Windows 7, y cómo se refleja en el cambio de todo de Microsoft en los últimos años.

Por una parte, ellos han declarado claramente que Microsoft “ama el código abierto” (sic).

Pero las cosas no siempre ocurrieron de esta manera, y podemos agradecer a activistas de todo el mundo el hacer que el mensaje del software libre sea tan fuerte que no se pueda ignorar.

En los titulares hemos visto muchas historias de personas que se sentían mal por el fin de soporte y una rabia justificable por ser forzadas a actualizar. Microsoft deja a sus usuarios huérfanos, pero no tienen por qué sentirse así. Hay otra opción.

Microsoft ha dado algunos pasos en la dirección correcta, como publicar pequeñas pero importantes partes de componentes de Windows como software libre. Queremos hacer que vayan más allá.

Necesitamos que Microsoft pruebe al mundo que su “amor” por el software libre no es solo una campaña publicitaria y que no están solo recolectando los beneficios del software libre para explotar a los usuarios.

Microsoft puede probar eso publicando Windows 7 bajo una licencia de software libre. La historia del software libre nos ha enseñado que el software no tiene por qué expirar y que incluso puede ser escrito para durar cincuenta años.

Y ahora que esta versión de su sistema operativo ha llegado al “final de su vida”, no tienen una buena razón para no hacerlo.

Necesitamos tu ayuda para pedir a Microsoft que ofrezca Windows 7 a la comunidad. Nuestro objetivo es conseguir que 7.777 seguidores que tomen una posición por la libertad del usuario. Firma la petición aquí.

Además de firmar la petición, también puedes:
* Compartir la imagen de #UpcycleWindows7 para mostrar tu apoyo a la campaña.
* Compartir en las redes sociales que tu has firmado la petición. Escribe tu propio mensaje o utiliza los nuestros:

El soporte de Microsoft a Windows 7 ha acabado, pero su vida úti no tiene por qué acabar. Únete a esta llamada a Microsoft para que permita reutilizar Windows 7 firmando https://u.fsf.org/upcycle #UpcycleWindows7 by signing

Aunque por mi parte ya hace años que no utilizo Windows en mi casa, quiero que se retraten y demuestren si de verdad “Microsoft loves open source” Yo firmaré ¿y tú? Si te animas pincha en este enlace:

• https://www.fsf.org/windows/upcycle-windows-7

In this text I share to members of the openSUSE community, succinctly / objectively, the reasons why I am applying for the openSUSE board member seats. I emphasize that I do not consider myself better than the other candidates, and even these carry attributes / characteristics to also occupy that position.

Mini Bio: Born in Bebedouro (interior of SP) on 05/27/1972, Founding partner of the company OITI / NETi TECNOLOGIA since 1996. First contact with technology in 1983, when 11 years old, in the city of Bebedouro (interior of SP). Takes Linux seriously, researches and works with biometrics and computer vision since 1998. Experience with facial biometrics since 2003,artificial neural networks and neurotechnology since 2009. Inventor of CERTIFACE technology, more than 100 lectures given, 14 printed articles published,more than 8 million page views in the 120 articles published on http://vivaolinux.com.br. Maintains open source projects and official linux packages, commiter openCV, OWASP SP Board Member, Global Innovator Intel, Mozillians Member and FIA Teacher.

Below are the main reasons that led me to apply for this position:

• I’m in love with openSUSE and SUSE;
• I take Linux seriously on the market since 1998;
• I defend the collaborative spirit and the Free Software community;
• I breathe openSUSE (at home and at work);
• I grew up with the Free Software community;
• I work with several contributions to the community (some evidence in this link);
• Ability and network / relationship in the market to promote openSUSE in Computer Vision and AI projects (Intel, Microsoft, IBM, Google and others);
• And the most important openSUSE is LIFE!

Role of the board

My goal is to increase the presence of openSUSE in the corporate market, and to make local companies trained to support this market. With this, in addition to evangelizing openSUSE Linux, we will have more job creation, increased circulation of financial resources and more revenue for the local government and, consequently, more resources for investment in basic services (health, education, security and others).

More information: https://en.opensuse.org/openSUSE:Board_election#Detailed_explanation_of_all_phases

As you may know, every single Email to admin@opensuse.org is forwarded into our ticket system at https://progress.opensuse.org/. As this Email is meanwhile widely known in the public Internet, we see a lot of Spam in our ticket system. So far, we mainly ignored that stuff and simply deleted the Email/Ticket.

But our ticket system is not really planned to become a ticket system: we run Redmine, which originally is intended to be a project management software. The ability to create issues (or tickets, as we call them) in the system by sending an Email was not really intended in the beginning. So the ability to detect and mark Spam Emails as such simply does not exist. Even worse: every Email results in a user, that get's created automatically, to allow us to send out an Email to this person as answer to his ticket.

All of this is not really problematic: you learn to deal with it. But with over 14,000 "users" in the database (and over 17,000 real tickets), the system started to become slow. So we invested a bit of our time and looked into the user list. Good for us: most of the Spammers seen to have special days to submit their stuff. And even more interesting: they do it at the same time from multiple accounts!

So we ended up in setting huge user blocks to "locked", which will not allow them to use the same Email account again to send their Spam to us - and on the other side this fastens up our database, as most queries only search for "active" users (which is the default). Maybe we can use the gathered Email addresses to feed a Spam filter - later, once we have one.

As good and simple as this message is: there is a small potential that we might have blocked/locked some real user accounts in our Redmine instance with this simple workaround. We tried our best and already excluded a lot of domains we trust (like '@opensuse.org') in the query. But we can not guarantee that we did not block your account at the moment, as there are simply too many (to us) unknown openSUSE users. And we want to spend more time on fixing your tickets than on finding out if one of the 10,000 now locked accounts is a false positive.

If you are locked out of https://progress.opensuse.org/ (and ONLY on this system/URL), please get in touch with us.

Neste texto disponibilizo para os membros da comunidade openSUSE, de maneira sucinta/objetiva os motivos pelos quais estou concorrendo a vaga para membro do conselho openSUSE. Ressalto que não me julgo melhor que os demais candidatos, e inclusive estes carregam atributos/características para também ocupar tal posição.

Mini Bio: Nascido em Bebedouro (interior de SP) no dia 27/05.1972, sócio fundador da empresa OITI/NETi TECNOLOGIA criada em 1996, primeiro contato com tecnologia em 1983 com 11 anos de idade. Leva o Linux a sério, pesquisa e trabalha com biometria e visão computacional desde 1998. Experiência com biometria facial desde 2003, redes neurais artificiais e neurotecnologia desde 2009. Inventor da tecnologia CERTIFACE, mais de 100 palestras ministradas, 14 artigos impressos publicados, mais de 8 milhões de acessos nos 120 artigos publicados no Viva O Linux. Mantenedor de projetos opensource e pacotes linux oficiais, commiter openCV, Membro do Conselho OWASP SP, Global Innovator Intel, Membro Mozillians, Docente do núcleo ProINFO da FIA.

A seguir os principais motivos que me levaram a concorrer esta posição:

• Sou apaixonado pelo openSUSE e SUSE;
• Levo o Linux a sério no mercado desde 1998;
• Defendo o espírito colaborativo e a comunidade de Software Livre;
• Eu respiro openSUSE (em casa e no trabalho);
• Eu cresci com a comunidade de Software Livre;
• Trabalho com diversas contribuições para comunidade (algumas evidências neste link);
• Habilidade e network/relacionamento no mercado para promover o openSUSE em projeto de Visão Computacional e IA (Intel, Microsoft, IBM, Google e outros);
• E o mais importante openSUSE é VIDA!

Principal plano de trabalho no Conselho.

Tenho como meta, aumentar a presença do openSUSE no mercado corporativo, e tornar as empresas locais treinadas para suportar este mercado. Pois com isto, além de evangelizar o openSUSE Linux, teremos mais geração de emprego, aumento da circulação de recursos financeiro e mais receita para o governo local e por consequência mais recursos para investimento em serviços básicos (saúde, educação, segurança e outros).

Mais detalhes neste link: https://en.opensuse.org/openSUSE:Board_election#Detailed_explanation_of_all_phases

Version in ENGLISH HERE!

Le gagnant du concours du logo de la conférence openSUSE + LibreOffice est Kukuh Syafaat d'Indonésie.

Le logo "Fresh Community Spirit" ("Nouvel esprit communautaire") de Kukuh est le gagnant et fait partie des 10 logos soumis dans le cadre du concours. La "Mystery Box" sera envoyée à Kukuh pour le dessin gagnant.

En 2020, openSUSE et LibreOffice organiseront une conférence commune du 13 au 16 octobre à Nuremberg, en Allemagne.

Le comité d'organisation de la conférence commune de cette année a sélectionné le design gagnant lors d'une réunion le 20 janvier. Le logo représentait une adéquation idéale pour la conférence puisque openSUSE et LibreOffice combinent leurs conférences communautaires pour une seule année en 2020 pour célébrer le 10ème anniversaire de LibreOffice et le 15ème anniversaire du projet openSUSE.

Maintenant que le logo a été annoncé, des dépliants et des affiches peuvent être créés pour aider à faire la publicité de l'événement. Le site web de la conférence sera bientôt disponible sur events.opensuse.org et l'appel à communications débutera le mois prochain.

Ce logo de la conférence openSUSE + LibreOffice ne doit pas être confondu avec le logo du 10e anniversaire de LibreOffice annoncé sur le blog de LibreOffice.

Traduction de l'article publié sur openSUSE News

Tumbleweed es una distribución “Rolling Release” de actualización contínua. Aquí puedes estar al tanto de las últimas novedades.

openSUSE Tumbleweed es la versión “rolling release” o de actualización continua de la distribución de GNU/Linux openSUSE.

Hagamos un repaso a las novedades que han llegado hasta los repositorios esta semana

El anuncio original lo puedes leer en el blog de Dominique Leuenberger, publicado bajo licencia CC-by-sa, en este enlace:

• http://dominique.leuenberger.net/blog/2020/01/opensuse-tumbleweed-review-of-the-week-2020-04/

Durante esta cuarta semana del año 2020 se ha publicado cinco snapshots y esto teniendo en cuenta que se han descartado 2 por problemas en los tests QA.

El test openQA ha salvado a los usuarios de que les fallase chromium dentro de una sesión de KDE/Wayland por ejmplo. Estas cincon snapshots fueron: 0116, 0117, 0118, 0121 y 0122.

Las actualizaciones más importantes que han traido son:The releases contained these updates:

• Mesa 19.3.2
• systemd 244
• Dracut 049+git118: el servicio de eliminación de kernels ha sido eliminado en favor de un paquete separado, basado en comandos de zypper. Ese servicio todavía no está habilitado (la llamada de zypper interactua negativamente con los complementos de notificaciones de PackageKit, pero se están preparando los parches para esto)
• Linux kernel 5.4.12 y 5.4.13
• Qt 5.14.0
• Poppler 0.84.0

Y entre las actualizaciones que llegarán pronto a los repositorios de openSUSE Tumbleweed, se puede destacar:

• Python 3.8
• Eliminación de python 2
• gettext 0.20.1
• libcap 2.30:
• GNU make 4.3
• KDE Plasma 5.18 (actualmente se está testeando la versión Beta)
• Linux kernel 5.4.14+

Si quieres estar a la última con software actualizado y probado utiliza openSUSE Tumbleweed la opción rolling release de la distribución de GNU/Linux openSUSE.

Mantente actualizado y ya sabes: Have a lot of fun!!

Enlaces de interés

• • • ¿Por qué deberías utilizar openSUSE Tumbleweed?
    • zypper dup en Tumbleweed hace todo el trabajo al actualizar
    • ¿Cual es el mejor comando para actualizar Tumbleweed?
    • Comprueba la valoración de las “snapshots” de Tumbleweed
    • ¿Qué es el test openQA?
    • http://download.opensuse.org/tumbleweed/iso/
    • https://es.opensuse.org/Portal:Tumbleweed

——————————–

Dear Tumbleweed users and hackers,

During week #4, we have released five snapshots. And this, despite having discarded two snapshots for QA issues. openQA saved our users from crashing chromium inside a KDE/Wayland session for example. The five snapshots released were 0116, 0117, 0118, 0121 and 0122.

The releases contained these updates:

• Mesa 19.3.2
• systemd 244
• Dracut 049+git118: the purge-kernels-service has been removed in favor of being in a separate package, based on zypper commands. That service is as of now not yet auto-enabled though (the zypper call negatively interacts with the PackageKit notification applets, fixes are being prepared)
• Linux kernel 5.4.12 & 5.4.13
• Qt 5.14.0
• Poppler 0.84.0

This was quite a bit of what was reported last week as being in the works. Staging/integration tests are curretnly busy with these changes:

• Python 3.8
• Removal of python 2
• gettext 0.20.1
• libcap 2.30: breaks fakeroot and drpm
• GNU make 4.3: has some major incompatibilities. Observe fallouts at in Staging:O.
• KDE Plasma 5.18 (currently beta being tested)
• Linux kernel 5.4.14+
• netcfg moves a few files from /etc to /usr/etc (services,. protocols): currently, AppArmor is blocking access to those files, so we need some changes there

The Contents

• Partitioner: An Actionable Overview Screen
• Not only Partitioner: Numeric Sorting in Tables
• Improving the NFS Module
• Package Installation:
  • Installation Progress Improvements
  • Doomsday Preparations: Retracted Packages
  • Qt Package Selection Gets Faster

An Actionable Partitioner Overview Screen

Until now, the Partitioner landing screen has been useful to have a big picture of the devices in your system and as a shortcut to jump directly to the device page just with a double click over it. But, do you know what? From yast-storage-ng 4.2.74 on you can work directly with devices from that screen similar as you already do in the more specific pages, through the contextual actions added below the devices list. That means, for example, no more jumps to Hard Disks just to add a new partition nor resize an existing one. Enjoy :wink:

More details: PR 1024

Numeric Sorting in Tables

We have improved the sorting for tables in libyui, the UI library of YaST. So far columns were sorted directly by the text displayed, e.g. the device name or the size in the expert partitioner. For some use-cases this resulted in unexpected ordering, e.g. partitions of a disk were ordered “/dev/sda1”, “/dev/sda10”, “/dev/sda2”, and sizes were ordered “1 GiB”, “2 TiB” and “4 GiB”.

Now it is possible to provide a sort-key for every table entry which is then used instead of the displayed text. This allows the expected ordering and is already implemented for the tables in the expert partitioner as the two pictures below show.

Improving the NFS Module

YaST offers a specific module to configure your NFS shares. Similar to every YaST module, you can run it by executing yast2 nfs in your terminal, or by launching it from the YaST Control Center. But there is another cool way to use the YaST NFS module: opening the Expert Partitioner!

The Expert Partitioner offers a NFS section on the left menu tree where you can do everything that the NFS module provides. Thanks to that, you can configure your NFS shares at the same time you format your partitions!

But that integration needed some improvements after we migrated YaST to the new Storage Stack (a.k.a. storage-ng). Moreover, some bugs were detected when using the NFS module for mounting and unmounting shares, see for example bsc#1006815 and bsc#1151426.

All those bugs were fixed, ww the NFS module behaves as expected in both cases, when running in standalone mode and inside the Expert Partitioner. Note that now the current status of the existing shares is preserved. That is, an unmounted share will continue unmounted after editing it. Unmounted entries are indicated with an asterisk in the list of shares, similar to what the Expert Partitioner does for the rest of unmounted devices. All these improvements will be available for SUSE Linux Enterprise SP1, openSUSE Leap 15.1 and openSUSE Tumbleweed.

Installation Progress Improvements

We got some bug reports about how installation progress reporting works and while we were touching it, we also added a few smaller improvements to the code.

The first change is that nowadays installing from multiple discs almost never happens but still there was always a “Medium 1” column which did not make much sense. So we removed the column and if there is a multi-media source, it will be appended to the name if needed.

The second visible change is a new Unicode character ⌛ (hourglass) during the initial phase of RPM installation until the remaining time can be estimated.

The third change is that now the maximum time is always capped at 2 hours, so even if there are multiple sources and some of them took more then two hours, it always show just “>2:00:00” and even in total it is capped, so it can no longer show something like “>6:00:00”.

The fourth one is that now you can read the release notes without disturbances. Previously you would get switched to the package log tab after each package finished its installation. Now it will redraw only when you go back from the release notes screen.

The fifth one is a fix for showing the remaining packages, where it is shown only for the active source and not for all. So now it shows remaining packages for all repositories.

And last but not least we do a bunch of refactoring, code quality improvements and also adding automatic unit tests to reduce regressions in the future.

Tumbleweed before and now:

SLE before and now:

and new ncurses:

Doomsday Preparations: Retracted Packages

If a maintenance update is released for any of our supported products, it may happen that after its release we realize that it introduces new problems, so we have to unpublish (retract) it.

So far, our maintenance team always managed to find other solutions, but sooner or later it will happen that it takes too long to realize that an update was broken, so users will install it.

For that purpose we introduced a new status retracted for patches and packages. We hope that we will never need it, but if we do, we need it in a hurry — until a better, fixed version of those packages is released.

We added new filters “Retracted Packages” and “Retracted Installed Packages” to the package selection, and the affected versions are colored in red and get a [RETRACTED] marker in the “Versions” tab:

Those lists should always be empty. Also, retracted versions will never automatically be installed. If package versions are retracted, but are already installed, the “Retracted Installed Packages” view will be opened automatically when starting the package selection to make you aware of them. Then you can choose to manually downgrade to a previous version or to wait until a fixed version is available.

In general, don’t worry: We never needed this so far, and we hope that we will never need it. Still, we take precautions for the worst case.

More details: PR 82

Qt Package Selection Gets Faster

This came as a byproduct of the previous item: While working on the new filter views for retracted packages, we found that it could take a long time (10-20 seconds) when switching away from the “All Packages” view, so we started digging deeper to find out why.

We found it strange that clearing the package list on the right side of that dialog was so slow; considerably slower than filling it with all packages. After some investigations, we found that in the course of all those changes for all those Qt versions (since Qt 3.x in mid-2006) some internal housekeeping for those list items was now no longer necessary because later Qt versions took over more and more of those responsibilities, and our own housekeeping now got in the way of that and was considerably slowing it down.

Once we found the cause, the fix was easy: We threw out our own housekeeping code and are now relying on what the Qt widget does, and hey presto, clearing that list now happens instantly instead of taking 10-20 seconds.

More details: PR 82 (“Other Fixes”)

The winner of the openSUSE + LibreOffice Conference logo competition is Kukuh Syafaat from Indonesia.

Kukuh’s “Fresh Community Spirit” was the winning design and was one of 10 designs submitted during the competition. “Mystery Box” will be sent to Kukuh for the winning design.

In 2020, openSUSE and LibreOffice will have a shared conference from October 13 – 16 in Nuremberg, Germany_._

The organizing committee for this year’s joint conference selected the winning design during a meeting on Jan. 20. The logo portrayed an ideal fit for the conference since openSUSE and LibreOffice are combining their community conferences for just one year in 2020 to celebrate LibreOffice’s 10-year anniversary and the openSUSE Project’s 15-year anniversary.

Now that the logo has been announced, fliers and posters can be created to help advertise the event. The conference website will soon be available on events.opensuse.org and the Call for Papers will begin next month.

This openSUSE + LibreOffice Conference logo should not be confused with the LibreOffice 10th anniversary logo announced on the LibreOffice blog.