Jeff, Just to let you know we are definitely not tied to one product, in fact one of the reasons that the steering committee decided to go with Drupal was it's ability to leverage these tools and integrate it with workflows and publishing systems within the Drupal framework.
I know that a lot of effort has already gone into Alfresco to Drupal integration. If there is a need to access, edit and republish documents under development through a native file system network folder I would we suggest we go towards leveraging these tools and move away from the work that has been done already. On the other hand we could use a version control system just like the development team does with GIT when working on and submitting source code, and Drupal supports this without the need for additional applications which would also support native file system support you are describing. On both counts however it requires an end user to learn another system, unlike the point and click type of system that OOoAuthors has and I have been working towards on Jean's advice. There is nothing stopping us integrating something like this down the track after an initial point and click system is in place. Thoughts? Michael Wheatland On 10/12/2010 9:26 PM, "Jeff Prater" <j...@thoughtreactor.com> wrote: > On Fri, Dec 10, 2010 at 12:24 AM, Narayan Aras <narayana...@hotmail.com >wrote: > >> >> There are many such products. Each has some feature that catches our eye. >> >> But such window-shopping won't be conclusive (especially when this is a >> group-decision). >> >> ... >> >> Let Michael have a fair shot at it and then let us decide. >> >> >> -Narayan >> > > We used to use O3Spaces at my job before switching to SharePoint (mainly > b/c SharePoint was just a better product). We used O3Spaces to coordinate, > develop, publish, and maintain our master documents (policies, procedures, > manuals, etc.) since it provided basically one-click document > check-in/check-out, joint editing, revision control, wiki-publishing, etc. >>From what I remember with OOoAuthors, once you downloaded a document, you > had to re-upload the same document. With O3Spaces, none of this was > necessary as the server handled all this for you in the background. It also > stored all the revision so reverting/merging revisions was a breeze and not > a manual process. I would think having a system that can do all of this > would be extremely beneficial to the production and maintenance of LibO > documents. > > O3Spaces is commercial software so I know it's out of the question, but > Alfresco seemed to have a very similar feature set. I'm just curious if any > of these products were even considered instead of possibly reinventing the > wheel with Drupal. > > Jeff > > -- > Unsubscribe instructions: E-mail to > documentation+h...@libreoffice.org<documentation%2bh...@libreoffice.org> > List archive: http://www.libreoffice.org/lists/documentation/ > *** All posts to this list are publicly archived for eternity *** > -- Unsubscribe instructions: E-mail to documentation+h...@libreoffice.org List archive: http://www.libreoffice.org/lists/documentation/ *** All posts to this list are publicly archived for eternity ***
