User:Dreddy

Revision as of 01:59, 1 June 2017

Deepti Reddy

Associate Professor in Computer Engineering department in SIES Graduate School of Technology, University of Mumbai, India.

The areas of interest are- Intelligent Tutoring System, Expert Systems, Semantic web, Technology enabled learning system for developing thinking skills.

Intro to FOSS Project Anatomy (Activity)

Basic aspects of FOSS project

Community of FOSS development-The position of person depends on the contribution to the projects- starts as user of the application, identify small changes that may lead to larger changes and responsible for larger portion of the project.

Leadership- "Benevolent Dictator", AKA "BD" takes decision usually in collaboration with major developers.

Forking- making changes to the copy of the existing project or code.

Communication- IRC, wikis, mailing lists, bug trackers.

Roadmaps- future of the projects, in form of enhancements or bugs fixed.

Releases- The developed project with code and documentation.

Repository- The place where software packages are saved for distribution, e.g. Launchpad, SourceForge, GitHub

Packaging- Packaging a project for distribution in zip or binary format.

Upstream/downstream- upstream is main project and downstream is copy of code for changes.

Version control- track of various versions of project

Trackers- bug report

Sugar Lab Project

Contribution Learning software for children, which consists of collection of tool for learners to explore, discover, create and reflect through collaboration. Contributors are- Teachers, content writers, People person, developer, designer, translator. Communication is through wiki, email, IRC. Community- the goals in terms of education, technical and community clearly stated. Roadmap- three phases- identifying goals, building project and iteration.

Tracker- The bugs can be submitted in github.com in issues tab, click on new issue. types/categories of tickets listed on this page as well as the information available for each ticket.

Types of tickets listed are- defect, enhancement, task Information available for each ticket are- ticket number, bug details, status, owner, type, priority, and milestone.

Repository- date of last commit is May 16, 2017

Release cycle- The roadmap is updated at the beginning of each release cycle.

SAHANA Foundation- Open Source Disaster Management Software

Provides platform for rapidly deploying information management system for disaster management.

One can contribute as a 1. Developer- Contribute to Sahana by closing tickets, updated wiki docs, writing tests and helping others on the mailing list. 2. Testers- manual testing and documenting test cases 3. Designer- to improve the look and feel of the site.

How the Sahana project structure different than Sugar lab? Sugarlab focus is more on activities to support learning and Sahana is more towards application so the contribution towards sahana is more technical than Sugarlab.

""Tracker"" The tickets in Sahana are categorized under various titles which is not the same in Sugarlab. ""Types/categories of tickets""- defuct/bug, documentation, enhancement, task, minor. ""Information available for each ticket""- ticket number, summary, component, version, priority, type, owner, status, created.