Survey

Introductions

Choose Teams

1) Create your blog and blog to introduce yourself and your plans.
2) Create a GitHub account.
3) Join class Wiki and list your name in lastName- alphabetical order hyperlinked to your blog

Blog SubTitle = "Introduction"

Get organized. Create Team wiki on team Github account and list team and wiki on class Wiki.

in class exercise: Team Intro

Team: Research and choose 3 open-source candidate projects that run on Linux and that you would like to participate in (preferably H/FOSS). Projects should be mature with online communities that welcome newcomers. We have some targeted projects as well. I may veto projects. Rank them.

Blog initial findings about projects and readings

Blog SubTitle = "My H/FOSS Preferences"

fyi: more H/FOSS

Publish findings on Wiki

Choose Team Projects

Plan team projects

The Cathedral and the Bazaar

Ethics of free software - Meyer

Rebuttal to Meyer

TOS Exercise 2.4.4
Blog about exercise and the readings

Blog SubTitle = "H/FOSS Experiences and Reflections"

Apache 2.0 License

TOS Chp 3

SD Chp 2 and 3

As applicable:

1) Select an IRC client and join the channel for your Team project; peruse the history and listen to current traffic;
2) Join the electronic mail list and/or newsgroup for your Team project; select an interesting thread and explore it;
3) Join the GitHub IssuesTracker for your Team project; select an interesting thread and explore it;

Blog about your experiences and readings

Blog SubTitle = "Joining the Project"

IRC Tutorial

IRC HowTo

Explore GitHub

Get and build the Code

Git Tutorial

TOS Chp 4

1) Experiment with Git and GitHub
2) Install Git and and a GitHub client on your own machine (suggest you install Ubuntu using Virtualbox);

Blog about experiences and compare and contrast the two systems

Blog SubTitle = "I'm Git'n it"

GitHub Guide

Learn Git

Git workflow

1) Publish a full report on your selected project, its members, history, etc. on the team wiki

2) Publish your ideas for contributing to this project including : select and describe one bug; find the bug in the code; describe how you will fix and test the bug; publish report

3) Download project code
Build project code
Install project
Publish experience report

Team Reports

Getting the Code

Do Freeciv example in TOS Chapter 5
publish experience report on blog

Explore http://opensource.com/
Read at least two medium length articles from the site and blog about what you learned and your response to the articles. Compare and contrast the articles if appropriate.

Blog SubTitle = "Reflections on Open Source in Today's World"

Engaging !

Team Reports

Blog about your experiences

Blog SubTitle = "Bug Juice"

1) Choose a bug or set of bugs or an improvement or set of improvements that your team will focus on for the rest of the semester and which you will officially submit to your chosen project; publish report

2) Produce a timeline for the rest of the semester, including a poster presented at SSM poster session, ending with a presentation during the period scheduled for the final; publish report

Do exercises in TOS 6.4, 6.5, 6.6, 6.7;

Blog experience report about exercises

Blog SubTitle = "This bugs me"

Testing and Debugging the Code

Team Reports

Blog experience report about bug hunting

Blog SubTitle = "Squashed?"

Fix a bug and submit your fix to the project; publish report

TOS Chp 7

chosen article

Do exercises in TOS 7.2.2, 7.8, 7.9; blog experience report

Blog your reflections on the article you chose from Software, Computer, or CoACM magazines PLUS this article

Blog SubTitle = "What's Happening?"

SD Chp 4

SD Chp 5.4, 5.5, 5.6

SD Exercises 5.7, 5.8 (requires planning and getting software example);

Blog experience report

Blog SubTitle = "Refactoring Mindset"

Fixing the Code

Team Reports

Blog experience report

Blog SubTitle = "Reflections on my Progress"

Select a meeting from this list and make plans to attend at least once. (see blog entry below)

Publish your progress and what you plan to have done by 15 March, after the break!

Blog about your experiences selecting from this list . Attend by 7 April if possible.

Blog SubTitle = "Planning to Meet Charleston"

TOS Chp 8

Do exercises in TOS 8.1.1, 8.4;

Blog about exercises and readings

Blog SubTitle = "The Doc is in!"

Blog about reading

Blog SubTitle = "Release early and often"

SD Chp 6

Do exercises SD 6.1 - 6.4;

Blog about exercises

Blog SubTitle = "Chapter 6"

R 17 Mar

F 18 Mar

Required Attendance or 1000 word paper.

Alumni Symposium

Blog SubTitle = "That could be me in x years!"

Team Reports

Blog SubTitle = "Reflections on my progress and plans"

Publish your progress relative to your planned timeline.

SD Chp 7

Do exercises SD 7.1 - 7.3;

Blog about reading and exercises

Blog SubTitle = "Chapter 7"

SD Chp 8

Do exercises 8.1.a, 8.1.b

Blog about reading and exercises

Blog SubTitle = "Chapter 8"

SD Chp 9

Do exercise 9.1

Blog about reading and exercise

Blog SubTitle = "Chapter 9"

Blog about attending the meeting you chose on 18 February

Blog SubTitle = "Meeting Charleston"

Team Reports

Poster Reviews

POSSCON plans

Select 3 presenters from the Great Wide Open schedule. Your goal is to ask them some questions; Blog your plans and then blog about your experiences (see below);

Blog SubTitle = "Preparing for Great Wide Open"

Evaluations:

• OAKS home page
• MyCharleston (from the link on their “Academic Services” tab)
• Direct web link: coursereview.cofc.edu
• CofC Mobile App: Android |  Apple | Other
• Personalized link that is emailed to students 3 times

T 12 Apr

Class

Blog about Great Wide Open

Blog SubTitle = "Great Wide Open Report"

Blog about SSM Poster Session

Blog SubTitle = "Poster Child"

Team Reports

Class Review

Create a PDF from your blog and email it to Dr. Bowring by NOON 26.April: [lastName]_462_2016_blog.pdf

Turn in team self-evaluations by hand.

Publish your progress relative to your planned timeline.

Create a PDF from your Wiki and email it to Dr. Bowring by NOON 26.April: [TeamName]_462_2016_wiki.pdf

R 21

Apr

T 26 April

Final

Team presentations in HW East 300 --------> 12PM - 3PM>> be sure to check out equipment before the event!

Final Presentation Notes:
Each team presents for 20 mins followed by 5 mins questions;
Each team member must present;
Content: Overview of project, people, etc.; Accomplishments; Issues; Lessons learned;

Final grades noon 3 May.