On 07/13/2011 08:24 AM, Kamil Paral wrote:
The questions that I still have are:
- Do we want to start generating API docs soon or wait until
later?
I would say let's have CI first and auto-docs second.
Sounds like a plan to me. I'm certainly not crazy about the idea of manually pushing docs somewhere.
- Where do we want to hold release planning docs, if we want them?
- Planning docs aren't quite the same and trac seems like a good
place to hold those with its integration into our ticketing system.
We can keep the planning docs in Trac, they are not permanent documentation but just short-term documents for us. Or we can create category "AutoQA:Planning" in MW. No strong opinion here.
I have a slight preference for trac because of it's ticket macros in the wiki but either is fine as long as we're consistent.
OTOH pages like "AutoQA configuration" should definitely move to MW, similarly as where all the other user documentation currently is.
What about the rpmguard and initscripts docs that are currently on the trac wiki?
- I suppose that a related question would be whether or not those
are worth the effort to create or not.
It's slightly easier to find it inside Trac than inside the mailing list archives.
Agreed. It's also cleaner to edit than email threads.
Tim