DeveloperDocumentation
Status
Summary
We should have well-organized developer-oriented documentation for our various tools and procedures, including freeze exceptions, merge-o-matic, seeds and their germination, and much, much more.
Interpretation and overall plan
During the first UBZ BOF, we concluded that the best way to achieve this would be to:
Create an Ubuntu Developers' Reference, which would be derived in the usual way (with a ubuntuNN version etc.) from the Debian Developers' Reference.
As well as deleting or replacing Debian-specific content from the DDR, we will transfer content from process-related wiki.ubuntu.com pages.
The Ubuntu Documentation Team will of course be consulted, but the UDR will be maintained primarily by Ubuntu developers since (a) much of the proposed (non-Debian) content is currently known only to Ubuntu developers and (b) the audience consists of Ubuntu developers.
Areas to cover (or consider covering)
BreezyReleaseSchedule (don't copy content, refer to it)
DeveloperResources (which should become a navigation page if not be completely deleted)
Different approaches to packaging, eg: debian/rules approaches (by-hand, debhelper, cdbs); patch systems (whether to use one, which one to use).
- Who to talk to to decide whether to make a particular change/upload - areas of responsibility
- Describe seeds and germination