User:Susan.Hammond
User: Susan.Hammond
Name: Susan Hammond
Position: Assistant Professor, Computer Science, Faulkner University, 5345 Atlanta Highway, Montgomery, AL 36109
email: shammond@faulkner.edu
Page: https://www.faulkner.edu/faculty/susan-hammond/
GitHub: https://github.com/sah0017
Bio: I am new to the Open Source world, but I'm really looking forward to learning more. I've been a professor for over 7 years. Fun fact: I am a swim official for USA and YMCA Swimming.
IRC Part 1:
- How do people interact? People type in the information they want to share in a rapid-fire session.
- What is the pattern of communication? The moderator appears to try to keep the conversation linear, but many branches organically occur. Interactions in the IRC are very informal. Conversations are one-to-many, but one-to-one discussions can occur as others are "listening" in.
- Are there any terms that seem to have special meaning? terms beginning with a hash symbol (#) are meetbot commands
- Other observations: team has been functioning together for a while. Much history between them. Each one has a role on the team.
- Bonus question: Looks like the names are case sensitive. When they did the #action command, for amber the cases matched, but for darci and heidi, they capitalized the name.
IRC Part 3: It appears that this IRC is in French.
Intro to FOSS Activity: Sugarlabs
Contributions
- Roles: For my students, I think the Developer Role makes the most sense. I have some international students who might be able to contribute in the Translator role.
- Commonalities: Many of the roles don't require coding skills and have common teams, such as the Documentation Team. In fact, most of the descriptions begin with 'Communicate through ' ...
- Differences: Each role is focused on a specific part of the project.
Tracker Sugarlabs uses Github to track issues. Instructions are to visit the github location for sugarlabs, either find a specific component or go to the generic sugar package, click on the issues tab, and press New Issue button. Type of issues include defects, enhancements, and tasks. One can see the ticket #, Summary, status, owner, type, priority, and milestone.
Repository - at the moment I am doing this exercise, the last commit was on April 30, 2019.
Release cycle The Roadmap is updated at the beginning of each release team. However, when I clicked on Roadmap, it said there was currently no text in this page. They must be lost :(. Sounds like a Roadmap is equivalent to an Agile Backlog which gets updated at the end of an iteration.
Sahana
Community
Sugarlabs had 6 roles; Sahana adds Bug Marshals, SysAdmin, and GIS Specialists. Sugarlabs is looking for content experts to help with their systems; sahana needs some specialists in geospatial technology. But the overall basic skill sets are the same. From a UI perspective, SugarLabs has the fun buttons to click on, Sahana has a nature theme going on.
Tracker Sahana uses Github to track issues. Issues are assigned an issue number, and pull requests include the issue number they are intended to fix. There is some color coding with blue, red, yellow, and orange, and then some different categories. Yellow type includes Bugs, Documentation, and Enhancement categories.
Repository Last commit when I checked was May 15, 2019. This appears to be a system that is continuously integrated because there are commits for almost every business day.
Release Cycle The page won't let me access that information without being logged in.
FOSS Field Trip:
Part 1 - GitHub
Q2.
- education repos - 27,765
- Javascript education repos - 3,447
- most recently updated: angular-education. least recently updated on first page: ShinyEd
Q3.
- education repo with most stars: freeCodeCamp, with 303k
Q5.
- Open issues: 223, Closed issues: 13,329
- Open pull requests: 1,868, closed: 20,220
- Insights tab provides metrics within a certain time period about pull requests, issues, and authors, along with a history.
- Insights/Commits shows a bar chart of commits over the past year, and a line chart of commits over the past week.
Q6.
- Humanitarian repos - 506
- crisischeckin stars - 178, language C#, last updated 10/24/18
- disaster management - 472
Part 1 - OpenHub
Q2.
- number of education projects ~ 2,270
Q3.
- Most active projects that I'm familiar with - Moodle
Q4.
- KDE education - repos are not on Github.
- 10 project similar to KDE.
- for each, you can see activity, major programming language and license info.
Q5.
- number of humanitarian project ~30
- number of disaster management - ~30
Q6.
- activity is not available because something is preventing OpenHub from collecting and analyzing code contribution statistics.
Q7.
- Organizations tab sows Most Active Orgs, Orgs by 30 Day Commit Volume, Newest Orgs, and Stats By Sector.
Q8.
- From the Orgs tab, search returns an Organization.
- OpenMRS has an Activity Not Available indicator, and it says it as last analyzed about 1 year ago.
Q9.
- In GitHub, the last commit for OpenMRS Core was May 8, 2019.
- With a novice's eye, I can't tell why OpenHub wouldn't be able to access stats on this project.
Q10.
- OpenHub appears to be able to find projects not hosted in GitHub (e.g., KDE), but there are instances where OpenHub can't get the stats that it wants out of GitHub.
PROJECT EVALUATION RUBRIC: OpenMRS
| Evaluation Factor | Level (0-2) |
Evaluation Data |
|---|---|---|
| Licensing | 2 | |
| Language | 2 | |
| Level of Activity | 2 | |
| Number of Contributors | 2 | |
| Product Size | 2 | 223.27 MB |
| Issue Tracker | 2 | open-1297, closed-14132, third issue opened on May 21, 2008 (?), some of these issues were created a long time ago. |
| New Contributor | 2 | welcoming-yes,
Q1. https://wiki.openmrs.org/display/docs/Developer+How-To+Guide Q2. https://wiki.openmrs.org/display/docs/Developer+Resources |
| Community Norms | 2 |
Q1.
Q2.
|
| User Base | 2 |
Q1. Yes, there are lots of views in the Ask OpenMRS community support site. Q2. Yes, on the wiki there is Implementer Documentation that explains how to get up and running. Q3. Yes, also on the wiki, there is an End User Guide. |
| Total Score | 18 |
Intro to Copyright and Licensing
| Project | License (0-2) |
Can | Cannot | Must | Comfortable Contributing (Y/N) |
|---|---|---|---|---|---|
| OpenMRS | Mozilla Public License, version 2.0 | Commercial Use, Modify, Distribute, Sublicense, Use Patent Claims, Place Warranty | Hold liable, Use Trademark | Include Copyright, Include License, Disclose Source, Include Original | Yes |
| Apache Fineract | Apache License, Version 2.0 | Commercial Use, Modify, Distribute, Sublicense, Private Use, Use Patent Claims, Place Warranty | Hold liable, Use Trademark | Include Copyright, Include License, State Changes, Include Notice | Yes |
| regulately back-end | no license | Yes | |||
|
The why of my 'Comfortable Contributing' might vary based on the reason I was contributing. If I were strictly working on it for academic or humanitarian purposes, I would be comfortable with all the conditions. If I were working on it as/with a business which had particular goals in mind for the software, then I might have to re-evaluate. | |||||
FOSS in Courses 1
My course is Project Management for Software Development. I listed the course content from the syllabus and could see using the following Activities to support those content areas.
| Course Content | Possible FOSS/POGIL Activities |
|---|---|
| Project Life Cycles | Software Development Activities, SDLC POGIL |
| Project Infrastructure | Intro to FOSS Project Anatomy (Activity), FOSS Business Models (POGIL) |
| Scope Management | (re-)Engineering a domain model (Activity), (Re-)Engineering a system vision (Activity) |
| Time Management | Story Point Estimating, Project Scheduling POGIL, Task tracking (Activity) |
| Cost Management | |
| Quality Management | (Re-)Engineering Quality requirements (Activity) |
| Human Resources Management | |
| Communications Management | Communications in Projects POGIL, Intro to IRC (Activity) |
| Risk Management | Risk Management POGIL |
| Procurement Management | |
| Integration Management | Release Life Cycles (?) |
Intro to Bug Trackers
Projects in GNOME's Issue Tracker: mutter, nautilus, evolution, fractal, gimp
Other info: brief description, when opened and by whom, last updated, and nbr of comments
Labels: webcam, RFC, Adwaita, Theme, Enhancement, Developer docs, Documentation, gmem, Needs Information
Individual Issues info: detailed description, Assignee, milestone, time tracking, due date, confidentiality, locked/unlocked, steps to reproduce
Label types: blue appears to be where info or discussion is needed, Orange indicates its not a bug or not our responsibility, purple is help wanted or good for newbies, green is accessibility and documentation, red appears to designate it to a specific project initiative team, dark green is for items that are bigger, more long term solutions.
Board: Open Issues are cards, and they are assigned to either Stretch or Deliverable iteration columns, then moved to the Closed column when appropriate.
Milestones: Issues are assigned to specific Group and Project milestones. They have a number of milestones that have expired without being designated as 100% complete. 132 open milestones seems to be a lot for any project to manage. Several indicate that they are 100% complete, which makes me think they should be marked as closed.
From their website: Use group milestones to manage issues from multiple projects in the same milestone.
Inside the milestones, the have boards that indicate the issues are open and unassigned, open and assigned, or closed.
Merge Requests: they have a description of resolution, along with merge request info. It looks like they are inserting a URL that links back to the Bugzilla page for the specific issue that this Merge Request resolves.
