Language Selection

English French German Italian Portuguese Spanish

LibreOffice Developer Interview: KOHEI YOSHIDA

Filed under
LibO
Interviews

Kohei Yoshida is a well-known individual on the LibreOffice project. To many, he is considered as one of the core group of developers who have contributed to the steady development and code improvement of the project, and one of the leaders of the calc component. Kohei takes a little time out from his busy schedule to let us know a little more about himself and why the LibreOffice project appeals to him.

How did you hear about LibreOffice?

Well, it’s hard not to have heard about LibreOffice as I’ve been there since day one.

Why did you get involved?

I got involved through my employer, SUSE.

What was your initial experience of contributing to LibreOffice like?

rest here




More in Tux Machines

8 Linux Security Improvements In 8 Years

At a time when faith in open source code has been rocked by an outbreak of attacks based on the Shellshock and Heartbleed vulnerabilities, it's time to revisit what we know about Linux security. Linux is so widely used in enterprise IT, and deep inside Internet apps and operations, that any surprises related to Linux security would have painful ramifications. In 2007, Andrew Morton, a no-nonsense colleague of Linus Torvalds known as the "colonel of the kernel," called for developers to spend time removing defects and vulnerabilities. "I would like to see people spend more time fixing bugs and less time on new features. That's my personal opinion," he said in an interview at the time. Read more

Linux from Square One

Despite the fact I have a different view of which distros are best for kids — Qimo (pronounced “kim-o,” as in the last part of eskimo, not “chemo”) tops the list, as it should, but the French distro Doudou (add your own joke here) is unfortunately left out — the link there is informative. So for those who are just getting their proverbial feet wet in Linux, this is a godsend. Read more

Explaining Security Lingo

This post is aimed to clarify certain terms often used in the security community. Let’s start with the easiest one: vulnerability. A vulnerability is a flaw in a selected system that allows an attacker to compromise the security of that particular system. The consequence of such a compromise can impact the confidentiality, integrity, or availability of the attacked system (these three aspects are also the base metrics of the CVSS v2 scoring system that are used to rate vulnerabilities). ISO/IEC 27000, IETF RFC 2828, NIST, and others have very specific definitions of the term vulnerability, each differing slightly. A vulnerability’s attack vector is the actual method of using the discovered flaw to cause harm to the affected software; it can be thought of as the entry point to the system or application. A vulnerability without an attack vector is normally not assigned a CVE number. Read more

​EMC partners with Canonical, Mirantis, and Red Hat for OpenStack

Do you want to use OpenStack, but you're afraid of the headaches of getting its architecture just right? Well, EMC is here to help with OpenStack reference architectures for three leading OpenStack vendors: Canonical, Mirantis, and Red Hat. Read more