starlee
/
prj_doc
0
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

change 4.2.3

This commit is contained in:
whystar 2020-08-21 17:13:52 +08:00
parent d9dbf01f1a
commit 6f2eec2880
2 changed files with 7 additions and 32 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
4_4.tex
View File

@ -77,22 +77,22 @@ at the launch time, as shown in Figure~\ref{fig:new_repo}.
\subsubsection{Update interval}
\subsubsection{Update frequency}
\label{interval}
We explored how frequent is community profile documentation updated.
For each document,
we compute the interval between every two adjacent commits.
we compute the intervals between every two adjacent commits.
The smaller the interval,
the more frequent the document is updated.
the more frequently the document is updated.
Figure~\ref{fig:main_interval} presents
the distribution of update interval for each kind of documentation in the studied projects.
The update interval (in day) of \RDM, \LIC, \CON, \COD and \TMP
The update interval (in day) of the \RDM, \LIC, \CON, \COD and \TMP documentation
is 44.42 (median: 3.75), 333.72 (median: 169.57), 99.39 (median: 18.54), 205.92 (median: 48.92), and 116.29 (median: 25.16), respectively.
We can note that \RDM files are updated more frequently by other files.
We can note that \RDM files are updated more frequently than other files.
There are two possible explanations.
First,
\RDM fils have a higher frequency to be read by community developers as the homepage of a project,
\RDM files have higher chances to be read by community developers as the homepage of a project,
and therefore the defects in \RDM files are more likely to be fixed.
Second,
the \RDM files are used to present the various information about the project~\cite{Prana2018Categorizing}
@ -104,7 +104,7 @@ and therefore they need to be frequently updated as the project evolves.
\begin{figure}[ht!]
\centering
\includegraphics[width=0.9\textwidth]{resources/interval.pdf}
\caption{The distribution of maintenance interval of documentation}
\caption{The distribution of update interval of documentation}
\label{fig:main_interval}
\end{figure}

25
scis_paper.out
View File

@ -1,25 +0,0 @@
\BOOKMARK [1][-]{section.1}{Introduction}{}% 1
\BOOKMARK [1][-]{section.2}{Related work}{}% 2
\BOOKMARK [1][-]{section.3}{Research Design}{}% 3
\BOOKMARK [2][-]{subsection.3.1}{Research questions}{section.3}% 4
\BOOKMARK [2][-]{subsection.3.2}{Dataset}{section.3}% 5
\BOOKMARK [3][-]{subsubsection.3.2.1}{Studied projects}{subsection.3.2}% 6
\BOOKMARK [3][-]{subsubsection.3.2.2}{Identification of documentation}{subsection.3.2}% 7
\BOOKMARK [3][-]{subsubsection.3.2.3}{Change history of documentation}{subsection.3.2}% 8
\BOOKMARK [1][-]{section.4}{Results}{}% 9
\BOOKMARK [2][-]{subsection.4.1}{RQ1: Documentation Prevalence}{section.4}% 10
\BOOKMARK [3][-]{subsubsection.4.1.1}{Overall prevalence}{subsection.4.1}% 11
\BOOKMARK [3][-]{subsubsection.4.1.2}{Prevalence by programming language}{subsection.4.1}% 12
\BOOKMARK [3][-]{subsubsection.4.1.3}{Prevalence by repository owner type}{subsection.4.1}% 13
\BOOKMARK [3][-]{subsubsection.4.1.4}{Prevalence by project age}{subsection.4.1}% 14
\BOOKMARK [3][-]{subsubsection.4.1.5}{Prevalence by community size}{subsection.4.1}% 15
\BOOKMARK [2][-]{subsection.4.2}{RQ2: Documentation Maintenance}{section.4}% 16
\BOOKMARK [3][-]{subsubsection.4.2.1}{Documentation location}{subsection.4.2}% 17
\BOOKMARK [3][-]{subsubsection.4.2.2}{Creation}{subsection.4.2}% 18
\BOOKMARK [3][-]{subsubsection.4.2.3}{Update interval}{subsection.4.2}% 19
\BOOKMARK [3][-]{subsubsection.4.2.4}{Maintainers}{subsection.4.2}% 20
\BOOKMARK [3][-]{subsubsection.4.2.5}{Triggers}{subsection.4.2}% 21
\BOOKMARK [1][-]{section.5}{Threats to validity}{}% 22
\BOOKMARK [2][-]{subsection.5.1}{Internal validity}{section.5}% 23
\BOOKMARK [2][-]{subsection.5.2}{External validity}{section.5}% 24
\BOOKMARK [1][-]{section.6}{Conclusion}{}% 25