Analysis

Overview

To improve the quality of code, visible product, documentation and its regular reading we must have strictly defined rules to follow.

Task requirements

In PROCESS page:

• some things should go to implementation section of PLATFORM_STANDARDS_CODE_R0
• the paragraphs should be revised, fixed and ordered
• all of us should look through the content and get familiar with the process
• we should vote for every change in the process (working time for example)

Task result

upgraded PROCESS page

Implementation idea

• add the review phase, remove Done phase, add more commit rules
• inspire others to read the fixed content of the process
• organize votes

Related

PROCESS

How to demo

Show the wiki page and describe the new process

Design

• in PROCESS:
  • add the review phase where needed (after each phase). Emphasize on it to be done when needed.
  • remove Done phase
• vote for working time
• add "focus" time rule
• you can add some Trac rules - logs, tickets, templates
• add reports rules (how to check the reports for errors)
• add what is and when is the weekly meeting
• rename and structure PROCESS section
• make everyone read the new process and write comments

Implementation

All steps of the design section were written and implemented. See PROCESS page.

Testing

Comments

Log

Analysis: Pav (done: 20m)
Review: 3.5 by todor. The analysis is ok, but it could be more specific.
Design: Pav (done: 20m)
Review: 3.5 by todor. The design is ok.
Implementation: Pav (done: 5h)
Review: 3.5 by todor. There was a missing link (I've added it), but overall the implementation is very good. Testing:
Comments: