text
stringlengths 0
634k
|
---|
As a result the offset/name-based technique could end up detecting a large share of older commits as authored by African developers, and to a lesser extent Europeans. |
To counter these issues we combine the two geolocation techniques together by applying the offset/name-based techniques to all commits with a non-zero UTC offset, and the email-based on to all other commits. |
\section{Results and Discussion} |
\label{sec:results} |
\begin{figure*} |
\centering |
\includegraphics[width=\linewidth]{stacked.pdf} |
\caption{Ratio of commits (above) and active authors (below) by world zone over the 1971--2020 period.} |
\Description[Chart]{Stacked bar chart showing the world zone ratios for commits and authors over the 1971--2020 period.} |
\label{fig:results} |
\end{figure*} |
To answer \cref{rq:geodiversity} we gathered the number of commits and distinct authors per year and per world zone. |
We present the obtained results in \Cref{fig:results} as two stacked bar charts, showing yearly breakdowns for commits and authors respectively. |
Every bar represents a year and is partitioned in slices showing the commit/author ratio for each of the world regions of \Cref{fig:worldmap} in that year. |
To avoid outliers due to sporadic contributors, in the author chart we only consider authors having contributed at least 5 commits in a given year. |
While observing trends in the charts remember that the total numbers of commits and authors grow exponentially over time. |
Hence for the first years in the charts, the number of data points in some world regions can be extremely small, with negative consequences on the stability of trends. |
\paragraph{Geographic diversity over time} |
Overall, the general trend appears to be that the \textbf{geographic diversity in public code is increasing}: North America and Europe alternated their ``dominance'' until the middle of the 90s; from that moment on most other world regions show a slow but steady increment. |
This trend of increased participation into public code development includes Central and South Asia (comprising India), Russia, Africa, Central and South America, |
Notice that also zones that do not seem to follow this trend, such as Australia and New Zealand, are also increasing their participation, but at a lower speed with respect to other zones. |
For example, Australia and New Zealand incremented the absolute number of their commits by about 3 orders of magnitude from 2000 to present days. |
Another interesting phenomenon that can be appreciated in both charts is the sudden contraction of contributions from North America in 1995; since the charts depict ratios, this corresponds to other zones, and Europe in particular, increasing their share. |
An analysis of the main contributions in the years right before the contraction shows that nine out of ten have \texttt{ucbvax.Berkeley.EDU} as author email domain, and the tenth is Keith Bostic, one of the leading Unix BSD developers, appearing with email \texttt{bostic}. |
No developer with the same email domain appears anymore within the first hundred contributors in 1996. |
This shows the relevance that BSD Unix and the Computer Systems Research Group at the University of California at Berkeley had in the history of open source software. |
The group was disbanded in 1995, partially as a consequence of the so-called UNIX wars~\cite{kernighan2019unixhistory}, and this contributes significantly---also because of the relatively low amount of public code circulating at the time---to the sudden drop of contributions from North America in subsequent years. |
Descendant UNIX operating systems based on BSD, such as OpenBSD, FreeBSD, and NetBSD had smaller relevance to world trends due to (i) the increasing amount of open source code coming from elsewhere and (ii) their more geographically diverse developer community. |
Another time frame in which the ratios for Europe and North America are subject to large, sudden changes is 1975--79. |
A preliminary analysis shows that these ratios are erratic due to the very limited number of commits in those time period, but we were unable to detect a specific root cause. |
Trends for those years should be subject to further studies, in collaboration with software historians. |
\paragraph{Colonialism} |
Another trend that stands out from the charts is that Africa appears to be well represented. |
To assess if this results from a methodological bias, we double-checked the commits detected as originating from Africa for timezones included in the $[0, 3]$ range using both the email- the offset/name-based methods. |
The results show that the offset/name-based approach assigns 22.7\% of the commits to Africa whereas the email-based one only assigns 2.7\% of them. |
While a deeper investigation is in order, it is our opinion that the phenomenon we are witnessing here is a consequence of colonialism, specifically the adoption of Europeans names in African countries. |
For example the name Eric, derived from Old Norse, is more popular in Ghana than it is in France or in the UK. |
This challenges the ability of the offset/name-based method to correctly differentiate between candidate places. |
Together with the fact that several African countries are largely populated, the offset/name-based method could detect European names as originating from Africa. |
While this cuts both way, the likelihood of a random person contributing to public code is very different between European countries, all having a well-developed software industry, and African countries that do not all share this trait. |
\paragraph{Immigration/emigration} |
Another area where a similar phenomenon could be at play is the evolution of Central and South America. |
Contribution from this macro region appears to be growing steadily. |
To assess if this is the result of a bias introduced by the name-based detection we analyzed the evolution of offset/name-based assignment over time for authors whose email domain is among the top-ten US-based entities in terms of overall contributions (estimated in turn by analyzing the most frequent email domains and manually selecting those belonging to US-based entities). |
In 1971 no author with an email from top US-based entities is detected as belonging to Central and South America, whereas in 2019 the ratio is 12\%. |
Nowadays more than one tenth of the people email-associated to top US-based entities have popular Central and South American names, which we posit as a likely consequence of immigration into US (emigration from Central and South America). |
Since immigration has a much longer history than what we are studying here, what we are witnessing probably includes long-term consequences of it, such as second and third generation immigrants employed in white-collar jobs, such as software development. |
\section{Limitations and Future Work} |
\label{sec:conclusion} |
We have performed an exploratory, yet very large scale, empirical study of the geographic diversity in public code commits over time. |
We have analyzed 2.2 billion\xspace public commits covering the \DATAYearRange/ time period. |
We have geolocated developers to \DATAWorldRegions/ world regions using as signals email domains, timezone offsets, and author names. |
Our findings show that the geographic diversity in public code is increasing over time, and markedly so over the past 20--25 years. |
Observed trends also co-occur with historical events and macro phenomena like the end of the UNIX wars, increase of coding literacy around the world, colonialism, and immigration. |
\medskip |
\emph{Limitations.} |
This study relies on a combination of two geolocation methods: one based on email domains, another based on commit UTC offsets and author names. |
We discussed some of the limitations of either method in \Cref{sec:method}, motivating our decision of restricting the use of the email-based method to commits with a zero UTC offset. |
As a consequence, for most commits in the dataset the offset/name-based method is used. |
With such method, the frequencies of forenames and surnames are used to rank candidate zones that have a compatible UTC offset at commit time. |
A practical consequence of this is that for commits with, say, offset UTC+09:00 the candidate places can be Russia, Japan and Australia, depending on the specific date due to daylight saving time. |
Popular forenames and surnames in these regions tend to be quite different so the likelihood of the method to provide a reliable detection is high. |
For other offsets the set of popular forenames and surnames from candidate zones can exhibit more substantial overlaps, negatively impacting detection accuracy. |
We have discussed some of these cases in \Cref{sec:results}, but other might be lingering in the results impacting observed trends. |
The choice of using the email-based method for commits with zero UTC offset, and the offset/name-based method elsewhere, has allowed us to study all developers not having a country-specific email domain (ccTLD), but comes with the risk of under-representing the world zones that have (in part and in some times of the year) an actual UTC offset of zero. |
A potential bias in this study could be introduced by the fact that the name database used for offset/name-based geolocation only contains names formed using Latin alphabet characters. |
We looked for names containing Chinese, Japanese, and Korean characters in the original dataset, finding only a negligible amount of authors who use non-Latin characters in their VCS names, which leads us to believe that the impact of this issue is minimal. |
We did not apply identity merging (e.g., using state-of-the-art tools like SortingHat~\cite{moreno2019sortinghat}), but we do not expect this to be a significant issue because: (a) to introduce bias in author trends the distribution of identity merges around the world should be uneven, which seems unlikely; and (b) the observed commit trends (which would be unaffected by identity merging) are very similar to observed author trends. |