A comment system would be fine indeed.
It would also be useful to have a tag system to easily identify pages which
need work, update, review, proof-reading. Wikipedia seems to be good at this.
BTW, the book publishers will surely do extensive proofreading, so will the
changes be made on
One can see in the planet that the wiki is going to be removed -
http://exploringopenerp.blogspot.com/2009/02/wiki-is-going-to-be-deleted.html.
Without wiki, what will be the place for the comunity to contribute with new
docs?
m2f
--
Hi,
You can create a small branch and propose your changes.
Regards,
OpenERP Developer
m2f
--
http://www.openobject.com/forum/viewtopic.php?p=32629#32629
m2f
On the launchpad project, using rst files:
https://launchpad.net/openobject-doc
The main branch is:
lp:openobject-doc
To download the documentation:
bzr branch lp:openobject-doc
Then, do changes and commit back to the branch (you have to be in the
openobject-community team on
Why not keep the wiki?
Every open source project has it's wiki!
It is easier to contribute to a wiki, everybody knows how it works.
Paulino
m2f
--
http://www.openobject.com/forum/viewtopic.php?p=32664#32664
m2f
while the community can contribute is fine but contributions are not reflected
automatically, then maybe that would be a problem because if a publication must
be instantly to share.
However automatically could be a problem if the contrib is wrong.
So, the doc now is great to begin but could be
fabien wrote:
... I consider that a wiki is not a good tool fro writing quality books and
documentations
I quite like the comment system in
[url=http://www.postgresql.org/docs/]postgresql. A mixture of structured
documentation and direct user comment.
Regards,
