User:JBarr
John Barr
John is an associate professor in the Department of Computer Science at Ithaca College. He's been teaching computer science for over 25 years and primarily works in the area of computer science education. He's taught in various locales in the U.S. and internationally (Egypt and Qatar). Recent work includes mobile development (iOS and Android), global software development education, and innovative computer science pedagogy.
Part A
Answers to the questions from "Intro to IRC" part 1:
How do people interact?
Through short messages and interactively. Much like texting.
What is the pattern of communication? Is it linear or branched? Formal or informal? One-to-many, one-to-one or a mix?
Informally. There seems to be an agenda, but the discussion varies broadly. Discussion is many-to-many though occasionally several people will dominate the conversation.
Are there any terms that seem to have special meaning?
Terms preceded by a hash seem to be commands.
Can you make any other observations?
Participants seem to have some idea of the agenda or topics before the discussion begins. The discussion also seems to be a continuation of an ongoing discussion. There are assignments made.
Answers to part 3:
Summarize your observations (of your selected HFOSS project). Pay particular attention to the ways that the selected project differs from the sample dialog you exampled in Part 1
Answers to part 6, Anatomy of a FOSS Project:
Contributions: Summarize the roles that you think would be most applicable for your students on your faculty wiki page. If you think that more than a single role is applicable, indicate why. What are the commonalities across roles? What are the differences?
Students could serve in a variety of roles. For example, students could serve in the "Educator" or "content writer" functions designing activities, creating media, etc. They could also serve as developers (our CS majors) or designers (our Emerging Media majors). Designers and developers share some overlap in the sense that each influences the other (and both work together in the engineering process). It seems that educators and content writers would work together in the same way.
Tracker: Describe the general process for submitting a bug and indicate the types/categories of tickets listed on this page as well as the information available for each ticket
Hmmm, signed into github and clicked on the "issues" tab of many projects, but none had issues.
Repository: Can you determine from the information provided here whether the project uses a web-based common repository or a local repo?
The project seems to sue GitHub, at least for many of their libraries and projects.
Release Cycle: Include an entry on your wiki page that describes how the release cycle and roadmap update are related.
The release cycle details how a release is produced in theory. The release team decides on the features, module versions, etc. to include in the release plans out the use of resources, etc. At the beginning of the release cycle the development team updates the roadmap to set specific schedules, module versions used, new features and tickets addressed in the release. The roadmap seems to be a public plan for the release.
