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.