407 lines
20 KiB
XML
407 lines
20 KiB
XML
<rdf:RDF
|
||
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
|
||
xmlns:z="http://www.zotero.org/namespaces/export#"
|
||
xmlns:dcterms="http://purl.org/dc/terms/"
|
||
xmlns:bib="http://purl.org/net/biblio#"
|
||
xmlns:foaf="http://xmlns.com/foaf/0.1/"
|
||
xmlns:link="http://purl.org/rss/1.0/modules/link/"
|
||
xmlns:dc="http://purl.org/dc/elements/1.1/"
|
||
xmlns:prism="http://prismstandard.org/namespaces/1.2/basic/">
|
||
<bib:Article rdf:about="https://doi.org/10.1186/s41469-020-00087-8">
|
||
<z:itemType>journalArticle</z:itemType>
|
||
<dcterms:isPartOf rdf:resource="urn:issn:2245-408X"/>
|
||
<bib:authors>
|
||
<rdf:Seq>
|
||
<rdf:li>
|
||
<foaf:Person>
|
||
<foaf:surname>Choudhury</foaf:surname>
|
||
<foaf:givenName>Prithwiraj</foaf:givenName>
|
||
</foaf:Person>
|
||
</rdf:li>
|
||
<rdf:li>
|
||
<foaf:Person>
|
||
<foaf:surname>Crowston</foaf:surname>
|
||
<foaf:givenName>Kevin</foaf:givenName>
|
||
</foaf:Person>
|
||
</rdf:li>
|
||
<rdf:li>
|
||
<foaf:Person>
|
||
<foaf:surname>Dahlander</foaf:surname>
|
||
<foaf:givenName>Linus</foaf:givenName>
|
||
</foaf:Person>
|
||
</rdf:li>
|
||
<rdf:li>
|
||
<foaf:Person>
|
||
<foaf:surname>Minervini</foaf:surname>
|
||
<foaf:givenName>Marco S.</foaf:givenName>
|
||
</foaf:Person>
|
||
</rdf:li>
|
||
<rdf:li>
|
||
<foaf:Person>
|
||
<foaf:surname>Raghuram</foaf:surname>
|
||
<foaf:givenName>Sumita</foaf:givenName>
|
||
</foaf:Person>
|
||
</rdf:li>
|
||
</rdf:Seq>
|
||
</bib:authors>
|
||
<link:link rdf:resource="#item_208"/>
|
||
<dc:subject>
|
||
<z:AutomaticTag><rdf:value>All remote</rdf:value></z:AutomaticTag>
|
||
</dc:subject>
|
||
<dc:subject>
|
||
<z:AutomaticTag><rdf:value>COVID-19</rdf:value></z:AutomaticTag>
|
||
</dc:subject>
|
||
<dc:subject>
|
||
<z:AutomaticTag>
|
||
<rdf:value>New forms of organizing</rdf:value>
|
||
</z:AutomaticTag>
|
||
</dc:subject>
|
||
<dc:subject>
|
||
<z:AutomaticTag>
|
||
<rdf:value>Organizational design</rdf:value>
|
||
</z:AutomaticTag>
|
||
</dc:subject>
|
||
<dc:subject>
|
||
<z:AutomaticTag><rdf:value>Remote work</rdf:value></z:AutomaticTag>
|
||
</dc:subject>
|
||
<dc:subject>
|
||
<z:AutomaticTag>
|
||
<rdf:value>Virtual organizations</rdf:value>
|
||
</z:AutomaticTag>
|
||
</dc:subject>
|
||
<dc:title>GitLab: work where you want, when you want</dc:title>
|
||
<dcterms:abstract>GitLab is a software company that works “all remote” at the scale of more than 1000 employees located in more than 60 countries. GitLab has no physical office and its employees can work from anywhere they choose. Any step of the organizational life of a GitLab employee (e.g., hiring, onboarding and firing) is performed remotely, except for a yearly companywide gathering. GitLab strongly relies on asynchronous coordination, allowing employees to work anytime they want. After highlighting some of the main practices implemented by GitLab to effectively work all remotely and asynchronously, I asked renowned organizational scientists their thoughts on this interesting case and to question the generalizability of the all remote asynchronous model. Understanding whether and under what conditions this model can succeed can be of guidance for organizational designers that are now considering different remote models in response of the COVID-19 shock and its aftermath.</dcterms:abstract>
|
||
<dc:date>2020-11-16</dc:date>
|
||
<z:language>en</z:language>
|
||
<z:shortTitle>GitLab</z:shortTitle>
|
||
<z:libraryCatalog>Springer Link</z:libraryCatalog>
|
||
<dc:identifier>
|
||
<dcterms:URI>
|
||
<rdf:value>https://doi.org/10.1186/s41469-020-00087-8</rdf:value>
|
||
</dcterms:URI>
|
||
</dc:identifier>
|
||
<dcterms:dateSubmitted>2026-04-15 16:57:19</dcterms:dateSubmitted>
|
||
<bib:pages>23</bib:pages>
|
||
<z:citationKey>choudhuryGitLabWorkWhere2020</z:citationKey>
|
||
</bib:Article>
|
||
<bib:Journal rdf:about="urn:issn:2245-408X">
|
||
<prism:volume>9</prism:volume>
|
||
<dc:title>Journal of Organization Design</dc:title>
|
||
<dc:identifier>DOI 10.1186/s41469-020-00087-8</dc:identifier>
|
||
<prism:number>1</prism:number>
|
||
<dcterms:alternative>J Org Design</dcterms:alternative>
|
||
<dc:identifier>ISSN 2245-408X</dc:identifier>
|
||
</bib:Journal>
|
||
<z:Attachment rdf:about="#item_208">
|
||
<z:itemType>attachment</z:itemType>
|
||
<dc:title>Full Text PDF</dc:title>
|
||
<dc:identifier>
|
||
<dcterms:URI>
|
||
<rdf:value>https://link.springer.com/content/pdf/10.1186%2Fs41469-020-00087-8.pdf</rdf:value>
|
||
</dcterms:URI>
|
||
</dc:identifier>
|
||
<dcterms:dateSubmitted>2026-04-15 16:57:19</dcterms:dateSubmitted>
|
||
<z:linkMode>1</z:linkMode>
|
||
<link:type>application/pdf</link:type>
|
||
</z:Attachment>
|
||
<bib:Article rdf:about="https://www.urncst.com/index.php/urncst/article/view/152">
|
||
<z:itemType>journalArticle</z:itemType>
|
||
<dcterms:isPartOf rdf:resource="urn:issn:2561-5637"/>
|
||
<bib:authors>
|
||
<rdf:Seq>
|
||
<rdf:li>
|
||
<foaf:Person>
|
||
<foaf:surname>Arefeen</foaf:surname>
|
||
<foaf:givenName>Mohammed Shamsul</foaf:givenName>
|
||
</foaf:Person>
|
||
</rdf:li>
|
||
<rdf:li>
|
||
<foaf:Person>
|
||
<foaf:surname>Schiller</foaf:surname>
|
||
<foaf:givenName>Michael</foaf:givenName>
|
||
</foaf:Person>
|
||
</rdf:li>
|
||
</rdf:Seq>
|
||
</bib:authors>
|
||
<dc:subject>agile</dc:subject>
|
||
<dc:subject>continuous integration</dc:subject>
|
||
<dc:subject>GitLab</dc:subject>
|
||
<dc:subject>software testing</dc:subject>
|
||
<dc:title>Continuous Integration Using Gitlab</dc:title>
|
||
<dcterms:abstract>The method of Continuous Integration (CI) enables developers to use fast-paced development environments, such as Agile, without the quality of code being compromised. The use of stable repositories on which developers frequently make small changes, running tests with each modification, results in code that is highly tested and readily deployable. GitLab, like other tools of its kind, offers CI features along with code versioning, and several team organizational features that correctly map with Agile artifacts. Before discussing GitLab, this report contains a literature review explaining existing CI practices, and it identifies fundamental aspects that are necessary to achieving the industry standards of CI. This report also evaluates GitLab’s effectiveness in maintaining CI standards using an available open-source project (OpenMCT), while also offering insight on the implications of the gathered findings. The paper concludes with possible directions of future inquiry, and also provides guidance on how one might expand on the work initiated by the team.</dcterms:abstract>
|
||
<dc:date>2019-09</dc:date>
|
||
<z:language>en</z:language>
|
||
<dc:identifier>
|
||
<dcterms:URI>
|
||
<rdf:value>https://www.urncst.com/index.php/urncst/article/view/152</rdf:value>
|
||
</dcterms:URI>
|
||
</dc:identifier>
|
||
<dcterms:dateSubmitted>2026-04-15</dcterms:dateSubmitted>
|
||
<dc:description>Citation Key: arefeen_continuous_2019</dc:description>
|
||
<bib:pages>1–6</bib:pages>
|
||
<z:citationKey>arefeen_continuous_2019</z:citationKey>
|
||
</bib:Article>
|
||
<bib:Journal rdf:about="urn:issn:2561-5637">
|
||
<prism:volume>3</prism:volume>
|
||
<dc:title>Undergraduate Research in Natural and Clinical Science and Technology Journal</dc:title>
|
||
<dc:identifier>DOI 10.26685/urncst.152</dc:identifier>
|
||
<dc:identifier>ISSN 2561-5637</dc:identifier>
|
||
</bib:Journal>
|
||
<rdf:Description rdf:about="https://docs.gitlab.com/">
|
||
<z:itemType>document</z:itemType>
|
||
<bib:authors>
|
||
<rdf:Seq>
|
||
<rdf:li>
|
||
<foaf:Person><foaf:surname>Gitlab</foaf:surname></foaf:Person>
|
||
</rdf:li>
|
||
</rdf:Seq>
|
||
</bib:authors>
|
||
<dc:title>GitLab Docs</dc:title>
|
||
<dc:identifier>
|
||
<dcterms:URI>
|
||
<rdf:value>https://docs.gitlab.com/</rdf:value>
|
||
</dcterms:URI>
|
||
</dc:identifier>
|
||
<dcterms:dateSubmitted>2026-04-16</dcterms:dateSubmitted>
|
||
<dc:description>Citation Key: gitlab_gitlab_nodate</dc:description>
|
||
<z:citationKey>gitlab_gitlab_nodate</z:citationKey>
|
||
</rdf:Description>
|
||
<rdf:Description rdf:about="https://thenextweb.com/news/github-rival-gitlab-building-business-just-0-1-paying-customers">
|
||
<z:itemType>document</z:itemType>
|
||
<bib:authors>
|
||
<rdf:Seq>
|
||
<rdf:li>
|
||
<foaf:Person>
|
||
<foaf:surname>Degeler</foaf:surname>
|
||
<foaf:givenName>Andrii</foaf:givenName>
|
||
</foaf:Person>
|
||
</rdf:li>
|
||
</rdf:Seq>
|
||
</bib:authors>
|
||
<dcterms:isReferencedBy rdf:resource="#item_214"/>
|
||
<dc:title>GitLab is building a business with 0.1% of paying customers</dc:title>
|
||
<dcterms:abstract>Long-distance relationships are never easy, but it seems to be less so for the relationships between co-founders of tech companies. See GitLab, for example.</dcterms:abstract>
|
||
<dc:date>2014-06</dc:date>
|
||
<z:language>en</z:language>
|
||
<dc:identifier>
|
||
<dcterms:URI>
|
||
<rdf:value>https://thenextweb.com/news/github-rival-gitlab-building-business-just-0-1-paying-customers</rdf:value>
|
||
</dcterms:URI>
|
||
</dc:identifier>
|
||
<dcterms:dateSubmitted>2026-04-16</dcterms:dateSubmitted>
|
||
<dc:description>Citation Key: degeler_gitlab_2014</dc:description>
|
||
<z:citationKey>degeler_gitlab_2014</z:citationKey>
|
||
</rdf:Description>
|
||
<bib:Memo rdf:about="#item_214">
|
||
<rdf:value>Section: Insider</rdf:value>
|
||
</bib:Memo>
|
||
<bib:Document rdf:about="https://about.gitlab.com/">
|
||
<z:itemType>webpage</z:itemType>
|
||
<dcterms:isPartOf>
|
||
<z:Website><dc:title>about.gitlab.com</dc:title></z:Website>
|
||
</dcterms:isPartOf>
|
||
<bib:authors>
|
||
<rdf:Seq>
|
||
<rdf:li>
|
||
<foaf:Person><foaf:surname>Gitlab</foaf:surname></foaf:Person>
|
||
</rdf:li>
|
||
</rdf:Seq>
|
||
</bib:authors>
|
||
<link:link rdf:resource="#item_216"/>
|
||
<dc:title>About Gitlab</dc:title>
|
||
<dcterms:abstract>Your intelligent orchestration platform for DevSecOps</dcterms:abstract>
|
||
<z:language>en-US</z:language>
|
||
<dc:identifier>
|
||
<dcterms:URI>
|
||
<rdf:value>https://about.gitlab.com/</rdf:value>
|
||
</dcterms:URI>
|
||
</dc:identifier>
|
||
<dcterms:dateSubmitted>2026-04-17 15:41:17</dcterms:dateSubmitted>
|
||
<z:citationKey>gitlab_about</z:citationKey>
|
||
</bib:Document>
|
||
<z:Attachment rdf:about="#item_216">
|
||
<z:itemType>attachment</z:itemType>
|
||
<dc:title>Snapshot</dc:title>
|
||
<dc:identifier>
|
||
<dcterms:URI>
|
||
<rdf:value>https://about.gitlab.com/</rdf:value>
|
||
</dcterms:URI>
|
||
</dc:identifier>
|
||
<dcterms:dateSubmitted>2026-04-17 15:41:23</dcterms:dateSubmitted>
|
||
<z:linkMode>1</z:linkMode>
|
||
<link:type>text/html</link:type>
|
||
</z:Attachment>
|
||
<bib:Document rdf:about="https://about.gitlab.com/blog/gitlab-dot-com-database-incident/">
|
||
<z:itemType>webpage</z:itemType>
|
||
<dcterms:isPartOf>
|
||
<z:Website><dc:title>about.gitlab.com</dc:title></z:Website>
|
||
</dcterms:isPartOf>
|
||
<link:link rdf:resource="#item_218"/>
|
||
<dc:title>GitLab.com database incident</dc:title>
|
||
<dcterms:abstract>Yesterday we had a serious incident with one of our databases. We lost six hours of database data (issues, merge requests, users, comments, snippets, etc.) for GitLab.com.</dcterms:abstract>
|
||
<z:language>en-US</z:language>
|
||
<dc:identifier>
|
||
<dcterms:URI>
|
||
<rdf:value>https://about.gitlab.com/blog/gitlab-dot-com-database-incident/</rdf:value>
|
||
</dcterms:URI>
|
||
</dc:identifier>
|
||
<dcterms:dateSubmitted>2026-04-17 16:46:23</dcterms:dateSubmitted>
|
||
<z:citationKey>GitLabcomDatabaseIncident</z:citationKey>
|
||
</bib:Document>
|
||
<z:Attachment rdf:about="#item_218">
|
||
<z:itemType>attachment</z:itemType>
|
||
<dc:title>Snapshot</dc:title>
|
||
<dc:identifier>
|
||
<dcterms:URI>
|
||
<rdf:value>https://about.gitlab.com/blog/gitlab-dot-com-database-incident/</rdf:value>
|
||
</dcterms:URI>
|
||
</dc:identifier>
|
||
<dcterms:dateSubmitted>2026-04-17 16:46:27</dcterms:dateSubmitted>
|
||
<z:linkMode>1</z:linkMode>
|
||
<link:type>text/html</link:type>
|
||
</z:Attachment>
|
||
<bib:Document rdf:about="https://www.heise.de/news/Versionsverwaltung-GitLab-rudert-beim-Loeschen-inaktiver-Repositories-zurueck-7203006.html">
|
||
<z:itemType>webpage</z:itemType>
|
||
<dcterms:isPartOf>
|
||
<z:Website><dc:title>Developer</dc:title></z:Website>
|
||
</dcterms:isPartOf>
|
||
<bib:authors>
|
||
<rdf:Seq>
|
||
<rdf:li>
|
||
<foaf:Person>
|
||
<foaf:surname>online</foaf:surname>
|
||
<foaf:givenName>heise</foaf:givenName>
|
||
</foaf:Person>
|
||
</rdf:li>
|
||
</rdf:Seq>
|
||
</bib:authors>
|
||
<link:link rdf:resource="#item_220"/>
|
||
<dc:title>Versionsverwaltung: GitLab rudert beim Löschen inaktiver Repositories zurück</dc:title>
|
||
<dcterms:abstract>Die Pläne, brach liegende Repositories komplett zu löschen, sind laut einem Tweet von GitLab vorerst auf Eis gelegt. Stattdessen sollen sie archiviert werden.</dcterms:abstract>
|
||
<dc:date>2022-08-05</dc:date>
|
||
<z:language>de</z:language>
|
||
<z:shortTitle>Versionsverwaltung</z:shortTitle>
|
||
<dc:identifier>
|
||
<dcterms:URI>
|
||
<rdf:value>https://www.heise.de/news/Versionsverwaltung-GitLab-rudert-beim-Loeschen-inaktiver-Repositories-zurueck-7203006.html</rdf:value>
|
||
</dcterms:URI>
|
||
</dc:identifier>
|
||
<dcterms:dateSubmitted>2026-04-17 16:57:10</dcterms:dateSubmitted>
|
||
<z:citationKey>onlineVersionsverwaltungGitLabRudert2022</z:citationKey>
|
||
</bib:Document>
|
||
<z:Attachment rdf:about="#item_220">
|
||
<z:itemType>attachment</z:itemType>
|
||
<dc:title>Snapshot</dc:title>
|
||
<dc:identifier>
|
||
<dcterms:URI>
|
||
<rdf:value>https://www.heise.de/news/Versionsverwaltung-GitLab-rudert-beim-Loeschen-inaktiver-Repositories-zurueck-7203006.html</rdf:value>
|
||
</dcterms:URI>
|
||
</dc:identifier>
|
||
<dcterms:dateSubmitted>2026-04-17 16:57:16</dcterms:dateSubmitted>
|
||
<z:linkMode>1</z:linkMode>
|
||
<link:type>text/html</link:type>
|
||
</z:Attachment>
|
||
<rdf:Description rdf:about="https://ieeexplore.ieee.org/document/10197778/">
|
||
<z:itemType>conferencePaper</z:itemType>
|
||
<dcterms:isPartOf rdf:resource="urn:issn:2770-8209"/>
|
||
<bib:authors>
|
||
<rdf:Seq>
|
||
<rdf:li>
|
||
<foaf:Person>
|
||
<foaf:surname>Fairbanks</foaf:surname>
|
||
<foaf:givenName>Jeffrey</foaf:givenName>
|
||
</foaf:Person>
|
||
</rdf:li>
|
||
<rdf:li>
|
||
<foaf:Person>
|
||
<foaf:surname>Tharigonda</foaf:surname>
|
||
<foaf:givenName>Akshharaa</foaf:givenName>
|
||
</foaf:Person>
|
||
</rdf:li>
|
||
<rdf:li>
|
||
<foaf:Person>
|
||
<foaf:surname>Eisty</foaf:surname>
|
||
<foaf:givenName>Nasir U.</foaf:givenName>
|
||
</foaf:Person>
|
||
</rdf:li>
|
||
</rdf:Seq>
|
||
</bib:authors>
|
||
<link:link rdf:resource="#item_222"/>
|
||
<dc:subject>
|
||
<z:AutomaticTag><rdf:value>Software</rdf:value></z:AutomaticTag>
|
||
</dc:subject>
|
||
<dc:subject>
|
||
<z:AutomaticTag><rdf:value>CI/CD</rdf:value></z:AutomaticTag>
|
||
</dc:subject>
|
||
<dc:subject>
|
||
<z:AutomaticTag><rdf:value>Codes</rdf:value></z:AutomaticTag>
|
||
</dc:subject>
|
||
<dc:subject>
|
||
<z:AutomaticTag>
|
||
<rdf:value>Mining Repositories</rdf:value>
|
||
</z:AutomaticTag>
|
||
</dc:subject>
|
||
<dc:subject>
|
||
<z:AutomaticTag>
|
||
<rdf:value>Open-Source Software</rdf:value>
|
||
</z:AutomaticTag>
|
||
</dc:subject>
|
||
<dc:subject>
|
||
<z:AutomaticTag><rdf:value>Pipelines</rdf:value></z:AutomaticTag>
|
||
</dc:subject>
|
||
<dc:subject>
|
||
<z:AutomaticTag><rdf:value>Recording</rdf:value></z:AutomaticTag>
|
||
</dc:subject>
|
||
<dc:subject>
|
||
<z:AutomaticTag>
|
||
<rdf:value>Software development management</rdf:value>
|
||
</z:AutomaticTag>
|
||
</dc:subject>
|
||
<dc:subject>
|
||
<z:AutomaticTag>
|
||
<rdf:value>Software engineering</rdf:value>
|
||
</z:AutomaticTag>
|
||
</dc:subject>
|
||
<dc:subject>
|
||
<z:AutomaticTag>
|
||
<rdf:value>Software Engineering</rdf:value>
|
||
</z:AutomaticTag>
|
||
</dc:subject>
|
||
<dc:title>Analyzing the Effects of CI/CD on Open Source Repositories in GitHub and GitLab</dc:title>
|
||
<dcterms:abstract>Numerous articles emphasize the benefits of implementing Continuous Integration and Delivery (CI/CD) pipelines in software development. These pipelines are expected to improve a project’s reputation and decrease the number of commits and issues in the repository. Although CI/CD adoption may be slow initially, it is believed to accelerate service delivery and deployment in the long run. This study aims to investigate the impact of CI/CD on commit velocity and issue counts in two open-source repositories, GitLab and GitHub. By analyzing more than 12,000 repositories and recording every commit and issue, it was discovered that CI/CD enhances commit velocity by 141.19% but also increases the number of issues by 321.21%.</dcterms:abstract>
|
||
<dc:date>2023-05</dc:date>
|
||
<z:libraryCatalog>IEEE Xplore</z:libraryCatalog>
|
||
<dc:identifier>
|
||
<dcterms:URI>
|
||
<rdf:value>https://ieeexplore.ieee.org/document/10197778/</rdf:value>
|
||
</dcterms:URI>
|
||
</dc:identifier>
|
||
<dcterms:dateSubmitted>2026-04-17 17:10:14</dcterms:dateSubmitted>
|
||
<dc:description>ISSN: 2770-8209</dc:description>
|
||
<bib:pages>176-181</bib:pages>
|
||
<bib:presentedAt>
|
||
<bib:Conference>
|
||
<dc:title>2023 IEEE/ACIS 21st International Conference on Software Engineering Research, Management and Applications (SERA)</dc:title>
|
||
</bib:Conference>
|
||
</bib:presentedAt>
|
||
<z:citationKey>fairbanksAnalyzingEffectsCI2023</z:citationKey>
|
||
</rdf:Description>
|
||
<bib:Journal rdf:about="urn:issn:2770-8209">
|
||
<dc:title>2023 IEEE/ACIS 21st International Conference on Software Engineering Research, Management and Applications (SERA)</dc:title>
|
||
<dc:identifier>DOI 10.1109/SERA57763.2023.10197778</dc:identifier>
|
||
<dc:identifier>ISSN 2770-8209</dc:identifier>
|
||
</bib:Journal>
|
||
<z:Attachment rdf:about="#item_222">
|
||
<z:itemType>attachment</z:itemType>
|
||
<dc:title>Full Text PDF</dc:title>
|
||
<dc:identifier>
|
||
<dcterms:URI>
|
||
<rdf:value>https://ieeexplore.ieee.org/stampPDF/getPDF.jsp?tp=&arnumber=10197778&ref=</rdf:value>
|
||
</dcterms:URI>
|
||
</dc:identifier>
|
||
<dcterms:dateSubmitted>2026-04-17 17:10:17</dcterms:dateSubmitted>
|
||
<z:linkMode>1</z:linkMode>
|
||
<link:type>application/pdf</link:type>
|
||
</z:Attachment>
|
||
</rdf:RDF>
|