The New Project Leads: NAKATA, Maho
Late last year, the leadership of several important core projects changed hands. Some of the new leads have been leads in other projects and take on new responsibilities; others are new to the job. What does a project lead do? That depends on the project, but it's usually considered role that combines administrative, managerial, and leadership duties, and represents a very high level of trust. The project leads for the accepted technical projects are in particular important to OpenOffice.org, for they are largely responsible for what makes up the source to the application, as well as for reaching out to developers.The following set of short interviews, of which this is the first (others will follow over the next week), is meant to introduce them to the community. As with all of OpenOffice.org's leads, they are open to the community and welcome developer interest and contact.
I was set to ask Maho NAKATA, the new lead of the QA Project (Joost Andrae and Caio Tiago Oliveira de Sousa are the co-leads) more or less the same questions I asked the others; however, Nakata-san beat me to the point and volunteered his own questions and answers. Nakata-san, I should add, has been a longtime developer associated with OpenOffice.org almost since its beginning, and has recently been re-elected lead of the Japanese Language project, which he founded, and which is one of the largest and most active projects in the OpenOffice.org rhizome. Late last year, he took over the leadership of QA from the longstanding lead, André Schnabel.
Other mini-interview in this series:
- Mathias Bauer, New Lead of Writer, Co-Lead of Framework
- Carsten Driesner, New Lead of the Framework Project
- Frank Meies, New Co-Lead of Writer
- Caio Tiago Oliveira de Sousa, New Co-Lead of QA Project
My name is NAKATA, Maho (Maho is my first name please call me maho, and NAKATA is my family name), living in Tokyo, Japan. I'm a post doctoral fellow in chemistry at the University of Tokyo. I'm interested in theory and doing chemistry with computers. Next year still I'm a postdoc at Riken. I'm programming for my researches for proof of concept, using C++, Fortran and Perl, etc. Some of you may be surprised still we are using Fortran77. Would you believe that there are some 30 years old codes that are still alive and very, very much trusted?
For my OpenOffice.org activities, my first commit is FreeBSD porting then founded ja.openoffice.org, also Mac OS X porting a bit (thus I created several CWS's and sometimes I was chosen as QA representative for some CWS's; many thanks to Pavel Jan√≠k). For Mac OS X, currently I'm providing builds for QA.
I'm interested in QA, and my first interest maybe automated QAtesttool. It is very impressive tool. I don't remember correctly, though, I saw a demonstration at OOoCon2003 or 2004. Also I wrote a page for FreeBSD, http://porting.openoffice.org/freebsd/QA.html in which many errors were identified, but these have not yet been fixed[!].
Also I'm interested in L10N, perhaps because Japanese is (IMHO) one of the most difficult languages in the world. Our language is so complicated, and has many problems within computer processing that it is natural for me to find l10n issues interesting.
As the lead [of QA], I must think about deeply about what is the quality, what the QA project should/can do, etc.
My first job might be coordinating QA of 2.1. As I wrote before, I'm interested in writing documents. So that *EVERYONE* can participate this QA project.
I also thank all of you in this community. I need your helps. I'm really appreciated for your helps.
Thanks again for Andre Schnabel.
To learn more about the QA project, visit the site, look over the mail list archives, subscribe to the email@example.com list, and dive in! I should add that the QA project is generally thought of as our starting point for contributors. It's where community members go to file bug reports, requests for enhancement (RFE), and so on. The project, in short, is very important.
Developers--and just about anyone else interested--can start learning more about OpenOffice.org by visiting our wiki.
Return to Articles