User:Iantonios
(→FOSS in Courses 2) |
|||
| (8 intermediate revisions by one user not shown) | |||
| Line 137: | Line 137: | ||
'''Regulately''': No license spelled out, implying that default copyright laws apply. Cannot reproduce, distribute, or create derivative works. Must obtain permission. Would not contribute to such a project. | '''Regulately''': No license spelled out, implying that default copyright laws apply. Cannot reproduce, distribute, or create derivative works. Must obtain permission. Would not contribute to such a project. | ||
| − | |||
== FOSS in Courses 1 == | == FOSS in Courses 1 == | ||
| Line 143: | Line 142: | ||
FOSS activities that would be of general interest to students in the capstone course: | FOSS activities that would be of general interest to students in the capstone course: | ||
| − | + | 1) Learning Git, 2) UML a project [http://foss2serve.org/index.php/UML_a_project] 3) Understanding Open in OpenSource Activity [http://foss2serve.org/index.php/Understanding_the_Open_in_OpenSource_Activity], 4) Intro to Style Guides [http://foss2serve.org/index.php/Intro_to_Style_Guides_(Activity)], and 5) Independent Capstone Project Design [http://foss2serve.org/index.php/Independent_Capstone_Project_Design] | |
| − | + | ||
| − | + | ||
| − | + | ||
== Intro To Bug Tracker == | == Intro To Bug Tracker == | ||
| Line 155: | Line 151: | ||
== FOSS in Courses 2 == | == FOSS in Courses 2 == | ||
| + | |||
| + | '''Possible activities to be adopted in capstone project course''' | ||
| + | |||
| + | '''1. Learning Git''': | ||
| + | |||
| + | Learning outcome: develop a familiarity with standard tools for distributed version control | ||
| + | |||
| + | Prerequisite: familiarity with command line interface. | ||
| + | |||
| + | Time required: 2-3 hour time commitment by students. | ||
| + | |||
| + | Input from HFOSS community: none | ||
| + | |||
| + | Contribution to HFOSS: none | ||
| + | |||
| + | Grading: | ||
| + | |||
| + | Questions/Concerns: | ||
| + | |||
| + | |||
| + | '''2. UML a Project''' | ||
| + | |||
| + | Learning outcome: | ||
| + | |||
| + | Prerequisite: | ||
| + | |||
| + | Time required: | ||
| + | |||
| + | Input from HFOSS community: | ||
| + | |||
| + | Contribution to HFOSS: | ||
| + | |||
| + | Grading: | ||
| + | |||
| + | Questions/Concerns: | ||
| + | |||
| + | |||
| + | '''3. Understanding Open in OpenSource Activity''' | ||
| + | |||
| + | Learning outcome: Develop a familiarity with philosophy behind open source software and various license types. | ||
| + | |||
| + | Prerequisite: none. | ||
| + | |||
| + | Time required: 1-2 hours. | ||
| + | |||
| + | Input from HFOSS community: none. | ||
| + | |||
| + | Contribution to HFOSS: none. | ||
| + | |||
| + | Grading: | ||
| + | |||
| + | Questions/Concerns: | ||
| + | |||
| + | |||
| + | '''4. Intro to Style Guide''' | ||
| + | |||
| + | Learning outcome: | ||
| + | |||
| + | Prerequisite: | ||
| + | |||
| + | Time required: | ||
| + | |||
| + | Input from HFOSS community: | ||
| + | |||
| + | Contribution to HFOSS: | ||
| + | |||
| + | Grading: | ||
| + | |||
| + | Questions/Concerns: | ||
| + | |||
| + | |||
| + | '''5. Independent Capstone Project Design''' | ||
| + | |||
| + | Learning outcome: | ||
| + | |||
| + | Prerequisite: | ||
| + | |||
| + | Time required: | ||
| + | |||
| + | Input from HFOSS community: | ||
| + | |||
| + | Contribution to HFOSS: | ||
| + | |||
| + | Grading: | ||
| + | |||
| + | Questions/Concerns: | ||
Latest revision as of 19:02, 20 April 2017
Contents |
Imad Antonios Bio
Imad Antonios is an Associate Professor in the computer science department at Southern Connecticut State University, which he joined in 2013.
Imad's research interests are in performance modeling of computer systems and networks, simulation, computer science education, and more recently data visualization and analytics.
Imad has taught a wide range of CS courses including as CS 1 and 2, algorithms, operating systems, computer graphics, simulation and modeling. He also teaches the senior project course where he hopes to get students engaged in HFOSS projects.
Imad's hobbies: photography (http://imadantonios.photography), travel, hiking and camping.
FOSS Project Anatomy
Sugar Labs Project [1]
Contributions Potential student roles would be Developer and Content Writer. The main commonality among roles is the ability to communicate, be it through code or in writing.
Tracker Bug submission: Identify relevant component repo, and then submit through Github. Bug types reported fall under either enhancement or defect.
Repository Last commit on 2/5/17
Release Cycle The roadmap is updated at the beginning of each release cycle.
The Sahana Eden Project [2]
Community Seems more open. Interested parties can simply join the mailing list, follow online training, and start contributing. With Sugar Labs, there's a contact person for each role.
Tracker Issues are organized by various criteria (e.g. owner, version, priority, etc.).
Repository Last commit on 4/4/2017.
Release Cycle Roadmap broken down by milestone. Each milestone includes a listing of features, modules affected and an estimate of of effort required (for future milestones).
FOSS Field Trip
Part 1 -- GitHub 2.1 Over 12,000 repos on education.
2.2. Timeline of project commits.
3.1. There are 290 repos with keyword humanitarian
3.2. Last update on HTBox was on 8/7/2016
4. There are 144 repos on disaster management.
Part 2 -- OpenHub
2.1. There are 3456 projects with keyword "education"
2.2. KDE is the code location
2.3. There are 10 similar projects to KDE Education
2.4. "People also use.."
3.1. ~40 projects with keyword "humanitarian" and ~60 with "disaster management"
3.2. Projects with no users on Open Hub don't have any activity information.
4. Repo statistics by types of organizations (e.g. commercial, non-profit, education, etc.) that use OpenHub.
5. Last commit to OpenMRS core was in March 2017.
6.1. According to GitHub, the last commit was on April 2, 2017.
6.2. Not clear
Project Evaluation
| Evaluation Factor | Level (0-2) |
Evaluation Data |
|---|---|---|
| Licensing | 2 | Mozilla Public License |
| Language | 2 | Java (95.4%), SQL (3.0%), GAP (0.7%) |
| Level of Activity | 2 | There are commits virtually every week |
| Number of Contributors | 2 | 256 contributors |
| Product Size | 2 | 218.82MB |
| Issue Tracker | 2 | 1244 Ready for Work, 9867 Closed. |
| New Contributor | 2 | The Developers page seems very welcoming of new contributors |
| Community Norms | 2 | The project Wiki contains a Code of Conduct. [3] |
| User Base | 2 | The Wiki has a User Guide. [4] |
| Total Score | 18 |
Intro to Copyright and Licensing
OpenMRS Core: Mozilla Public License. Can user commercially, modify, distribute, sublicense, place warranty. Cannot use Trademark or hold liable. Must include copyright, license, disclose source and include original. Would be comfortable contributing to this project.
Incubator: Apache License. Can user commercially, modify, distribute, sublicense, place warranty. Cannot use Trademark or hold liable. Must include copyright, license, state changes, and include notice. Would be comfortable contributing to this project.
Regulately: No license spelled out, implying that default copyright laws apply. Cannot reproduce, distribute, or create derivative works. Must obtain permission. Would not contribute to such a project.
FOSS in Courses 1
I hope to incorporate HFOSS into the senior capstone course which I regularly teach. Students interested in participating would be expected to complete a design documented as outlined in [5], and carry out the implementation.
FOSS activities that would be of general interest to students in the capstone course: 1) Learning Git, 2) UML a project [6] 3) Understanding Open in OpenSource Activity [7], 4) Intro to Style Guides [8], and 5) Independent Capstone Project Design [9]
Intro To Bug Tracker
Intro to GitHub
FOSS in Courses 2
Possible activities to be adopted in capstone project course
1. Learning Git:
Learning outcome: develop a familiarity with standard tools for distributed version control
Prerequisite: familiarity with command line interface.
Time required: 2-3 hour time commitment by students.
Input from HFOSS community: none
Contribution to HFOSS: none
Grading:
Questions/Concerns:
2. UML a Project
Learning outcome:
Prerequisite:
Time required:
Input from HFOSS community:
Contribution to HFOSS:
Grading:
Questions/Concerns:
3. Understanding Open in OpenSource Activity
Learning outcome: Develop a familiarity with philosophy behind open source software and various license types.
Prerequisite: none.
Time required: 1-2 hours.
Input from HFOSS community: none.
Contribution to HFOSS: none.
Grading:
Questions/Concerns:
4. Intro to Style Guide
Learning outcome:
Prerequisite:
Time required:
Input from HFOSS community:
Contribution to HFOSS:
Grading:
Questions/Concerns:
5. Independent Capstone Project Design
Learning outcome:
Prerequisite:
Time required:
Input from HFOSS community:
Contribution to HFOSS:
Grading:
Questions/Concerns:
