Revision as of 20:47, 14 June 2019

Dave Lillethun

Affiliation: Computer Science Dept., Seattle University

Email: lillethd AT seattleu

Website: http://dave.lillethun.org

New to HFOSS. Looking forward to getting started!

Intro to IRC activity

• How do people interact?
  • It seems to flow similar to an Agile / SCRUM type of meeting. Someone has the spotlight and talks about what they're working on - they do most of the talking, and others chime in now and then to offer suggestions, ask questions, etc. Then the spotlight moves to a different person to talk about a topic, and so on. Meanwhile, darci uses the bot to take meeting notes (which the bot will format nicely for them, as we find out in the next stage of the IRC activity)

• What is the pattern of communication? Is it linear or branched? Formal or informal? One-to-many, one-to-one or a mix?
  • There is some branching, but without going too far off topic too long - like Charlie Brown's Christmas Tree, not Yggdrasil. The language is pretty informal, and much of it is one-to-many (with a few many-to-one replies) but some of the branches seem to occasionally go one-to-one just for brief moments.

• Are there any terms that seem to have special meaning?
  • Starting a message with "Name:" seems to be a common way to address a message to a specific person, and there were one or two uses of /me . Of course, there are the # commands. Also, there are naturally a lot of technical terms being used.

• Can you make any other observations?
  • A lot of this feels pretty comfortable if you're used to online chat.  :)

• Bonus question: Why didn't Heidi and Darci's actions get picked up by the meetbot?
  • Looks like user names are case-sensitive, and heidi and darci's names start with lowercase letters, but the actions had their names spelled with capitals.

Project Evaluation activity

OpenMRS

https://github.com/openmrs/openmrs-core

Intro to Bug Trackers activity

Current GNOME issues:

• gnome-builder
• evolution
• gnome-control-center
• librsvg

Other information on the list view:

• issue title
• time and user opened
• time last updated
• comments and upvotes

Example labels:

• 1. Enhancement
• refactoring
• 6. Component: Sound
• 6. Component: Background

Issue details:

https://gitlab.gnome.org/GNOME/evolution/issues/489

• Evolution version tested against
• Description of the problem (this issues is very good! it has clear reproduction steps)
• Asignee: None (this was a fairly new bug at the time of reading)
• Milestone: None
• Time tracking: No estimate or time spent
• Due date: None
• List of participants (Is a participant just anyone who's editing the issue ticket?)

Labels:

• 1 is for real issues to be addressed (incl. both bugs and feature requests and more)
• 2 is for things that need more investigation or discussion
• 3 is for things that will not be fixed/addresses (as a deliberate decision, for some specified reason)

Boards: It looks like boards group bugs by their current status. Right now, it's only showing "open" and "closed"... I wonder if there are more boards that could show up here?

Milestones: No milestones are currently being shown, but it looks like they let you assign issues to your project milestones so you can keep track of your progress towards completing the milestone. (I wonder if projects use burndown charts or anything like that?)