1. why individuals participate
2 resources and capabilities supporting development activities
3. how cooperation coordination, and control are realized in projects
4. alliance formation and inter-project social networking
5. FOSS as a multi-project software ecosystem
6. FOSS as a social movement
Free software generally appears licensed with the GNU General Public License (GPL), while OSS may use either the GPL or some other license that allows for the integration of software that may not be free software. Free software can be seen as a social movement, whereas OSS is just a software development methodology,...
Participates join the FOSSD projects for various reasons:
Sometimes they may simply see their effort as something that is fun, personally rewarding, or provides a venue where they can exercise and improve their technical skill or competence in a manner that may not be possible within their current job or line of work....building trust and reputation, achieving "geek fame", being creative, advancing through evermore challenging technical roles,...
The following are the resources needed to help make FOSS efforts more likely to succeed:
Personal software development resources: Volunteers participates the project via Internet and they can bring their development methodologies to the project.
Beliefs supporting FOSSD: Beliefs are freedom of experession and freedom of choice.
in FOSS projects, these additional freedoms are expressed in choices for what to develop or work on , how to develop it, and what tools to employ. They also are expressed in choices for when to release work products, determining what to review and when, and expressing what can be said to whom with or without reservation.
FOSSD informalisms: the information the participants use to describe, proscribe, or presecribe what is happening in a FOSSD project.
(i) communications and messages within project Email lists, (ii) threaded message discussion forums,
bulletin boards, or group blogs, (iii) news postings, (iv) project digests, and (v) instant messaging or Internet relay chat. They also include (vi) scenarios of usage as linked Web pages, (vii) how-to guides, (viii) to-do lists, (ix) FAQs, and other itemized lists, and (x) project Wikis, as well as (xi) traditional system documentation and (xii) external publications. FOSS (xiii) project property licenses are documents that also help to define what software or related project content are protected resources that can subsequently be shared, examined, modified, and redistributed. Finally, (xiv) open software architecture diagrams, (xv) intra-application functionality realized via scripting languages like Perl and PHP, and the ability to either (xvi) incorporate plug-in externally developer software modules, or (xvii) integrate software components, modules, or scripts from other OSSD efforts
Competently skilled, self-organizing and self-managed FOSS developers: Volunteers require a base of prior experience in constructing open systems and experience in project management fools.
Discretionary time and effort of FOSS developers: Participants contribute their time and effort to the project because of various reasons:
self-determination, peer recognition, project affiliation or identification, and self-promotion, as well as belief in the inherent value of free software.
Trust and social accountability mechanisms: Developing FOSS source code and applications requires trust and accountability among project participants.
Software version control tool is required to resolve conflicts in the course of FOSS development, and this tool has the following elements:
(a) a centralized mechanism for coordinating and synchronizing FOSS development...
(b) an online venue for mediating control over what software enhancements, extensions, or architectural revisions will be checked-in and made available for check-out throughout the decentralized project as part of the publicly released version
Many FOSSD projects are interdependent through the networking of software developers, development artifacts, common tools, shared Web sites, and computer-mediated communications.
REFERENCE
[1] Scacchi, W. 2007. Free/open source software development. In Proceedings of the the 6th Joint Meeting of the European Software Engineering Conference and the ACM SIGSOFT Symposium on the Foundations of Software Engineering (Dubrovnik, Croatia, September 03 - 07, 2007). ESEC-FSE '07. ACM, New York, NY, 459-468. http://doi.acm.org/10.1145/1287624.1287689
[2] Scacchi, W. 2007. Free/open source software development: recent research results and emerging opportunities. In the 6th Joint Meeting on European Software Engineering Conference and the ACM SIGSOFT Symposium on the Foundations of Software Engineering: Companion Papers (Dubrovnik, Croatia, September 03 - 07, 2007). ESEC-FSE companion '07. ACM, New York, NY, 459-468. http://doi.acm.org/10.1145/1295014.1295019
[3] Ye, Y. and Kishida, K. 2003. Toward an understanding of the motivation Open Source Software developers. In Proceedings of the 25th international Conference on Software Engineering (Portland, Oregon, May 03 - 10, 2003). International Conference on Software Engineering. IEEE Computer Society, Washington, DC, 419-429.
No comments:
Post a Comment