User:Pnarwal
(→PART -C Introduction to Bug Trackers activity) |
(→FOSS in courses 2) |
||
| (6 intermediate revisions by one user not shown) | |||
| Line 243: | Line 243: | ||
4 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? | 4 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? | ||
| − | + | {| class="wikitable" | |
!Name | !Name | ||
!#Contributions | !#Contributions | ||
| Line 257: | Line 257: | ||
|- | |- | ||
|} | |} | ||
| + | |||
5 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 | 5 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? | patch contributors and patch reviewers? | ||
| − | + | ||
| + | {| class="wikitable" | ||
!Name | !Name | ||
!#Contributions | !#Contributions | ||
| Line 274: | Line 276: | ||
|- | |- | ||
|} | |} | ||
| + | |||
| + | |||
| + | |||
| + | What class were the majority of the bugs for braille? | ||
| + | [[File:report-2017-06-28.png]] | ||
| + | [https://bugzilla.gnome.org/report.cgi?y_axis_field=bug_severity&cumulate=0&z_axis_field=&format=bar&x_axis_field=component&no_redirect=1&query_format=report-graph&short_desc_type=allwordssubstr&short_desc=&product=orca&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=NEEDINFO&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_id=&bug_id_type=anyexact&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&emailtype3=substring&email3=&chfieldvalue=&chfieldfrom=&chfieldto=Now&j_top=AND&f1=noop&o1=noop&v1=&action=wrap] | ||
| + | |||
| + | What other reports can you generate? | ||
| + | |||
| + | Line graph, pie charts | ||
== '''FOSS in courses 2''' == | == '''FOSS in courses 2''' == | ||
| + | |||
| + | |||
| + | Directions | ||
| + | |||
| + | Recalling your list of activities/topics from FOSS in Courses 1 (Instructors), identify the ways that these FOSS activities/topics can be structured. | ||
| + | |||
| + | Possibilities include: | ||
| + | |||
| + | 1 Lectures | ||
| + | |||
| + | 2 In-class activity | ||
| + | |||
| + | 3 Homework | ||
| + | |||
| + | 4 Stream of related activities | ||
| + | |||
| + | 5 Project | ||
| + | |||
| + | 6 List the revised activities on your wiki page. For each activity/topic: | ||
| + | |||
| + | 7 Identify some possible learning outcomes that should be fulfilled with the activities/task. | ||
| + | |||
| + | 8 Describe any prerequisite knowledge needed to complete the activity. This does not need to be a complete list. | ||
| + | |||
| + | 9 Estimate the time required for instructor prep, for student completion and elapsed calendar time. Are you going to have to synchronize your activity with | ||
| + | the community or can the activity/topic be covered independent of the HFOSS community schedule. | ||
| + | |||
| + | 10 Think about possible input required from the HFOSS community. How much input is required and what kind? | ||
| + | |||
| + | 11 If the result of the activity is contributed back to the HFOSS project, describe the contribution and its usefulness. | ||
| + | |||
| + | 12 Describe the assessment/grading approach - What will the basis for grading be? Will this be a team activity or individual? Is there a role for the HFOSS | ||
| + | community in helping assess student work? For instance, must the work be committed or otherwise accepted by the community? | ||
| + | |||
| + | 13 List any questions or concerns that you have about the activity/task. | ||
| + | |||
| + | 14 List any stumbling blocks or barriers to carrying out the activity/task. | ||
Latest revision as of 19:23, 29 June 2017
Contents |
Priti Narwal
Priti Narwal is an Assistant Professor in Department of Computer Science and Engineering, Faculty of Engineering and Technology in Manav Rachna International University, Faridabad, India where she is taking undergraduate courses like Introduction to Virtualization & Cloud Computing, Cloud Deployment Model, Computer Graphics, Data Warehouse & Data Mining, Compiler Design, Computer Networks and Network Security and Management.
Apart from her academic responsibilities, she has been actively participating as a Technical Reviewer in the Program committee of International Conferences like ICRITO'2016, ICRITO'2017 and ICTUS'2017. She is also pursuing Ph.D from Amity University, Noida, India and her research interests include Game Theory, Virtualization, Cloud Security and Deployment.
Intro to Foss Project Anatomy
The Sugar Labs Project
Contributions that can be done by our students
Developer
In my opinion, our students can contribute to the project as Developers as they can work with C, JavaScript, Web App development and GNU/Linux system administration.
Designer
This can also be chosen by students as they already have a course in their syllabus named Computer Graphics in which they would use their C/C++ programming skills to implement Graphics and Animation in their labs. So, they would feel motivated to learn and use additional vector & raster graphics tools required for this role.
The similarities could be the possibilities for the students to use their programming skills as both developer and designer but as the roles are different, outcomes may also differ.
Tracker
General Process of submitting a Bug
If you find a bug or would like to report an issue with Sugar, visit https://github.com/sugarlabs and look for the activity or a sugar component repository that you think is relevant.
If you don't know which one to use, use https://github.com/sugarlabs/sugar, and be sure to sign up and sign in to Github.
Then visit the issues tab of the repo, and hit the big green button to report your issue.
If you haven't written issue reports before, here's a great guide: http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
Types/Categories of Tickets
The tickets are being generated with Ticket no, Summary, Status, Type and Priority. Defect, Enhancement and Task are some of the ticket types where priority level also vary from low, normal or high.
Repository
Date of the last commit: June 5 2017
Release cycle
The roadmap is updated by the release team before each release cycle.
Communication
Communication between members of this project is through following mediums:
IRC: https://wiki.sugarlabs.org/go/Internet_Relay_Chat
Mailing lists: http://lists.sugarlabs.org/
Blog: http://planet.sugarlabs.org/
Wiki: http://wiki.sugarlabs.org/go/Welcome_to_the_Sugar_Labs_wiki
The Sahana Eden Project
Sahana Eden is an Open Source Humanitarian Platform which can be used to provide solutions for Disaster Management, Development, and Environmental Management sectors.
Community
To contribute to Sahana Eden
Developers, Testers, Bug Marshals, Newsletter Report Writers, Documenters, Translators, Designers, SysAdmin and GIS Specialists.
The roles that would be most applicable for my students are:
1. Developers 2. Testers - 3. Designers- This requires skills like CSS and HTML as pre-requisites and they have a subject named Web Technology and Cyber security in their undergraduate course in which they use HTML and Javascript.
Tracker
The information on Sahana Eden Bug tracker page is more then that of Sugar Lab page as the bugs are assigned keywords like easy, sandy easy which makes it suitable for new developers to tackle. Moreover, Column and filter component is also added in this bug tracker page.
Types/Categories of Tickets
The types are: enhancement and defect/bug where priority is minor, major and trivial
Repository
Date of the last commit: June 11 2017
Release cycle
No release
Communication
IRC: http://eden.sahanafoundation.org/wiki/Chat Mailing lists:
Wiki: http://wiki.sahanafoundation.org/community/mailing_lists
Google Groups: https://groups.google.com/forum/?fromgroups#!forum/sahana-eden
Part B- Foss Field Trip Activity
Part 1 - GitHub
For Educational Repositories
1. No. of Repositories for Educational applications- 13,576
2. This shows the date of latest commits by users
For Humanitarian Repositories
1. No. of repositories for Humanitarian applications- 303
2. Last update- 22/04/17
For Disaster Management Applications
1. How many projects are there in this category? 153 repository results
Part 2 - OpenHub
Education
1. Number of educational projects-3470
2. KDE education is the third result, shows 23 code locations on GitHub
3. There are 10 similar projects to KDE- KStars, Step. Kmplot, Kig, KAlgebra, KTurtle, Gally, KStars, KBruch, KPercentage
4. It shows the project summary as- 54,172 commits made by 538 contributors that represents 928,274 lines of code which is mostly written in C++
Humanitarian and Crisis Management
1. 40 Projects
2. Mostly projects have no latest commits and contributors.
Organizations
1. They are categorized as Most active and newest organizations with organizaton type, size, projects and 30 days commits.
OpenMRS
OpenHub
1. Last commit for OpenMRS was 2 months ago i.e. April 2017
GitHub
1. Last commit for OpenMRS was on June 7,2017
Introduction to Copyright and Licensing
Identify the license for the following projects:
1 https://github.com/openmrs/openmrs-core MPL 2.0 w/ HD © OpenMRS Inc.
Can : Commercial Use, Modify, Distribute Sublicense, Place Warranty, Use Patent Claims Cannot : Hold Liable Must have : Include copyright, Include license, state changes, disclose source
2 https://github.com/apache/incubator-fineract Apache License Version 2.0
Can : Commercial Use, Modify, Distribute Sublicense, Place Warranty, Use Patent Claims, private use Cannot : Hold Liable, use trademark Must have : Include copyright, Include license, state changes, include notice
3 https://github.com/regulately/regulately-back-end - No license
FOSS in course 1
1. In this semester, I am going to teach Software Project Management to 7th semester students in which they are dealing with the theoretical aspects of software management activities like planning of software development lifecycle, project tracking, effort estimation and scheduling (PERT and CPM scheduling), Quality planning and risk management. So we can further extend it by introducing them to practical approaches by contributing in HFOSS project.
2. Students can contribute to Sahana-Eden project as they can work as a Graphic Designer, Developers and Testers. This requires skills like CSS and HTML as pre-requisites and they have a subject named Web Technology and Cyber security in their undergraduate course in which they use HTML and Javascript.
3. Moreover, they have also studied a subject Computer Graphics in 5th semester in which they have already worked on Graphics and Animation using C programming language. So, I am going to encourage my students to take up the role of Designer.
PART -C Introduction to Bug Trackers activity
Part 2 - Collective Reports
Click on the “Reports” link on the top of the page. Click on the "Summary of Bug Activity for the last week".
1 How many bug reports were opened in the last week? How many were closed?
Total Reports: 50575 (256 reports opened and 205 reports closed.
2 What was the general trend last week? Were more bugs opened than closed or vice versa?
More reports open then closed
3 Who were the top three bug closers? Why is this important to know?
| Name | #Contributions |
|---|---|
| Piotr Drag | 18 |
| Sebastien Wilmet | 10 |
| Michael Catanzaro | 11 |
4 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?
| Name | #Contributions |
|---|---|
| Dan Jacobson | 16 |
| Bastein Nocera | 13 |
| Stephen | 6 |
5 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?
| Name | #Contributions |
|---|---|
| Nicolas Dufresne (stormer) | 14 |
| Bastein Nocera | 13 |
| Christophe Fergeau | 12 |
What class were the majority of the bugs for braille?
[1]
What other reports can you generate?
Line graph, pie charts
FOSS in courses 2
Directions
Recalling your list of activities/topics from FOSS in Courses 1 (Instructors), identify the ways that these FOSS activities/topics can be structured.
Possibilities include:
1 Lectures
2 In-class activity
3 Homework
4 Stream of related activities
5 Project
6 List the revised activities on your wiki page. For each activity/topic:
7 Identify some possible learning outcomes that should be fulfilled with the activities/task.
8 Describe any prerequisite knowledge needed to complete the activity. This does not need to be a complete list.
9 Estimate the time required for instructor prep, for student completion and elapsed calendar time. Are you going to have to synchronize your activity with the community or can the activity/topic be covered independent of the HFOSS community schedule.
10 Think about possible input required from the HFOSS community. How much input is required and what kind?
11 If the result of the activity is contributed back to the HFOSS project, describe the contribution and its usefulness.
12 Describe the assessment/grading approach - What will the basis for grading be? Will this be a team activity or individual? Is there a role for the HFOSS community in helping assess student work? For instance, must the work be committed or otherwise accepted by the community?
13 List any questions or concerns that you have about the activity/task.
14 List any stumbling blocks or barriers to carrying out the activity/task.
