#340: Write 0.10 to 0.11 migration guide
---------------------------+------------------------------------------------
Reporter: david | Owner: david
Type: task | Status: closed
Priority: highest | Milestone: 0.11
Component: documentation | Version:
Severity: blocker | Resolution: wontfix
Keywords: |
---------------------------+------------------------------------------------
Comment(by anonymous):
default as a design pattern rather than trying to put it all together.
That way you can never create offline or print docs of high quality
without again having the devs or current admins maintain the comments and
annotations. Hopefully a small Wiki quality team will evolve (i am against
ops or admins) to review and summarize the contributions. I hope this
gives us more users as contributors than having the docs focused on the
devs. Cheers, duns [http://www.about-china.net.cn/wrought-iron/cat_4.html
china tour] I still prefer a wiki like approach since the php (or mysql)
docs are very cluttered when you have to take their comments in account.
On the other hand they are professionally maintained imho, since they are
*much* better than KDE documentation. KDE is by far larger and has so many
different apps, which need screenshots and end user not dev/api docs, that
more help is needed as long as the devs prefer to code than to write nice
docs. And it is their choice to some degree imo. Technically interested
but non-dev end users, which are plenty out there, are the users of and
the best contributers to the docs
--
Ticket URL: <http://trac.agavi.bitxtender.net/ticket/340#comment:4>
Agavi <http://www.agavi.org/>
An MVC Framework for PHP5
_______________________________________________
Agavi Tickets Mailing List
[email protected]
http://lists.agavi.org/mailman/listinfo/tickets
