User:Cmurphy
(Difference between revisions)
(→Release Cycle) |
(→Part A: Project Anatomy) |
||
| Line 25: | Line 25: | ||
=====Repository===== | =====Repository===== | ||
it seems to be a local repository | it seems to be a local repository | ||
| − | |||
=====Release Cycle===== | =====Release Cycle===== | ||
The roadmap is updated at the beginning of each release cycle. | The roadmap is updated at the beginning of each release cycle. | ||
| Line 31: | Line 30: | ||
====Sahana Eden==== | ====Sahana Eden==== | ||
=====Community===== | =====Community===== | ||
| − | * Developers: | + | * Developers: people who develop the software; names and roles do not seem to be defined, unlike Sugar Labs; rather, there seems to be more "how to get started" info here |
| − | * Testers | + | * Testers: non-technical users who do QA through manual testing; there are links for documenting test cases, as well as links for developers |
| − | * Designers | + | * Designers: people who work on the user interface |
====Tracker==== | ====Tracker==== | ||
| − | + | * types: defect/bug, documentation, enhancement, task | |
| − | + | * info available for each ticket: ID#, reported by, owned by, priority, milestone, component, version, keywords, CC, due date, launchpad bug, description, attachments, change history | |
| + | * this is different from Sugar Labs because the tickets are organized into reports, rather than just presenting one large list | ||
====Repository==== | ====Repository==== | ||
| − | + | since this is hosted on github, it is a shared/web repository | |
====Release Cycle==== | ====Release Cycle==== | ||
| − | + | The roadmap/milestones seems to be based on the completion of features and not a specific date-driven release cycle. | |
Revision as of 18:45, 14 October 2014
Contents |
Chris Murphy
Chris is an Associate Professor of Practice at the University of Pennsylvania.
He is the director of the Masters of Computer & Information Technology program, and teaches graduate and undergraduate software engineering courses. He also oversees Penn's participation in the Facebook Open Academy Program, an academic initiative sponsored by Facebook in which students contribute to open-source projects under the advisement of a professional mentor.
Chris earned a PhD from Columbia University in 2010, and his research focuses on software testing and computer science education.
Stage 1 Activities
Part A: Intro to IRC, Part 1
- How do people interact? briefly, but politely, and usually offering to help out or at least make helpful suggestions
- What is the pattern of communication? generally focused on a particular issue: someone raises it and the others try to help out
- Are there any terms that seem to have special meaning? technical terms, of course, but also the commands to MeetBot
- Can you make any other observations? amber does not seem to be a big fan of capitalization and punctuation :-p
Part A: Project Anatomy
Sugar Labs
Community
- Activity Team: develops and maintains many of the activities; there are 2 coordinators and 13 contributors
- Development Team: build and maintain the core Sugar environment; there is no coordinator and 4 "people" listed; there is no overlap with the Activity team
- Documentation Team: provide the Sugar community with high quality documentation; no coordinator or contributors are listed
Tracker
- types: defects and enhancements
- info available for each ticket: ID#, reported by, owned by, priority, milestone, component, version, severity, keywords, CC, distribution/OS, status, description, attachments, change history
Repository
it seems to be a local repository
Release Cycle
The roadmap is updated at the beginning of each release cycle.
Sahana Eden
Community
- Developers: people who develop the software; names and roles do not seem to be defined, unlike Sugar Labs; rather, there seems to be more "how to get started" info here
- Testers: non-technical users who do QA through manual testing; there are links for documenting test cases, as well as links for developers
- Designers: people who work on the user interface
Tracker
- types: defect/bug, documentation, enhancement, task
- info available for each ticket: ID#, reported by, owned by, priority, milestone, component, version, keywords, CC, due date, launchpad bug, description, attachments, change history
- this is different from Sugar Labs because the tickets are organized into reports, rather than just presenting one large list
Repository
since this is hosted on github, it is a shared/web repository
Release Cycle
The roadmap/milestones seems to be based on the completion of features and not a specific date-driven release cycle.
