User:Gpinto
Gustavo Pinto is an Assistant Professor at the Federal University of Pará, Brazil. He received his Ph.D. from the Federal University of Pernambuco, also form Brazil. During his Ph.D., he was a visiting scholar at the State University of New York at Binghamton.
Currently, prof. Pinto focus most of his efforts on the broad area of software engineering, with an emphasis to open-source software and communities, mining software databases, and refactoring.
His personal website is: www.gustavopinto.org
Notes for the Sugar Labs project
Contributions
Since I teach programming language courses, the developer role is the most applicable roles for my students. However, the translator and the designer role might be applicable for some students that have such skills, but it is not always the case. That said, one commonality across role is that they require participates to communicate with each other. Since I work in a non-English speaking country, the lack of English skills is a serious problem. As regarding the difference, each role requires different skills. It might be harder for a content writer do the work of a developer, if she does not have such skills.
Tracker
Submitting a bug is a fairly easy process. If you find a bug, you just need to fill an open form with information about this bug. In particular, you need to describe the step by step that one needs to do to reproduce the bug. This is an example of a sequence of steps that helps one to reproduce a bug:
1. start HelloWorld activity, change name to example1, then stop, 2. start HelloWorld activity, change name to example2, then stop, 3. resume example1, 4. in the journal, try to rename example2.
https://bugs.sugarlabs.org/ticket/4982
Some suggestions on how to fix the bug are welcome, but are not mandatory.
When filling a report, one can describe a bug, that is, a "defect", but one can also suggest "enhancement" or "task" that might be valuable for the project. Whether these reports will be fixed or not is a hard question.
The last commit of the sugar lab project was on May 15th. So this might be a fairly active project.
Finally, the roadmap and the releases are related in the sense that the roadmap contains a schedule of the release dates. The release, therefore should ensure that the tasks are done on time for releasing.
FOSS Field Trip (Activity)
On Github
There are 13,576 projects under search word Education. Project nodejs/education has 28 commits by Jun 10th.
There are 303 humanitarian projects. The last commit of project HTBox/crisischeckin was on April 22 (52774db). There are 152 disaster management projects.
On OpenHub
There are 3470 educational projects. KDE is the third result. The codes have a git URL but I didn’t find the Github URL. There are 10 similar projects. OpenHub provides information about programming language, cost, security, commits, and contributors.
There are 34 Humanitarian projects and 54 disaster management projects If the project does not have any commit in the last 24 months, OpenHub shows it as inactive. The menu Organizations show the organizations behind the OSS projects. The last commit of project OpenMRS Core was on April 17, 2017 On Github, the last commit of project OpenMRS Core was on June 7, 2017. Maybe the case that OpenHub does not work properly when trying to update some projects’ data.
One of the benefits of using Github and OpenHub for selecting projects is that it is easy to see if a project is active or if it is diverse, in terms of contributors. However, there are problems if merging data from these two websites: they may not be the same.
Project Evaluation (Activity)
| Evaluation Factor | Level (0-2) |
Evaluation Data |
|---|---|---|
| Licensing | 2 | MPL 2.0 w/ HD © OpenMRS Inc. |
| Language | 2 | Java 95.4% SQLPL 3.0% GAP 0.7% XSLT 0.4% CSS 0.3% JavaScript 0.1% HTML 0.1% |
| Level of Activity | 2 | openmrs-core is very active |
| Number of Contributors | 2 | openmrs-core has 263 different source code contributors |
| Product Size | 1 | openmsr-core has 3.73M lines of code |
| Issue Tracker | 2 | 512 Open issues. 3,223 closed issues. 5th issue open on Nov 27, 2013. Issues are as active as code. |
| New Contributor | 2 | It is clearly stated how can one contribute to the project (on this https://github.com/openmrs/openmrs-core/blob/master/CONTRIBUTING.md file). It shows IRC channel, JIRA website, how to download and use, etc. |
| Community Norms | 2 | openmsr-core states some code conventions at this website: https://wiki.openmrs.org/display/docs/Conventions. Conventions are related to Java code, JavaScript code, git, github, code review, etc. Talk can be found here: https://talk.openmrs.org/. Examples include technical issues (https://talk.openmrs.org/t/new-rest-implementation-for-systeminformation/11829), organizational issues (https://talk.openmrs.org/t/need-to-retire-original-jetstream-project-and-move-to-official-one/11516), or demo inviations (https://talk.openmrs.org/t/openmrs-sprint-6-demo-invitation/11398). |
| User Base | 2 | the Talk website shows that there are many users using openmrs, e.g., https://talk.openmrs.org/t/installation-error-on-centos-6-8/10759 |
| Total Score | 17 | openmrs seems very good to students work on. |
Licenses
openmrs-core uses Mozilla 2.0 Free incubator-fineract uses Apache 2.0 Open comfortable regulately-back-end does not state a license
I am comfortable contributing to any software that at least states an open-source license.
FOSS In Courses 1
This term I’m teaching algorithms. In this course, I envision two ways that students can use OSS as part of the course.
First, students can work on trying to find bugs on existing programs. It is not require to come up with a solution, but it would be better. Second, students will be invited to improve the documentation. This can be done in terms of translation (e.g., translating to Portuguese) or creating an example.
Students more motivated can go further and do source-code modifications. Students can start with simple changes (e.g., changing a variable name or adding comments). If time permits, students can try to fix a bug (probably the bug previously reported).
Bug Reports
ID: an auto-incremental value for the pull request. Sev: I didnt find this one. It might be severity. Pri: Might be the priority of the bug OS: The operating system in which the bug was found Product: How bugs are categorized Status: If the bug was confirmed by another developers Resolution: If one resolution was indicated Summary: The summary of the bug
- I inferred most of the information above. For other cases, I relied at the bug repository, which contains details about some of these variables. - The bugs are ordered by status (UNCO first, then NEW) - Colors are meant to describe the importance of the bug - Bug 741944 was submitted on 2014-12-24 15:21 UTC, only one comment was made, the bug was assigned to Banshee Maintainers. To fix this bug, one need to import one audio feature to Banshee.
Collective Reports
- How many bug reports were opened in the last week? 94
- How many were closed? 74
- More bugs were opened than closed in the last 7 days
- Nicolas Dufresne, Piotr Drąg, Michael Catanzaro are the top three bug closers. I think it is important to recognize the effort that the members of the community place on making the project stable (that is, little bugs).
- Dan Jacobson, Bastien Nocera, and Guillaume Desmottes are the top three bug reporters. That is little overlap between bug closers and bug reporters.
- Severity of orca:
[[1]]
- Most of braile bugs are normal ones. - Several other graphics can be made, in terms of classification, product, component, etc.
Github
Pull request made at: https://github.com/foss2serve/git-activity/pull/91
