User:Josh.dehlinger

Josh Dehlinger

Josh Dehlinger is an Associate Professor in the Department of Computer and Information Sciences at Towson University. Before joining Towson University in 2008, he was a Research Associate in the Charles L. Brown Department of Electrical and Computer Engineering at The University of Virginia. He received his Ph.D. in Computer Science from Iowa State University in 2007 working under the advisement of Dr. Robyn Lutz.

Part A, Part 1, Activity 4: Introduction to IRC - Walk through of IRC Conversation

• How do people interact? Interaction is quite informal, conversational and concise.

• What is the pattern of communication? The pattern of communication follows a typical stand-up meeting in Scrum where each developer talks about: 1. What did I accomplish; 2. What obstacles are impeding my progress; and, 3. What will I work on next. Clearly, in this meeting Darci is the coordinator/project manager since she is leading the meeting and keeping it focused.

• Are there any terms that seem to have special meaning? There are several IRC meetbot specific terms that have special meeting, including #topic, #info, #action and #link. There are also some notation to indicate non-verbal types of communication, including name: to direct a comment to a person (i.e., equivalent to the Twitter version of @name).

• Can you make any other observations? None.

Part A, Part 3, Activity 3: Introduction to IRC - Join and Observe Channel Discussion

• Summarize your observations of a selected HFOSS project(s). Between 7/18/15 - 7/20/15, I observed the #foss2serve, #openmrs and #ushahidi IRC channels using the Kiwi IRC web application. During this period, there was very little / no activity on both the #foss2serve and #openmrs channels, but the #openmrs channel was somewhat active with most of the messages seeming to be automated bot messages from a build/repository/issue tracker agent indicating pull requests were made, commits were made or files changed.

Part A, Part 6, Activity 4: Anatomy of a FOSS Project - Guided Tour: Sugar Labs Project

• Activity Team - develops and maintains many of the activities available for Sugar; recruits, mentors and supports folks who develop Sugar activities
• Development Team - implements, builds and maintains the core Sugar environment; works with the Design Team
• Documentation Team - provides the Sugar community with high quality documentation, including learners' manuals, programming references, and tutorials

All of the teams have clearly defined mission statements and distinct roles within the Sugar Project and collaborate/coordinate with other teams. Both the Activity and Development team utilize IRC for meetings (its not immediately clear what the Documentation Team uses).