User:Ssheth
(Difference between revisions)
(→Part 3) |
(→Stage 1 Part A: Adding anatomy of FOSS) |
||
| Line 29: | Line 29: | ||
# I'm stuck.. help me with X | # I'm stuck.. help me with X | ||
#* In this case, people are trying to install/work with some software/framework/library and getting error messages. This seems like a faster, 90s version of StackOverflow for people to get answers. | #* In this case, people are trying to install/work with some software/framework/library and getting error messages. This seems like a faster, 90s version of StackOverflow for people to get answers. | ||
| − | |||
# What is a good way to do X? | # What is a good way to do X? | ||
#* In this case, people are unsure what's a "good" (optimal, efficient, faster, better) way of doing something - A or B. They want advice from the more-seasoned users in the channel. Comparing to StackOverflow, I see this as a big advantage as something "subjective" is not a good question to ask on StackOverflow. | #* In this case, people are unsure what's a "good" (optimal, efficient, faster, better) way of doing something - A or B. They want advice from the more-seasoned users in the channel. Comparing to StackOverflow, I see this as a big advantage as something "subjective" is not a good question to ask on StackOverflow. | ||
| + | |||
| + | === Anatomy of a FOSS Project === | ||
| + | |||
| + | ==== The Sugar Labs Project ==== | ||
| + | |||
| + | * Community | ||
| + | *# Activity Team | ||
| + | *#* Develops and Maintains the activities; recruits developers | ||
| + | *#* There are 2 coordinators and a lot of contributors | ||
| + | *# Development Team | ||
| + | *#* Builds and Maintains the core Sugar Project | ||
| + | *#* There is no coordinator and four people (assuming they're contributors?) listed | ||
| + | *# Documentation Team | ||
| + | *#* Provides high quality documentation (learner's manual, programming references, and tutorials) | ||
| + | *#* There is no coordinator here as well and two editors with their areas of speciality listed | ||
| + | * Tracker | ||
| + | * Repository | ||
| + | * Release Cycle | ||
| + | * Communication | ||
| + | |||
| + | ==== The Sahana Eden Project ==== | ||
| + | |||
| + | * Community | ||
| + | * Tracker | ||
| + | * Repository | ||
| + | * Release Cycle | ||
| + | * Communication | ||
Revision as of 03:11, 15 October 2014
Contents |
Swapneel Sheth
Swapneel Sheth is a Lecturer in the Computer and Information Science department at the University of Pennsylvania.
His research and teaching interests are Software Engineering, Privacy, and the Web.
Stage 1 Part A
Intro to IRC
Part 1
- How do people interact?
- In an informal manner
- What is the pattern of communication?
- Usually question and answer - somebody has a question or a problem, other tries to help solve it
- Are there any terms that seem to have special meaning?
- The chat bot commands
- Can you make any other observations?
- It's nice to have the meeting transcribed by meetbot in a relatively easy manner, with annotations
Part 3
I've been following the #ushahidi channel periodically, but it seems to have very little activity.
I've looked at other interesting (to me) open-source channels - #rvm, #ruby-lang, #rubyonrails. These are a lot more active and seem to have two kinds of questions.
- I'm stuck.. help me with X
- In this case, people are trying to install/work with some software/framework/library and getting error messages. This seems like a faster, 90s version of StackOverflow for people to get answers.
- What is a good way to do X?
- In this case, people are unsure what's a "good" (optimal, efficient, faster, better) way of doing something - A or B. They want advice from the more-seasoned users in the channel. Comparing to StackOverflow, I see this as a big advantage as something "subjective" is not a good question to ask on StackOverflow.
Anatomy of a FOSS Project
The Sugar Labs Project
- Community
- Activity Team
- Develops and Maintains the activities; recruits developers
- There are 2 coordinators and a lot of contributors
- Development Team
- Builds and Maintains the core Sugar Project
- There is no coordinator and four people (assuming they're contributors?) listed
- Documentation Team
- Provides high quality documentation (learner's manual, programming references, and tutorials)
- There is no coordinator here as well and two editors with their areas of speciality listed
- Activity Team
- Tracker
- Repository
- Release Cycle
- Communication
The Sahana Eden Project
- Community
- Tracker
- Repository
- Release Cycle
- Communication
