> The next step will be an internal vote to let the community decide if they > think Apache Hop (Incubating) is ready to graduate as a Top Level Project.
If I recall correctly, the vote is typically on the text of the graduation proposal. Included in that text are the initial PMC and chair (done) but also the mission statement of the project. Formally, we need to agree the values <Name> and <Mission statement> to substitute into the template. Bart’s previous message to the IPMC had the variables <Name> = “Hop” and <Mission statement> = "short for the Hop Orchestration Platform. Written completely in Java it aims to provide a wide range of data orchestration tools, including a visual development environment, servers, metadata analysis, auditing services and so on. As a platform, Hop also wants to be a reusable library so that it can be easily reused by other software.” substituted into the template Establish the Apache <Name> Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to <a clear mission statement> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache <Name> Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED,that the Apache <Name> Project be and hereby is responsible for the creation and maintenance of software related to <same mission statement>. RESOLVED, that the office of "Vice President, Apache <Name>" be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache <Name> Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache <Name> Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache <Name> Project: << here, list out each PMC member, in the format of * First Last <apache email> >> NOW, THEREFORE, BE IT FURTHER RESOLVED, that <Elected VP> be appointed to the office of Vice President, Apache <Name>, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache <Name> PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache <Name> Project; and be it further RESOLVED, that the Apache <Name> Project be and hereby is tasked with the migration and rationalization of the Apache Incubator <Name> podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator <Name> podling encumbered upon the Apache Incubator Project are hereafter discharged. In my opinion the current mission statement is too long and should be tightened up. Julian
