Changes between Version 43 and Version 44 of WKTRaster/PlanningAndFunding


Ignore:
Timestamp:
04/16/09 02:08:29 (16 years ago)
Author:
mloskot
Comment:

Linked names to websites

Legend:

Unmodified
Added
Removed
Modified

  • WKTRaster/PlanningAndFunding

    v43 v44  
    55This is the development page of [wiki:WKTRaster PostGIS WKT Raster] - a project extending PostGIS engine with raster support.
    66
    7 If you need support for raster in PostgreSQL or you have to do raster/vector operations, help us develop WKT Raster! WKT Raster developement is a work in progress. Each slice of 2000$ will bring new functions in! The approximate cost of the whole project is about 60 000$US. If 30 groups each give 2000$US, we will have the best seamless raster/vector set of SQL functions available by the end of 2009!
     7If you need support for raster in [http://www.postgresql.org/ PostgreSQL] or you have to do raster/vector operations, help us develop WKT Raster! [wiki:WKTRaster WKT Raster] developement is a work in progress. Each slice of 2000$ will bring new functions in! The approximate cost of the whole project is about 60 000$US. If 30 groups each give 2000$US, we will have the best seamless raster/vector set of SQL functions available by the end of 2009!
    88
    99You can contribute with money or developer time. Contributing give you the opportunity to have a word to say on the development priorities and on the schedule.
    … …  
    1111For financial contribution, the conversion rate between time and money is 1200$ per week ˜ 5000US$ per month ˜ 60 000 US$ per year. Coders have to be experienced C developer with a minimal object oriented database development experience. There are some developers out there willing to offer their services to implement your needs.
    1212
    13 
    1413We expect that developers will:
    1514
    1615 * Try to follow the schedule or at least arrange it to fit their particular needs as much as possible in accordance with the project roadmap. The project is divided into coherent groups of tasks. We are very flexible on modifying the content of those sections.
    17  * Contribute to the specifications in order to agree and to keep track of what's done. Specifications of the intented development should be described in the Specifications page and submited to the postgis-devel mailing list  for comments before starting development. Ask Pierre Racine to get write access to the specification page.
     16 * Contribute to the specifications in order to agree and to keep track of what's done. Specifications of the intented development should be described in the Specifications page and submited to the postgis-devel mailing list  for comments before starting development. Ask [http://www.cef-cfr.ca/index.php?n=Membres.PierreRacine Pierre Racine] to get write access to the specification page.
    1817 * Contribute to the Documentation as much as they can to make sure we produce a coherent and a professional open source product.
    1918