Hi Frank,
Frank Peters wrote:
Hi Marko & Andreas, all
Frank would You be so kind and answer to the post of Andreas or tell me
why you can't answer?
I apologize for the delay in my answer.Me too ;-)
No problem Frank, it was only some kind of 'wakeup call' :-)
because in my mind it is worth to talk about it.
At first let me thank You for all the energy You've invested in the
documentation project.
>> How about the plone solution of Andreas?
>> We have a lot of very good feedback of the docu volunteers working on
>> OOoAuthors.org with this tool.
>>
>> One of the reasons for OOoAuthors.org was the very uncomfortable stuff
>> on the documentation project.
But that was before the doc project used the wiki at all. I agree
that Issuezilla+website was very inconvenient and inefficient.
>> The suggested solution of Andreas could be a a way to bring all the
>> power of documention.openoffice.org an OOoAuthors.org together again.
Everyone should know that I am a strong advocate of joining the
docs forces of doc.oo.o and oooauthors. It would certainly be a
win for all of us, not least for the user.
That#s true and many thanks for it ;-)
>> Andreas sent You a mail about it some time ago and post a hint
yesterday
>> too.
>>
>> It will be great to get some feedback for this idea.
I know that you and Andreas are strong advocates of a plone
based solution for multi-language documentation maintenance.
I have been discussing this with Andreas several times.
Let me emphasize that I am not an opponent of a plone
based solution, and I am in fact in favor of a solution that
offers more CMS functionality than the current wiki solution.
However, I think that in the current situation it would be better
to find a solution for the wiki because that is the platform
that is available on oo.o. Given the hint from lepennuisic,
it looks like it would be possible to implement something
lightweight very easily (even without having to reorganize the
wiki structure for the localized content, or without having
to have all structures to be the same).
Good goal indeed.
If we really want to implement a long term solution for
maintaining a multilingual content management for documentation
(and I think we should), I would then like to work with all of
you at doc.oo.o and the NLC to set up a catalog of requirements,
and after that look for a solution.
Plone will certainly be one of the possible solutions
(especially given the fact that there is already considerable
expertise in the community), but may not be the only
candidate.
To have more than one choice to find the best solution is always better.
Before switching to another solution (that is currently
not supported inside the OOo domain) I would suggest to
be clear about all requirements.
I created the following page to collect requirements
and suggestions for tools to use:
http://wiki.services.openoffice.org/wiki/Documentation/Dashboard/CMS_Evaluation
Thank You. Andreas has added some lines meanwhile.
After we have settled the requirements we can go ahead
and look at the suggested tools how well they fit and
eventually select one for implementation.
Let me know what you think
Frank
Last but not least a few words ... ;-)
All the activities to make documentation.openoffice.org better and with
a higher usability are needed and on a good way. Thanks for that!
But keep in focus that the best website is nothing without actual
content. So that is what is really needed. Take a look at documentation.:-(
A lot of stuff is outdated (partly only for version 1.x).
The biggest problem was (and is) that a lot of new volunteers starts
enthusiastic an then resign and leave us, cause there are 'lost in
transit'. The new version of
http://documentation.openoffice.org/contributing.html
is a better starting point now for new volunteers :-)
We have to keep the volunteers in mind too if we talk about changes.
So we should not establish new stuff (or use available stuff like the
wiki) before we are sure that the volunteers are willing to use it.
And we have to find responsible persons (editors) too how are able an
willing to maintain the content. In the past we have to learn (in the
German documentation team) that a community based work is great but that
some kind of 'work flow' is still needed. There must be an responsible
editor in order to finish an publish documentations.
The new solution (what way or product ever) should be a solution for the
future and should (as You said it) fit the needs of both, users and
volunteers. If it takes some days more to find it, that's ok :-)
Regards
Marko
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
