User:Sdekhane

(Difference between revisions)
Jump to: navigation, search
(Project Anatomy Activity)
Line 19: Line 19:
 
== Project Anatomy Activity ==
 
== Project Anatomy Activity ==
 
=== The Sugar Labs Project ===
 
=== The Sugar Labs Project ===
* The activity team is responsible for creating and maintaining educational activities that are collaborative and constructivist. They are also responsible for recruiting activity mentors and collaborating with the Education team to create their activities. Finally, this team is responsible for gathering feedback on the use of these activities in the field. Apart from creating the activities this team also has maintainers and testers to ensure the quality of the activities created.  
+
* The activity team is responsible for creating and maintaining educational activities that are collaborative and constructivist. They are also responsible for recruiting activity mentors and collaborating with the Education team to create their activities. Finally, this team is responsible for gathering feedback on the use of these activities in the field. Apart from creating the activities this team also has maintainers and testers to ensure the quality of the activities created.
 +
* The development team is responsible for developing and maintaining the core Sugar environment. They work in conjunction with the design team and the testing team.
 +
* The documentation team is responsible for creating and maintaining project documentation such as user manuals, programmer's references and tutorials.     
  
One of the common things that struck me between these teams is that they all collaborate with some of the other teams. All of the teams provide plenty of resources on their wiki pages to support their work.
+
One of the common things that struck me between these teams is that they collaborate with some of the other teams. All of the teams welcome participants and provide plenty of resources on their wiki pages to support their participants.

Revision as of 17:36, 1 May 2013

Sonal Dekhane is an Assistant Professor of Information Technology at Georgia Gwinnett College (GGC). She is heavily involved in curriculum development and program assessment at GGC. Dekhane is committed to providing an authentic learning experience to her students. To meet that goal her software development class includes an interdisciplinary real world project where the students practice all stages of SDLC working with a real client on a regular basis and participating in activities such as client interviews, prototyping sessions, peer review sessions, usability testing with end users, etc. She is looking forward to revamp this course using knowledge gained through the HFOSS community and workshop. More information about Sonal Dekhane can be found here.


IRC Conversation Answers

  • How do people interact?

The interaction among people on IRC seems very casual.

  • What is the pattern of communication?

It reminds me of instant messaging. When addressing someone specific, their IRC name along with a colon is used. For example: "joanie: newbie question about GIT"

  • Are there any terms that seem to have special meaning?

The commands start with a #. For example: #topic

  • Can you make any other observations?

The text following the commands seems to be part of meeting notes.


Project Anatomy Activity

The Sugar Labs Project

  • The activity team is responsible for creating and maintaining educational activities that are collaborative and constructivist. They are also responsible for recruiting activity mentors and collaborating with the Education team to create their activities. Finally, this team is responsible for gathering feedback on the use of these activities in the field. Apart from creating the activities this team also has maintainers and testers to ensure the quality of the activities created.
  • The development team is responsible for developing and maintaining the core Sugar environment. They work in conjunction with the design team and the testing team.
  • The documentation team is responsible for creating and maintaining project documentation such as user manuals, programmer's references and tutorials.

One of the common things that struck me between these teams is that they collaborate with some of the other teams. All of the teams welcome participants and provide plenty of resources on their wiki pages to support their participants.

Personal tools
Namespaces
Variants
Actions
Events
Learning Resources
HFOSS Projects
Evaluation
Navigation
Toolbox