Intro to FOSS Project Anatomy (Activity)

From Foss2Serve
Revision as of 22:35, 20 April 2013 by Darci.burdge (Talk | contribs)
Jump to: navigation, search

Contents

Preparation:

Description Introduce participant to structure, processes and development tools used in FOSS projects.
Source
Prerequisite Knowledge None
Estimated Time to Completion 60 minutes
Learning Objectives
Materials/Environment Access to Internet/Web and web browser.
Additional Information Producing Open Source Software] by Karl Fogel
Rights  ?

Background:

FOSS projects have a distinct culture and set of tools that support project development. The form of the culture and the specific tools vary somewhat across projects, but there is significant commonality such that many FOSS developers migrate easily among FOSS projects.

Now that you have an understanding of the communication tools used in FOSS environments, this activity will provide a high-level understanding of some of the culture and development tools that you will use when participating in a FOSS project. The goal of this activity is not to provide depth in any one tool or aspect of culture, but to provide a high-level view of what a typical FOSS project looks like.

Directions:

BLAH BLAH

Working Material

  • Stoney
  • Peter
  • Darci
  • TO THE ACTIVITY DEVELOPER
  • A directed walkthrough into a specific project. Participants answer questions engaging with terminology.
  • TO-DO LIST
  • Pick project: Peter
  • Gather links
  • Draft walkthrough
  • Topics
    • What is a forge?
    • Not all open source projects exist in a forge.
    • The status of a project may be anywhere in the planning to mature stages.
    • Regarding community - What major roles/teams exist within the project?
    • releases: find version number system for project.
    • code repository policies:
    • packaging
    • upstream (no artifact)
    • downstream (no artifact)
    • trackers: find the tracker
    • tickets: look at some tickets
    • roadmap, etc.: find the roadmap. How are releases managed? How


Peter's Silly Attempt

The Sugar Labs Project (http://sugarlabs.org/)

Read the information found here to get an overview of the goals of the project and the expectations of contributors.

Community

In the first paragraph, they indicate the the community is organized into teams. Follow this link to the teams page. You will note that there are a wide variety of teams, each with a distinct responsibility. Follow the 'Contacts' link (found in the green option bar) for each of the following teams and summarize the information you find there on your faculty wiki page. For example, are there any commonalities? Is there something distinct for each type of team?

    • Activity Team
    • Development Team
    • Documentation Team

Tracker/Tickets

The Sugar Labs bug tracker can be found here. On your wiki page indicate the types/categories of tickets listed on this page.

Darci's Excellent Attempt

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