User:Mgerosa

Latest revision as of 01:17, 18 June 2018

Marco Gerosa

Marco Aurelio Gerosa is an Associate Professor and in the School of Informatics, Computing, and Cyber Systems at the Northern Arizona University (NAU). NAU is located in the beautiful city of Flagstaff, close to the Grand Canyon. The school recently received solid investment to increase the number of faculties and the infrastructure for research.

Dr. Gerosa researches Software Engineering and CSCW (Computer Supported Cooperative Work and Social Computing). Recent projects include the development of tools and strategies to support newcomers onboarding to open source software communities and the design of chatbots for tourism. He published more than 200 papers and has served on the program committee (PC) of important conferences, such as FSE, CSCW, SANER, and MSR. He has more than 16 years of teaching experience.

Prior to coming to NAU, Dr. Gerosa was an Associate Professor at the University of São Paulo, Brazil.

More details on my web page: http://www.marcoagerosa.com

Activity: Intro to FOSS Project Anatomy

SugarLab: Students can perform several roles, such as developer, content writer, and translator. I found interesting to have an "What can I do in an hour" page. To report a bug, the person should go to the GitHub page and open an issue on the appropriate component. There are several types of tickets such as defect, enhancement, and task. Each ticket has who reported, priority, component, severity, bug status, milestone, version, distribution/OS, and description. At the time if this writing, the last commit was made on Apr 29, 2018. The Development Team's Roadmap is updated at the beginning of each release cycle.

The Sahana Eden Project: There are multiple ways of contributing. As in the SugarLab, there are domain-specific roles (e.g. GIS Specialists) as well as common roles (e.g., developers, testers, designers, translators, etc.). The project as an issue tracker with several tickets, encompassing categories such as defect/bug, enhancement, documentation, and task. These categories are mostly similar to the ones from the SugarLab project. The information for each ticket is also similar between the projects. Few additional fields are due date, cc, and launchpad bug. At the time if this writing, the last commit was made on Jun 15, 2018. In the roadmap, they list milestone, including the progress, the number of tickets closed and active, the planned date, and the features. however, this page doesn't seem to be updated very often.

Activity: FOSS Field Trip

GitHub: I found 20,721 repositories by searching for "Education." The first project is timjacobi/angular-education. The insights/commits lists the number of commits per week and per day of the last week. The search for "humanitarian" resulted in 399 repositories. The HTBox/crisischeckin project was last updated on Apr 22, 2017. There are 237 repositories for "disaster management."

OpenHub: I found aprox. 2,260 projects by searching for "Education." For the KDE Education project, all the code locations point to kde.org. Four projects are listed as similar. OpenHub provides a lot of information about the project, such as licenses and statistics of code, activity, and community. In the searches for "humanitarian" and "disaster management," I could find 21 and 30 projects respectively. The organizatons web page reports the most active and the newest organizations as well as some stats by sector. Searching for OpenMRS, I could find that the last commit was made 3 months ago. On GitHub, the last commit was yesterday. OpenHub reports that the project was analyzed 3 months ago.

I think both sites have complementary information. OpenHub presents a better overview of the project while GitHub provides more specific and current information.

Activity: Project Evaluation

Activity: Intro to Copyright and Licensing

Licenses: https://github.com/openmrs/openmrs-core ---> Mozilla Public License, version 2.0 https://github.com/apache/incubator-fineract ---> Apache License Version 2.0 https://github.com/regulately/regulately-back-end ---> No license

MPL 2.0: https://tldrlegal.com/license/mozilla-public-license-2.0-(mpl-2) Apache 2.0: https://tldrlegal.com/license/apache-license-2.0-(apache-2.0)

The MPL seems less restrictive. I am more comfortable with less restrictive licenses.

Activity: OSS in Courses 1

I plan to use OSS in Software Engineering, covering the following activities:

• Coding
• Documentation
• Software architecture
• Software testing
• Reverse engineering
• Requirements
• Process

Activity: Intro to Bug Trackers

PART I (1) 304 bugs found. (2) ID = Identifier - 78201 to 795807 Product = product affected by the bug Comp = Component (accessibility, API, application, etc.) Assignee = assigned to Status = UNCONFIRMED, NEW, ASSIGNED, REOPENED, NEEDINFO Resolution = all bugs have this fied as blank Summary = description of the bug (3) I found this information by analyzing the list and opening bugs. (4) I could not identify the order. (5) Importance: critical, normal, and enhancement. (6) Bug 668439 - Create help text object property When was the bug submitted? 2012-01-22 15:41 UTC What recent discussion has there been about the bug? None Is the bug current? Possibly not Is the bug assigned? To whom? ATK maintainer(s) Describe what you would need to do to fix the bug. Find all places where AtkObjects are used and include the help property. (7) Bug 648260 - Improve the documentation of ATK_STATE_VISIBLE and deprecate ATK_STATE_SHOWING When was the bug submitted? 2011-04-20 00:01 What recent discussion has there been about the bug? Sharing a blog post Is the bug current? No Is the bug assigned? To whom? ATK maintainer(s) Describe what you would need to do to fix the bug. Improve the documentation.

PART II How many bug reports were opened in the last week? How many were closed? 56 reports opened and 245 reports closed What was the general trend last week? Were more bugs opened than closed or vice versa? More closed than opened Who were the top three bug closers? Why is this important to know? André Klapper, António Fernandes, and John Ralls. These are very active developers in the community. Who were the top three bug reporters? Are these the same as the top three bug closes? What is the overlap in these two lists? Arnaud B., Mathieu Duponchelle, and Piotr Drąg. No overlap between the lists. Who are the top three reviewers of patches? What is the overlap between these lists and the bug closers and bug reporters? What is the overlap between patch contributors and patch reviewers? Víctor Manuel Jáquez Leal, Mathieu Duponchelle, and Sebastian Dröge (slomo). The only overlap is Mathieu Duponchelle. Click on the "Reports" link at the top of the page and then click on the “Generate Graphical Reports” link. The possible reports are: Summary of bug activity for the last week. Generic tabular reports Generic graphical reports Change Over Time Old Charts - plot the status and/or resolution of bugs against time, for each product in your database. New Charts - plot any arbitrary search against future time. Far more powerful. Frequently (and recently) duplicated bugs Unreviewed patches Frequently Duplicated Stack Traces