#29 - Establishing the Sahana PHP Project and Project Management Committee

google_logo.jpg Referencing Sections 6.1 - 6.5 of the bylaws of the Sahana Software Foundation, the Sahana Software Foundation Board hereby establishes the Sahana PHP Project and Project Management Committee.

Members: Invitations to the initial membership of the PMC shall be extended to a subset of the members of the former PMC who elected to become members of the Sahana Software Foundation and are currently active in leading the project. This list includes the following members:

  • Mifan Careem
  • Chamindra de Silva
  • Mahesh Kaluarachchi
  • Greg Miernicki
  • Darmendra Pradeeper
  • Mark Prutsalis
  • Gavin Treadgold

In addition, the following persons shall also be invited to join this group:

  • Chad Hescheuber
  • Joseph Priyanga

Invitees shall be encouraged to accept only if they plan to be active in the project and shall have two weeks to respond, after which time the initial membership shall be fixed. A Chair shall be appointed by the Board for a term to run through the end of the calendar year following the formation of the PMC once its initial membership is confirmed.
In recognition of their contributions to Sahana, the following shall be listed as Emeritus members of the Sahana PHP Project PMC and may request to be restored to active status at any time:

  • David Bitner
  • Ravith Botejue
  • Don Cameron
  • Paul Currion
  • Trishan de Lanerolle
  • Ravindra de Silva
  • Sudheera Fernando
  • Sanjeewa Jayasinge
  • Dominic Konig
  • Prabath Kumarasinghe
  • Ishan Liyanage
  • Tim McNamara
  • Louiqa Raschid
  • Isuru Samaraweera
  • Nuwan Waidyanatha
  • Sanjiva Weerawarana
  • Tom Worthington


Name of Project: Within one month of the passing of this resolution, in consultation with the community, the PMC must decide on the official name for the project that meets SSF naming guidelines and submit it to the board for approval.

Software Grant Agreement: Within one month, the chair of the PMC shall sign and return a Software Grant Agreement on behalf of the project.

License: The license of the Sahana PHP Project shall be GNU LGPL v.3

Responsibilities: The Sahana PHP Project is established as a Technical Project of the Sahana Software Foundation, with the responsibility for PHP versions of the Sahana application.

The mission of the Project Management Committee is:

  • Provide oversight of the project, ensure that all legal issues are addressed, that procedure is followed, and that each and every release is the product of the community as a whole.
  • Ensure the long term development and health of the community as a whole, and to ensure that balanced and wide scale peer review and collaboration does happen.
  • Communicate with stakeholders, domain experts and users.
  • Coordinate with other Sahana Software Foundation Committees and Projects


The Board retains the right to specify a public repository for all releases.

The Project Management Committee must ensure the following for their project:

  • Ensure all source code is accessible on a public repository as specified by the Board.
  • Ensure all releases are accessible on a public download location/server as specified by the Board
  • Ensure the licensing compatibility of all 3rd party components included in the project.
  • Ensure that all PMC members and Committers have returned signed CLAs to the Foundation.
  • Ensure that all any code committed to the main trunk, experimental, deployment or any other branch of the project hosted on the Foundation's infrastructure and all releases can be freely redistributed by the Sahana Software Foundation; this includes ensuring compatible open source licenses are utiilized for all relevant libraries and further ensuring that CLAs have been signed by all contributors whose code or design or other intellectual property (such as detailed blueprints or other requirements specifications) has been committed to the code and releases.
  • Ensure that project sites use a subdomain of the sahanafoundation.org domain and respect Sahana and Sahana Software Foundation branding;
  • Adhere to common standards as specified by the Board or a coordinating committee to ensure interoperability, synchronization and synergy between Sahana projects.


Adopted by a unanimous vote of 9-0-0 (yes-no-abstain) or +9 votes (5.5 required to pass) on 26 March 2010

#30: Establishing the Sahana Python Project and Project Management Committee

Referencing Sections 6.1 - 6.5 of the bylaws of the Sahana Software Foundation, the Sahana Software Foundation Board hereby establishes the Sahana Python Project and Project Management Committee.

Members: Invitations for members of the PMC shall be extended to all members of the former PMC who elected to become members of the Sahana Software Foundation and are active in the Sahana Python project. This list includes:

  • Fran Boon
  • Chamindra de Silva
  • Dominic Konig
  • Mark Prutsalis
  • Gavin Treadgold


In addition, the following persons shall also be invited to join this group:

  • Praneeth Bodduluri
  • Michael Howden


Invitees shall be encouraged to accept only if they plan to be active in the project and shall have two weeks to respond, after which time the initial membership shall be fixed. A initial chair shall be appointed by the Board for a term to run through the end of the calendar year following the formation of the PMC once its initial membership is known.

Name of Project: Within one month of the passing of this resolution, in consultation with the community, the PMC must decide on the official name for the project that meets SSF naming guidelines and submit it to the board for approval.

Software Grant Agreement: Within one month, the chair of the PMC shall sign and return a Software Grant Agreement on behalf of the project.

License: The license of the Sahana Python Project shall be GNU LGPL v.3

Responsibilities: The Sahana Python Project is established as a Technical Project of the Sahana Software Foundation, with the responsibility for Python versions of the Sahana application.

The mission of the Sahana Python Project is:

  • Provide oversight of the project, ensure that all legal issues are addressed, that procedure is followed, and that each and every release is the product of the community as a whole.
  • Ensure the long term development and health of the community as a whole, and to ensure that balanced and wide scale peer review and collaboration does happen.
  • Communicate with stakeholders, domain experts and users.
  • Coordinate with other Sahana Software Foundation Committees and Projects


The Board retains the right to specify a public repository for all releases.

The Project Management Committee must ensure the following for their project:

  • Ensure all source code is accessible on a public repository as specified by the Board.
  • Ensure all releases are accessible on a public download location/server as specified by the Board
  • Ensure the licensing compatibility of all 3rd party components included in the project.
  • Ensure that all PMC members and Committers have returned signed CLAs to the Foundation.
  • Ensure that all any code committed to the main trunk, experimental, deployment or any other branch of the project hosted on the Foundation's infrastructure and all releases can be freely redistributed by the Sahana Software Foundation; this includes ensuring compatible open source licenses are utiilized for all relevant libraries and further ensuring that CLAs have been signed by all contributors whose code or design or other intellectual property (such as detailed blueprints or other requirements specifications) has been committed to the code and releases.
  • Ensure that project sites use a subdomain of the sahanafoundation.org domain and respect Sahana and Sahana Software Foundation branding;
  • Adhere to common standards as specified by the Board or a coordinating committee to ensure interoperability, synchronization and synergy between Sahana projects.


Adopted by a unanimous vote of 9-0-0 (yes-no-abstain) or +9 votes (5.5 required to pass) on 26 March 2010

#31 - Establishing the Sahana Standards and Interoperability Project and Project Management Committee

Referencing Sections 6.1 - 6.5 of the bylaws of the Sahana Software Foundation, the Sahana Software Foundation Board hereby establishes the Sahana Standards and Interoperability Project and Project Management Committees

Members: The initial persons invited to become members of the Sahana Standards and Interoperability Committee shall be:

  • David Bitner
  • Praneeth Bodduluri
  • Fran Boon
  • Mifan Careem
  • Chamindra de Silva
  • Chad Heuschuber
  • Greg Miernicki
  • Mark Prutsalis
  • Louiqa Raschid
  • Nilushan Silva
  • Gavin Treadgold
  • Nuwan Waidyanatha


Invitees shall be encouraged to accept only if they plan to be active in the project and shall have two weeks to respond, after which time the initial membership shall be fixed. A Chair shall be appointed by the Board for a term to run through the end of the calendar year following the formation of the PMC once its initial membership is confirmed.

Name of Project: This project shall be known as the “Standards and Interoperability Project”

Responsibilities: The Sahana Standards and Interoperability Project is established as a Coordinating Project of the Sahana Software Foundation, with the responsibilities across multiple Sahana Technical Projects.

The mission of the Standards and Interoperability Project is:

  • recommend common standards to ensure interoperability, synchronization and synergy between Sahana projects and between Sahana and other open source projects.
  • set minimum standards for interoperability between Sahana software projects
  • promote the use of Open Standards for data exhange and interoperability, including, but not limited to those of such governing bodies as OASIS, OGC, and others as appropriate.
  • participate in working groups such as the OASIS Emergency Management Technical Committee, W3C Emergency Information Interoperability Framework Incubator Group (EIIF XG) and/or its successor.


Adopted by a unanimous vote of 9-0-0 (yes-no-abstain) or +9 votes (5.5 required to pass) on 26 March 2010


QR Code
QR Code foundation:sandbox (generated for current page)