FOSS Community Structures (Activity)

From Foss2Serve
(Difference between revisions)
Jump to: navigation, search
 
(One intermediate revision by one user not shown)
Line 46: Line 46:
 
{{Learning Activity Info
 
{{Learning Activity Info
 
|acm unit=
 
|acm unit=
* [[SE Software Project Management]] (structure & roles in typical FOSS communities)
+
* [[:Category:SE Software Project Management|SE Software Project Management]] (structure & roles in typical FOSS communities)
* [[SP Economies of Computing]] (motivations of FOSS developers)
+
* [[:Category:SP Economies of Computing|SP Economies of Computing]] (motivations of FOSS developers)
 
|acm topic=
 
|acm topic=
 
|difficulty=
 
|difficulty=
Line 69: Line 69:
 
[[Category:Culture and Intellectual Property]]
 
[[Category:Culture and Intellectual Property]]
 
[[Category:Introduction]]
 
[[Category:Introduction]]
 +
[[Category:SE Software Project Management]]
 +
[[Category:SP Economies of Computing]]
 
[[Category:Information Processing]]
 
[[Category:Information Processing]]
 
[[Category:Teamwork]]
 
[[Category:Teamwork]]
[[Category:Ready To Use]]
+
[[Category:Ready to Use]]

Latest revision as of 12:23, 15 October 2018


Overview

Title

FOSS Community Structures (Activity)

Overview

We refer to FOSS culture or community (singular), but every project is its own community, and has its own rules, processes, and norms. This POGIL activity explores some elements, structures, and principles that are common across many (not all) FOSS and HFOSS communities.

Prerequisites

None

Learning
Objectives
After successfully completing this activity, the learner should be able to:
  • Describe and give multiple examples of organizations with a pyramidal structure.
  • Describe roles in a typical FOSS project, and how people transition between roles.
  • Describe the common motivations for FOSS participants.
Process Skills
Practiced

Information Processing,Teamwork


Background, Directions, Deliverables

See details in the Student version of the POGIL activity.

Notes for Instructors

See details in the Teacher version of the POGIL activity.

Assessment

  • How will the activity be graded?
  • How will learning will be measured? Ideally, there should be a way to measure each of the objectives described above.
  • How will feedback to the student be determined?

This is a classroom POGIL activity, so all teams should complete it in class with correct answers. Thus, the activity is typically not graded, but there might be related quiz or exam questions later.

Suggestions for Open Source Community

N/A

Additional Information

ACM BoK
Area & Unit(s)
ACM BoK
Topic(s)
Difficulty

easy

Estimated Time
to Complete

1 hour

Environment /
Materials

paper activity (1-2 per team or 1 per student) or Google Doc activity (1 per team)

Author(s)

Clif Kussmaul

Source

http://cspogil.org/Software+Engineering (for sample version)

License

This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License

Creativecommons-by-nc-sa-40.png



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