There should be a section for documenting how to use the stuff in contrib. Among other things, the script introduced in bug 198458 should be documented.
Priority: -- → P4
Target Milestone: --- → Bugzilla 2.18
Yeah, I was going to do that as part of the checkin for that bug. :) I have a full printout of the cvs logs for everything in that directory, and was planning to expand the README file a bit :)
Adding Matt Barnson, who mentioned in IRC tonight that he was working on some of this already.
Jake is leaving for a while (Reserve unit got called up), and we don't have a new docs owner yet. Anyone interested in helping out, please add email@example.com to your watch list in your email preferences in Bugzilla.
Assignee: jake → documentation
Enhancements which don't currently have patches on them which are targetted at 2.18 are being retargetted to 2.20 because we're about to freeze for 2.18. Consideration will be taken for moving items back to 2.18 on a case-by-case basis (but is unlikely for enhancements)
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20
all docs are current milestone
Target Milestone: Bugzilla 2.20 → Bugzilla 2.18
For what it's worth, if you add POD to any of the files in contrib/, that POD will show up automatically in the API docs.
Summary: contrib/ stuff needs documentation → Modern contrib/ stuff lacks documentation
I believe this is a duplicate of 356926, which has a patch under review
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 356926
You need to log in before you can comment on or make changes to this bug.