User:Dreddy
Deepti Reddy
Associate Professor in Computer Engineering department in SIES Graduate School of Technology, University of Mumbai, India.
The areas of interest are- Intelligent Tutoring System, Expert Systems, Semantic web, Technology enabled learning system for developing thinking skills.
Prat A- Intro to FOSS Project Anatomy (Activity)
Basic aspects of FOSS project
Community of FOSS development-The position of person depends on the contribution to the projects- starts as user of the application, identify small changes that may lead to larger changes and responsible for larger portion of the project.
Leadership-Benevolent Dictator takes decision usually in collaboration with major developers.
Forking- making changes to the copy of the existing project or code.
Communication- IRC, wikis, mailing lists, bug trackers.
Roadmaps- future of the projects, in form of enhancements or bugs fixed.
Releases- The developed project with code and documentation.
Repository- The place where software packages are saved for distribution, e.g. Launchpad, SourceForge, GitHub
Packaging- Packaging a project for distribution in zip or binary format.
Upstream/downstream- upstream is main project and downstream is copy of code for changes.
Version control- track of various versions of project
Trackers- bug report
Sugar Lab Project
Contribution Learning software for children, which consists of collection of tool for learners to explore, discover, create and reflect through collaboration. Contributors are- Teachers, content writers, People person, developer, designer, translator. Communication is through wiki, email, IRC. Community- the goals in terms of education, technical and community clearly stated. Roadmap- three phases- identifying goals, building project and iteration.
Tracker- The bugs can be submitted in github.com in issues tab, click on new issue. types/categories of tickets listed on this page as well as the information available for each ticket.
Types of tickets listed are- defect, enhancement, task Information available for each ticket are- ticket number, bug details, status, owner, type, priority, and milestone.
Repository- date of last commit is May 16, 2017
Release cycle- The roadmap is updated at the beginning of each release cycle.
SAHANA Foundation- Open Source Disaster Management Software
Provides platform for rapidly deploying information management system for disaster management.
One can contribute as a
1. Developer- Contribute to Sahana by closing tickets, updated wiki docs, writing tests and helping others on the mailing list.
2. Testers- manual testing and documenting test cases
3. Designer- to improve the look and feel of the site.
How the Sahana project structure different than Sugar lab? Sugarlab focus is more on activities to support learning and Sahana is more towards application so the contribution towards sahana is more technical than Sugarlab.
Tracker The tickets in Sahana are categorized under various titles which is not the same in Sugarlab.
Types/categories of tickets- defuct/bug, documentation, enhancement, task, minor.
Information available for each ticket- ticket number, summary, component, version, priority, type, owner, status, created.
Part B- FOSS Field Trip (Activity)
Github Educational applications Number of repositories in education category-13397 Nodejs- Commit has list of updates date wise made by users.
humanitarian applications Number of repositories – 301 Last update- April 22, 2017
Disaster management No of projects- 152
Openhub
Number of educational project-3470 KDE education code is located in Github
Information about project- Name of the project, overview, lines of code, contributors, date of last commit, review, option to compare projects.
Number of humanitarian projects- 40 Activity not available is shown for projects that do not have recent analysis because of problems with their code locations or other problems blocking Open Hub from collecting and analyzing code will show the Not Available icon.
Last commit for OpenMRS- April 2017, last 2 months ago
Advantages of Openhub over Github Openhub gives more summarized overview of a project in the search list, so no need to open the project to get more details. It also provides option to compare and analyze the projects. Information provided is more useful to a developer.
Project Evaluation (Activity)
Evaluation Rubric for OpenMRS project
| Evaluation Factor | Level (0-2) |
Evaluation Data |
|---|---|---|
| Licensing | 2 | Mozilla public licence version 2 and is completely free open source software. |
| Language | 2 | Java JDK |
| Level of Activity | 2 | Almost 200 commits in last 6 months |
| Number of Contributors | 2 | Total contributors are 100 |
| Product Size | 2 | 3.73M lines of code |
| Issue Tracker | 2 | issues are noted and updated |
| New Contributor | 2 | has links to get more info on how to contribute as a developer, issue tracker or talk to community- https://wiki.openmrs.org/display/docs/ |
| Community Norms | 2 | code of conduct specified- considerate, respectful, collaborative, etc. Type of conversation- introduction, queries, enhancement, etc. No inappropriate comments found. |
| User Base | 2 | http://openmrs.org/download/ |
| Total Score | 18 |
FOSS in Course 1
Data Structure Course-second year CS students
1. Encourage students to use Linux OS to write and compile C programs in Data Structures course. (http://foss2serve.org/index.php/Introduction_to_building_open_source_software)
2. The programs written should have comments to help others understand the code.
3. Writing and documenting test cases to test if the code has bugs.
Web technology lab- Third year CS students
Students can do the case study on OpenMRS architecture. (http://foss2serve.org/index.php/OpenMRS_Architecture_activity)
Part C- Bug tracker (Activity) Used for change management, report about a error by the users or developers Bugs follow a Life cycle- report a bug-> assign to developer-> report the status-> …->close.
Activity 1. Define what each of the column names below indicate. Include the range of possible values for 2-7 below.
i. ID- unique id assigned to each bug ii. Severity- specifies how severe the bug is iii. Priority- used to prioritize the bug iv. OS- v. Product- name of the tool vi. Status- gives the status of the issue, specifying it as new, assigned, reopened, etc. vii. Resolution- indicates what happened to this bug viii. Summary- specifies short description about the bug 2. Describe how you discovered the definitions and how did you find the information from above (hint: the advanced search shows the options or the Reports link has a link). By understanding the content of the bugs given in the list and from Google search about Bugzilla. 3. Identify the order in which the bugs are initially displayed. Alphabetically ordered on assignee field. 4. What is the meaning of the colors used when describing a bug (red, gray, black)? (Hint: click on the Bug ID and examine the fields) No colors were used to describe a bug 5. Select a bug that you think that you might be able to fix and look at it more closely (click on the bug number). i. Identify when the bug was submitted. Jan 6, 2010 ii. Identify if there has been recent discussion about the bug? No, the last discussion was on Aug 14, 2013 iii. Is the bug current?
no
iv. Is the bug assigned? To whom? Assigned to At-spi maintainer v. Describe what you would need to do to fix the bug. Access controls are to be modified
