User:Jim.huggins

From Foss2Serve
Revision as of 01:21, 19 August 2015 by Jim.huggins (Talk | contribs)
Jump to: navigation, search

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. Availabile 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
Personal tools
Namespaces
Variants
Actions
Events
Learning Resources
HFOSS Projects
Evaluation
Navigation
Toolbox