Changes between Version 137 and Version 138 of WKTRaster/PlanningAndFunding

Timestamp:

Sep 14, 2011, 6:39:26 AM (13 years ago)

Author:

pracine

Comment:

—

WKTRaster/PlanningAndFunding

@@ -18 +18 @@
 This is the development page of [wiki:WKTRaster PostGIS Raster] - a project extending PostGIS engine with raster support.
 
-'''Need more PostGIS Raster features? -''' If you need support for raster in [http://www.postgresql.org/ PostgreSQL] or you have to do raster/vector operations, help us develop PostGIS Raster! PostGIS Raster development 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!
+'''Need more PostGIS Raster features? -''' If you need support for raster in [http://www.postgresql.org/ PostgreSQL] or you have to do raster/vector operations, help us develop PostGIS Raster! PostGIS Raster development is a work in progress. Each slice of 2000$ will bring new functions in!
 
 '''Time or Money -''' You can contribute with money or developer time (!DevTime). Contributing give you the opportunity to have a word to say on the development priorities and on the schedule.
 
-For financial contribution, the conversion rate between time and money is 1200$ per week = approx. 5000US$ per month = approx. 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.
+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.
 
 '''Expectations -''' We expect that contributors will:
 
- * 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.
- * 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.
- * Contribute to the Documentation as much as they can to make sure we produce a coherent and a professional open source product.
+ * Try to follow the roadmap or at least arrange it to fit their particular needs as much as possible in accordance with the existing roadmap. The planning is divided into coherent groups of tasks. We are very flexible on modifying the content of those groups.
+ * Contribute to the specifications in order to come to an agreement on how things should be done 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.
+ * Contribute to the Documentation as much as they can to make sure we produce a coherent and a professional open source product. Specifications should details the new functionality and be written so they can be used as a reference to document the new feature.
 
 '''Advices to developers -''' We can assure degree of quality with obeying basic rules and development cycle process, most of them are easily executable: