What was the code name for SharePoint?
Displaying all 13 posts by 12 people.
Post #1
4 replies
Microsoft SharePoint wroteon November 12, 2007 at 6:37pm
And why/how was that code name given?
[JeffTe: Do not answer until other people have given it a guess or two! :-)]
[JeffTe: Do not answer until other people have given it a guess or two! :-)]
Post #2
David replied to Microsoft SharePoint's poston November 12, 2007 at 7:59pm
Fox Pro 98 had the same code name.
Don't think I ever heard a reason...
Don't think I ever heard a reason...
Post #3
Raj replied to Microsoft SharePoint's poston November 13, 2007 at 1:12am
Tahoe? I assume you mean STS? ie v1
Post #4
Dave wroteon November 13, 2007 at 1:57pm
definitely Tahoe
Post #5
Bil wroteon November 13, 2007 at 8:15pm
The only code name for SharePoint (there wasn't one for MOSS, it's just an acronym) was Tahoe. This was for SharePoint Portal Server 2001 (not STS).
Tahoe, as with most Microsoft code names, is supposidly the place where the team goes when the product is delivered (I'm not sure if this is urban legend or truth).
Tahoe, as with most Microsoft code names, is supposidly the place where the team goes when the product is delivered (I'm not sure if this is urban legend or truth).
Post #6
2 replies
Jeff replied to Microsoft SharePoint's poston November 14, 2007 at 3:23pm
Ok. Here's the answer from someone who was kind of involved :-).
There were a few indepedent incubation projects which later converged. "Tahoe" became "SharePoint Portal Server 2001". "Tahoe" was built on ASP and a modular version of the Exchange store called "Magma". "Office Web Server" was a project combining the FrontPage Server Extensions, the Office Server Extensions (web discussions and subscriptions) and an incubation effort called "TeamPages" which became the list features of SharePoint today (and where CAML was invented in the very early XML days). This became "SharePoint Team Services". Our branding team came up with the name "SharePoint" initially for "Tahoe" (I loved the simplicity) but we decided it was a better fit for OWS given the collab focus. We decided to target "Tahoe" at portals aggregating team sites and other info and higher value document storage. We finally came up with the "Team" and "Portal" labels pretty late in the release to indicate the positioning and long-term roadmap. As folks may remember we shipped these with the Office XP wave and the brought them together on ASP.NET + SQL Server which was a major new architectural bet for Microsoft, SharePoint and Office.
Since then we just refer to the next release as "V3" or the "12 wave of SharePoint" to coincide with the Office System 12 wave that became 2007. This keeps attention focused on the real product customers can use today and avoids building equity in some temporary codename vs. building equity in the long-term brand.
There were a few indepedent incubation projects which later converged. "Tahoe" became "SharePoint Portal Server 2001". "Tahoe" was built on ASP and a modular version of the Exchange store called "Magma". "Office Web Server" was a project combining the FrontPage Server Extensions, the Office Server Extensions (web discussions and subscriptions) and an incubation effort called "TeamPages" which became the list features of SharePoint today (and where CAML was invented in the very early XML days). This became "SharePoint Team Services". Our branding team came up with the name "SharePoint" initially for "Tahoe" (I loved the simplicity) but we decided it was a better fit for OWS given the collab focus. We decided to target "Tahoe" at portals aggregating team sites and other info and higher value document storage. We finally came up with the "Team" and "Portal" labels pretty late in the release to indicate the positioning and long-term roadmap. As folks may remember we shipped these with the Office XP wave and the brought them together on ASP.NET + SQL Server which was a major new architectural bet for Microsoft, SharePoint and Office.
Since then we just refer to the next release as "V3" or the "12 wave of SharePoint" to coincide with the Office System 12 wave that became 2007. This keeps attention focused on the real product customers can use today and avoids building equity in some temporary codename vs. building equity in the long-term brand.
Post #7
Jeff replied to Jeff's poston November 14, 2007 at 3:27pm
As far as why "Tahoe", at that point, most Microsoft teams were using locations as codenames so we went with that. One attraction besides being cool a place was it looked good on T-Shirts and Sweaters that it wasn't this big giant Microsoft Logo so you could go without leaking the name of a then secret project. We had a nice skier logo. I still wear my Tahoe Sweatshirt but its on its last days. Most teams never went on trips to the place of their codename (I think there were a couple exceptions) so no we never went to "Tahoe". It is true there was a FoxPro release that used this codename first. We found this out after we'd been using it a while but decided it wasn't worth changing.
Post #8
Sezai wroteon November 15, 2007 at 12:43am
Post #10
Amit wroteon May 5, 2008 at 5:36am
Can't trust anything with hoe in the name.
Post #11
Wasay wroteon May 21, 2008 at 9:43am
man their is just too must history with the code name itself... I am just staying with the release version name lol
Post #12
Guido wroteon May 22, 2008 at 8:56am
Tahoe
Post #13
Edward replied to Jeff's poston December 18, 2008 at 7:20pm
Does CAML have documented future with webcast, tutorials and lots of MSDN articles or can I continue to avoid it because I have deemed it to be evil due to my ignorance (or lack of expertise) on the topic?
** CAML was invented to send me into early retirement **
** CAML was invented to send me into early retirement **