User:Fsiddiqui

From Foss2Serve
(Difference between revisions)
Jump to: navigation, search
 
(19 intermediate revisions by one user not shown)
Line 31: Line 31:
  
 
The releases page provides information about the various released versions, number of tickets for each (active and closed), and key features of each version.
 
The releases page provides information about the various released versions, number of tickets for each (active and closed), and key features of each version.
 +
 +
'''FOSS Field Trip'''
 +
 +
'''Part 1- GitHub'''
 +
 +
2.1. There are 20,378 repositories in the "education" category (retrieved: May 27 2018)
 +
2.2. The Insights page of the first project (timjacobi/angular-education) shows the commit activity for the entire year as well as for a specific week.
 +
 +
3.1 There are 396 repositories in the "humanitarian" category (retrieved: May 27 2018)
 +
3.2  For the HTBox/crisischeckin project, the last update was on April 22, 2017
 +
 +
4.1 For the "disaster management" category, there exist 229 projects (retrieved: May 27 2018)
 +
 +
'''Part 2- OpenHub'''
 +
 +
2.1 For the "education" category, 2260 projects were returned.
 +
2.2 For "KDE Education", none of the projects are on GitHub.
 +
2.3 There exist 10 similar projects
 +
2.4 OpenHub provides the following information about the project: project summary, code data, SCM data, community data
 +
 +
3.1 Number of "humanitarian" projects returned = 21.  Number of  "disaster management" projects returned =  30
 +
3.2 Several projects do not have activity information available probably due to very few contributors or the lack of activity updates posted.
 +
 +
4.1 The organizations page provides information about the newest as well as most active organizations. Information such as number of projects, affiliates, commits, etc is listed.
 +
 +
5.1 The last commit for openMRS Core was in Feb 2018
 +
 +
6.1 The last commit for openMRS on GitHub was on May 22, 2018.
 +
6.2 The commits information on both sites differs probably because OpenHub is not actively updated.
 +
 +
7. OpenHub provides an index to the available repositories. GitHub provides a repository where code and other data can be stored. However, lack of synchronization between information on the two sites can be a drawback.
 +
 +
'''Project Evaluation'''
 +
 +
 +
{| class="wikitable" style="width:100%;"
 +
|-
 +
! Evaluation Factor
 +
! Level<br/>(0-2)
 +
! style="width:60%;" | Evaluation Data
 +
|-
 +
| '''Licensing'''
 +
|  2
 +
|Mozilla Public License, version 2.0
 +
|-
 +
| '''Language'''
 +
|  1
 +
|Java, SQLPL
 +
|-
 +
| '''Level of Activity'''
 +
| 2
 +
| Active, commits in each week
 +
|-
 +
| '''Number of Contributors'''
 +
|  2
 +
|  303
 +
|-
 +
| '''Product Size'''
 +
| 2
 +
|222.42 MB
 +
|-
 +
| '''Issue Tracker'''
 +
|  2
 +
| Ready for Work: 1257 issues; Closed : 12875 issues; 5th Issue (Displaying service info in XForms) was created on 2013-10-25 11:30:51 GMT. Issues are being resolved.
 +
|-
 +
| '''New Contributor'''
 +
|  2
 +
| Installation information is available
 +
|-
 +
| '''Community Norms'''
 +
|  2
 +
| Observations about OpenMRS Code of Conduct : i. Well defined code of conduct. ii. Ways of creating a respectful community are clearly outlined. iii. Consequences of rule violation have also been outlined well. The interaction between members is very polite and members seem motivated to share information and help.
 +
|-
 +
| '''User Base'''
 +
|  2
 +
| There is a user base. Instructions for downloading, installing and using software exist.
 +
|-
 +
| '''Total Score'''
 +
|  17
 +
|
 +
|}
 +
 +
'''Intro to Copyright and Licensing'''
 +
 +
1. https://github.com/openmrs/openmrs-core has a license: Mozilla Public License, version 2.0  https://github.com/apache/incubator-fineract has a license: Apache License, Version 2.0  https://github.com/regulately/regulately-back-end : could not locate this repo
 +
 +
2.  Mozilla Public License, version 2.0
 +
 +
Can: commercial use, modify, distribute, sublicense, place warrant, use patient claims.
 +
 +
Cannot: use trademark, hold liable
 +
 +
Must: include copyright, include license, disclose source, include original
 +
 +
Apache License, Version 2.0
 +
 +
Can: commercial use, modify, distribute, sublicense, private use, use patient claims, place warranty
 +
 +
Cannot: hold liable, use trademark
 +
 +
Must: include copyright, include license, state changes, include notice
 +
 +
3. I would be comfortable contributing code to both project, given the known licenses.
 +
 +
'''FOSS in Courses 1'''
 +
 +
Identify activities or topics that you are interested in within your HFOSS project of interest:
 +
 +
Coding
 +
 +
Documentation
 +
 +
Bug fixing
 +
 +
Project Evaluation
 +
 +
Activities for a Computer Networking and Security class:
 +
 +
I found some useful activities which can be used (the Tor project) https://research.torproject.org:
 +
 +
Data collection
 +
 +
Analysis
 +
 +
Measurement and attack tools
 +
 +
Novel attacks and defenses
 +
 +
 +
ID - An identifier assigned to a specific bug
 +
Product - Name of the product that the bug is related to
 +
Comp - The component that contains the bug
 +
Assignee - The user to whom the bug is assigned for resolution
 +
Status - Indicates if the bug is new or re-opened, etc..
 +
Resolution - indicates if the bug has been fixed or not (will not fix, obsolete, etc).
 +
Summary - gives a short description of the bug
 +
 +
 +
Identify the order in which the bugs are initially displayed: Bugs are initially displayed decreasing order of bug ids
 +
 +
What is the meaning of the colors used when describing a bug (red, gray, black)?
 +
 +
The importance level.
 +
 +
Select a bug that you think that you might be able to fix and look at it more closely (click on the bug number).
 +
 +
786850
 +
 +
When was the bug submitted?
 +
 +
2017-08-26 22:00 UTC by Jeremy Bicha
 +
 +
What recent discussion has there been about the bug?
 +
 +
No recent discussion after having been reported
 +
 +
Is the bug current?
 +
 +
Yes
 +
 +
Is the bug assigned? To whom?
 +
 +
Yes, to Control-Center Maintainers
 +
 +
Describe what you would need to do to fix the bug.
 +
 +
Probably examine any compatibility issues with the screen reader.
 +
 +
Repeat the previous step with a different kind of bug.
 +
 +
 +
 +
 +
 +
Select a bug that you think that you might be able to fix and look at it more closely (click on the bug number).
 +
 +
742818
 +
 +
When was the bug submitted?
 +
 +
2015-01-12 19:05 UTC by Jeb Eldridge
 +
 +
What recent discussion has there been about the bug?
 +
 +
No recent discussion
 +
 +
Is the bug current?
 +
 +
Yes
 +
 +
Is the bug assigned? To whom?
 +
 +
Yes, to NetworkManager maintainer(s)
 +
 +
Describe what you would need to do to fix the bug.
 +
 +
Probably reinstall network tools
 +
 +
Part 2: Collective Reports
 +
 +
How many bug reports were opened in the last week? How many were closed?  58 opened, 248 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? 
 +
1 André Klapper 166
 +
2 António Fernandes 15
 +
3 John Ralls 14
 +
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?
 +
1 Mathieu Duponchelle 3
 +
2 Arnaud B. 3
 +
3 sreerenj 2
 +
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?
 +
1 Víctor Manuel Jáquez Leal 14
 +
2 Sebastian Dröge (slomo) 8
 +
3 Thibault Saunier 5
 +
Click on the "Reports" link at the top of the page and then click on the “Generate Graphical Reports” link.
 +
Plot a line graph of the severity of bugs by component for Orca:
 +
Select "Severity" for the vertical axis
 +
Select "Component" for the horizontal axis
 +
Select "Bar Graph" for type of graph
 +
Leave the "Multiple Images" as <none>
 +
Scroll down and select Orca from the Product menu.
 +
Click "Generate Report".
 +
 +
[[File:report.png]]
 +
What class were the majority of the bugs for braille? Minor
 +
What other reports can you generate? Line, Table, CSV for various products

Latest revision as of 12:46, 18 June 2018

Farhan Siddiqui is an Assistant Professor in the Department of Computer Science at Dickinson College in Pennsylvania. Dickinson is a liberal arts institution that offers undergraduate degree in various disciplines.

Dr. Siddiqui teaches a range of Computer Science courses including entry-level programming, advanced object oriented programming, networking, operating systems, and programming languages (imperative, functional, as well as declarative programming paradigms).

Dr. Siddiqui’s scholarly interests are in Computer Science Education, and Computer Networking with a focus on Wireless Networks, Sensor Networks, and the Internet of Things.

Sugar Labs Project Review

Roles applicable for my students include developer and content writer.

Commonalities across roles: It appears like all roles require participants to perform some type of pedagogy and communication. Educators explain and clarify complex ideas, content writers use their technical knowledge to provide documentation, a people person uses his/her people skills to create awareness about this project among people and encourages them to participate. Developers communicate by writing code, and a designer communicates via images and other state-of-the art graphics tools. Translators communicate to provide the technical knowledge to people in other languages.

Differences between roles: The methodology of implementing pedagogy and communication varies in each role.

In order to submit a bug, one needs to go to the correct Github repository. Then click on the Issues tab. The button called “New Issue” on the Issues tab should be used for logging a new issue and then clicking the “Submit New Issue” tab submits the issue.

The type of tickets include defect, enhancement, and task. Each ticket has a ticket number, summary, status, owner, priority, and milestone.

The date of the last commit is April 29, 2018.

The development team’s roadmap is updated at the beginning of each release cycle by the release team.


Sahana Eden Project Review

The Sahana bug tracker has a number of categories . The categories include active tickets, active tickets by version, milestone, by owner, recently fixed bugs, old bugs, etc.

The types of tickets under the active tickets link include defect, documentation, enhancement and task. Other information associated with each ticket includes the summary, component, version, priority, owner, status and date created.

The last commit was on May 4, 2018.

The releases page provides information about the various released versions, number of tickets for each (active and closed), and key features of each version.

FOSS Field Trip

Part 1- GitHub

2.1. There are 20,378 repositories in the "education" category (retrieved: May 27 2018) 2.2. The Insights page of the first project (timjacobi/angular-education) shows the commit activity for the entire year as well as for a specific week.

3.1 There are 396 repositories in the "humanitarian" category (retrieved: May 27 2018) 3.2 For the HTBox/crisischeckin project, the last update was on April 22, 2017

4.1 For the "disaster management" category, there exist 229 projects (retrieved: May 27 2018)

Part 2- OpenHub

2.1 For the "education" category, 2260 projects were returned. 2.2 For "KDE Education", none of the projects are on GitHub. 2.3 There exist 10 similar projects 2.4 OpenHub provides the following information about the project: project summary, code data, SCM data, community data

3.1 Number of "humanitarian" projects returned = 21. Number of "disaster management" projects returned = 30 3.2 Several projects do not have activity information available probably due to very few contributors or the lack of activity updates posted.

4.1 The organizations page provides information about the newest as well as most active organizations. Information such as number of projects, affiliates, commits, etc is listed.

5.1 The last commit for openMRS Core was in Feb 2018

6.1 The last commit for openMRS on GitHub was on May 22, 2018. 6.2 The commits information on both sites differs probably because OpenHub is not actively updated.

7. OpenHub provides an index to the available repositories. GitHub provides a repository where code and other data can be stored. However, lack of synchronization between information on the two sites can be a drawback.

Project Evaluation


Evaluation Factor Level
(0-2) 		Evaluation Data
Licensing 2 Mozilla Public License, version 2.0
Language 1 Java, SQLPL
Level of Activity 2 Active, commits in each week
Number of Contributors 2 303
Product Size 2 222.42 MB
Issue Tracker 2 Ready for Work: 1257 issues; Closed : 12875 issues; 5th Issue (Displaying service info in XForms) was created on 2013-10-25 11:30:51 GMT. Issues are being resolved.
New Contributor 2 Installation information is available
Community Norms 2 Observations about OpenMRS Code of Conduct : i. Well defined code of conduct. ii. Ways of creating a respectful community are clearly outlined. iii. Consequences of rule violation have also been outlined well. The interaction between members is very polite and members seem motivated to share information and help.
User Base 2 There is a user base. Instructions for downloading, installing and using software exist.
Total Score 17

Intro to Copyright and Licensing

1. https://github.com/openmrs/openmrs-core has a license: Mozilla Public License, version 2.0 https://github.com/apache/incubator-fineract has a license: Apache License, Version 2.0 https://github.com/regulately/regulately-back-end : could not locate this repo

2. Mozilla Public License, version 2.0

Can: commercial use, modify, distribute, sublicense, place warrant, use patient claims.

Cannot: use trademark, hold liable

Must: include copyright, include license, disclose source, include original

Apache License, Version 2.0

Can: commercial use, modify, distribute, sublicense, private use, use patient claims, place warranty

Cannot: hold liable, use trademark

Must: include copyright, include license, state changes, include notice

3. I would be comfortable contributing code to both project, given the known licenses.

FOSS in Courses 1

Identify activities or topics that you are interested in within your HFOSS project of interest:

Coding

Documentation

Bug fixing

Project Evaluation

Activities for a Computer Networking and Security class:

I found some useful activities which can be used (the Tor project) https://research.torproject.org:

Data collection

Analysis

Measurement and attack tools

Novel attacks and defenses


ID - An identifier assigned to a specific bug Product - Name of the product that the bug is related to Comp - The component that contains the bug Assignee - The user to whom the bug is assigned for resolution Status - Indicates if the bug is new or re-opened, etc.. Resolution - indicates if the bug has been fixed or not (will not fix, obsolete, etc). Summary - gives a short description of the bug


Identify the order in which the bugs are initially displayed: Bugs are initially displayed decreasing order of bug ids

What is the meaning of the colors used when describing a bug (red, gray, black)?

The importance level.

Select a bug that you think that you might be able to fix and look at it more closely (click on the bug number).

786850

When was the bug submitted?

2017-08-26 22:00 UTC by Jeremy Bicha

What recent discussion has there been about the bug?

No recent discussion after having been reported

Is the bug current?

Yes

Is the bug assigned? To whom?

Yes, to Control-Center Maintainers

Describe what you would need to do to fix the bug.

Probably examine any compatibility issues with the screen reader.

Repeat the previous step with a different kind of bug.



Select a bug that you think that you might be able to fix and look at it more closely (click on the bug number).

742818

When was the bug submitted?

2015-01-12 19:05 UTC by Jeb Eldridge

What recent discussion has there been about the bug?

No recent discussion

Is the bug current?

Yes

Is the bug assigned? To whom?

Yes, to NetworkManager maintainer(s)

Describe what you would need to do to fix the bug.

Probably reinstall network tools

Part 2: Collective Reports

How many bug reports were opened in the last week? How many were closed? 58 opened, 248 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? 1 André Klapper 166 2 António Fernandes 15 3 John Ralls 14 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? 1 Mathieu Duponchelle 3 2 Arnaud B. 3 3 sreerenj 2 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? 1 Víctor Manuel Jáquez Leal 14 2 Sebastian Dröge (slomo) 8 3 Thibault Saunier 5 Click on the "Reports" link at the top of the page and then click on the “Generate Graphical Reports” link. Plot a line graph of the severity of bugs by component for Orca: Select "Severity" for the vertical axis Select "Component" for the horizontal axis Select "Bar Graph" for type of graph Leave the "Multiple Images" as <none> Scroll down and select Orca from the Product menu. Click "Generate Report".

Report.png What class were the majority of the bugs for braille? Minor What other reports can you generate? Line, Table, CSV for various products

Retrieved from "http://foss2serve.org/index.php?title=User:Fsiddiqui&oldid=12380"
Personal tools
Namespaces
Variants
Actions
Events
Learning Resources
HFOSS Projects
Evaluation
Navigation
Toolbox