User:Wjin

(Difference between revisions)
Jump to: navigation, search
(Wei Jin Bio)
(Intro to Copyright and Licensing)
Line 129: Line 129:
 
|}
 
|}
  
 +
The information contained in the table below is from https://tldrlegal.com/.
  
 
{| class="wikitable" style="width:100%;"
 
{| class="wikitable" style="width:100%;"
Line 138: Line 139:
 
|-
 
|-
 
| MPL 2.0 w/ HD
 
| MPL 2.0 w/ HD
 +
|
 +
|
 +
|
 +
|-
 +
| Apache License Version 2.0
 
|  
 
|  
 
|  
 
|  

Revision as of 20:29, 25 May 2018

Contents

Wei Jin Bio

Wei Jin is an Associate Professor at the Dept. of Information Technology at Georgia Gwinnett College.

Dr. Jin's primary focus is continuing improvement of student learning in CS1, the introductory programming course.

She previously worked on Automatic Tutoring Systems for introductory programming, for which she hopes to resume the work soon.

Since Spring 2017, she participated in the CS-POGIL project, which aims to improve student learning in CS1 through Process Oriented Group Inquiry Learning (POGIL).

Most recently, she was accepted into the 2018 POSSE (http://foss2serve.org/index.php/POSSE_2018-06) and she hopes that she can help engage students using real-world FOSS projects.

Page: http://www.ggc.edu/about-ggc/directory/wei-jin

POSSE Journal - Entry 1

The Sugar Labs Project (http://sugarlabs.org/)

Contributions -- The page Getting Involved lists different ways people can contribute to Sugar Labs project. GGC, we have four tracks in Information Technology, including Digital Media and Software Development. Digital Media students could contribute as designers, while Software Development students could contribute as developer. They could collaborate on the same game/education tool.

Tracker -- From the Submit Bugs page, all you need to do is to identify the activity or a sugar component repository that you think is relevant, visit the issues tab of the repo, and hit the big green button to report your issue. For each ticket, you will need to include a summary title, type, priority and milestone. Each ticket will be assigned a ticket number and its status will start with new and can change to accepted, assigned, and etc. See here for a query result.

Repository -- According to https://github.com/sugarlabs/sugar/, the most recent commit is April 29.

Release cycle -- According to Information about Sugar's release cycle and roadmap, the roadmap is update at the beginning of each release cycle.

The Sahana Eden Project (https://sahanafoundation.org/eden/)

Community -- The structure is very similar to the one that I found on Sugars Labs website. For example, designers and developers are both ways that my students can contribute. The difference lie at the different nature of each project. Sugar involves educators, while Sahana Eden involves GIS specialists.

Tracker -- According to the Sahana Eden bug tracker, the bugs report is organized by categories, such as Active Tickets, Accepted & Active Tickets by Owner, My Tickts, All tickets, and etc. For each ticket, there are also differences as to what information is shown on the summary page. For example, priority and owner are information that are not shown at the summary page for Sugar but for Sahana Eden.

Repository -- According the https://github.com/sahana/eden, the date of last commit is May 2, 2018.

Release cycle -- The the page for the information about Sahana Eden's release cycle and roadmap is organized by milestones. Each milestone contains a data, the progress (a bar showing how much of the goal is done), and a list of issues to be addressed, with issues already resolved marked done.

POSSE Journal - Entry 2

One of the best known FOSS project hosting sites Github (https://github.com/)

Education -- A search for Education rendered 20,321 results. For each project, the Insight tab will provide information of the activities on the repository. For example, the Pulse page shows the activity summary of the current week, including the number of different activities and activities per person as a bar chart. The Commits page shows the commits along a time line and shows a line graph of comments vs. days of the week. For the free-programming-books project, most commits were done on Tuesdays.

Humanitarian -- A search for Humanitarian rendered 394 results. HTBox/crisischeckin is one of the projects. It is an application meant to capture, share and integrate the data around volunteers, organizations and resources actively deployed into a disaster. It was last updated on Nov 29, 2017.

Disaster Management Applications -- There are currently 36 such repositories for this category.

Another FOSS project site OpenHub (https://www.openhub.net/)

Education -- A search for Education rendered 2252 projects (226 pages of results, with each page 10 results and 2 results on the last page). KDE Education is one of the projects. It has 23 code locations. Each of them is located at a place like git://anongit.kde.org/*.gitNone of the location.

On the project place, four similar projects are shown. Towards the bottom of the project page, you will see summary of the project, including lines of code of the project overtime, line graph of commits per month vs the time line, contributors per month over vs the time line, programming languages used in the project, and etc.

Humanitarian -- A search for Humanitarian rendered 21 results.

Disaster Management Applications -- There are currently 6 such projects for this category.

Organizations Page -- This page provides four categories of information: (1) the most active organizations, (2) the new organization, (3) Orgs by 30 Day Commit Volume, which can be displayed with different filters, and (4) Stats by Sector (commercial, non-profit, education, and government).

Project OpenMRS Core -- The last commit for the project was on March 11, 2018.

Benefits/Drawbacks of using both GitHub and OpenHub to search for a project -- Github is a FOSS repository site, while OpenHub is not a repository site but contains information for FOSS projects that have code locations elsewhere. I would think that OpenHub uses software to discover FOSS projects on the web. It is also possible that it includes manual maintenance. These two sites complement each other. Together they give a more complete set of FOSS projects out there.

Project Evaluation Rubric for Choosing a HFOSS Project

Evaluation of the OpenMRS core repository (https://github.com/openmrs/openmrs-core)

Evaluation Factor Level
(0-2)
Evaluation Data
Licensing 2 MPL 2.0 w/ HD
Language 2 Java 96.2%, SQLPL 2.9%, Other 0.9%
Level of Activity 2 Activities in the current week
Number of Contributors 2 303 contributors and the top 5 is very active within the past year
Product Size 2 222.42MB (5.2 MB zip)
Issue Tracker 2 18084 issues documented at https://issues.openmrs.org/secure/Dashboard.jspa, with 1256 ready to work and 12874 closed. The fifth issue ready to work on is Displaying service info in XForms. The most recent activity on this issue is a question about whether this issue is still open in 2016.
New Contributor 2 Clear instructions on how to start working in this project
Community Norms 2 Code Norm: (1) Clear convention for Java and JavaScript (2) A clear code review process (3) clear standards for data model, naming, and web application development. Communication norm on the talk forum: very professional, no indication of rude or inappropriate behavior.
User Base 2 OpenMRS is now in use around the world. There are issue tracking tools.There are instructions for downloading and setting up the software for use by clients. There are demo and instructions for how to use the software.
Total Score 18 All above


Intro to Copyright and Licensing

Project License Type
https://github.com/openmrs/openmrs-core MPL 2.0 w/ HD
https://github.com/apache/incubator-fineract Apache License Version 2.0
https://github.com/regulately/regulately-back-en No license stated

The information contained in the table below is from https://tldrlegal.com/.

License cans cannots musts
MPL 2.0 w/ HD
Apache License Version 2.0


For each license, state whether you would (or would not) be comfortable contributing code to that project and why (or why not)

FOSS in Courses 1

  1. My HFOSS project of interest:
    1. Activities or topics that I'm you are interested in within my HFOSS project of interest. This can be a rough list and can serve as the basis for identifying possible class activities/topics.
  2. My Course
    1. Now that you have an idea of the possible types of activities or topics, identify one or two that you think would fit in your class. These do not need to be polished. This can be a rough list of ideas.
    2. In your reading, did you find existing materials? If so, describe how would you modify them to fit your class?
    3. If you did not find existing materials, summarize the activity in a sentence or two.
    4. Post the activity to your wiki page. Note that you may end up identifying more activities than you can use in a single class. Think big!
Personal tools
Namespaces
Variants
Actions
Events
Learning Resources
HFOSS Projects
Evaluation
Navigation
Toolbox