-
Notifications
You must be signed in to change notification settings - Fork 0
/
annot.bib
42 lines (36 loc) · 4.03 KB
/
annot.bib
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
% This is annote.bib
% Author: Ketlin de Mello Moreira
% A demo for the CCI Program Project Summer 2021.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%
@misc{Rogers21,
title = {Querying the Exascale Compute Project – How do Cross-Team Collaborations Enable Interoperable Software?},
author = {Rogers, David M. and Milewicz, Reed and Sims, Benjamin and Watson, Greg and Raybourn, Elaine M.},
month = "March",
year = {2021},
annote = {The author presents an analytical investigation on an ongoing study of collaboration patterns and dependencies among ECP software projects. The presentation exemplifies how the repository mining tool "Reposcanner" can be utilized to gather data on commits, issues, comments, and reactions on GitHub repositories, and how such information could be used to identify practices to aid collaboration between the Exascale Compute Project community. Key takeaways from the source include: a highly interconnected ecosystem of project teams actively make use of pull requests and issues, large teams, code tests, and examples all go together, as well as code examples attract collaborators, and lead to implementing automated build and test systems.},
note = {Labels: contributors; continuous integration; documentation; tutorials; test}
}
@misc{Norris21,
title = {Data-driven Analysis of HPC Software Development Processes},
author = {Norris, Boyana and Perkins, Carter and Ndemeye, Bosco and Fickas, Stephen and Acosta, Armando and Sood, Kanika and Dubey, Anshu},
month = "June",
year = {2021},
annote = {The presentation by Boyana Norris features to analyze available data such as git activity, issues, and mailing list to help define patterns that have been shown to impact developer's productivity and code quality in the HPC community.
Insightful graphs within the presentation include "User and community engagement," "Reliance on an individual developer," "Hot topics based on issues," and "Changes on code complexity." This presentation helps guide understanding of how developers' behaviors impact the success of software productivity and sustainability.}
}
%%
%Check about the right reference for this - article or report
%TECHREPORT{bele:01,
@article{Heroux20,
title = {Advancing Scientific Productivity through Better Scientific Software: Developer Productivity and Software Sustainability Report},
author = {Heroux, Michael A. and McInnes, Lois and Bernholdt, David and Dubey, Anshu and Gonsiorowski, Elsa and Marques, Osni and Moulton, J. David and Norris, Boyana and Raybourn, Elaine and Balay, Satish and Bartlett, Roscoe A. and Childers, Lisa and Gamblin, Todd and Grubel, Patricia and Gupta, Rinku and Hartman-Baker, Rebecca and Hill, Judith and Hudson, Stephen and Junghans, Christoph and Klinvex, Alicia and Milewicz, Reed and Miller, Mark and Ah Nam, Hai and O Neal, Jared and Riley, Katherine and Sims, Ben and Schuler, Jean and Smith, Barry F. and Vernon, Louis and Watson, Gregory R. and Willenbring, James and Wolfenbarger, Paul},
doi = {10.2172/1606662},
url = {https://www.osti.gov/biblio/1606662},
place = {United States},
year = {2020},
month = {February},
annote = {The Exascale Computing Project provides an opportunity to advance computational science and engineering through an accelerated growth phase in extreme-scale computing. However, changes and computer architecture give rise to challenges on development productivity, product quality, development time, software sustainability, and evolving software capabilities.
This report summarizes technical and cultural challenges in software productivity, sustainability and introduces work by IDEAS within ECP to foster and advance software development for extreme-scale environments. IDEAS goal is comprised of four synergetic strategies: (1) Customize and curate methodologies, (2) Incrementally and iteratively improve software practices, (3) Establish software communities, (4) Engage in community outreach.}
}
%%