2.1 or 2.9x for 'internal' production?

[folke]

Hi,

We are looking at changing our dokuwiki / "different documents scattered over different places" system with perhaps Alfresco.
We have used dokuwiki for some time now, but the need tu upload pdf's and ms documents is taking more and more time.
So I have looked at alfresco for some time now and it really looks good.
The thing that really appeals is the option to both run versioningon both CIFS and web part.

But now to the question in hand, the use is for internal tech documentation for our IT-Department.
Do you think that we should start up with 2.1 community, or directly go to 2.9B and then update to 3.0 in july/august?

We are mostly going to use document, versioning, cifs. So no fancy wcm stuff at first at least.

[andries]

We are using Alfresco for the same things. A few months ago we upgraded from 2.1CE to 2.9B, because 2.9B seems stable and because 2.9B has quota. No problems at all, the systems are running fine.

[folke]

We are using Alfresco for the same things. A few months ago we upgraded from 2.1CE to 2.9B, because 2.9B seems stable and because 2.9B has quota. No problems at all, the systems are running fine.

Hi,

Nice to hear.
May I ask how you use it? Any external plugins?

Is there a simple way to do a changelog on a server/system. Perhaps comments or discussion plugin or sumfink like that?
We are now in dokuwiki using 2 ways of navigation in the documentation tree.

All the servers in one index.
and then sorted by systems.
System -> link to servers in that system.
And then on every server there is a changelog, that is meant to been tailed on the systempage.
One of my thoughts were if it was possible to send mail to one "directory" (server). Then consultans easaly could send in changelogs when they mess around with our servers with an easy mail.

Any ideas that is working instead of my thougts

[andries]

We use it in a simple yet effective way. Per system we use a space to put in all documents regarding the very system. These documents are a mix of Word docs, PDFs, html-files and flat text. We didn't spent much time designing a complex hierarchy to put documents in. Instead we rely on search within the repository to find info when needed. We use these main spaces: (our) systems, projects, contracts, product info & third parties.

[folke]

We use it in a simple yet effective way. Per system we use a space to put in all documents regarding the very system. These documents are a mix of Word docs, PDFs, html-files and flat text. We didn't spent much time designing a complex hierarchy to put documents in. Instead we rely on search within the repository to find info when needed. We use these main spaces: (our) systems, projects, contracts, product info & third parties.

Ah, I had something like this in mind. http://www.mockel.se/wordpress/wp-content/uploads/2008/06/20080613150017642.pdf
But I'm not sure how to do the "template" for servers / systems.

Perhaps using tags as system so that you can connect servers to different systems..

Any thoughts out there?