Language Selection

English French German Italian Portuguese Spanish

New “Usability” Group in KDE Review Board

Filed under
KDE

There are (loosely) three phases to fixing a design issue:

Phase 1: The issue is reported in a bug or brought up in IRC or the project mailing list
Phase 2: The issue is discussed and a solution is designed and agreed on
Phase 3: The solution is coded, reviewed, and committed

As a designer and someone who doesn’t code, I work in Phase 1 and mostly in Phase 2. However, that doesn’t mean I disappear in Phase 3. Often Phases 2 and 3 iterate because a proposed solution might not be possible or the developer thinks of a different way the problem could be solved.

Sometimes this communication happens over IRC or the mailing list as the developer is trying to figure out a solution, but it can also happen during code review with other developers of the project — especially if it is a patch from outside the core project.

KDE’s Review Board is a useful way for contributors inside and outside a project to submit patches and have them reviewed and approved by core developers. However, sometimes these patches specifically address design issues, or may introduce new design issues that a designer might need to review. If they are subscribed to the project mailing list or they regularly check Review Board, a designer might be able to notice requests they should comment on.

In order to help make this process more design-friendly, there is now a “usability” group on Review Board. I hope this new group will serve two purposes:

rest here




More in Tux Machines

Embedded Development with ARM mbed on Linux

The ARM CPU used in the BeagleBone Black and other single board computers is designed to interface with half to a few gigabytes of RAM and allow a full operating system such as Linux to be run on the computer. (See my long series of reviews on Linux.com of ARM-based computers that run Linux). By contrast the ARM Cortex-M is a microcontroller level chip which might run at 16-100Mhz, contain 2-100kb of RAM, and some flash memory to contain only the program that you want to execute. Read more

Confessions of a systems librarian

These are just two examples of serious flagship projects, but even on a day-to-day level there are plenty of opportunities for systems librarians to interact with open source software. A large amount of vendor software runs on Linux, so there’s plenty of systems administration to do. I work in a relatively small library, and even here we run five Drupal websites: one as a portal for library services, one as the primary repository for our archive, another provides the public interface for an aboriginal research center, and one to manage safety information for our bio sciences lab. Read more

IoT, Revolution In Personal Computing, or FLOSS Taking Over the World of IT

What can you say? In a few short years, that other OS has gone from mainstream to niche and Android/Linux and GNU/Linux are stepping up to displace it as the goto OS of the world. It’s all good. This is the right way to do IT with the world making its own software throughout the whole stack: OS on client and server and a ton of applications too. There is no need for a monopoly in IT. The world wants a revolution not lock-in. Read more

Political parties favour openness to reconstruct Greek productivity

Ahead of the parliamentary elections in Greece last week, the Greek Free/Open Source Software Society (GFOSS) contacted all political parties to ask about their positions [in Greek] with regard to open software, open data, open hardware and open government. The four parties to respond all came out generally in favour of openness. Some of them were even able to present very detailed planning on how to improve the current institutional and legislative framework and outlined how openness could help reconstruct Greek productivity. Read more