User:Mgerosa
| Line 87: | Line 87: | ||
The MPL seems less restrictive. I am more comfortable with less restrictive licenses. | 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 | ||
Revision as of 15:54, 15 June 2018
Contents |
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
| Evaluation Factor | Level (0-2) |
Evaluation Data |
|---|---|---|
| Licensing | 2 | MPL 2.0 w/ HD |
| Language | 2 | 1. Java 96.2%
2. SQLPL 2.9% 3. Other 0.9% |
| Level of Activity | 2 | Commits in every quarter last year |
| Number of Contributors | 2 | 303 contributors |
| Product Size | 2 | 222.45 MB |
| Issue Tracker | 2 | Closed issues – 12950
Open issues – 1254 5th issue was created on 2013-10-25 |
| New Contributor | 2 | Welcoming new contributors. |
| Community Norms | 2 | There are conventions such as coding practice, naming and GitHub conventions.
The communications between members appear to be professional and polite. |
| User Base | 2 | There is a well-established user base, with several tutorials. |
| Total Score | 18 |
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
