Intro to FOSS Project Anatomy (Activity)

(Difference between revisions)
Jump to: navigation, search
(Background:)
Line 24: Line 24:
 
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.  
 
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 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 of aspect of culture, but to provide a high-level view of what a typical FOSS project looks like.  
+
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 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: ===
 
=== Directions: ===

Revision as of 21:18, 20 April 2013

Contents

Preparation:

Description Introduce participant to common tools and processes 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 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

Stoney's Ludicrous Attempt

Darci's Excellent Attempt

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