\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[round]{natbib}
\let\cite\citep




\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}








% Use this header.tex file for:
% 1. frontmatter/preamble LaTeX definitions
%  - Example: \usepackage{xspace}
% 2. global macros available in all document blocks
%  - Example: \def\example{This is an example macro.}
%
% You should ONLY add such definitions in this header.tex space,
%  and treat the main article content as the body/mainmatter of your document
% Preamble-only macros such as \documentclass and \usepackage are
% NOT allowed in the main document, and definitions will be local to the current block.


\begin{document}

\title{A Thesis on The Life and Times of Spongebob Squarepants (A Test
Document)}



\author[1]{Devon Gaydos}%
\affil[1]{North Carolina State University}%


\vspace{-1em}



  
  \date{May 25, 2024}


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





\selectlanguage{english}
\begin{abstract}
Ohhhh who lives in a pineapple under the sea? A thesis on the life and
times of Mr. Spongebob Squarepants.~\cite{Tabachnick_1991}%
\end{abstract}%



\sloppy


\section*{A Sponge -- With Pants}\label{a-sponge-with-pants}

Who's porous and yellow? \emph{Absorbent} is he.

If \textbf{nautical} nonsense be something you wish.. \cite{1994}

Then hop on the deck and flop like a fish! \cite{1967}

\section*{Chapter One: Ripped Pants}

{\label{641126}}

\section*{Open Source Project:
GnuCash}\label{open-source-project-gnucash}

\subsection*{Home website:}\label{home-website}

{[}https://www.gnucash.org/{]}

\subsection*{Purpose:}\label{purpose}

It's a free financial accounting software meant for individuals and
small-businesses. It's meant to be an alternative to Mint. It allows you
to track bank accounts, stocks, income and expenses.

\subsection*{Why I Chose This One:}\label{why-i-chose-this-one}

I was looking through different open source projects, and I found this
one especially interesting in light of the recent Equifax hack. People
are understandably cagey about their personal financial information
right now considering the rise of cybercrime and identity theft. I was
wondering how an open source project reconciles a high level of security
with a flexible, open source product.

Nowhere in the FAQ page do they mention security in any way. I find this
deeply suspicious. Maybe I'm missing something about the implementation
of the program that would answer this question for me, but it seems like
something that should have been addressed upfront.

\subsection*{Community:}\label{community}

It says the community is mainly made up of volunteers working in their
spare time. There is a small group of developers.

\subsection*{Project License:}\label{project-license}

GNU GPL

\subsection*{Is the license approved by OSI or
FSF?}\label{is-the-license-approved-by-osi-or-fsf}

Yes, it's approved by both.

\subsection*{Type of license:}\label{type-of-license}

It's a copyleft license, so derivative work can only be distributed
under the same license terms. It allows users the run, study, share and
modify the software.

\subsection*{How to report bugs:}\label{how-to-report-bugs}

They suggest you read these two tutorials:
\href{http://www.catb.org/~esr/faqs/smart-questions.html}{How to Ask
Questions the Smart Way}
\href{https://www.chiark.greenend.org.uk/~sgtatham/bugs.html}{How to
Report Bugs Effectively}

They recommend you make sure that what you found is actually a bug. They
suggest checking the mail archives for gnucash developers, gnucash
users, and the gnucash mailing lists for other languages. If you have
actually found a bug, you can report the bug in the Bugzilla database.

\subsection*{How to request new
features:}\label{how-to-request-new-features}

Same as with reporting bugs, you are supposed to request any new
features via Bugzilla. They request that you ask nicely, and try to sell
developers on the idea.

\subsection*{How to ask questions:}\label{how-to-ask-questions}

They suggest you first check all the documentation. But if that doesn't
answer a question, here is a webpage detailing other ways to get help:
\href{https://wiki.gnucash.org/wiki/Getting_Help}{Getting Help}.
Basically they recommend the mailing lists, IRC chat, or reporting bugs.

\subsection*{How to contact developers:}\label{how-to-contact-developers}

Contact {[}gnucash-devel@gnucash.org{]}

\subsection*{Who provides commercial
support:}\label{who-provides-commercial-support}

I don't think there is any commercial support.

\subsection*{Where do get the latest source
code?}\label{where-do-get-the-latest-source-code}

You can download the program via an installer, or from the source code,
at \href{https://www.gnucash.org/download.phtml}{the download page}

You can also download the code via their github at
{[}https://github.com/Gnucash{]}

\subsection*{Where to get info about contributing to the
project?}\label{where-to-get-info-about-contributing-to-the-project}

This page describes all the ways that you can contribute to the project:
\href{https://wiki.gnucash.org/wiki/Contributing_to_GnuCash}{Contributing
Instructions}. They suggest you can contribute by testing, providing
feedback, advocating for gnucash, donating money, writing documentation
for how to do things, writing helpful pieces of code, and translating
the program to a different language.

\subsection*{Whether the project is
active?}\label{whether-the-project-is-active}

Yes the project is active. The latest release was on 07/02/2017.

No girl ever wants to dance with a fool who went and ripped his
pants~\citep{W_rsig_2010}, \citep{Kim_2015}.~

\par\null

\selectlanguage{english}
\FloatBarrier
\bibliographystyle{plainnat}
\bibliography{bibliography/converted_to_latex.bib%
}

\end{document}

