Los eventos libres son el punto de partida de muchos usuarios a la hora de involucrarse en el Software Libre, ademas de ser un buen lugar donde los desarrolladores intercambian experiencias y ideas. Por ello es bueno estar al tanto donde y cuando se organizan para publicitarlos al máximo.Hoy, 3r Encuentro del Software Libre del [&hellip
Saber cuál es tu ip en tu red local es muy útil en muchas ocasiones, sobretodo si configuras la asignación de este número en DCHP. Este dato se puede conocer de muchas formas, por ejemplo mediante el comando de consola ifconfig. No obstante hoy os enseñaré cómo saber la ip de tu ordenador en KDE. [&hellip
Los cambios se han convertido en algo habitual en nuestra sociedad, aunque haya personas reacios a ellos. Todo evoluciona: la educación, el software, la sociedad, los hábitos, etc. Y este blog no es ninguna excepción, os invito a ver las bases del nuevo KDE Blog 2.0. KDE Blog 1.0 Este blog nació como algo personal [&hellip
Today KDE released updates for its Applications and Development Platform, the second in a series of monthly stabilization updates to the 4.12 series. This release also includes an updated Plasma Workspaces 4.11.6. Both releases contain only bugfixes and translation updates; providing a safe and pleasant update for everyone.
More than 20 recorded bugfixes include improvements to Personal Information Management suite Kontact, Umbrello UML Modeller, document viewer Okular, web browser Konqueror, file manager Dolphin and others. A more complete list of changes can be found in KDE's issue tracker.
To find out more about the 4.12 versions of KDE Applications and Development Platform, please refer to the 4.12 release notes.Dot Categories:
Ya tenemos KDE 4.12.2 y KDE 4.11.6 disponibles para su actualización. Como cada nuevo mes y, fiel a su cita, el equipo de desarrollo de KDE nos ofrece una nueva versión de su escritorio. Y en esta ocasión, por partida doble. Y no será la última. KDE 4.12.2 y KDE 4.11.6 coordinados Para no ir anunciando [&hellip
Una de las tareas que me he encomendado a la hora de mejorar el blog es optimizar el tiempo de carga del mismo. Para ello las imágenes que se suben al blog deben “pesar” poco, así que me ha tocado aprender cómo reducir el tamaño de las imágenes en Linux. Aunque se puede realizar una [&hellip
Con el uso masivo de los teléfonos móviles inteligentes (smartphones) han nacido nuevos canales de comunicación a la vez que otros desaparecían. Uno de los que han triunfado ha sido Whatsapp, que siempre ha tenido el halo de la inseguridad en su gestión de la información. Afortunadamente, para los que nos preocupa un poco la [&hellip
Supongo que los lectores habituales del blog se habrán dado cuenta (cómo no) que este blog está en un proceso de cambio, tanto en el aspecto externo como en algunos asuntos internos en aras de ofrecer más y mejores noticias sobre KDE. Hoy os comentaré los cambios estéticos y estructurales de KDE Blog. Cambios estéticos [&hellip
Si ayer hablaba del calendario de lanzamiento de Plasma Next, hoy toca hablar del aspecto estético y para ello lo mejor es presentar al nuevo equipo de diseño para Plasma Next. El apartado visual de un sistema operativo es algo básico para su éxito. No por nada los sistemas Mac OS X justamente destacan [&hellip
Aunque no es del todo 100% oficial ya tenemos el calendario de lanzamientos de Plasma Next, el nombre que han elegido los miembros de la Comunidad KDE para el siguiente paso de su proyecto. Plasma Next Tras una larga discusión en las listas de correo, finalmente la Comunidad KDE decidió que el mejor nombre para [&hellip
Existe un buen número de lanzadores de aplicaciones en KDE que cubren los gustos de la mayoría de los usuarios: Kickoff (el oficial), Lancelot (el lanzador vitaminado), Daisy (el simple y original), etc. Recientemente, ha sido lanzado Homerun 1.2, un lanzador que promete dar mucho que hablar y que viene cargado de novedades. ¿Qué es [&hellip
Fosdem 2014 (del inglés Free and Open source Software Developers’ European Meeting) es un evento anual de dos días que reune a la comunidad del Software Libre) y que se celebra desde 2001, con cada vez más participantes, charlas y talleres. Fosdem 2014 Para este 2014, Fosdem se realizará el fin de semana del [&hellip
Las II Jornadas Libres de la UNED Vila-real fueron presentadas el 7 de octubre de 2013 en un acto sencillo en la UNED de Vila-real. Hoy me complace en recordar la presencia de KDE en las II Jornadas Libres que tendrá lugar el 19 de febrero. KDE en las II Jornadas Libres: 19 de febrero [&hellip
Las grandes posibilidades de personalizar nuestro KDE es una de las bazas con las que contamos a la hora de defender nuestro escritorio libre favorito. En KDE todo es fácilmente personalizable, desde el fondo de escritorio hasta los colores de las ventanas pasando por el puntero del ratón. Los iconos del sistema no son [&hellip
Uno de los descubrimientos de la última encuesta sobre la mejor distribución GNU/Linux para KDE del 2013 que se realizó a inicios de año en el blog fue la existencia de KaOS, una nueva distribución GNU/Linux que promete ser una de las revelaciones del 2014 ¿Cuáles son sus cartas?¿Vale la pena probarla? Sigue leyendo y [&hellip
Caledonia es una minimalista, elegante y estilosa suite artística para personalizar tu entorno de escritorio KDE. El pasado 24 de noviembre fue lanzado Caledonia 1.5, un nuevo paso adelante de este espectacular tema para Plasma KDE, y hace bien poco ha sido lanzado Caledonia Downloader 1.7, el asistente que te ayudar a instalar esta magnífica suite [&hellip
In the second week of January, KDE's Plasma team gathered in the Blue Systems office in Barcelona, Spain, to discuss and work on the next generation of KDE's popular workspace products. The meeting comes just at the right time, as the Plasma team has just finished a first technology preview, which puts the base technology in place and allows for an evaluation of the current progress. It also gives an opportunity for more refined plans for a first stable release.
In this article, we will give you an impression of some of the topics which have been discussed. Please note that discussions have by now moved to the various online communication channels, such as mailinglists and IRC. Not all results are set in stone, they rather serve as blueprints for ongoing discussions.Naming and repository structure
One of the things that had been discussed online, but has not been concluded, is the naming of Plasma's next release. A proposal has been made to continue calling KDE's workspace products "Plasma", possibly extended as "Plasma by KDE". The term "workspace" will be on the way out, as it bears rather little meaning to most users. Plasma simply refers to all the workspace products, with the technology itself taking care of the distinguishing UI per device.
In line with this thinking, the repository structure will be changed. There is a number of interesting repositories, which are oriented towards likely deployment scenarios. The plasma-frameworks repository contains the library pieces needed to run a Plasma environment and build applications using Plasma technology. The kde-workspace repository will be split into a generic repository, which contains device-independent components. Then there will be repositories for different form-factor UIs. This means, that on a typical desktop system, one would install plasma-framework, plasma-generic and plasma-desktop. To add support for other devices, one can simply add another repository (such as a mediacenter or tablet user experience), and a specialized UI will be offered for this.Supporting Plasma
Plasma, being a central product for KDE, receives many bugreports. In order to provide good support, better prioritization and focus is needed. For this reason, the team plans to structure the different components in Bugzilla in a way that makes it easier to identify higher priority problems (for example in default components), and make a clearer distinction between "officially supported" and "community-supported" components. This should lead to improved stability and shorter reaction times for the core components of the desktop.Launcher
One of the things that kept the Plasma developers busy during the sprint was the question what to do with the main application launcher. This seems to be a question which has a different answer for almost every user. Plasma's strategy has been to offer a well-tested default (Kickoff), with other options to choose from (traditional menu, Lancelot). For the next release, this flexibility will remain intact. The idea is to replace the traditional menu with one that works similarly, but sports an updated look and some interaction improvements. The current version of Kickoff, which has already been reimplemented in QML will get a visual update.KRunner Plans
The future of KRunner, Plasma's mini-commandline was discussed. There is a replacement in the works, though at this early stage is it unclear when it is going to land. In order to allow an alternative to fully mature before it replaces a core component, the team decided to port the current version of KRunner, and adapt it for improvements in the desktop search area.Logging in
The team also discussed the login procedure. While KDM has reached the end of its lifetime, being a fork of the ancient XDM, there are better alternatives on the horizon. The Plasma developers decided to improve and update the theming of LightDM and SDDM, although neither are currently perfect solutions. LightDM suffers from requirements around copyright assignment, which some developers refuse to sign; on the other hand, SDDM is not yet fully finished in terms of features needed.
Activity Switching (click for larger)
by Martin Klapetek (CC BY) Activity Switching
Plasma developer Ivan Čukić presented a redesign of Plasma Desktop's activity switcher. The new design has a vertical layout and presents a more visual way to manage activities, move and assign windows, and add and rename them. The design presented was well thought out, and apart from a few visual changes, Ivan's concept was received very positively.Notication Area Improvements
The team discussed the current version of the systemtray, also known as notification area. The new approach to use one popup dialog for all, which reduces visual clutter, was welcomed. The team has identified a few issues with the current implementation, which will be addressed in the coming weeks. One of the things that was brought up is that applications or services should have a way to enable a Plasma widget in the system tray. This could be useful for Bluetooth, for example, where a widget would show up as soon as the Bluetooth hardware is found or enabled. On the other hand, some widgets which do not make sense in a given hardware environment could be entirely hidden (for example, the battery widget on non-laptop systems).
Wayland discussion (click for larger)
by Martin Klapetek (CC BY) Kwin/Wayland
KWin maintainer Martin Gräßlin presented the status of KWin and Wayland support in the window manager and compositor, and shared his plans for the future. Wayland support is well under way, although not everything is entirely clear from an architectural point of view. There is simply no example or reference implementation for many of the technical problems we face, so his work is, to no small degree, about covering new ground.A new focus on design
One of the hot topics during the sprint was the visual and interaction design in Plasma. These things have been identified as needing a more structured approach. Thanks to the effort of Jens Reuterberg, an illustrator from Sweden who recently joined the Plasma team, work has commenced on forming a stronger design team. Another topic in this area was the creation of visual guidelines, which has already been started. The team hopes that these efforts will result in greater visual consistency and more elegance throughout the whole user experience.
Group photo: Left to right: (top) Martin Klapetek, Mitch Curtis, Ivan Čukić, Jens Reuterberg, David Edmundson, Martin Gräßlin, Aleix Pol, Giorgos Tsiapaliokas, Sebastian Kügler, Antonis Tsiapaliokas, (front) Marco Martin, Vishesh Handa, Àlex Fiestas (click for larger)
by Martin Klapetek (CC BY) Much hacking
Of course there is not sprint without hacking. Many ideas have been put into code already, various pieces have been cleaned up, missing features were implemented. Everyone attending enjoyed the sprint, especially the productive and friendly atmosphere. The whole team is excited and already working on the results of the sprint.
Hace poco hablé del lanzamiento de Netrunner, 13.12, una de las distribuciones con mucho futuro y realmente interesante que se está haciendo hueco entre los usuarios no desarrolladores. Hoy os traigo un par de vídeos de las nuevas características de Netrunner 13.12. ¿Qué es Netrunner? Ante de nada, recordar qué es Netrunner: Netrunner se trata de [&hellip
Una decena de desarrolladores de KDE se dieron cita en la oficina de BlueSystems del 10 al 16 de enero para trabajar en la nueva versión de Plasma, bautizada provisionalmente como Plasma2. Esta evolución del escritorio KDE (que va unida al nuevo Frameworks) supone un gran cambio tecnológico, con la introducción preliminar de Wayland y [&hellip
From its beginning, KDE has been a leader in innovation in free (libre) and open source software (FLOSS), but there is a threat to that leadership in one of the fastest growing areas of technology. The advantages of free and open development and use are clear for software; now closed and proprietary strategies have become standard in other kinds of technology. The need for technology freedom has moved from software to other more corporate-controllable areas—notably hardware and the Internet.
As was the case when KDE started, community-developed, freedom-oriented technology is necessary to break the stranglehold of large companies that are more committed to managers and investors than to users. But this won’t be easy and it can’t be left to a few people. The entire KDE Community has a stake in the outcome. For that matter, this should be a concern to anyone who develops free and open software, anyone who uses it, anyone who benefits from it. And that includes just about everyone using technology today.
New hardware has been announced that addresses the need for openness beyond software. Community help is needed to support a generous, far-sighted open hardware project involving mostly KDE people and certainly following KDE principles. Please consider contributing financially to open hardware for KDE.
More of the story follows...The threat of proprietary & closed
The Internet is under threat from companies that seek unfair leverage with their massive investments...investments, by the way, that are already well compensated. The nature of these companies is such that every possible means must be used to extract value.
The digital hegemony of several U.S. companies (Amazon, Apple, Facebook, and Google) plus Samsung dominate technology. All of these companies depend to a great extent on free and open software. Microsoft tries (and fails) to stay in this league with such schemes as using its monopoly position to force conditioned users to adopt Windows 8—a mobile phone GUI blown up to a touch interface on a 19" monitor, positioned by clever marketers as "platform convergence".
What these companies are doing is not wrong; it’s the way most things work these days.
KDE’s leadership is an opportunity to extend free and open technology, providing creative minds unlimited room to innovate. Mainstream tech companies try to do this without disrupting their profits or stock prices. We are fortunate to have such freedom.Plasma Active
Nine years ago, KDE started planning for a shared technology base for all types of computers. In September 2011, Plasma Active was released. It shared almost all the underlying code base of the other Plasma Workspaces, along with an innovative user interface specifically designed for tablets and the way they are used. KDE quietly offered platform convergence well before Microsoft or Canonical jumped on the bandwagon.
Plasma Active fits well with KDE’s original goal. As Matthias Ettrich wrote in the announcement of KDE:
"The idea is to create a GUI for an ENDUSER" and "IMHO a GUI should offer a complete, graphical environment. It should allow users to do everyday tasks with it, like starting applications, reading mail, configuring the desktop, editing some files, delete some files, look at some pictures, etc. All parts must fit together and work together."
Plasma Active is free and open software, readily available to install on any tablet. But it has been installed on only a few types of tablets, and requires higher than average technical know-how to install and maintain.
Virtually all tablets on the market have either Google’s Android operating system or Apple’s iOS. Neither is truly free and open. Apple technology is closed and proprietary...Apple’s business model. Android is 23% open according to VisionMobile. Installing a different operating system and user interface means violating warranty terms. In addition, there is no standard version of the Android operating system even with the same version number. These operating systems and user interface designs are controlled by Apple, Google and Samsung (which sells approximately 40% of all Android devices). These companies have no interest in making their hardware run KDE software. In fact, doing so would be contrary to the fundamental purpose of such enterprises.
The environment for Plasma Active is far different (and more restricted) than that for other KDE software. With any commercially available desktop or laptop, it is simple to install and run KDE and other free and open software. While there may be some occasional hassles with wireless or graphics, those are easily overcome. Plasma Active comes standard on the open hardware platform called Improv.
Software can’t be free and open if its hardware is closed and proprietary. Improv is as open and free as possible.The tablet market
In October 2013, Gartner reported that global tablet sales would grow 53.4% for the year, and PC shipments would be down over 11% from the previous year. By 2015, tablets and PCs will sell about the same level.
Users will continue to want the kind of software KDE provides for traditional PCs, for several reasons. (Jos Poortvliet’s presentation at Akademy 2013 has some background.) KDE is viable for the foreseeable future...in the desktop and laptop space. But not for tablets, the fastest growing and highly visible personal computing segment.
Several free and open projects have been started to address the need for alternatives to the Android/iOS market dominance in tablets and other devices. Those projects have faced difficulties that point to the daunting nature of challenges to the Google, Samsung and Apple mobile oligopoly. Other projects such as CyanogenMod have chosen the venture capital route to try and compete. The fundraising goals are substantial:
- Jolla – €200 million
- CyanogenMod - $30 million
- Ubuntu Edge – projected a requirement for $32 million
- Tizen – multimillion dollar project sponsored by the Linux Foundation and supported by Intel and Samsung
Where do these projects stand?
Jolla began offering a smartphone in Finland at the beginning of December 2013. Their tablet operating system has been exhibited but is not commercially available. A mainstream journalist reports that the Jolla smartphone is a "work in progress" that still has some rough edges, and refers to the 'beta' nature of the handset and software.
Prominent venture capitalists have made substantial investments in CyanogenMod. So at least for the moment CyanogenMod is doing fine. They will have to capture major market share to satisfy venture capital investors...time will tell. This professional investment establishes a substantial value for CyanogenMod as a company and hints at the attractiveness of the device market. A market in which there's a danger of KDE being irrelevant.
Canonical tried to crowdfund a smartphone to round out their converged computing initiative. Against a goal of $32 million, there were commitments of about $12 million. Canonical hinted at backing from major hardware suppliers, but this news was light on detail.
Samsung was expected to launch a Tizen phone at Mobile World Congress in February. Now it appears that Tizen will not challenge Android and iOS this year after all. A Samsung switch to Tizen would be a blow to Android, but it would be good for Samsung’s already rich bottom line. And would further entrench the oligopoly.
According to the tech news site Gigaom, both Tizen and Ubuntu Touch have been set back. However with its substantial, prestigious backing, Tizen is almost certain of being successful.
All of these projects are associated to some degree with free and open software; their funding experiences—successful or not—indicate the potential value of the device industry. None of the organizations promise the degree of freedom and openness typical of KDE."The KDE Tablet"
Several years ago, KDE developers confronted 2 questions:
- How can we ensure that KDE software is relevant to computer users today and tomorrow? KDE development teams are addressing this in various ways.
- However, without proper hardware, some kinds of software development are not possible (for example, Qt on Android). What hackable ARM-based hardware exists that supports KDE software out of the box?
The answer was "NONE".
So in early 2012, Aaron Seigo announced the Spark (later renamed "Vivaldi") tablet, which would be produced by the Make Play Live (MPL) project (comprised mostly of people and companies associated with KDE). It would make the necessary hardware available.
Many readers will be familiar with the background. Plucky Aaron and his MPL team have faced significant challenges. One of the most difficult things to overcome has been the nonchalance of hardware suppliers about open source licensing. In addition, suppliers changed components without notice or consultation. In short, it has been an ongoing battle to produce hardware that would run Plasma Active out of the box.
In fact, Aaron and his small hardware development team were forced to engineer hardware from scratch. According to Aaron, there will be an open hardware tablet; it’s a question of when it will be available.Improv
In the mean time, the efforts to produce an open hardware tablet revealed a need for general hardware development expertise for free and open projects. The Vivaldi lessons could be applied more broadly to all manner of hardware development.
Out of this realization, the MPL hardware development team created Improv.
Improv has two parts:
- An interchangeable card with a dual core 1 GHz ARM processor, 1 GB memory, 4GB NAND flash storage, Micro SD card reader,
- The standard connector on this card plugs into a feature board that provides access to I/O functions, including USB, HDMI, SATA, VGA, and a 44 pin DIL with a range of I/O possibilities.
Improv hardware drawings are open and readily available, software is covered by free and open source licenses, and interfaces are well-documented. In other words, Improv is open hardware, as open as it can be given that all graphics processing units (GPU) are closed and proprietary.
More information and detailed specifications are available at the MakePlayLive website. Improv comes with the Mer operating system, the lean Core Linux distribution that is a direct descendent of MeeGo. Additional software configurations are available, in fact encouraged.
Improv has been designed, prototyped, tested and retested. It can’t be bricked by installing other software or experimenting with configurations; there's no need to root the device. Concepts prototyped on Improv can be turned into complete, custom products using the same hardware.
Improv & Plasma Media Center
Improv is done. It’s ready. In typical KDE fashion, Improv was accomplished while others were saying what they were gonna do.
Aaron said this about the Improv:
Improv is hardware produced *for* free software rather than hardware that *happens to run* free software. It supports a range of software from a standard modern Linux user space all the way up to a full featured desktop. Openness for hardware and software is the goal rather than an accident or a market result.
For the KDE Community—KDE software on the device is just part of the picture. The device itself is a gift to KDE. We made Improv so we could have such a device for KDE.
Improv is a hardware template, a starting point for new products without requiring the resources of a large company with an in-house hardware team. Use it at home for a personal server or other project. It’s perfect in a school setting for education. But it can also be used to create entirely new products, experiment and prototype, and manufacture if there is demand. Improv is designed to grow from idea to finished product, all on the same hardware/software platform.
The know-how and manufacturing chain that has been assembled for Improv is available to anyone who wishes to build upon it. Rather than starting from scratch, Improv is a ready-made starting point for product development and creation.
Improv is a product that can open the doors to the world of ubiquitous, device-centric computing for KDE and other free and open projects. No more waiting for a big vendor to be kind and take our needs into consideration. No more trying to shoehorn KDE software into devices with proprietary lock-in.
Improv & Konqueror I understand...how do I contribute?
That’s the pressing dilemma. With software, it’s easy for developers to contribute. A lot of people make their first contribution to free and open software with a single patch. Anyone can download the code and work with it. Start small. There's room for many contributors.
Hardware development is different; it involves physical pieces and is done in chunks. For example, board layout with multiple components and complicated routing is a one-person job.
Aaron and the small team have succeeded at creating the hardware. No further contributions are necessary towards its development. Improv works and works well.
However, there is another big difference between hardware and software—cost. Creating software has no out-of-pocket expense beyond the initial investment in a computer. Distributing one more copy of a KDE application has virtually no associated cost. On the other hand, hardware has a direct cost. Designing a printed circuit board is mostly done in software. But there is a cost to prototype and produce each copy of that physical board.
Aaron and a few others have personally paid these development costs. As can be inferred from the budgets mentioned above, Improv hardware development has not come cheap. There are no venture capitalists handing out money on this project. This is not a get-rich-quick scheme. It is a many year project, involving considerable personal sacrifice on behalf of KDE and free/open technology. Improv is based on generosity, not greed.
The team had high expectations that Improv pre-production sales would be enough to cover these expenses. They will eventually, but people want to get their hands on Improvs now. Delivery delays harm the project.Please lend a hand
Funding is needed for the direct costs associated with manufacturing: electronic parts, feature board assembly and CPU cards.
Hundreds of people have already supported the project by buying an Improv.
You can help...
Consider buying an Improv, even if you don’t plan to play with it. Give it to a student who has just started learning about technology.
Company engineers might use Improv as a platform for building a custom product. It serves well for prototyping, and can mature gracefully to market readiness. Most importantly, Improv can reduce a hardware development schedule by many months with substantial cost savings.
Please consider donating to the project. Donations will only be used for direct manufacturing costs. Any money contributed beyond the goal of $125,000 will be used to produce Improvs for education.
Improv works. Please help push it from proven-design-ready-for-manufacturing to full production.
Take a stand for digital choice. A stand for what KDE has proven to be successful—free and open wins.Dot Categories: