User:Andrea.tartaro

Andrea Tartaro is an Assistant Professor of Computer Science at Furman University. She teaches courses on introductory computer science and programming, object-oriented design and data structures, human-computer interaction, computer graphics, and freshman writing. Her professional work includes research on computer science education that emphasizes interdisciplinary initiatives, as well as human-computer interaction research related to designing computer systems to support behavior change goals. Prior to joining Furman University, she received her Ph.D. from Northwestern University and taught at Union College in Schenectady, NY.

---

Intro to IRC Activity

Part 1:

• People interact in short, colloquial sentences or phrases. Multiple sentences or phrases are usually split over multiple contributions.
• People can direct comments directly to other users using either their name or their user names, or can direct comments to the group in general. There seem to be tags for notes, like assigning tasks or indicating something was completed.
• Words with hashtags appear to be used for specific purposes (e.g., #action, #info)
• It's a little hard to follow when comments are not specifically addressed to a person.

Part 3:

I logged onto the OpenMRS IRC channel for about 48 hours, and then brilliantly closed out the window without reading it. Fortunately I found the logs of the channel. The OpenMRS channel had a fair amount of activity, limited to a few users for a while. It looks like a new user setting up the system for the first time needed some help setting up the project and others quickly responded to help. User "dkayiwa" seems to monitor the channel and perhaps is a lead on the project. It also looks like there was a meeting with updates.

---

Project Anatomy Activity

The primary responsibility for the Activity Team is to develop and maintain Sugar Platform activities (what they call apps). They recruit and support developers, as well as gather and organize information about how activities are used and new ideas for activities. The Development Team builds and maintains the core Sugar platform, as well as manage releases. This group is charge of bugs and new features for the Sugar Platform. Where as the Activity Team is primarily in charge of individual activities (apps), the development team is primarily in charge of the core of the platform. The documentation team is responsible for all manner of documentation for the Sugar platform, including manuals, programming guides, etc. Both the Activity Team and the Development Team probably need to work with the documentation team for maintaining documentation of their components.

---

FOSS Field Trip Activity

Part 1: Source Forge

1. Go to: http://sourceforge.net/
2. Use the Search feature in the center of the screen to view applications in an area of interest to you (e.g., gaming, sports, music, computing, etc.).

fitness

1. How many projects are there in this category?

22 recently updated and for my OS or 194 total

1. How many different programming languages are used to write software in this category?

15 (to choose from under Programming Languages in "refine search")

1. List the top four programming languages used to write programs in this category.

Java, C#, PHP, C++, Python

1. Identify the meaning of each of the statuses below:

1. 1. Inactive
   2. Mature
   3. Production/Stable
   4. Beta
   5. Alpha
   6. Pre-Alpha
   7. Planning

These are the various stages of development. There are 7 levels from planning to inactive. In between are various production/release stages.

1. Compare two projects in this category that have two different statuses. Describe the differences between the statuses.

1. Which projects are the most used? How do you know?
2. Pick a project in your category. Answer the questions below:
   1. What does it do?
   2. What programming language is the project written in?
   3. Who is likely to use the project? How do you know this?
   4. When was the most recent change made to the project?
   5. How active is the project? How can you tell?
   6. How many committers does the project have?
   7. Would you use the project? Why or why not?