User:Jim.huggins

Jim Huggins is an Associate Professor of Computer Science at Kettering University in Flint, Michigan.

Jim's research interests include formal methods, computer science education, computing history, and computing ethics. He is also involved with the AP Computer Science A and Computer Science Principles examination communities.

Jim's outside interests include church life, piano playing, and geocaching.

Introduction to IRC Activity Responses (Stage 1, Part A, Number 5)

1. How do people interact? Informally. It appears everyone knows each other on a first-name basis. Lots of references to people not in the chat.
2. What is the pattern of communication? Mostly linear, but with occasionall overlaps due to the nature of distributed chat. (E.g. someone starts a new topic while an old topic is still underway.)
3. Are there any terms that seem to have special meaning? Lots of them ... mostly technical terms dealing with the project at hand.
4. Can you make any other observations? Darci seems to do a nice job of summarizing salient points and decisions made (as should happen in real meetings, even though it doesn't :) )

Project Anatomy Activity Responses (Stage 1, Part A, Number 6)

Sugar Labs

1. Community: Seems like things are awfully loosely organized; I suspect more people are involved than those listed. (Or, people suck at updating the membership lists.)
   1. Activity Team: 2 coordinators, 13 contributors, mailing list & IRC channel
   2. Development Team: no coordinators (vacancy noted), 4 contributors, IRC channel
   3. Documentation Team: no coordinators (vacancy noted), 2 editors, IRC channel
2. Tracker
   1. Types of tickets: defect, enhancement, task
   2. Available information: ticket number, summary, status, owner, type, priority, milestone
3. Repository: pretty clearly a web-based repository (using Git)
4. Release Cycle: roadmap is updated at the beginning of each release cycle

SahanaEden

1. Community: less emphasis on names of contributors, more emphasis on the work to be done (and how to get working on it).
   1. Developers: full step-by-step instructions on how to join the community, get the development environment, and find tasks to perform
   2. Testers: less instructions, more lists of project areas to work on. One note on ways for less tech-familiar people to get involved, but less detail on the process
   3. Designers: even less information, just a few links to areas of design need
2. Tracker: main page has various (presumably) common queries of subsets of bugs in the system
   1. Types of tickets: defect/bug, documentation, enhancement, task
   2. Available information: ticket number, summary, component, version, priority, type, owner, status, date created
3. Repository: again, appears to be a web-based repository (using Git)
4. Release Cycle: roadmap has a few milestones with key features noted. Dates appear to be slipping rather dramatically.

FOSS In Courses Activity (Stage 2, Item 4)

Okay, so, in order for this to make sense, you may want to read my blog entry which describes my intended use case.

At the moment, I've