[p4] Perforce and Sharepoint
busterrey at speakeasy.net
Fri Nov 17 07:02:48 PST 2006
Robert, thanks for the link. And thanks to everyone for their input.
So far I've been very confused by what Sharepoint is suppose to do. I am
also still trying to get a handle on what tasks the group that proposed
it are trying to do.
Most likely I'll recommend that engineering documents get checked into
Perforce and that they can do anything they want with non-engineering
stuff. As has been pointed out - engineering design docs are really part
of the product and should be under SCM control.
Thanks for the help folks,
Robert Cowham wrote:
>For a possibly biased but interesting take:
>You look on the Microsoft web site and it is a very confused picture. You
>are not told what Sharepoint is; you are told what Sharepoint does....
>Sharepoint is first and foremost an exercise by Microsoft to extend their
>monopoly of Office...
>At the end of the demo, you get a circular diagram that lists:
>Collaboration, Portal, Search, Content Management, Business Process
>Management and Business Intelligence, surrounding a platform core circle.
>This is to illustrate the very confusing distinction of Microsoft Office
>Sharepoint Server (MOSS 2007) from the operating system level of Windows
>Sharepoint Services 3.0. Obviously a Microsoft turf war in the making....
>Note the writer, John Newton, and links to
>http://www.alfresco.com/ which looks very interesting.
>>From about page: founded in 2005 by John Newton, co-founder of DocumentumR
>and John Powell, former COO of Business ObjectsR. Its investors include the
>leading investment firms Accel Partners and Mayfield Fund.
>>From: perforce-user-bounces at perforce.com
>>[mailto:perforce-user-bounces at perforce.com] On Behalf Of Scott Barney
>>Sent: 16 November 2006 20:05
>>To: busterrey at speakeasy.net; perforce-user at perforce.com
>>Subject: Re: [p4] Perforce and Sharepoint
>>Be clear whether you're talking about SharePoint Team
>>Services (included with Windows Server) or SharePoint Portal
>>Server, a separate product.
>>The names have caused (IMHO) a lot of confusion. If I may
>>They started as completely unrelated products -- SharePoint
>>Portal Server grew out of Site Server, SharePoint Team
>>Services grew out of the server-side FrontPage Server
>>Extensions. Both provide (or have provided) document
>>repositories with pretty different capabilities.
>>The 2001 release of Portal Server included a document
>>management system with simple workflow (eg, different users
>>could be marked as authors/editors/approvers for different
>>documents). That system was based on the Exchange data store,
>>which kind of lost out to SQL Server.
>>In V2 (2003?) the system still existed, but was deprecated. I
>>don't know about V3+.
>>The 2001 release of Team Services started with a nice concept
>>of shared lists, stored in SQL Server. A calendar could be
>>handled as a list of meetings; a discussion area as a list of
>>messages; and a file repository as a list of records
>>(metadata) with attached binary files. There wasn't much
>>(any?) workflow or security, although that's probably improved.
>>One detail that might be important to this audience: To my
>>knowledge, MS provides no filesystem support for either kind
>>of repository. Access is through Office's Web Folders shell
>>extension -- which works great for Office and the like, but
>>there's nothing you can CD to and no way to run simple
>>command-line utilities (perl scripts or compilers) on the files.
More information about the perforce-user