You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
|
|
# Road Map #
This document is the KiCad Developer's road map document. It is a livingdocument that should be maintained as the project progresses. The goal ofthis document is to provide an overview for developers of where the projectis headed beyond the current development cycle road map (currently[version 6](./v6_road_map.html) to prevent resource conflicts and endlessrehashing of previously discussed topics. It is broken into sections foreach major component of the KiCad source code and documentation. It definestasks that developers an use to contribute to the project and provides updatedstatus information. Tasks should define clear objectives and avoid vaguegeneralizations so that a new developer can complete the task. It is not aplace for developers to add their own personal wish list It should only beupdated with approval of the project manager after discussion with the leaddevelopers.
Each entry in the road map is made up of four sections. The goal shouldbe a brief description of the what the road map entry will accomplish. Thetask section should be a list of deliverable items that are specific enoughhat they can be documented as completed. The dependencies sections is a listof requirements that must be completed before work can begin on any of thetasks. The status section should include a list of completed tasks or markedas complete as when the goal is met.
[TOC]
# Project # {#project}
This section defines the tasks for the project related goals that are notrelated to coding or documentation. It is a catch all for issues such asdeveloper and user relations, dissemination of information on websites,policies, etc.
# General # {#general}
This section defines the tasks that affect all or most of KiCad or do notfit under as specific part of the code such as the board editor or theschematic editor.
# Build Tools # {#build_tools}
This section covers build tools for both the KiCad source as well as thecustom dependency builds required to build KiCad.
# Common Library # {#common_lib}
This section covers the source code shared between all of the KiCadapplications
# KiCad: Application Launcher # {#kicad}
This section applies to the source code for the KiCad application launcher.
# Eeschema: Schematic Editor # {#eeschema}
This section applies to the source code for the Eeschema schematic editor.
# CvPcb: Footprint Association Tool # {#cvpcb}
This section covers the source code of the footprint assignment tool CvPcb.
# Pcbnew: Circuit Board Editor # {#pcbnew}
This section covers the source code of the board editing application Pcbnew.
# GerbView: Gerber File Viewer # {#gerbview}
This section covers the source code for the GerbView gerber file viewer.
# Documentation # {#documentation}
This section defines the tasks for both the user and developer documentation.
## Maintenance ## {#doc_maintenance}
**Task:**- Keep screen shots current with the source changes.
**Dependencies:**- None.
**Status:**- No progress.
# Unit Testing # {#unittest}
**Goal:**
Improve the quality of KiCad and ensure changes do no break existingcapabilities.
**Task:**- Explore the possibility of including a C++ unit test framework in addition to the existing Python framework.- Create robust enough test coverage to determine if code changes break any core functionality.
**Dependencies:**- Completion of the initial release of this document.
**Status:**- In progress.
[kicad-website]:http://kicad-pcb.org/[kicad-docs]:http://ci.kicad-pcb.org/job/kicad-doxygen/ws/Documentation/doxygen/html/index.html
|