島根大学「プロジェクト研究推進機構」特別研究部門

HOME2011 OSR Workshop in East Asia>講演


TITLE:

Open Source Programming Language Ruby and Ruby City MATSUE Project

AUTHORS:

Tetsuo NDOA, Information-processing Center, Shimane University, Shimane.
Terutaka TANSHO, Collaboration Center, Shimane University, Shimane.
Chi JIA, Faculty of Law and Literature, Shimane University, Shimane.

ABSTRACT:

Ruby is the Object-oriented Script Language released by Mr. Yukihiro Matsumoto, called "Matz" in open source communities, and was opened to the public in 1993. Matz lives in Matsue City in Japan and has been developing Ruby with many open source developers all over the world through the Internet. And Ruby is very few open source projects that Japanese engineers are mainly engaged in developing. 
In 2006, Matsue City started "Ruby City MATSUE Project", considering open source programming language "Ruby" as a regional resource of the city. The software development method by open source software has a possibility to release the relationship, called "vendor lock-in" typically in Japanese information industry.

This paper examines this possibility referring a regional industry promotion project through the cooperation of the industrial-government-academic complex in typical local country city in Japan. Matsue City is facing the problems embedded in this "vender lock-in" and then introduced the new project concept, open source programming language "Ruby" and "People" around this community as regional resource.
This paper also illustrates this project schemes and concrete activities. This may be a small project in the global context, however, implies new movement and potential in open source and regional industry promotion. Moreover, this paper is intended to put on a firm footing of the evaluation of open source software, by measuring the productivity of programming language Ruby and web application framework Ruby on Rails, compared with other open source software. --


TITLE:

ODPG: Discussion Group for Introduction of Open-Source Productivity Suite into Japanese Businesses

AUTHORS:

J. Iio, H. Shimizu, K. Kobayashi, and T. Ogawa

ABSTRACT:

In these days, a number of local governments in Japan have begun to adopt open-source productivity software such as OpenOffice.org, mainly in order to reduce the cost by replacing proprietary products with open-source products. On the other hand, enterprises, especially if the organization is large enough, are still hesitating such a migration for some reasons.

ODPG, discussion group for introduction of open-source productivity suite, was organized last year to promote utilization of OO.o and ODF in not only public sectors but also private firms. Currently, ODPG has two working groups. One working group is the case study working group, which collects the best practices in migration strategy and planning, migration tools, and practical migration examples. The other one is the technology evaluation working group, which studies interoperability issues between proprietary and open-source products.

In Japan, some groups and communities including ODPG are actively working on promotion of ODF and open-source productivity software. ODPG proceeds its promoting activity to spread the use of open-source software into enterprises, in cooperation with the other associated organizations. In this presentation, we also discuss the other activities regarding the promotion of OO.o and ODF by these groups in addition to ODPG's promotion. --


TITLE:

OSS Communities on Twitter: A Preliminary Network Analysis

AUTHOR:

Jonathan Lewis, Graduate School of Social Sciences, Hitotsubashi University, Tokyo.
jonathan_lewis@mac.com

ABSTRACT:

Electronic communication between users and developers of open source software has traditionally taken place on mailing lists and internet relay chat. However, in recent years new channels of communication have started to play significant roles. The role of project-specific mailing lists in providing answers to questions about software is being challenged by language-independent sites such as stackoverflow.com. Meanwhile, many users and developers are using Twitter to ask questions, express enthusiasm and vent frustration about open source software. Given the high visibility of Twitter compared to IRC, it is important to understand how people are using it to communicate and learn about OSS; we also need to know how Twitter users are connecting to each other both within particular open source project communities and across project boundaries.

This paper presents a preliminary analysis of the networks of OSS users and developers on Twitter. First, a database is assembled of Tweets regarding a number of open source software projects including Apache, Firefox/Mozilla, libreoffice/OpenOffice and Plone. The database currently contains 385,428 Tweets sent in June and July 2011. We do some basic profiling of message authors to identify e.g. particularly active users. Then we find links between users based on @ sign mentions, replies, retweets and follower information. We use Pajek to identify components of the networks, the structural cohesion of the networks for different projects, and the people who play key roles in disseminating information about OSS projects and who provide links between projects. We discuss problems with data sources, limitations of the analysis and avenues for future research. --


TITLE:

QA communities in OSS development - A case study of Mozilla

AUTHOR:

Adina Barham,  Hitotsubashi University, Graduate School of Social Sciences
2-1 Naka, Kunitachi, Tokyo 186-8601, Japan

ABSTRACT:

The number of OSS projects that formally define a QA step in the development cycle has been increasing in recent years. This suggests that the development model is changing, and brings up a new range of questions regarding the impact that this phenomenon is having on the structure of OSS communities. Although much research has been done on open source communities, little attention has been paid to the people performing the quality assurance phase. Do QA team members migrate from developer teams? Have they done QA work in other OSS or commercial projects? Or are they users of the software who find QA offers them a way to start contributing to the project? Furthermore, does participation in QA lead to involvement in other phases of the development cycle? Who coordinates these teams developers or members of the QA team?
As a first step towards answering these questions, I apply social network analysis to mailing list communication among QA teams for Mozilla. Mozilla QA or QMO (quality.mozilla.org) is structured into 5 teams that use two separate mailing lists, both of which are publicly available on Google Groups. The first and the most active of the the two mailing lists contains 2717 messages that are organized in 1249 threads (before data cleaning). I use the SNA software Pajek to define communication patterns between authors. The preliminary results show that the teams sharing the first mailing list are connected in a large component. The next step is to analyze the second mailing list, cross reference the results and see if and how the five teams are connected.

--