User:Dinclezan

Revision as of 16:57, 23 May 2019

Name: Daniela Inclezan

Position: Assistant Professor, Computer Science and Software Engineering, Miami University, 501 E High St, Oxford, OH 45056

email: inclezd@miamioh.edu

Page: http://miamioh.edu/cec/academics/departments/cse/about/faculty-and-staff/inclezan_daniela/index.html

GitHub:

IRC: server: nick: channels:

HFOSS Projects:

HFOSS-Related Courses:

Grants:

Publications:

Other Organizations:

Bio: I am involved with the Humanitarian Engineering and Computing (HE&C) minor at Miami University and serve as the advisor for the Computer Science students enrolled in this the minor. I am also the faculty advisor of the local chapter of the Girls Who Code club. I am interested in the HFOSS initiative as a way to recruit and retain minority students and provide learning opportunities for students in the HE&C minor.

Stage 1A. Intro to FOSS Project -- Notes

SUGAR LABS

1. Contributions
   • Roles most applicable to my students:

     Developer

     writing and testing code, reporting bugs

     Designer

     user interface design, web design, mock-ups design -- suitable for my students majoring in Software Engineering

   • Commonalities across roles: Focus on communication and education.
   • Differences between roles: Different skillsets are required.
2. Tracker
   • Submitting a bug: Find the relevant activity or repo component; go to the issues tab; press the green button to submit a bug.
   • Types of tickets: defect, enhancement, task
   • Information available for each ticket: ticket (number), summary (description), status (new, assigned, reopened, accepted, closed), owner, type, priority(unspecified, normal, high, low), milestone
3. Repository
   • Date of last commit: March 13, 2019
4. Release Cycle:

   • Relationship between the release cycle and roadmap update: The roadmap is updated at the beginning of each release cycle. The roadmap may include

     the schedule of release dates and freeze points; the list of modules and external dependencies; references to tickets considered for the release; references to new feature proposals.

SAHANA EDEN

1. Community
   • Commonalities between contributor groups: Most of the roles are rather on the technical side. The only exceptions are the tester and translator roles.
   • Differences between contributor groups: technical vs. non-technical contributor; required expertise (e.g., GIS, sys admin, etc.); amount of details, guidelines and training provided
   • Differences in structure compared to the Sugar Labs website: The technical roles are more in number and divided into separate categories (developers, designers, Sys Admins, GIS specialists); generally more guidelines and instructions; a higher level of technical expertise seems to be required at first glance.
2. Tracker
   • Differences with respect to the Sugar Labs tracker page:
     • Preset labels can be selected from a dropdown menu
     • Labels are not grouped by type of information in the list of labels to choose from (e.g., priority labels, type of issue labels and component information are all mixed together in the same list), but they are color-coded
     • The date when the issue was open is recorded
     • Comments are available
   • Types of issues: bug, enhancement, documentation
3. Repository
   • Date of last commit: April 26, 2019
4. Release Cycle: Unable to access the page (ERROR: FORBIDDEN)

Stage 1B.1 FOSS Field Trip -- Notes

Part 1. GitHub

• (2.1) How many repositories are found for "education"? 27,839

• (2.2) How many of these repos use the JavaScript language? 3,456

• (2.3) In the first page of results, which repo was updated most vs least recently? nodeschool/los-angeles vs drongous/ems

• (3.1) Which education repo has the most stars? How many? freeCodeCamp - 303k

• (5.1) How many issues are open? closed? 228 Open; 13,336 Closed

• (5.2) How many pull requests are open? closed? 1,781 Open; 20,332 Closed

• (5.3) Click on the Insights tab. What do you see? An overview and graph for the most recent pull requests and issues (default: last week)

• (5.4) Within Insights, go to the left menu and click on Commits. What do you see? A chart with the number of commits per week. The most commits were done in early October 2018.

• (6.1) Search for "humanitarian" projects. How many repos are found? 507

• (6.2) Find HTBox/crisischeckin. How many stars does it have? What language(s) does it use? When was the last update? 178 stars; C#; Oct 24, 2018

• (6.3) Search for "disaster management", or terms that interest you. How many repos are found? disaster management - 473; language preservation - 18

Part 2. OpenHub

• (2.1) Search for "education." The listing shows the number of pages, not the number of projects. By default, each page shows 10 projects. How many projects were found?2,262

• (3.1) Which (if any) of the most active projects do you recognize? Sakai (11th most active)

• (4.1) From the KDE Education page, click on Code Locations (on the right side). Are any of the repo locations on GitHub? No (does not seem so based on the repository URLs)

• (4.2) Go back to KDE Education, and click on Similar Projects (below Code Locations). How many similar projects are listed? 10

• (4.3) This page contains general information for the similar projects. What info is shown for each? Name, activity level, language, license, and icon

• (5.1) How many projects did the search for "humanitarian"/ "disaster management"/ desired term return? humanitarian - 23; disaster management - 30; language preservation - 16

• (6) Why is "activity not available"? Because of problems with the projects' code locations or other problems blocking Open Hub from collecting and analyzing code

• (7.1) Organizations: What info is shown? Most active orgs, newest orgs, orgs by 30 day commit volume, stats by sector

• (8.1) In Organizations, search for "OpenMRS". Do the search results show projects or organizations? organizations

• (8.2) Find the project "OpenMRS Core". When was the last commit? Hard to find: February 2018?

• (9) Search for "OpenMRS Core" in GitHub. When was the last commit? On May 20, 2019 (9 hours ago).

• (9.1) Why do you think these sites have different info? Because the project was transferred from OpenHub to GitHub? Or because OpenHub requires more information to analyze in order to show a project as active

• (10) What are some benefits & drawbacks of searching for a project in both GitHub & OpenHub? Benefits: they complement each other (e.g., info about last commit was easier to find in GitHub; can search by organization in OpenHub). Drawbacks: the information is organized and presented differently on the two platforms and you have to learn both.

Stage 1B.2 Project Evaluation -- Notes

Stage 1B.3 Intro to Copyright and Licensing -- Notes

1. Project Licenses:
   • https://github.com/openmrs/openmrs-core: Mozilla Public License, version 2.0
   • https://github.com/apache/incubator-fineract: Apache License, Version 2.0, January 2004
   • https://github.com/regulately/regulately-back-end: No license
2. License "cans", "cannots", and "musts":
   1. Mozilla Public License, version 2.0:
      • "Cans": commercial use, modify, distribute, sublicense, place warranty, use patent claims
      • "Cannots": use trademark, hold liable
      • "Musts": include copyright, include license, disclose source, include original
   2. Apache License, version 2.0:
      • "Cans": commercial use, modify, distribute, sublicense, private use, use patent claims, place warranty
      • "Cannots": hold liable, use trademark
      • "Musts": include copyright, include license, state changes, include notice
3. Consider contributing:
   1. Mozilla Public License, version 2.0: No. Does no include the possibility of private use
   2. Apache License, version 2.0: Yes.

Stage 1B.4 FOSS in Courses (1) -- Notes

1. Capstone Project (CSE 448/449):
2. Valuable resources:
   • Independent Capstone Project Design
   • Teaching Open Source: Sept 2018 - April 2019
   • Have students go through some of the POSSE activities:
     • Intro to FOSS (1A.1) -- select three projects they may be interested in as a team (or I pre-select three projects for them to consider?!?)
     • Intro to FOSS Project Anatomy (1A.6)
     • FOSS Field Trip (1B.1) -- the parts that relate the the three selected projects
     • Project Evaluation (1B.2) -- evaluate each of the three selected projects; choose one project that the team will actually work on
   • Contribute (in this order; decide a minimum of contributions accepted by the community for each grade level):
     • Documentation (software engineering majors especially)
     • Clean up tickets
     • Propose UX design improvements (software engineering majors especially)
     • Fix bugs
3. Comparative Programming Languages (CSE 465):
4. Technology, Ethics, and Global Society (CSE 262):