We are implementing a script that will look for certain keywords in commit logs, and finding one, Cc:'s the commit message to a particular mailing list. Our first implementation looks for *docs* and Cc:'s the commit log to relnotes@xxxxxxxxxxxxxxxxxxx The release notes beat writers can then decide which beat is appropriate for that note, pass it on to a particular guide or tutorial, or drop it as irrelevant. This script is live now. Before we ask developers to start using it, we need to give them some guidelines of where, when, and why to use it. This page is a first pass at guidelines for developers on what to document: http://fedoraproject.org/wiki/DocsProject/WhatToDocument Please help fill out these guidelines. We'll announce to the developers when we have enough of a guideline for them to follow. - Karsten -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Red Hat SELinux Guide http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/
Attachment:
signature.asc
Description: This is a digitally signed message part
-- fedora-docs-list@xxxxxxxxxx To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-docs-list
