zcy
/
tinyriscv-openocd
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update main page of doxygen developer documentation: 

- Rewrite copy to give a better introduction and overview.
- Add subpages: The List, Style Guide, Patch Policies, and Bug Reporting.


git-svn-id: svn://svn.berlios.de/openocd/trunk@1897 b42882b7-edfa-0310-969c-e2dbd0fdcd60
__archive__
zwelch 2009-05-23 22:52:47 +00:00
parent 3131636492
commit 08d5f114c9
1 changed files with 25 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

33
doc/manual/main.txt
View File

@ -1,14 +1,31 @@
/** @mainpage OpenOCD Reference Manual
@ref oocd explains how the code has been organized into layers
of APIs and gives an overview of how they fit together. These pages
attempt to give developers a high-level perspective of the various
code modules provided by OpenOCD.
@ref primer provide introductory materials for new developers.
Welcome to the OpenOCD Reference Manual -- the developer's resource for
learning about the internal architecture of the OpenOCD project.
The List of @ref thelist enumerates opportunities for improving or
extending the OpenOCD platform.
In addition, this document contains the tactical and strategic plans
and processes that have been devleoped by and for the community.
Developers that want to contribute to OpenOCD should read the following
sections before starting work:
- The List of @subpage thelist enumerates opportunities for improving or
extending the OpenOCD platform. If your ideas are on The List, you might
check the mailing list archives to find the status of your feature (or bug).
- The @subpage styleguide provides rules that developers should
follow when writing new code for OpenOCD.
- The @subpage patchguide provides policies that developers should
follow when submitting patches to the project.
- The @subpage bugs page contains the content of the BUGS file, which
provides instructions for submitting bug reports to the maintainers.
@ref primer provide introductory materials for new developers on various
specific topics.
Finally, the @ref oocd pages explain how the code has been organized
into layers of APIs, providing an overview of how they fit together.
These pages attempt to give developers a high-level perspective of the
various code modules provided by OpenOCD.
*/