Tool for collaborative temporal-based software version management

Software version management is the processes of identifying and keeping track of different versions of a software.Complexity level of this process would become complicated should software was distributed in many places.This paper present a new dimension in software version management which based on temporal elements.Temporal elements such as valid time and transaction time are the main attributes considered, to be inserted into the software version management database.By having these two attributes, it would help the people involved in software process to organize data and perform activity monitoring with more efficient. For a practical application of the model, therefore an automate tool has been developed that could be applied under collaborative software process called TEMVer

Folding and unfolding : balancing openness and transparency in open source communities

Open source communities rely on the espoused premise of complete openness and transparency of source code and development process. Yet, openness and transparency at times need to be balanced out with moments of less open and transparent work. Through our detailed study of Linux Kernel development we build a theory that explains that transparency and openness are nuanced and changing qualities that certain developers manage as they use multiple digital technologies and create, in moments of needs, more opaque and closed digital spaces of work. We refer to these spaces as digital folds. Our paper contributes to extant literature: by providing a process theory of how transparency and openness are balanced with opacity and closure in open source communities according to the needs of the development work; by conceptualizing the nature of digital folds and their role in providing quiet spaces of work: and, by articulating how the process of digital folding and unfolding is made far more possible by select elite actors’ navigating the line between the pragmatics of coding and the accepted ideology of openness and transparency

Version control software in the open source process: A performative view of learning and organizing in the Linux collectif.

This research describes a study of learning and organizing within the Linux kernel open source collective. For its empirical focus it concentrates on Linux kernel development activities and this collective's debates about the role of, and need for, an agreed approach to version control software. This is studied over a period of eight years from 1995-2003. A textual analysis of messages in the Linux Kernel mailing list is used as the primary data source, supported by other contemporary accounts. In this work learning and organizing are understood to be mutually constitutive, where one entails and enables the other. Learning is about interacting with the environment, organizing is about reflecting this in the collective. The thesis uses the theoretical approach of actor network theory, Bateson's levels of learning and Weick's concept of organizing, to analyze learning and organizing in the kernel collective. The analysis focuses on the discourse and interplay between relevant actors (human and non-human), and the ongoing debates among kernel developers over whether to use version control software, and then which version control software to adopt. The persistence and passion of this debate (it spans the 8 years studied and is ongoing) is evident, and allows a longitudinal study of the becoming of learning and organizing. Drawing on actor network theory, the thesis emphasizes the performative (worked out, lived, 'in the doing of', in other words the becoming) character of learning and organizing. The findings of the study reveal how learning is understood in the collective and is, to a degree, reflected in its organizing activity. Key themes that emerge include: the organizing of time and space, maintaining of transparency and the overall concern with sustaining the assemblage. The thesis offers a distinctive account of technical actors as an essential part of the open source process. In conclusion, it re-emphasizes the significance of code and the agency of non-human actors