User:Mallen
| Line 5: | Line 5: | ||
Meghan has been teaching in Computer Science at UBC since 2007 and has focused on teaching CS1, CS2 and an Introduction to Software Engineering course. She is currently focusing on creating curriculum and teaching for Vantage College, which offers an innovative, first-year program for international students. | Meghan has been teaching in Computer Science at UBC since 2007 and has focused on teaching CS1, CS2 and an Introduction to Software Engineering course. She is currently focusing on creating curriculum and teaching for Vantage College, which offers an innovative, first-year program for international students. | ||
| − | Intro to IRC | + | ===Intro to IRC=== |
| − | How do people interact? | + | '''How do people interact?''' |
The interactions seem fairly casual, but it seems like there is a chair of the meeting that keeps the conversation on track. The chair uses some meetbot commands to take minutes. The team members give updates and help each othr when they can. | The interactions seem fairly casual, but it seems like there is a chair of the meeting that keeps the conversation on track. The chair uses some meetbot commands to take minutes. The team members give updates and help each othr when they can. | ||
| − | What is the pattern of communication? | + | '''What is the pattern of communication?''' |
It seems like one person at a time talks about what they've been working on and others jump in if they have questions or something to add. | It seems like one person at a time talks about what they've been working on and others jump in if they have questions or something to add. | ||
| − | Are there any terms that seem to have special meaning? | + | '''Are there any terms that seem to have special meaning?''' |
The meetbot commands, and it seems that you can mention a member of the conversation (e.g. to ask them a question) | The meetbot commands, and it seems that you can mention a member of the conversation (e.g. to ask them a question) | ||
| + | |||
| + | ===Anatomy of a FOSS Project=== | ||
| + | |||
| + | '''Sugar Project''' | ||
| + | Activity team: develops and maintains activities for Sugar as well as interacting with community contributors. Works with Development and Infrastructure teams to ensure developers have what they need. Documents activities | ||
| + | Development team: designs and implements core Sugar environment. Works closely with the Design and Testing teams | ||
| + | Documentation team: creates documentation for users and developers | ||
| + | |||
| + | Some commonality between the teams is that the Activity and Documentation teams both work on documentation although at a different scale. Also, the Development and Activity teams both do development, but they develop different things. | ||
| + | |||
| + | Issues: | ||
| + | types/categories: defects or enhancements | ||
| + | For each ticket, the following information is included | ||
| + | - reporter, priority, relevant component, severity, list of other interested team members, status, owner, milestone fix is planned for, keywords, distribution or OS that the issue occurs in and a description. Each ticket also includes attachments, a reference to related change sets, comments and a history of changes | ||
| + | |||
| + | I think Sugar uses a web-based common Git repo | ||
| + | |||
| + | The Development Team's Roadmap is updated at the beginning of each release cycle by the release team. | ||
| + | |||
| + | '''Sahana Eden Project''' | ||
| + | Developers: Once developers get set up, they can choose what size and kind of project to work on | ||
| + | Testers: The project lists many ways for people to get involved with Testing. Testers can choose to manually test, write test cases or work on the CI server. | ||
| + | Designers: Designers are graphic designers who wish to contribute to the project. The project prefers HTML/CSS contributions but accepts others. | ||
| + | |||
| + | This is different than what I found for the Sugar project because the developers are not broken into teams. There are also tasks listed for potential contributors with a range of skills (manual tests, graphic designers, CI server specialists, etc.) so it seems like it would be easier for someone to figure out how they could contribute to Sahana than it would be to figure out how to contribute to Sugar. | ||
| + | |||
| + | The Sahana tickets are grouped into specific queries - to see all the open tickets I have to click on Active tickets. | ||
| + | types of tickets: defect/bug, documentation, task, enhancement | ||
| + | each ticket includes reporter, priority, relevant component, keywords, due date, description, owner, milestone and version, list of other interested community members, comments, change history | ||
| + | |||
| + | I think Sahana uses a local repo | ||
| + | |||
| + | Sahana's roadmap page includes current and past milestones, including the details of what has changed for each milestone | ||
Revision as of 03:51, 24 October 2014
Meghan Allen
Meghan Allen is an Instructor in Computer Science at the University of British Columbia (UBC) and Vantage College at UBC. The department of Computer Science has 55 faculty members, approximately 1300 undergraduate computer science majors and 200 graduate students. Vantage College has welcomed its first class of 187 students in August, 2014.
Meghan has been teaching in Computer Science at UBC since 2007 and has focused on teaching CS1, CS2 and an Introduction to Software Engineering course. She is currently focusing on creating curriculum and teaching for Vantage College, which offers an innovative, first-year program for international students.
Intro to IRC
How do people interact? The interactions seem fairly casual, but it seems like there is a chair of the meeting that keeps the conversation on track. The chair uses some meetbot commands to take minutes. The team members give updates and help each othr when they can.
What is the pattern of communication? It seems like one person at a time talks about what they've been working on and others jump in if they have questions or something to add.
Are there any terms that seem to have special meaning? The meetbot commands, and it seems that you can mention a member of the conversation (e.g. to ask them a question)
Anatomy of a FOSS Project
Sugar Project Activity team: develops and maintains activities for Sugar as well as interacting with community contributors. Works with Development and Infrastructure teams to ensure developers have what they need. Documents activities Development team: designs and implements core Sugar environment. Works closely with the Design and Testing teams Documentation team: creates documentation for users and developers
Some commonality between the teams is that the Activity and Documentation teams both work on documentation although at a different scale. Also, the Development and Activity teams both do development, but they develop different things.
Issues: types/categories: defects or enhancements For each ticket, the following information is included - reporter, priority, relevant component, severity, list of other interested team members, status, owner, milestone fix is planned for, keywords, distribution or OS that the issue occurs in and a description. Each ticket also includes attachments, a reference to related change sets, comments and a history of changes
I think Sugar uses a web-based common Git repo
The Development Team's Roadmap is updated at the beginning of each release cycle by the release team.
Sahana Eden Project Developers: Once developers get set up, they can choose what size and kind of project to work on Testers: The project lists many ways for people to get involved with Testing. Testers can choose to manually test, write test cases or work on the CI server. Designers: Designers are graphic designers who wish to contribute to the project. The project prefers HTML/CSS contributions but accepts others.
This is different than what I found for the Sugar project because the developers are not broken into teams. There are also tasks listed for potential contributors with a range of skills (manual tests, graphic designers, CI server specialists, etc.) so it seems like it would be easier for someone to figure out how they could contribute to Sahana than it would be to figure out how to contribute to Sugar.
The Sahana tickets are grouped into specific queries - to see all the open tickets I have to click on Active tickets. types of tickets: defect/bug, documentation, task, enhancement each ticket includes reporter, priority, relevant component, keywords, due date, description, owner, milestone and version, list of other interested community members, comments, change history
I think Sahana uses a local repo
Sahana's roadmap page includes current and past milestones, including the details of what has changed for each milestone
