Erinevus lehekülje "Open Source management" redaktsioonide vahel

Allikas: KakuWiki
Mine navigeerimisribaleMine otsikasti
14. rida: 14. rida:
 
#* Course intro - what is going to happen
 
#* Course intro - what is going to happen
 
#* lecture: FLOSS definition, differences from proprietary models. Free Software vs Open Source vs Freeware. FSF  vs OSI
 
#* lecture: FLOSS definition, differences from proprietary models. Free Software vs Open Source vs Freeware. FSF  vs OSI
#* homework some readings (Stallman vs Raymond). Write a review (can be blogged or e-mailed; deadline: next Monday)
+
#* homework: some readings (Stallman vs Raymond). Write a review (can be blogged or e-mailed). Due: next Monday, February 1.
 
# Monday, January 25. T-321, 12.15 - 13.45
 
# Monday, January 25. T-321, 12.15 - 13.45
 
#* lecture/demonstration/practice: Battle for Wesnoth as our playground. Main ideas of the game, overview of the wesnoth/data directory. Creating a scenario and a campaign. WML.
 
#* lecture/demonstration/practice: Battle for Wesnoth as our playground. Main ideas of the game, overview of the wesnoth/data directory. Creating a scenario and a campaign. WML.
 
# Tuesday, January 26. T-321, 10.15 - 11.45
 
# Tuesday, January 26. T-321, 10.15 - 11.45
#* homework: installing and playing Wesnoth. Write a review (can be blogged or e-mailed; deadline: next Monday)
+
#* Wesnoth lab, formation of the teams, accounts for Trac and Subversion
 +
#* homework: installing and playing Wesnoth. Write a review (can be blogged or e-mailed). Due: next Monday, February 1.
 
# Wednesday, January 27, T-321, 10.15 - 11.45
 
# Wednesday, January 27, T-321, 10.15 - 11.45
 
#* lecture: FLOSS development:  environments, tools and methods. Trac (wiki, tickets, versioning) and Subversion (with possible tools).
 
#* lecture: FLOSS development:  environments, tools and methods. Trac (wiki, tickets, versioning) and Subversion (with possible tools).
#* homework – initial project the campaign, milestones etc (deadline at the last meeting on February 3)
+
#* homework: the first draft of the campaign, milestones etc. Due:  Wednesday, February 3 (the last meeting)
 
# Wednesday, January 27, T-321, 11.15 - 13.45
 
# Wednesday, January 27, T-321, 11.15 - 13.45
#* Wesnoth and tools lab
+
#* Wesnoth and tools lab.
 
# Thursday, January 28, T-321, 10.15 - 11.45
 
# Thursday, January 28, T-321, 10.15 - 11.45
 
#* lecture: FLOSS as business: different models
 
#* lecture: FLOSS as business: different models
#* homework: case studies (Deadline: 2 weeks)
+
#* homework: case studies. Due: Monday, February 15
 
# Thursday, January 28, T-321, 12.15 - 13.45
 
# Thursday, January 28, T-321, 12.15 - 13.45
 
#* Wesnoth lab
 
#* Wesnoth lab
 
# Monday, February 1, T-321, 10.15 - 11.45
 
# Monday, February 1, T-321, 10.15 - 11.45
 
#* legal framework of FLOSS. Licenses, patents etc.
 
#* legal framework of FLOSS. Licenses, patents etc.
#* homework: case studies (Deadline: 2 weeks)
+
#* homework: case studies. Due: Monday, February 15
 
# Tuesday, February 2, T-321, 10.15 - 11.45
 
# Tuesday, February 2, T-321, 10.15 - 11.45
 
#* lecture: community building and management
 
#* lecture: community building and management
#* homework: readings, analysis of the Wesnoth community (based on the forum), ideastorming on better campaign building
+
#* homework: readings, analysis of the Wesnoth community (based on the forum), ideastorming on better campaign building. Due: Monday, March 1.
 
# Wednesday, February 3, T-321, 10.15 - 11.45
 
# Wednesday, February 3, T-321, 10.15 - 11.45
 
#* lecture: Free Culture: the wider social impact of FLOSS
 
#* lecture: Free Culture: the wider social impact of FLOSS
#* homework: readings, case studies
+
#* homework: readings, case studies. Due: Monday, March 1.
 
# Wednesday, February 3, T-321, 11.15 - 13.45
 
# Wednesday, February 3, T-321, 11.15 - 13.45
#* lab/discussion: Wesnoth campaign building. Campaign deadline: December 10)
+
#* lab/discussion: Wesnoth campaign building
  
  
 
=== Independent work ===
 
=== Independent work ===
  
* Campaign project - story outline, main characters, rough overview of scenarios - should be put up to the team's Trac page. Deadline - February 22 (3 weeks from the end of the lectures)
+
* Campaign project - story outline, main characters, rough overview of scenarios - should be put up to the team's Trac page. Due: Monday, February 22 (3 weeks from the end of the lectures)
 
* Beta milestone - end of March (should be ready/playable with minor omissions)
 
* Beta milestone - end of March (should be ready/playable with minor omissions)
* Final milestone - April 5 (a week before the end of the course)
+
* Final milestone - April 5 (a week before the end of the course). The campaign should be finished and the final version made available for download (in order to let others review it).
* Playtesting the other team's campaign. Write a review (can be blogged or e-mailed). During the final week - deadline April 12 (the final day of the course)
+
* Playtesting another team's campaign. Write a review (can be blogged or e-mailed). During the final week - deadline April 12 (the final day of the course)
  
  

Redaktsioon: 20. jaanuar 2010, kell 13:26

NB! This page now reflects the Spring 2010 course! The stuff is under construction.


Course Schedule

The course runs in three parts:

  • Lecture/lab session - end of January / beginning of February
  • Independent work - February - April
  • Final seminar - April 12.

Lecture/lab session

  1. Monday, January 25, T-321, 10.15 - 11.45
    • Course intro - what is going to happen
    • lecture: FLOSS definition, differences from proprietary models. Free Software vs Open Source vs Freeware. FSF vs OSI
    • homework: some readings (Stallman vs Raymond). Write a review (can be blogged or e-mailed). Due: next Monday, February 1.
  2. Monday, January 25. T-321, 12.15 - 13.45
    • lecture/demonstration/practice: Battle for Wesnoth as our playground. Main ideas of the game, overview of the wesnoth/data directory. Creating a scenario and a campaign. WML.
  3. Tuesday, January 26. T-321, 10.15 - 11.45
    • Wesnoth lab, formation of the teams, accounts for Trac and Subversion
    • homework: installing and playing Wesnoth. Write a review (can be blogged or e-mailed). Due: next Monday, February 1.
  4. Wednesday, January 27, T-321, 10.15 - 11.45
    • lecture: FLOSS development: environments, tools and methods. Trac (wiki, tickets, versioning) and Subversion (with possible tools).
    • homework: the first draft of the campaign, milestones etc. Due: Wednesday, February 3 (the last meeting)
  5. Wednesday, January 27, T-321, 11.15 - 13.45
    • Wesnoth and tools lab.
  6. Thursday, January 28, T-321, 10.15 - 11.45
    • lecture: FLOSS as business: different models
    • homework: case studies. Due: Monday, February 15
  7. Thursday, January 28, T-321, 12.15 - 13.45
    • Wesnoth lab
  8. Monday, February 1, T-321, 10.15 - 11.45
    • legal framework of FLOSS. Licenses, patents etc.
    • homework: case studies. Due: Monday, February 15
  9. Tuesday, February 2, T-321, 10.15 - 11.45
    • lecture: community building and management
    • homework: readings, analysis of the Wesnoth community (based on the forum), ideastorming on better campaign building. Due: Monday, March 1.
  10. Wednesday, February 3, T-321, 10.15 - 11.45
    • lecture: Free Culture: the wider social impact of FLOSS
    • homework: readings, case studies. Due: Monday, March 1.
  11. Wednesday, February 3, T-321, 11.15 - 13.45
    • lab/discussion: Wesnoth campaign building


Independent work

  • Campaign project - story outline, main characters, rough overview of scenarios - should be put up to the team's Trac page. Due: Monday, February 22 (3 weeks from the end of the lectures)
  • Beta milestone - end of March (should be ready/playable with minor omissions)
  • Final milestone - April 5 (a week before the end of the course). The campaign should be finished and the final version made available for download (in order to let others review it).
  • Playtesting another team's campaign. Write a review (can be blogged or e-mailed). During the final week - deadline April 12 (the final day of the course)


Grading

  • Wesnoth campaign (participation in team; everyone writes a short report about his/her role and contribution) – 50%
  • Campaign testing/review (for another team's work) - 15%
  • reviews/reflections/case studies - 35%


Lecture notes