Awareness of Concurrent Changes in Distributed Software Development

Ignat, Claudia-Lavinia; Oster, Gérald

doi:10.1007/978-3-540-88871-0_32

Cited by 6 publications

(9 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In our previous work, we were able to provide similar awareness features as presented in this paper [4,5]. Both [4] and [5] applied OT to localize concurrent remote updates in the context of local document states. In [4], we combined OT with a central version control repository.…”

Section: Related Workmentioning

confidence: 85%

“…Awareness during distributed collaboration has got wide attention for many years, such as in the context of collaborative software development [3,4,10]. A recent study suggests that "developers would appreciate having access to awareness information frequently but not in real time; they have, however, diverse preferences regarding the level of detail in which such information should be made available" [3].…”

Section: Related Workmentioning

confidence: 99%

“…Both [4] and [5] applied OT to localize concurrent remote updates in the context of local document states. In [4], we combined OT with a central version control repository. Because local and remote replicas share some common base version of the document, we need only to maintain operation histories after the base version.…”

Section: Related Workmentioning

confidence: 99%

See 2 more Smart Citations

Handling Disturbance and Awareness of Concurrent Updates in a Collaborative Editor

Oster

Ignat

2017

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

When people work collaboratively on a shared document, they have two contradictory requirements on their editors that may affect the efficiency of their work. On the one hand, they would like to know what other people are currently doing on a particular part of the document. On the other hand, they would like to focus their attention on their own current work, with as little disturbance from the concurrent activities as possible. We present some features that help the user handle disturbance and awareness of concurrent updates. While collaboratively editing a shared document with other people, a user can create a focus region. The user can concentrate on the work in the region without being interfered with the concurrent updates of the other people. Occasionally, the user can preview the concurrent updates and select a number of these updates to be integrated into the local copy. We have implemented a collaborative editing subsystem in the GNU Emacs 5 text editor with the described features.

show abstract

Section: Related Workmentioning

confidence: 85%

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Handling Disturbance and Awareness of Concurrent Updates in a Collaborative Editor

Oster

Ignat

2017

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

show abstract

“…Other interior nodes are identified by their path in the tree. For instance, in Figure 3c, the span node <span style='bold'> with the content ''February 2, 2016'' is identified by [2,0]. A character in a text node is identified by the path to the text node and a position pos inside the text node.…”

Section: Operationsmentioning

confidence: 99%

“…Email: claudia.ignat@inria. Ignat et al [1,2,3,4] highlight the fact that conflicts are reduced if users see modifications of other users in real-time, i.e. immediately, and that conflicts are increasing with the delay users see modifications of other users.…”

mentioning

confidence: 99%

Enhancing rich content wikis with real‐time collaboration

Ignat

André

Oster

2017

Concurrency and Computation

Self Cite

View full text Add to dashboard Cite

SUMMARYWikis are one of the most important tools of Web 2.0 allowing users to easily edit shared data. However, wikis offer limited support for merging concurrent contributions on the same pages. Users have to manually merge concurrent changes and there is no support for an automatic merging. Real-time collaborative editing reduces conflicts as the time frame for concurrent work is very short. In this paper, we propose extending wiki systems with real-time collaboration. We propose an automatic merging solution adapted for rich content wikis. Our solution relies on an operational transformation algorithm defined for high level operations that capture user actions such as move, merge and split. Copyright c 0000 John Wiley & Sons, Ltd.KEY WORDS: CSCW; collaborative editing; operational transformation; wiki INTRODUCTIONThe Web 2.0 era is associated with the growing success of participatory collaborative tools for public users. Enterprises have integrated a part of these tools in their information systems to improve their productivity and to facilitate the emergence of a form of collective intelligence.Among these tools, wikis efficiently share and structure a large amount of knowledge. Wikis are interlinked pages of rich text. Any user can view and edit these pages. For instance, a software development team can dedicate a wiki page to the minutes of their meetings, another one to their bug reports and a last one to the progress of their development. This way, everybody can keep an eye on when is the next meeting, who will attend, the minutes of a previous meeting, what are the bugs found or fixed, and the completed work on the project. Moreover, a wiki allows fast updates and everybody can edit the content without any restriction. A wiki offers all these features in a single tool.However, most existing wiki systems such as MediaWiki do not automatically merge parallel modifications on the same page. This becomes critical when changes have to be performed very quickly. A typical example is breaking news, when it is common that hundreds of people contribute to the same related Wikipedia pages in a very short amount of time. If two users are concurrently editing the same article, when they try to save their changes, the changes of only one user are published. The other user will be presented with two versions of the wiki page: the one that the user tried to publish and the recently published version. Conflicts, i.e. concurrent changes on the same article, have to be manually resolved by users by retyping or copying and pasting the changes they performed in the last version that was published. Moreover, users are unaware of other concurrent updates on the same article until they try to publish their own changes. Resolving conflicts might become very tedious, and this can be critical when a change has to be published almost instantly. * Correspondence to: Inria Centre Nancy -Grand Est, 615 rue du Jardin Botanique, 54600 Villers-lès-Nancy, FR. Email: claudia.ignat@inria. Ignat et al. [1,2,3,4] highlight the fact that co...

show abstract