Hi Jean, Sanket, On Wed, Aug 1, 2012 at 6:17 PM, Jean Weber <jeanwe...@gmail.com> wrote: > knowledge about > the Docs team's intended workflow.
Well, yeah, I should have said that it's not so much Jean that needs the documentation, it's more a question of getting new contributors up and running quickly and efficiently, without their having to come back and ask the same beginner's questions each time. So, what we really need is - as far as the docs contributors are concerned - is a good contributor's guide for Alfresco - initially for the docs team. In reality, this would become a section in the main docs team contributor's guide, which covers other aspects of docs team contribution than Alfresco. Drafting that guide entails liaising with the docs team and the docs team leader, Jean, and establishing what the workflow would become when usage of Alfresco is integrated, and then establishing what configuration work needs to be done on Alfresco to fit-in with then need. In reality - at least IMHO - we don't need to devise any Alfresco workflows as such. It could end up being constraining for the docs contributors. My own cogitation on the subject came to the conclusion that Alfresco's out-of-the-box functionalities already provide some great pluses. Also, by not asking them to fit-in with an Alfresco workflow, we leave the docs team flexibility to gravitate to a workflow naturally, progressively as they start to really adopt Alfresco and get used to it. IMHO, simply using Alfresco in much the same way as Windows Explorer or Gnome's Nautilus already leverages a lot of what Alfresco has to offer, while being pretty easy to learn. But these are simply my own initial views, and all needs to be validated by consulting with the docs team, and in the light of the experience of knowledgeable Alfresco specialists. Subsequently, after addressing the needs of the docs team contributors, we need an admin's guide. And then we would also need a *generic* Alfresco user's guide for users coming from other teams within the project. I'm pretty certain that when we have those assets, people generally within the LibreOffice project will be a lot more open to adopting Alfresco. Ultimately, we might also look at the idea of requesting a VPS or other server from TDF and implementing the Alfresco platform on there. I say this because I'm currently the provider of the VPS and the only regular admin, and I wonder whether this isn't a brake for some people... However, I'm also very happy to go on providing the Alfresco platform and server for the project if other people are happy with that solution and don't feel reluctant to use the tool under those conditions. Anyway, Sanket, I think this outlines the work needed at the present time. I'll leave you to reflect on the matter, And, once again, we'd be very happy to count you as one of "the staff". :-) -- David Nelson -- Unsubscribe instructions: E-mail to documentation+h...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/documentation/ All messages sent to this list will be publicly archived and cannot be deleted
