Yekaterina (Kate) Kharitonova is a visiting assistant professor at Harvey Mudd College in Claremont, CA.
Intro to FOSS Project Anatomy (Activity)
The Sugar Labs Project (http://sugarlabs.org/)
- Educator: create educational materials and activities, use Sugar for learning and provide feedback about it to developers.
- Content writer: generate content for the various projects or activities.
- People person: communicate with others about Sugar, by either promoting it, supporting it, or organizing events.
- Developer: dive into the source code — design, test, debug, and code.
- Designer: create visual content (e.g., icons, logos, images), design and mock-up web pages, publications, and various materials (e.g., T-shirts)
- Translator: translate user interface and Sugar materials as well as provide culture-specific feedback to other teams.
What are the commonalities across roles? What are the differences?
- Similarities: most roles require familiarity with Sugar Labs, and heavily rely on good communication skills
- Differences: main differences stem from _who_ the person is communicating with and the medium/skills that they use for fulfilling the role.
Tracker / Repository
The issue/bug tracker is a bit confusing.
The latest commit on the SugarLabs master branch (568888f) was on Oct 10, 2016. https://github.com/sugarlabs/sugar/commit/568888faab66c2de280f4df1af937195cb80d5df
The Sugar Labs site (https://bugs.sugarlabs.org/) is using Trac to keep track of bugs, and seems to be more updated than Github (latest ticket https://bugs.sugarlabs.org/ticket/4972 was on Feb. 18, 2017). On that site, there is a link to "git", which points to http://git.sugarlabs.org. The latest commit there is a857c10e on the scan-activity/scan-activity:master branch on March 10, 2017 09:33.
Each release cycle includes releases for the development, beta, release, and final stages of the iteration. The relationship between release cycle and roadmap: the release team updates the roadmap at the beginning of each release cycle with the schedule of release dates, a list of modules and external dependencies, references to all the tickets considered for the release, and new feature proposals.
The Sahana Eden Project (sahanafoundation.org/eden)
- Are there any commonalities between the roles? Is there something distinct for each type of contributor? How is this structure different than the one you found on the Sugar Labs website?
Just like the Sugar Labs, Sahana Eden also has developers, designers, and translators. The instructions on the Sahana Eden website are a bit more detailed, listing concrete starting points and guidelines. Developers have a much finer breakdown in the framework they are using: e.g., developer Blueprints includes backups, dashboards, and database migration, to name a few. There are also more development opportunities for testing, bug marshalling, and sysadmin tasks.
The Sahana Eden bug tracker (http://eden.sahanafoundation.org/report).
- How is the information Sahana Eden bug tracker different than the information found on the Sugar Labs tracker page?
The issue tracker on the Eden project can provide bug reports grouped by various categories, such as active tickets (also filtered by version and milestone), feature requests, or easy bugs for beginners.
- Indicate the types/categories of tickets listed on the Active Tickets page as well as the information available for each ticket.
- type (e.g., enhancement, task, defect/bug)
- priority (e.g., critical, major, trivial)
- component (e.g., sync, msg, org)
- status (e.g., new, assigned, accepted)
- version (e.g., trunk, pakistan).
Additionally, each ticket has a unique number, owner, date created.
Repository -- https://github.com/sahana/eden
Latest commit to the master branch was on March 13, 2017 3:55AM PDT (@flavour prs l10n updates from ARCS).
Release cycle Information about Sahana Eden's release cycle and roadmap can be found on http://eden.sahanafoundation.org/roadmap
- Milestone 0.9.0 "Medway" (92% complete)
- Milestone: 1.0 "Avon" (73% complete) // Planned for: May 2012 (Draft)
- Milestone: 2.0 (98% complete)