BACKGROUND [0001] Meetings occur in the content of larger goals such as a project, creating a document, or establishing a team, for example. The meeting is a tool to get the work of the project done by bringing people together to exchange information and find solutions. [0002] The current meeting experience (e.g., online) can be disjointed from the rest of a team's work. For example, consider that a team is organized and has all meeting materials (e.g., documents, video files, agenda, etc.) in one place and ready for use. Before an online meeting can start, all of these materials have to be uploaded to the online meeting application. Depending on the size of the files, this can take time to not only upload the files but to address overly large files that can be prohibitively large to upload, or once uploaded, to launch. Moreover, as part of this process, the online meeting application can convert the files into a format that works for the online meeting application, but is not reusable to the end user. New items created in the online meeting application, such as whiteboards, may also not be downloadable after the meeting so that the knowledge created during the meeting can be revised. [0003] In the meeting lifecycle of pre-meeting, during the meeting, and post-meeting environments, there are many useful pieces of information that can be made part of the overall meeting lifecycle to provide a good end-to-end meeting experience. SUMMARY [0004] The following presents a simplified summary in order to provide a basic understanding of some novel embodiments described herein. This summary is not an extensive overview, and it is not intended to identify key/critical elements or to delineate the scope thereof. Its sole purpose is to present some concepts in a simplified form as a prelude to the more detailed description that is presented later. [0005] The disclosed architecture provides a mechanism that synchronizes meeting information (e.g., recordings, documents, agenda, action items, notes, attendees, join information, etc.) between clients and servers throughout the different stages of the meeting lifecycle. The meeting lifecycle is the ordered stages of experience which an end-user goes through when interacting with meeting or other collaborative session. These stages can include, but are not limited to, scheduling, pre-meeting, joining, in-meeting, and post-meeting. In the meeting experience, many different kinds of client software and server software can be used in the various stages. BRIEF DESCRIPTION OF THE DRAWINGS [0010] FIG. 1 illustrates a computer-implemented meeting lifecycle system in accordance with the disclosed architecture. [0011] FIG. 2 illustrates a computer-implemented meeting lifecycle system that includes client-based synchronization. [0012] FIG. 3 illustrates a generalized system for synchronizing meeting information between three lifecycle components. [0013] FIG. 4 illustrates that synchronization to one lifecycle component can automatically facilitate synchronization to the other lifecycle components. [0014] FIG. 5 illustrates a system where each lifecycle component communicates with a compatible client in a client-server relationship. [0015] FIG. 6 illustrates one example of the stages of a meeting lifecycle framework. [0016] FIG. 7 illustrates one implementation of a system showing components and data flow. [0017] FIG. 8 illustrates a computer-implemented meeting lifecycle method. [0018] FIG. 9 illustrates an alternative flow for a meeting lifecycle method. [0019] FIG. 10 illustrates a method of presenting relevant meeting information during a stage of the lifecycle framework. [0020] FIG. 11 illustrates a method of synchronizing meeting information to meeting lifecycle servers. [0021] FIG. 12 illustrates a block diagram of a computing system operable to execute client synchronization of meeting information in accordance with the disclosed architecture. [0022] FIG. 13 illustrates a schematic block diagram of a computing environment for meeting lifecycle client-based data synchronization. DETAILED DESCRIPTION [0023] The disclosed architecture is s synchronization architecture for synchronizing meeting information across core meeting services, such as scheduling, document management and meeting management. Synchronization can be accomplished via client-side synchronization, server-side synchronization, or combination of both. Client synchronization can be accomplished via an email client, personal information manager (PIM) client, content management sharing client (e.g., via a collaborating application), and meeting environment (e.g., multi-modal communications). The meeting environment is conceptually defined as the multiple stages associated with a meeting lifecycle (as described herein) such as preparing, conducting, and completing a meeting, and the meeting information is that information which is seated, utilized and synchronized as part of the multiple stages. [0024] The content management experience links to the scheduling experience for updates to data associated with the invitation text, such as documents, presenter data, attendee data, meeting time data, and so on. The content management experience shows aspects of the meeting that are most interesting based on the phase (stage) of the meeting lifecycle the meeting currently occupies. For example, after the meeting, participant attendance can be shown, but before the meeting participant responses to the invitation are shown. [0025] Information from the scheduling solution, including but not limited to invitation text, attached documents, attendee lists, meeting location, can be written asynchronously to the servers, for example, the meeting server and document server. Updates made to any one server are automatically synchronized to the other lifecycle servers, as needed. In other words, the meeting information ran include information portions that provide updates to one server, but not another server. [0026] Reference is now made to the drawings, wherein like reference numerals are used to refer to like elements throughout, in the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding thereof. It may be evident, however, that the novel embodiments can be practiced without these specific details. In other instances, well known structures and devices are shown in block diagram form in order to facilitate a description thereof. The intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the claimed subject matter. [0027] FIG. 1 illustrates a computer-implemented meeting lifecycle framework 100 in accordance with the disclosed architecture. The framework 100 includes a meeting environment represented as being associated with multiple stages of preparing, conducting, and completing a meeting. All stages associated with the meeting environment are involved with meeting information 102 such as attendees, invitation text, documents, and location, to name just a taw pieces of information. The meeting information 102 changes over the lifetime of the meeting. In other words, the meeting information 102 can be a continually changing aggregation of information created as part of preparation, in-meeting, and post-meeting stages. Alternatively, the meeting information 102 can represent selected portions of the overall information generated, changed, updated, and/or deleted during stages of the meeting lifecycle. For example, a user can employ a client scheduling application to schedule the meeting, and link documents for upload as part of the meeting start. This information can then be part of the meeting information 102. [0028] The multiple stages can be associated with disparate lifecycle components 104 for generating and processing the meeting information 102. The meeting information 102 can include scheduling information and meeting content, for example. The framework 100 can also include a synchronization component 106 for automatically synchronizing the meeting information 102 among one or more of the lifecycle components 104. [0029] The lifecycle components 104 can include a scheduling component 108, an in-meeting component 110, a content management component 112, and other components as well. The synchronization component 106 can be associated with a client application of the scheduling component 108, a client application of the in-meeting component 110, and/or a client application of the content management component 112, where each of the clients can synchronize the meeting information 102 or portions thereof to some or all of the lifecycle components 104. The doted line indicates that the synchronization component 106 can communicate with one or more of the bicycle components 104. [0030] The disclosed framework 100 provides a complete end-to-end meeting lifecycle facilitating a seamless user experience across the core components and meeting stages. The multiple stages can include scheduling, pre-meeting, joining, in-meeting, and post-meeting stages, for example. [0031] Each of the lifecycle components 104 can provide information to the synchronization component 106 in order to facilitate synchronization of some or all of the meeting information 102, as needed, between all other components. The scheduling component 108 can provide meeting information available at the time scheduling components are created, modified or deleted. This can include, but is not limited to, the time when the meeting is scheduled, when new invitations are generated, data synchronization, and/or when meeting in citations are updated. The in-meeting component 110 can provide meeting information available at the time the meeting is actually occurring, or information that resulted from the meeting itself. The content management component 112 can provide meeting information available between scheduling and the actual meeting occurrence as well as information that is updated after the meeting has already ended. [0032] In a specific implementation, the scheduling component 108 can synchronize permissions for a meeting invitation, the in-meeting component 110 can create and store a meeting record (or recording), and the content management component 112 can store and playback the meeting record (or recording). The synchronization to one of the lifecycle components 104 initiates synchronization to the remaining lifecycle components. Synchronization can be initiated manually and/or automatically. [0033J In other words, the scheduling component 108 functionality includes the synchronizing of data to both the in-meeting component 110 and content management component 112, the data including but not limited to, attendees, invitation text, documents, location, join URL (uniform resource locator), and audio dial-in information. Synchronization also can include permissions for the meeting invitation such as attendee roles (e.g., presenter or organizer). Selection from the scheduling component 108 can include the content management component 112 and the in-meeting component 110. [0034] The content management component 112 comprises functionality related to editing meeting data, including but not limited.' to. attendee list, agenda/invitation text, documents, and attendance records. The storage and playback of the meeting recordings can be performed, as well as synchronization of data to both the scheduling and in-meeting components (108 and 110). The in-.ideating component 110 can include the editing of meeting data, including but not limited to, attendee list, agenda/invitation text, documents, attendance records, etc., creating and storing the meeting recordings, and synchronizing data to both the scheduling component 108 and the content management component 112. [0035] The synchronization component 106 includes the functionality to accommodate data synchronization when not connected to any of the lifecycle components (e.g., no Internet connectivity, no connectivity to the scheduling server, no connectivity to the document server, no connectivity to the meeting server, etc.). For example, the synchronization component 106 enquires data for synchronization when the client goes offline and completes synchronization of the data when the client goes online. Logic and heuristics are included to manage the unlit-master synchronization of the architecture. [0036] FIG. 2 illustrates a computer implemented meeting lifecycle framework 200 that includes client-based synchronization. The framework 200 includes a conceptual representation of a meeting environment 202 of multiple stages 204 (Stage, Stage2,...,Staged for preparing and conducting the meeting, the lifecycle components 104 for generating and processing the meeting information 102, and the synchronization component 106 for synchronizing the meeting information 102 among one or more of the lifecycle components 104. The lifecycle components 104 include the scheduling component 108, the in-meeting component 110, the content management component 112, and other components as well. [0037] Note that as illustrated for c