\documentclass[10pt]{article}

\usepackage{fullpage}
\usepackage{setspace}
\usepackage{parskip}
\usepackage{titlesec}
\usepackage[section]{placeins}
\usepackage{xcolor}
\usepackage{breakcites}
\usepackage{lineno}
\usepackage{hyphenat}





\PassOptionsToPackage{hyphens}{url}
\usepackage[colorlinks = true,
            linkcolor = blue,
            urlcolor  = blue,
            citecolor = blue,
            anchorcolor = blue]{hyperref}
\usepackage{etoolbox}
\makeatletter
\patchcmd\@combinedblfloats{\box\@outputbox}{\unvbox\@outputbox}{}{%
  \errmessage{\noexpand\@combinedblfloats could not be patched}%
}%
\makeatother


\usepackage{natbib}




\renewenvironment{abstract}
  {{\bfseries\noindent{\abstractname}\par\nobreak}\footnotesize}
  {\bigskip}

\titlespacing{\section}{0pt}{*3}{*1}
\titlespacing{\subsection}{0pt}{*2}{*0.5}
\titlespacing{\subsubsection}{0pt}{*1.5}{0pt}


\usepackage{authblk}


\usepackage{graphicx}
\usepackage[space]{grffile}
\usepackage{latexsym}
\usepackage{textcomp}
\usepackage{longtable}
\usepackage{tabulary}
\usepackage{booktabs,array,multirow}
\usepackage{amsfonts,amsmath,amssymb}
\providecommand\citet{\cite}
\providecommand\citep{\cite}
\providecommand\citealt{\cite}
% You can conditionalize code for latexml or normal latex using this.
\newif\iflatexml\latexmlfalse
\providecommand{\tightlist}{\setlength{\itemsep}{0pt}\setlength{\parskip}{0pt}}%

\AtBeginDocument{\DeclareGraphicsExtensions{.pdf,.PDF,.eps,.EPS,.png,.PNG,.tif,.TIF,.jpg,.JPG,.jpeg,.JPEG}}

\usepackage[utf8]{inputenc}
\usepackage[english]{babel}



\usepackage{float}








\begin{document}

\title{HardOps: Utilising the software development toolchain for hardware
design}



\author[1]{Julian Stirling }%
\author[2]{Kaspar Bumke }%
\author[2]{Joel Collins }%
\author[2]{Vimal Dhokia }%
\author[2]{Richard Bowman }%
\affil[1]{University of Bath}%
\affil[2]{Affiliation not available}%


\vspace{-1em}



  
  \date{May 27, 2024}


\begingroup
\let\center\flushleft
\let\endcenter\endflushleft
\maketitle
\endgroup





\selectlanguage{english}
\begin{abstract}
Preprint of journal article.

\textbf{Abstract}:

Collaborative design of physical products between remote partners poses
unique challenges. This is due to both the complex and interconnected
data required for product design and manufacture, and to the centralised
computing infrastructure traditionally used to manage product lifecycle
data. While modern cloud based solutions to collaborative design are
gaining popularity, they diminish the control of each design partner. In
contrast, software designers readily collaborate on highly complex
software, while retaining direct control of the files they are editing
due to the dominance of distributed version control. This version
control can be coupled with ``Developer Operations'' or DevOps tools to
automate critical processes and facilitate communication. In this paper
we explore how DevOps workflows can be adapted to the development of
hardware. We include concrete examples of how this can be implemented in
practice from a case study of the OpenFlexure Microscope project. While
much ground remains to be broken in this field, we believe DevOps for
hardware can support a new paradigm of distributed hardware development,
with enormous benefits for both commercial and open-source hardware.\\%
\end{abstract}%



\sloppy




\selectlanguage{english}
\FloatBarrier
\end{document}

