User:JBarr

(Difference between revisions)
Jump to: navigation, search
(POSSE 2016 Exercises: formatting and added exercises.)
(Stage 1 Part A)
Line 11: Line 11:
 
==Stage 1 Part A==
 
==Stage 1 Part A==
  
'''Answers to the questions from "Intro to IRC" part 1:'''
+
====Answers to the questions from "Intro to IRC" part 1:====
  
 
'''How do people interact?'''
 
'''How do people interact?'''
Line 31: Line 31:
 
----
 
----
  
'''Answers to part 3: Intro to Wiki'''
+
====Answers to part 3: Intro to Wiki====
  
 
'''Summarize your observations (of your selected HFOSS project).
 
'''Summarize your observations (of your selected HFOSS project).
Line 38: Line 38:
 
----
 
----
  
'''Answers to part 6, Anatomy of a FOSS Project:'''
+
====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?
 
'''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?

Revision as of 16:46, 7 June 2016

Contents

John Barr

Bio

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.


POSSE 2016 Exercises

Stage 1 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: Intro to Wiki

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?

Sugar Labs Project

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.

SahanaEden Project

Community Summarize the information about contribution types. For example, are there any commonalities? Is there something distinct for each type of contributor? How is this structure different than the one you found on the Sugar Labs website?

The contribution types seem to be quite distinct at least in terms of required skills. Developers seem to work in python, designers use client-side web technologies (e.g., CSS and html), and testers seem to mostly do use-case testing. This implies that the roles would fit different types of classes since the student skills would have to vary across these roles.

Tracker How is the information here different than the information found on the Sugar Labs tracker page?

This project seems to be using a wiki or perhaps dedicated tracking software whereas the Sugar Lab tracker was part of github. In the SahanaEden tracker tickets seem to be listed in the order received; in the Sugar Labs tracker it was by project or module.

Click the Active Tickets link. Indicate the types/categories of tickets listed on this page as well as the information available for each ticket.

request management, gis tracking, tests, css-UI, etc. Information includes version, priority, type, owner, status, and creation date.

Repository Can you determine from the information provided here whether the project uses a web-based common repository or a local repo?

They apparently use gitHub, so a web-based common repository.

Release cycle Include an entry on your wiki page that describes the information you find here.

The roadmap lists key features integrated, the developer responsible for the feature, whether the feature was added in beta or stable form (for modules) or was backend, internationalization or support material. For future features a time estimate is also given.


Stage 1 Part B

Answers to the questions from "FOSS Field Trip" part 1:

See Blog.


Answers to the questions from "Project Evaluation Activity" part 2:

See Blog.


Answers to the questions from "Blogging Activity" part 3:

uh, see Blog.


Answers to the questions from "FOSS in Course Planning I" part 4:

Chosen project: Ushahidi wiki or Ushahidi home

FOSS topics for COMP 39000, Mobile Proramming:

  • General FOSS topics
    • Open Source philosophy
    • IRC, wiki's, blogs
    • GIT
  • Ushahidi topics:
    • Overview
    • Installing Ushahidi
Personal tools
Namespaces
Variants
Actions
Events
Learning Resources
HFOSS Projects
Evaluation
Navigation
Toolbox