[gst-devel] API reference updating for 0.9 -- your help needed!
wingo at pobox.com
Mon Oct 31 04:16:30 CET 2005
On Friday we tried to work on getting the API reference documentation in
a respectable condition. Thomas, Wim, Julien, Stefan, Edward, Mike, and
I chose different files and went through them. This was coordinated via
a wiki page .
We focused on consistency, correctness, and readability. We fixed easy
things and wrote down some notes for future fixes, although these notes
are not online atm. There were some teething problems, but we eventually
settled on a common style .
So we got through a few files. It went slowly at first but the next time
that we do it it will go faster. The problem is, there are about 140
files that we need to review, and 4 weeks in which to do it. If each
file optimistically takes half an hour, that is about *3 hours per week
per hacker* that each person needs to spend on the docs.
This is then a call for help! How, you say? Why it's quite simple:
* All of the people mentioned above should continue to work on docs
on a weekly basis.
* Anyone else who understands what the docs should say is MORALLY
OBLIGATED to help out.
* Anyone else with CVS commit access but who does not feel
comfortable reviewing content can help out greatly by making the
existing docs more consistent. For example, change this:
* @pad: the #GstPad to stop the task of
* @pad: a #GstPad
and the other guidelines listed in .
* Those without CVS commit access can comment on the "Description"
sections of the API docs at , which we will keep up-to-date,
filing bugs if the sections are not clear or incorrect, preferably
More information about the gstreamer-devel