User:Jklukowska
Jklukowska (Talk | contribs) m (→Stage 1 Activities) |
Jklukowska (Talk | contribs) m (→Stage 1 Activities) |
||
| Line 25: | Line 25: | ||
The release cycle provides a structures of stages during which teams need to accomplish certain goals. The roadmap of the project is providing the deadlines by which those stages need to be completed. The roadmap also specifies which particular modules are included in the specific release. | The release cycle provides a structures of stages during which teams need to accomplish certain goals. The roadmap of the project is providing the deadlines by which those stages need to be completed. The roadmap also specifies which particular modules are included in the specific release. | ||
| + | |||
| + | |||
| + | |||
| + | ===Part B=== | ||
Revision as of 02:58, 2 November 2014
Contents |
Joanna Klukowska
Joanna Klukowska is a Clinical Assistant Professor of Computer Science at Courant Institute of Mathematical Sciences of New York University.
Dr. Klukowska joined the Computer Science Department of NYU as a full time faculty in the fall of 2014. She is teaching undergraduate courses. She is currently working in development of special topics courses in the area of open source tools and image processing.
Stage 1 Activities
Part A
Introduction to IRC, Part 1
- How do people interact? - using short messages addressed to the whole group or particular users
- What is the pattern of communication? - short messages that together form a conversation, but sometimes different conversations seem to be mixed up
- Are there any terms that seem to have special meaning? - #topic, #action, #info, #startmeeting, #link, #endmeeting
- Can you make any other observations? - I have never used IRC before. I am curious how it works with many participants covering different topics all at once.
Introduction to IRC, Part 3
I have been observing the GNOME Accessibility Team channel. So far people join and leave, but no discussion.
Anatomy of a FOSS project
Looking at the SugarLabs and the Sahana Eden wikis.
The different teams are working on the same project but the teams differ in which part of the project they are involved in. It seems that different teams require very different set of skills: development of the core of the project vs. development of activities vs. providing documentation (which sadly does not seem to have any contributors).
Trackers or tickets seem to be both the serious bugs (nicely called defects), requests for improvements (called enhancements) and documentation requests. I looked at a few of the enhancements and it is not clear why they are not considered to be minor defects. Both enhancements and defects have a priority level associated with them. The Sahana Eden page provides a grouping of the tickets into tickets specific to the particular products/projects.
The release cycle provides a structures of stages during which teams need to accomplish certain goals. The roadmap of the project is providing the deadlines by which those stages need to be completed. The roadmap also specifies which particular modules are included in the specific release.
