Version 4 (modified by deyan, 16 years ago) (diff) |
---|
Analysis
Overview
Better structured code standards, requirements for reviews.
Task requirements
- Create PLATFORM_STANDARDS_CODE
- Review PLATFORM_STANDARDS_CODE_R0 implementation section create a better structure and link the pages there in [PLATFORM_STANDARDS_CODE]. The resulting page should be renamed to satisfy the wiki naming convention.
- Define rules for reviewing coding tasks' implementation
- Required section - things that are obligatory for the implementation in order to pass the review
- Recommended section - things that are recommended for the implementation, needed for higher score
- Optional section - things that can be included in the implementation and may be rated with higher score.
These rules should be stuctured like a checklist. See implementation idea for more detailed information. These requirements will be updated each week when suggestions are made.
- Explain when requesting a superreview is allowed.
- Add a requirement that the reviewer should either stick to these rules or comment them in the comment section.
Task result
(The Analysis should contain strict requirements about the end product of the task (for example the result must be source code, the result must be google doc, etc.))
Implementation idea
(It is advisable to include some rough implementations ideas.)
Related
(Here you can add related tasks that could be useful or helpful.)
How to demo
(In this section you must add instructions for the demo of the task.)
Design
Implementation
(Implementation results should be described and linked here (from the wiki or the repository))
Testing
Comments
(Write comments for this or later revisions here.)