![]() The user mlep also deserves a mention since he is also actively involved on the forum and is one of the moderators.Ĭontributors and the core developers communicate through GitHub by addressing issues and discussing code. The communicators on this forum with the most replies are Tobias Diez, Matthias Geiger, and Christoph Schwentker, who are all part of the core developers. There is also a forum on the JabRef website where users and other people can ask questions. The help page contains most of the information needed for setting up and using JabRef. ![]() First off we have the creators of the JabRef help website, mainly the core developers but also other contributors have worked on this. There is a diverse group of communicators and support staff. When someone offers to contribute to the project, they are asked to run a set of unit tests to make sure any additions do not cause problems in the system.įurthermore, the assessors and testers also request that the contributor creates additional unit tests when implementing new features.Īll the developers are a part of the assessors because they are responsible for conforming to certain standards and legal regulations, since the contributions are considered to be made under the MIT license. These contributors are part of the developers class, since they make contributions to the development of JabRef through pull requests.Ĭontributors are also considered to be part of the maintainers, since they provide assistance in maintaining the system by making pull requests.īoth the core developers and contributors make up the assessors and testers groups. Since JabRef is an open source project and contributions from outside are actively encouraged, there are also a lot of people outside of the core development team who have made contributions to the JabRef code base. They are also the ones who manage and deploy the different aspects of building, testing, and running the system. This means they determine which contributions get merged and which get rejected. They actively contribute to the development of the project and are the ones who are responsible for reviewing and merging pull requests. We also consider these core developers a part of the developers, maintainers, and production engineers stakeholder groups. The following persons make up the core development team of JabRef: Stefan Kolb, Oliver Kopp, Tobias Diez, Matthias Geiger, Jörg Lenhard, Simon Harrer, Oscar Gustafsson, and Christoph Schwentker. They share their vision and roadmap via GitHub and the JabRef website. Since the core developers of JabRef determine the direction of the product we consider these the acquirers of the project. ![]() ![]() While they support the development of JabRef, they do not play an active role in steering of the project.Ĭurrently the project relies on volunteers for the development of the project, although they are trying to attract a funded developer. The sponsors of JabRef are Baola and Neuronade. In addition we have also identified a stakeholder group that was not a part of the eleven types proposed by the book, the sponsors. In this section we will describe the different stakeholder classes as proposed by Rozanski and Woods and relate our views of the classes in relation to the JabRef project. Next, the interaction of JabRef with its environment is illustrated through analysis of the context view.įurthermore, the development view is described to find code structure and dependencies.įollowing that, an overview of the technical debt of JabRef is given by characterizing some of its issues.Īfter that, this chapter continues with an evolution perspective of JabRef, which shows the history of JabRef.įinally, the chapter concludes by listing the most important findings. This chapter gives a structured overview of JabRef by providing descriptions of the various parts that compose its architecture, in order to explain the system and how it works.Īfter introducing the system, the most prominent stakeholders and their workflow are identified. JabRef is a graphical BibTeX reference manager, used for structuring large BibTeX databases in a orderly fashion. This chapter studies JabRef by looking at its architecture, and by looking at the system through different viewpoints and perspectives. The fact that the project is under active development can be deduced from the speed at which pull requests are merged: usually within a day.Īs of 20-03-2017, the project has over 135.000 lines of code, 95 contributors, and 31 releases. The system has been in development since November 2003 and is still actively maintained. It can be used to structure and manage large BibTeX/BibLaTeX reference databases used for writing scientific papers. JabRef is an open source BibTeX reference manager, written in Java. JabRef - A Graphical Application for Managing BibTeX DatabasesĪlborz Salimian Rizi, Owen Huang, Rolf Starre, and Tim van Rossum.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |