To provide a foundation of infrastructure, interaction and guidance upon which innovation can be based.
New York PHP takes a collaborative and consensus oriented approach using the following general structure:
A Principal is any person demonstrating ongoing participation in New York PHP. Principals are associated with Departments.
A Department is comprised of two or more Principals who work together and share related skills and interests to carry out Projects and other associated tasks.
The Principals of a Department elect from among themselves a Vice President, whose duty it is to manage the Department, and represent it on the Board of Directors. A person can be the Vice President for only a single Department. Vice Presidents are responsible for the day-to-day affairs of their Department, and for assuring that Projects overseen by their Departments are completed in a timely and acceptable manner. Vice Presidents may be removed at the request of the Department's Principals and with the approval of the Board of Directors.
A Project is a goal overseen by a Department and directly managed by a Project Manager. Projects can be either directly technical or indirectly technical in nature.
Project Managers are drawn from the Principals of the Department overseeing a Project. It is their duty to organize the Project and they are responsible for their Project's successful conclusion. Project Managers may be removed or reappointed by the overseeing Department. A Vice President may be a Project Manager. A Principal may be a Manager for more than one Project.
The Board of Directors is responsible for the management, oversight and direction of New York PHP. The Board is comprised of the Vice President from each Department, plus the President.
The President is the Chairman of the Board and is elected by the Board of Directors. It is the President's duty to ensure that New York PHP develops in a manner consistent with its Mission, the goals set by the Board of Directors, and the goals of its Principals and Departments.
An Associate is any person subscribing to and participating in New York PHP's public mailing lists but not otherwise participating on an ongoing basis in New York PHP activities. An Associate, after demonstrating ongoing participation, may become a Principal upon application to a Department's Vice President, who has sole discretion to approve or reject the application.
Effective methods of communication and consistent processes within New York PHP affect all operations. All operations without more specific terms should adhere to the Protocols and Procedures described here.
New York PHP implements silence is acceptance as a general protocol.
The President is authorized to have and use without prior approval an automatically renewed Petty Cash account of $150.
No elections shall take place during an initial organizational period from 1 March 2004 to 28 February 2005. Thereafter, elections shall take place annually on or about 1 March. At the first election on or about 1 March 2005, Vice Presidents shall be elected for one-year terms, but thereafter for two-year terms. The President shall be elected for a two-year term. The two-year terms for Vice Presidents of Departments created after the initial organizational period shall be coterminous with that of the President.
Elections for Vice President shall take place by email. All Principals of a Department are eligible to vote. The person receiving the majority of votes cast shall be elected.
Central to New York PHP communication is the use of mailing lists. Departments and the Board of Directors each have a mailing list. Mailing lists are the place for general and informal discussion. They are also the place for formal actions and proposals. In these cases, these Protocols and Procedures should be followed.
Principals involved in a Planned Action are encouraged to keep the appropriate mailing list(s) carbon-copied when communicating with an external entity. In the case of a Principal acting on behalf of a specific Department, the Department's mailing list is appropriate. In the case of a Principal acting on behalf of New York PHP in general, the New York PHP Development mailing list is appropriate.
Principals are subscribed to New York PHP's internal mailing lists. If the Board decides upon review that a Principal's project has stalled, or that the Principal's participation has lacked, that Principal will be unsubscribed from all internal mailing lists.
The mailing lists of New York PHP may not be used to:
The Board of New York PHP shall determine whether a violation of appropriate use has occurred, and if it has, the President shall issue a warning notice in writing to the violator.
Anyone who again violates appropriate use after having been already issued a warning notice shall be excluded from any and all participation in New York PHP.
The Board of Directors acts on matters brought to it for review and of its own initiation. Unless otherwise determined, all matters brought to vote are considered approved if a majority is in favor. Each Department's Vice-President holds one vote. The President holds one vote and has no veto power.
Departments are the main organizational unit of New York PHP. Each Department's Principals share a common set of interests, skills, and talents. It is the objective and responsibility of the Department to carry out its own Projects, and to provide resources for other Departments, Projects, and Principals.
Departments can be added or removed with the approval of the Board of Directors.
Responsibilities of each Department are outlined below. These responsibilities are in addition to those required by any Projects overseen by the Department.
Projects are the heart of New York PHP's activities, and may develop independently or in conjunction with one another. Projects must have a sponsoring Department and a Project Manager. New York PHP supports many facets of Project development through technical know-how, infrastructure, organization, and exposure. New York PHP adopts Projects that are both explicitly technical and implicitly technical.
All Departments are expected to provide resources to all Projects, even those sponsored by other Departments.
The Board of Directors has the sole authority to approve changes in Project status, and may change a Project status at any time. Projects may be in only one of the following statuses:
Active Projects are subject to review by the Board of Directors at any time. To remain an active and supported New York PHP Project, a Project Manager must ensure that they fulfill the following ongoing requirements:
Project Managers may request, through their overseeing Departments, resources and support from any New York PHP Department, or other active Project.
Projects that are determined to have failed, or remain inactive for an extended period of time, have their status changed to either postponed or rejected. Project Managers or Vice Presidents may consider a project to have failed under any of the following circumstances:
The Board of Directors determines if the Project meets any of these circumstances and will decide the status of the Project.
A Project Proposal Form is submitted to the New Project Coordinator, who reviews it for completeness and merit, and creates a node for it under the Proposals node.
The Board reviews the proposed Project, voting to approve, reject, or postpone it.
Approved Projects are under the auspices of an overseeing Department, which is usually the sponsoring Department. At any time, and by recommendation by the Board of Directors, overseeing Department, or Project Manager, a Project may change its overseeing Department. Any change in overseeing Departments must be approved by the Board of Directors.
Project Managers must maintain status reports and communicate with their overseeing Department on a regular basis.
Internal Project organization and structure is at the sole discretion of the Project Manager. Project Managers are free to recruit personnel or resources as they see fit, and organize themselves in any manner necessary.
Interaction and recruitment between active New York PHP Projects is subject to the review of overseeing Departments and the Board of Directors.
Any member of The Board of Directors may initiate a modification of this Charter by submitting it via email to the Board, with the words "PROPOSED CHARTER REVISION: 48 HOUR RULE" in the subject line. Other members of the Board of Directors will have 48 hours to respond with an opinion on the proposal. No response shall be interpreted as approval.
All changes to the website must be approved by the Board of Directors. Such approval may be retroactive.
Free API and developer tools console for PageSpeed optimization.