<?xml version="1.0" encoding="utf-8"?>
<export-example>
  <doc>
    <id>3642</id>
    <completedYear/>
    <publishedYear>2013</publishedYear>
    <thesisYearAccepted/>
    <language>eng</language>
    <pageFirst>196</pageFirst>
    <pageLast>203</pageLast>
    <pageNumber/>
    <edition/>
    <issue>5</issue>
    <volume>55</volume>
    <type>article</type>
    <publisherName>de Gruyter</publisherName>
    <publisherPlace/>
    <creatingCorporation/>
    <contributingCorporation/>
    <belongsToBibliography>0</belongsToBibliography>
    <completedDate>--</completedDate>
    <publishedDate>--</publishedDate>
    <thesisDateAccepted>--</thesisDateAccepted>
    <title language="eng">Open Source Engineering Processes</title>
    <abstract language="eng">Software engineering  in open source projectsfaces similar challenges as in traditional software development(coordination of and cooperation between contributors, changeand release management, quality assurance, . . .), but often usesdifferent means of solving them. This leads to some salientdistinctions between both worlds, especially with respect tocommunication and how technical issues are addressed. Thevariations within open source software (OSS) communities areconsiderable, and many different approaches are currently inuse, ranging from informal conventions to highly systematic,formally specified and rigidly applied processes. We discussthe archetypal best practises in the field, illustrate them bypresenting example projects, and provide a comparison to tradi-tional approaches.</abstract>
    <parentTitle language="eng">it - Information Technology</parentTitle>
    <additionalTitle language="deu">Open Source-Entwicklungsprozesse</additionalTitle>
    <identifier type="doi">10.1515/itit.2013.1008</identifier>
    <enrichment key="opus.import.date">2022-04-28T11:07:17+00:00</enrichment>
    <enrichment key="opus.source">sword</enrichment>
    <enrichment key="opus.import.user">importuser</enrichment>
    <enrichment key="BegutachtungStatus">peer-reviewed</enrichment>
    <enrichment key="opus.doi.autoCreate">false</enrichment>
    <enrichment key="opus.urn.autoCreate">false</enrichment>
    <licence>Keine Lizenz - Es gilt das deutsche Urheberrecht: § 53 UrhG</licence>
    <author>Wolfgang Mauerer</author>
    <author>Michael C. Jaeger</author>
    <subject>
      <language>eng</language>
      <type>uncontrolled</type>
      <value>Open-Source-Softwaretechnik</value>
    </subject>
    <subject>
      <language>eng</language>
      <type>uncontrolled</type>
      <value>Softwareentwicklungsprozesse</value>
    </subject>
    <subject>
      <language>eng</language>
      <type>uncontrolled</type>
      <value>Softwarereleases</value>
    </subject>
    <subject>
      <language>eng</language>
      <type>uncontrolled</type>
      <value>Linux</value>
    </subject>
    <collection role="institutes" number="FakIM">Fakultät Informatik und Mathematik</collection>
    <collection role="othpublikationsherkunft" number="">Externe Publikationen</collection>
    <collection role="othforschungsschwerpunkt" number="16311">Digitalisierung</collection>
    <collection role="oaweg" number="">Hybrid Open Access - OA-Veröffentlichung in einer Subskriptionszeitschrift/-medium</collection>
  </doc>
</export-example>
